Cristiane Lana e Délcio Silva Software Architecture ... · • Software Architecture Description &...
40
Cristiane Lana e Délcio Silva Software Architecture - SSC9441 Prof. Dr. Elisa Yumi Nakagawa Institute of Mathematics and Computational Sciences - ICMC
Transcript of Cristiane Lana e Délcio Silva Software Architecture ... · • Software Architecture Description &...
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Introduction
bull Architectural Description
bull Understand the ISOIECIEEE 420102011
bull Architectural Frameworks
bull Final considerations
bull Interesting Links
2
Age
nd
a
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull To build a software architecture is necessary to know the stakeholders
bull Architectural descripition is a artifact tangible
bull Help in the communication process with stakeholders
bull Implementation assessment
bull Entry for tool
ndash Example simulation
3
Intr
od
uct
ion
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It provides a common language to express differentinterests
4
Intr
od
uct
ion
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
we
ce
ub
cc
a~
ma
teiE
EC
E4
17
BA
SS
ch
01
lev
1se
c1
ht
ml
bull It can be influenced by
5
Intr
od
uct
ion
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a artifact that express a system architecture
bull It describe a possible architecture for the
system
bull It can be
ndash Document model groups model repository among
others
bull What is AD
6
Arc
hit
ect
ura
l De
scri
pti
on
[ISOIECIEEE 42010]
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Why it is made
bull Support tondash Understand
ndash Analyze
ndash compare Architectures
ndash Used as ldquoblueprintsrdquo for planning and construction
ndash Documentation
ndash hellip
[ISOIECIEEE 42010]
7
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It can be used as templates that support the description process
bull It is dependent of the stakeholders
bull Based on interests and domain
bull Choose the view that make up the system architecture
bull How is it done
[ISOIECIEEE 42010]
8
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When is it done
[ISOIECIEEE 42010]
9
wwwbatalascoukwwwartsbmaorg
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Problems with communication in the requirements phase
10
ww
ws
lide
sh
are
ne
tA
rch
ite
ctu
ral D
esc
rip
tio
n
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When it is not done correctly
11
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull For who
and
httpwwwcrisismanagementtony-Ridleycom
12
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Who does it
http
alld
ub
aia
ed
ub
ai-a
rch
itec
ts-dire
cto
ry
13
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Enterprise Strategy and Architecture
It is a set of best practices for the architectural
description
14
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
replaces
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
15
[ISOIECIEEE 42010]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a collection of models representing the architecture of the whole system relative to a set of concern
[ISOIECIEEE 42010]
16
bull A structural view
Shared data view of an agent[Guessi Damasceno 2016]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Introduction
bull Architectural Description
bull Understand the ISOIECIEEE 420102011
bull Architectural Frameworks
bull Final considerations
bull Interesting Links
2
Age
nd
a
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull To build a software architecture is necessary to know the stakeholders
bull Architectural descripition is a artifact tangible
bull Help in the communication process with stakeholders
bull Implementation assessment
bull Entry for tool
ndash Example simulation
3
Intr
od
uct
ion
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It provides a common language to express differentinterests
4
Intr
od
uct
ion
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
we
ce
ub
cc
a~
ma
teiE
EC
E4
17
BA
SS
ch
01
lev
1se
c1
ht
ml
bull It can be influenced by
5
Intr
od
uct
ion
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a artifact that express a system architecture
bull It describe a possible architecture for the
system
bull It can be
ndash Document model groups model repository among
others
bull What is AD
6
Arc
hit
ect
ura
l De
scri
pti
on
[ISOIECIEEE 42010]
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Why it is made
bull Support tondash Understand
ndash Analyze
ndash compare Architectures
ndash Used as ldquoblueprintsrdquo for planning and construction
ndash Documentation
ndash hellip
[ISOIECIEEE 42010]
7
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It can be used as templates that support the description process
bull It is dependent of the stakeholders
bull Based on interests and domain
bull Choose the view that make up the system architecture
bull How is it done
[ISOIECIEEE 42010]
8
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When is it done
[ISOIECIEEE 42010]
9
wwwbatalascoukwwwartsbmaorg
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Problems with communication in the requirements phase
10
ww
ws
lide
sh
are
ne
tA
rch
ite
ctu
ral D
esc
rip
tio
n
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When it is not done correctly
11
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull For who
and
httpwwwcrisismanagementtony-Ridleycom
12
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Who does it
http
alld
ub
aia
ed
ub
ai-a
rch
itec
ts-dire
cto
ry
13
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Enterprise Strategy and Architecture
It is a set of best practices for the architectural
description
14
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
replaces
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
15
[ISOIECIEEE 42010]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a collection of models representing the architecture of the whole system relative to a set of concern
[ISOIECIEEE 42010]
16
bull A structural view
Shared data view of an agent[Guessi Damasceno 2016]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull To build a software architecture is necessary to know the stakeholders
bull Architectural descripition is a artifact tangible
bull Help in the communication process with stakeholders
bull Implementation assessment
bull Entry for tool
ndash Example simulation
3
Intr
od
uct
ion
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It provides a common language to express differentinterests
4
Intr
od
uct
ion
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
we
ce
ub
cc
a~
ma
teiE
EC
E4
17
BA
SS
ch
01
lev
1se
c1
ht
ml
bull It can be influenced by
5
Intr
od
uct
ion
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a artifact that express a system architecture
bull It describe a possible architecture for the
system
bull It can be
ndash Document model groups model repository among
others
bull What is AD
6
Arc
hit
ect
ura
l De
scri
pti
on
[ISOIECIEEE 42010]
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Why it is made
bull Support tondash Understand
ndash Analyze
ndash compare Architectures
ndash Used as ldquoblueprintsrdquo for planning and construction
ndash Documentation
ndash hellip
[ISOIECIEEE 42010]
7
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It can be used as templates that support the description process
bull It is dependent of the stakeholders
bull Based on interests and domain
bull Choose the view that make up the system architecture
bull How is it done
[ISOIECIEEE 42010]
8
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When is it done
[ISOIECIEEE 42010]
9
wwwbatalascoukwwwartsbmaorg
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Problems with communication in the requirements phase
10
ww
ws
lide
sh
are
ne
tA
rch
ite
ctu
ral D
esc
rip
tio
n
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When it is not done correctly
11
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull For who
and
httpwwwcrisismanagementtony-Ridleycom
12
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Who does it
http
alld
ub
aia
ed
ub
ai-a
rch
itec
ts-dire
cto
ry
13
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Enterprise Strategy and Architecture
It is a set of best practices for the architectural
description
14
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
replaces
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
15
[ISOIECIEEE 42010]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a collection of models representing the architecture of the whole system relative to a set of concern
[ISOIECIEEE 42010]
16
bull A structural view
Shared data view of an agent[Guessi Damasceno 2016]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull It provides a common language to express differentinterests
4
Intr
od
uct
ion
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
we
ce
ub
cc
a~
ma
teiE
EC
E4
17
BA
SS
ch
01
lev
1se
c1
ht
ml
bull It can be influenced by
5
Intr
od
uct
ion
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a artifact that express a system architecture
bull It describe a possible architecture for the
system
bull It can be
ndash Document model groups model repository among
others
bull What is AD
6
Arc
hit
ect
ura
l De
scri
pti
on
[ISOIECIEEE 42010]
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Why it is made
bull Support tondash Understand
ndash Analyze
ndash compare Architectures
ndash Used as ldquoblueprintsrdquo for planning and construction
ndash Documentation
ndash hellip
[ISOIECIEEE 42010]
7
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It can be used as templates that support the description process
bull It is dependent of the stakeholders
bull Based on interests and domain
bull Choose the view that make up the system architecture
bull How is it done
[ISOIECIEEE 42010]
8
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When is it done
[ISOIECIEEE 42010]
9
wwwbatalascoukwwwartsbmaorg
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Problems with communication in the requirements phase
10
ww
ws
lide
sh
are
ne
tA
rch
ite
ctu
ral D
esc
rip
tio
n
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When it is not done correctly
11
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull For who
and
httpwwwcrisismanagementtony-Ridleycom
12
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Who does it
http
alld
ub
aia
ed
ub
ai-a
rch
itec
ts-dire
cto
ry
13
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Enterprise Strategy and Architecture
It is a set of best practices for the architectural
description
14
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
replaces
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
15
[ISOIECIEEE 42010]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a collection of models representing the architecture of the whole system relative to a set of concern
[ISOIECIEEE 42010]
16
bull A structural view
Shared data view of an agent[Guessi Damasceno 2016]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
http
ww
we
ce
ub
cc
a~
ma
teiE
EC
E4
17
BA
SS
ch
01
lev
1se
c1
ht
ml
bull It can be influenced by
5
Intr
od
uct
ion
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a artifact that express a system architecture
bull It describe a possible architecture for the
system
bull It can be
ndash Document model groups model repository among
others
bull What is AD
6
Arc
hit
ect
ura
l De
scri
pti
on
[ISOIECIEEE 42010]
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Why it is made
bull Support tondash Understand
ndash Analyze
ndash compare Architectures
ndash Used as ldquoblueprintsrdquo for planning and construction
ndash Documentation
ndash hellip
[ISOIECIEEE 42010]
7
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It can be used as templates that support the description process
bull It is dependent of the stakeholders
bull Based on interests and domain
bull Choose the view that make up the system architecture
bull How is it done
[ISOIECIEEE 42010]
8
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When is it done
[ISOIECIEEE 42010]
9
wwwbatalascoukwwwartsbmaorg
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Problems with communication in the requirements phase
10
ww
ws
lide
sh
are
ne
tA
rch
ite
ctu
ral D
esc
rip
tio
n
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When it is not done correctly
11
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull For who
and
httpwwwcrisismanagementtony-Ridleycom
12
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Who does it
http
alld
ub
aia
ed
ub
ai-a
rch
itec
ts-dire
cto
ry
13
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Enterprise Strategy and Architecture
It is a set of best practices for the architectural
description
14
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
replaces
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
15
[ISOIECIEEE 42010]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a collection of models representing the architecture of the whole system relative to a set of concern
[ISOIECIEEE 42010]
16
bull A structural view
Shared data view of an agent[Guessi Damasceno 2016]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull It is a artifact that express a system architecture
bull It describe a possible architecture for the
system
bull It can be
ndash Document model groups model repository among
others
bull What is AD
6
Arc
hit
ect
ura
l De
scri
pti
on
[ISOIECIEEE 42010]
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Why it is made
bull Support tondash Understand
ndash Analyze
ndash compare Architectures
ndash Used as ldquoblueprintsrdquo for planning and construction
ndash Documentation
ndash hellip
[ISOIECIEEE 42010]
7
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It can be used as templates that support the description process
bull It is dependent of the stakeholders
bull Based on interests and domain
bull Choose the view that make up the system architecture
bull How is it done
[ISOIECIEEE 42010]
8
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When is it done
[ISOIECIEEE 42010]
9
wwwbatalascoukwwwartsbmaorg
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Problems with communication in the requirements phase
10
ww
ws
lide
sh
are
ne
tA
rch
ite
ctu
ral D
esc
rip
tio
n
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When it is not done correctly
11
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull For who
and
httpwwwcrisismanagementtony-Ridleycom
12
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Who does it
http
alld
ub
aia
ed
ub
ai-a
rch
itec
ts-dire
cto
ry
13
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Enterprise Strategy and Architecture
It is a set of best practices for the architectural
description
14
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
replaces
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
15
[ISOIECIEEE 42010]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a collection of models representing the architecture of the whole system relative to a set of concern
[ISOIECIEEE 42010]
16
bull A structural view
Shared data view of an agent[Guessi Damasceno 2016]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Why it is made
bull Support tondash Understand
ndash Analyze
ndash compare Architectures
ndash Used as ldquoblueprintsrdquo for planning and construction
ndash Documentation
ndash hellip
[ISOIECIEEE 42010]
7
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It can be used as templates that support the description process
bull It is dependent of the stakeholders
bull Based on interests and domain
bull Choose the view that make up the system architecture
bull How is it done
[ISOIECIEEE 42010]
8
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When is it done
[ISOIECIEEE 42010]
9
wwwbatalascoukwwwartsbmaorg
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Problems with communication in the requirements phase
10
ww
ws
lide
sh
are
ne
tA
rch
ite
ctu
ral D
esc
rip
tio
n
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When it is not done correctly
11
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull For who
and
httpwwwcrisismanagementtony-Ridleycom
12
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Who does it
http
alld
ub
aia
ed
ub
ai-a
rch
itec
ts-dire
cto
ry
13
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Enterprise Strategy and Architecture
It is a set of best practices for the architectural
description
14
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
replaces
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
15
[ISOIECIEEE 42010]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a collection of models representing the architecture of the whole system relative to a set of concern
[ISOIECIEEE 42010]
16
bull A structural view
Shared data view of an agent[Guessi Damasceno 2016]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull It can be used as templates that support the description process
bull It is dependent of the stakeholders
bull Based on interests and domain
bull Choose the view that make up the system architecture
bull How is it done
[ISOIECIEEE 42010]
8
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When is it done
[ISOIECIEEE 42010]
9
wwwbatalascoukwwwartsbmaorg
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Problems with communication in the requirements phase
10
ww
ws
lide
sh
are
ne
tA
rch
ite
ctu
ral D
esc
rip
tio
n
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When it is not done correctly
11
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull For who
and
httpwwwcrisismanagementtony-Ridleycom
12
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Who does it
http
alld
ub
aia
ed
ub
ai-a
rch
itec
ts-dire
cto
ry
13
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Enterprise Strategy and Architecture
It is a set of best practices for the architectural
description
14
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
replaces
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
15
[ISOIECIEEE 42010]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a collection of models representing the architecture of the whole system relative to a set of concern
[ISOIECIEEE 42010]
16
bull A structural view
Shared data view of an agent[Guessi Damasceno 2016]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull When is it done
[ISOIECIEEE 42010]
9
wwwbatalascoukwwwartsbmaorg
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Problems with communication in the requirements phase
10
ww
ws
lide
sh
are
ne
tA
rch
ite
ctu
ral D
esc
rip
tio
n
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When it is not done correctly
11
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull For who
and
httpwwwcrisismanagementtony-Ridleycom
12
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Who does it
http
alld
ub
aia
ed
ub
ai-a
rch
itec
ts-dire
cto
ry
13
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Enterprise Strategy and Architecture
It is a set of best practices for the architectural
description
14
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
replaces
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
15
[ISOIECIEEE 42010]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a collection of models representing the architecture of the whole system relative to a set of concern
[ISOIECIEEE 42010]
16
bull A structural view
Shared data view of an agent[Guessi Damasceno 2016]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Problems with communication in the requirements phase
10
ww
ws
lide
sh
are
ne
tA
rch
ite
ctu
ral D
esc
rip
tio
n
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull When it is not done correctly
11
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull For who
and
httpwwwcrisismanagementtony-Ridleycom
12
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Who does it
http
alld
ub
aia
ed
ub
ai-a
rch
itec
ts-dire
cto
ry
13
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Enterprise Strategy and Architecture
It is a set of best practices for the architectural
description
14
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
replaces
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
15
[ISOIECIEEE 42010]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a collection of models representing the architecture of the whole system relative to a set of concern
[ISOIECIEEE 42010]
16
bull A structural view
Shared data view of an agent[Guessi Damasceno 2016]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull When it is not done correctly
11
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull For who
and
httpwwwcrisismanagementtony-Ridleycom
12
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Who does it
http
alld
ub
aia
ed
ub
ai-a
rch
itec
ts-dire
cto
ry
13
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Enterprise Strategy and Architecture
It is a set of best practices for the architectural
description
14
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
replaces
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
15
[ISOIECIEEE 42010]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a collection of models representing the architecture of the whole system relative to a set of concern
[ISOIECIEEE 42010]
16
bull A structural view
Shared data view of an agent[Guessi Damasceno 2016]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull For who
and
httpwwwcrisismanagementtony-Ridleycom
12
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Who does it
http
alld
ub
aia
ed
ub
ai-a
rch
itec
ts-dire
cto
ry
13
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Enterprise Strategy and Architecture
It is a set of best practices for the architectural
description
14
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
replaces
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
15
[ISOIECIEEE 42010]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a collection of models representing the architecture of the whole system relative to a set of concern
[ISOIECIEEE 42010]
16
bull A structural view
Shared data view of an agent[Guessi Damasceno 2016]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Who does it
http
alld
ub
aia
ed
ub
ai-a
rch
itec
ts-dire
cto
ry
13
Arc
hit
ect
ura
l De
scri
pti
on
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Enterprise Strategy and Architecture
It is a set of best practices for the architectural
description
14
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
replaces
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
15
[ISOIECIEEE 42010]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a collection of models representing the architecture of the whole system relative to a set of concern
[ISOIECIEEE 42010]
16
bull A structural view
Shared data view of an agent[Guessi Damasceno 2016]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
Enterprise Strategy and Architecture
It is a set of best practices for the architectural
description
14
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
replaces
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
15
[ISOIECIEEE 42010]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a collection of models representing the architecture of the whole system relative to a set of concern
[ISOIECIEEE 42010]
16
bull A structural view
Shared data view of an agent[Guessi Damasceno 2016]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
15
[ISOIECIEEE 42010]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is a collection of models representing the architecture of the whole system relative to a set of concern
[ISOIECIEEE 42010]
16
bull A structural view
Shared data view of an agent[Guessi Damasceno 2016]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull It is a collection of models representing the architecture of the whole system relative to a set of concern
[ISOIECIEEE 42010]
16
bull A structural view
Shared data view of an agent[Guessi Damasceno 2016]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull It is artifact that establishes conventions for creatinginterpreting and use viewsndash Example language notation design rules model types modeling
methods analysis techniques and any associated methods
bull It expresses how to construct a view
bull It ensures that the concern of stakeholders are⁻ Identified allocated and covered
[Guessi 2013] [ISOIECIEEE 42010]
17
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull The 42010 has not a standard convention
flexible choice
Concern vary systems to systems
Better meet the concern of stakeholders
bull One viewpoints should
Define functions and methods associated
Many organizations already have these pre-established decisions
Based on the architects experience
Example structural system etc
[ISOIECIEEE 42010]
Stakeholders and identified concern =gt viewpoint =gt view
18
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Metaphorbull view viewpoint map legend
[ISOIECIEEE 42010]
19
A legend defines
bull the conventions used in preparing a map (such as its scale colors and other
symbology) to aid readers in interpreting that map as intended
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
ndash Separation of concerns
ndash Communication with stakeholders groups
ndash Management of complexity
ndash Improvement developer focus
[Rozanski and Woods sd]
20
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
ndash Inconsistency
ndash Selection of the wrong set of views
ndash Fragmentation
21
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Rozanski and Woods sd]
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull A view is composed of architecture models
bull Each model is constructed following conventionsestablished by its models kind
bull It can belong to one or more viewsndash Example client-server distributed objects layers
[ISOIECIEEE 42010]
22
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull It defines the conventions for one type of architecturemodelndash Example meta-models
[ISOIECIEEE 42010]
23
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull It expresses a relation between AD Elements
bull It are used to express architecture relations such asndash composition refinement consistency traceability
dependence constraints and obligation
[ISOIECIEEE 42010]
24
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[ISOIECIEEE 42010]
25
Consider two views of a system S a hardware view HW(S) and a
software component view SC(S) Given that SC(S) includes software
elements e1 hellip e6 and HW(S) includes hardware platforms p1 hellip p4
a correspondence expressing which software elements execute on
which platforms
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull It governs correspondence
bull It expresses a constraint to be enforced on acorrespondence
bull Example
[ISOIECIEEE 42010]
26
R1 Every software element ei as defined by Software
Components needs to execute on one or more platforms
pj as defined by Hardware
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull It records the explanation justification or reasoningabout particular decisionndash Example reasons for the decision alternatives and
exchanges considered possible consequences
[ISO
IEC
IEE
E 4
20
10
] [Gu
essi 2
01
3]
27
Un
der
stan
d t
he
ISO
IEC
IEE
E 4
20
10
20
11
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Federal Enterprise Architecture
bull Kruchtenrsquos 4+1 Framework
bull It establishes a common practice forndash creating interpreting analyzing and using architecture
descriptions
ndash a particular domain of application or stakeholder community
28
Arc
hit
ect
ure
Fram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
29
[ISO
IEC
IEE
E 4
20
10
]A
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
http
ww
win
stitu
togtic
om
br
30
Development View
DevelopersConfiguration Management
Process View
Performance
Scalability
Throughput
System Integrators
Physical View
Topology System
Communication
Provisioning
Support Analyst
Logical View
Functionality
Users Final
logical physical
Use Case View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
httpwwwinstitutogticombr
31
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Use Case Viewndash Content software functionality its external interfaces and key users
ndash Diagrams use case diagrams
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
32
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Logical Viewndash Content organizations of the elements of analysis and software design
and use case realizations
ndash Diagrams class sequence communication state
ndash Interested users systems of analysts architects developers
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
33
ndash Content allocations of software design elements on components and subsystems and organizational components subsystems and layers
ndash Diagrams component and package diagrams
ndash Interested architects developers integrators
bull Development View
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
http
ww
win
stituto
gtic
om
br
[Ale
xa
nd
re_L
ea
ondash
UF
PE
20
10
]
34
bull Physical Viewndash Content components allocation in artifacts artifacts in the hardware and
software infrastructure and organization of hardware and software infrastructure
ndash Diagrams deployment
ndash Interested architects integrators support of analysts operators
Arc
hit
ect
ure
Fra
mew
ork
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Process View ndash Content addresses the concurrent aspects and distribution system
integrity and fault-tolerance of a system at runtime
ndash Diagrams Sequence Communication Activity Activity Timing and Interaction Overview
ndash Interested architects integrators support analyst
http
ww
win
stituto
gtic
om
br
35
Inst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
CA
rch
ite
ctu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull What is use
http
ww
win
stituto
gtic
om
br
bull Not all systems need all viewsndash Small systems (it discount the implementation view)
ndash Single processor (it can discount the deployment)
ndash Single process (it can discount the process view)
bull Some systems require additional viewsndash Data view
ndash Security view
ndash Among others
36
Arc
hit
ectu
re F
ram
ewo
rk
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
Architectural Description
bull are used by the parties that create utilize and manage modern systems toimprove communication and co-operation enabling them to work in anintegrated coherent fashion
bull is a work product which models the architecture of a system-of-interest
bull have many uses by a variety of stakeholders throughout the system life cycle
bull shall identify the system stakeholders having concerns considered fundamentalto the architecture of the system-of-interest
37
Fin
al C
on
sid
era
tio
ns
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull ISO-IEC-FDIS-42010
bull Software Architecture Description amp UML Workshop
bull A Conceptual Model of Architecture Description
bull Using the UML for Architectural Description
bull System and Software Architecture Description Example
bull Views and Viewpoints in Software Systems Architecture
bull Documenting Software Architecting View and Beyond
bull Document Software Architecture
bull Architectural Description Guideline
38
Inte
rest
ing
Lin
ks
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
bull Guessi M Subsiacutedios para a representaccedilatildeo de arquitetras de referecircncia de sistemas embarcados Dissertation (Master) Institute of Mathematics and Computation Science ndashICMC ndash University of Satildeo Paulo (USP) Satildeo Carlos Brazil 2013
bull Bass L Clements P amp Kazman R (2003) Software Architecture in Practice Addison-Wesley Professional 2nd edition
bull ISOIECIEEE 420102010 International Standard for Systems and Software Engineering --Architectural description
bull Rozanski N and Woods E Applying viewpoints and views to software engineering Available in httpwwwviewpoints-and-perspectivesinfovpandpwp-contentthemessecondeditiondocVPandV_WhitePaperpdf Acess in 2016-03-29
39
Bib
liogr
aph
y
University of Satildeo Paulo ndash Satildeo CarlosDepartment of Computer Systems
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
Cristiane Lana e Deacutelcio Silva
Software Architecture - SSC9441
Prof Dr Elisa Yumi NakagawaInst
itu
te o
f M
ath
em
atic
s an
d C
om
pu
tati
on
al S
cie
nce
s -
ICM
C
