system architecture and testing (apu)

8/9/2019 System Architecture and Testing (APU)

1/26


2/26

System Architecture and Testing

2


3/26


4/26


1.2 Reason for Chosen System

;ased on the introduction9 the system hae many enefits for the users ut also some

,ea"ness ,hen using the file sharing and synchronizing system. *here are some security issues

a++ear in this system and that cause so of the users data hae een stole. *he generated lin" can

e share to others y other users ,ithout the o,ner "no,ing9 so that the original data inside the

system can e do,nload y others.

Furthermore9 the data that store y using this system can also e oer,rite ,hen the users

u+load something to the storage or +ut inside the folder of the system. It ,ill e the ,ea"ness of

the system also ecause of the oer,riting function. If a user using the system offline and moe

some ne, file into the folder9 ,heneer the deice is connecting to internet and the ne, file ,ill

e remoe ecause the system ,ill synchronizing the online storage file to the deice.

*he reason for choosing file sharing and synchronizing system is try to eliminate the

,ea"ness of the system y using the architecture ealuation. *here +ossile some missing

com+onent in the eisting architecture diagram so that affected the system +erformance and

security.

Furthermore9 to ensure the system can e modify easily ,ill e the reason as ,ell. If a

system is +lanned ,rongly9 it is +ossile affect the system difficult to modify or might cause

some im+act to others function in the system ,hen modified.

4


5/26


1.3 Ealuation Criteria

;ased on the reason for chosen system aoe9 the system is ready for an architecture

ealuation. Currently9 the system already hae eist architecture diagram ut the diagram had

ust sho,ing casually and it shall do the architecture ealuation again. Redo the architecture

ealuation can reduce the security issues that mentioned at the +reious +art. #dditional9 the

architecture ealuation not only reduce the issues ut also im+roing the system functional and

+erformance.

*he architecture ealuation can e do as soon as +ossile so that the issues ale to reduce

early and the system ,ill cause less issues in the future. *he architecture ealuation can also

clearly state out the


6/26


*he Entity Relationshi+ iagram aoe clearly sho,n the relation et,een the entities. *he

user can has one or more deices to connect to one storage that they rought and the storage can

store u+ to ! gigayte files ,ith different data ty+e. *he user can also share one or more file and

folder lin" that contain all the stuff the o,ner hae.

-


7/26


8/26


*he


9/26


Inestigation and #nalysis

Step 3: Identify the Architectural Approaches

*he diagram sho, the user can u+load9 ie, and share their files from the or to the onlinestorage. *his system is comination of ,e a++lication9 serice management9 data access and

storage on des"to+ and moile o+erating system. So the user can manage their files such as

u+load ne, file9 modify the files or remoe the files and the system automatically synchronize

the ne, file or the oer,ritten files.

)


10/26


*he system o,ner ale to see the re+ort and ie, the access log of the users. 7heneer a

user login to the system or logout9 the re+ort of the o,ner ,ill automatically ,rite a ne, line of

log that store the login and logout date of users. #dditional9 the u+load files that o,n y users

also ,ill e record to the log.

10


11/26


Step 4: Generate the Quality Attriute !tility "ree

In this ste+9 utility tree ,ill e uild and it is use to +rioritize and identify the system6s

most im+ortant


12/26


Scenario of file sharing and synchronizing system=>

#eliaility

1. *he system minimum failure +er month can only e once.

Availaility

1. *he dataase must e ac"u+ y using the etra hard,are and during the main dataase

corru+ted or damaged9 the system ale to s,itch to the ac"u+ dataase in maimum 2

minutes.

Security

1. *he system must restrict the authorized users to access to the system.

2. *he system must identify the users efore the users are going access to the dataase.

$odifiaility

1. *he system can e u+date easily ,heneer the serice o,ner needed and the u+date ,ill

not giing the im+act to the function of the system.

Portaility

1. *he system must e ale to running in multi+le +latform such as 7indo,s S9 8inu S9

#++le S9 and #ndroid S.

12


13/26


Step %: Analy&e the Architectural Approaches

#fter generate the utility tree9 the


14/26


15/26


Re+orting

Step *: Present the #esults

#t the last +hase and the last ste+9 the collected information9 utility tree9 scenario and


16/26


Soft,are #rchitecture #nalysis $ethod %S##$&

erie, of S##$

Soft,are #rchitecture #nalysis method %S##$& is a relatiely sim+le architecture

ealuation of method to define the change of the future ,ill affect to the


17/26


In+ut of S##$ Ealuation

For S##$ ealuation to +roceed9 some form of descri+tion of the architecture should

re;ased

Soft,are #rchitecture9 2013&

*herefore9 S##$ is ery serious to the


18/26


ut+ut of S##$ Ealuation

*he main out+ut is +roide an ealuation re+ort to list out ,hich +oint from the

architecture has not meet the


19/26


Ste+ of S##$ Ealuation

*he diagram on aoe is sho,ing the seeral ste+s of actiities and de+endencies in S##$

#nalysis. S##$ has - main ste+s ,hich are=

1. eelo+ Scenarios

2. escrie Candidate #rchitecture3. Classify and (rioritize Scenarios4. Indiidually ealuate Indirect Scenarios

!. #ssess Scenario Interactions

-. Create the erall Ealuation

1)


20/26


Ste+ 1 eelo+ Scenarios

eelo+ Scenarios is the first ste+ to illustrate the sco+e of identifying the ty+e of

actiities that the system should su++ort and illustrate the changes that the client antici+ates ,ill

e made to the system. uring deelo+ing scenarios9 there is ery im+ortant to ca+ture all maor

uses and the users in the system9 antici+ated changes to the system9 all ;ased Soft,are #rchitecture9 2013&

*herefore9 scenarios re+resent tas" releant to different "ind of roles such as customer9

end user9 mar"eting manager9 system administrator9 system deelo+er and technician. *he

deelo+ scenarios ste+ ,ill usually +erformed t,o times ecause more iteration and architectural

has een shared and there ,ill e more scenarios +artici+ate. *hus9 +erform in +arallel these

actiities can let them share out the idea and o+inion to discuss and sole together.

File Sharing and Synchronizing system deelo+er or sta"eholders hae to come out ,ith

the scenario of this system such as the scenario ,ith the users. Furthermore9 system deelo+er

should illustrate ,hat "ind of actiities that the system should ale e su++ort and ,hat changes

that made y client such as ,hat +latform can e su++ort on user deices9 ,hat re


21/26


Ste+ 2 escrie Candidate #rchitecture

*he second ste+ ,hich is the candidate architecture should e descried in a syntactic

architectural notation that used to e ,ell understood y the +artici+ants that inoled in the

analysis. *he architectural descri+tion should e indicating the data com+onents9 system

com+utation and interconnections ,ith the enironments as ,ell as all releant connections.

%Scenario>;ased #nalaysis of S#9 1))-& ;y static re+resentation of the architecture is a

descri+tion of ho, the system ehaes re+resentation oer time or more dynamic re+resentation.

*he file sharing and synchronizing system +resenter need to indicate clearly aout ho, to

use architecture to communicate ,ith the usiness enironment and ,hat com+onents has to use

such as metadata can +roides information aout a certain item details. :sing natural language or

some other more formal s+ecification ,ill ale to let user more clearly understood aout the

system. Furthermore9 the deelo+er should +roide an architectural descri+tion forces the

sta"eholders to thin" aout scenarios that address s+ecific characteristic of the architecture under

consideration.

21


22/26


Ste+ 3 Classify and (rioritize Scenarios

Classify and +rioritize scenarios is the third ste+ of the scenarios analysis and it can e

classified in direct D indirect scenarios. irect scenario can e defined as direct su++orted y the

architecture ased on the system re


23/26


Ste+ 4 Indiidually Ealuate Indirect Scenarios

nce a set of scenarios has een categorized to direct and indirect grou+9 these scenarios

,ill ma+ into the architectural descri+tion. For each scenario ,ill determine in a tale ,hether

the architecture can eecuted directly or a change ,ould e re


24/26


Ste+ ! #ssess Scenario Interaction

#ssess Scenario Interaction can e define as different indirect scenarios re


25/26


26/26


References

1. #non.9 1))-. Scenario-Based Analaysis of SA. GnlineH

#ailale at= htt+=,,,.sei.cmu.eduliraryassetsscenarioasedanalysis.+df

2. #non.9 2013. Scenario-Based Software Architecture. GnlineH

#ailale at= htt+=,,,.,in.tue.nloasarchitectingaimes+a+ersScenario>;ased

20S7#20Ealuation20$ethods.+df

3. #non.9 2014. Software Architecture Analaysis Method (SAAM). GnlineH

#ailale at= htt+=aa.dzone.comarticlessoft,are>architecture>analysis

4. Clement9 (.9 2000.ATAM: Method for Architecture Evaluation. :.S.= Soft,are

Engineering Institute.

!. Clements9 (.9 2001.Evaluating Software Architectures Methods and case Studies.

#merica= #ddison 7esley.

-. Clements9 (.9 2002.Evaluating Software Architectures Methods and Case Studies.

s.l.=#ddison 7esley.

'. in9 B.9 200/. Software Architecture. s.l.=S+ringer.

/. Bhu9 ?.9 200!. Software esign Methodology. s.l.=;utter,orth>?einemann.

2-

system architecture and testing (apu)

Documents