ArchitectureBasedonBassCH4-6

ArchitectureBasedonBassCH4-6 - Exercise Email a short...

Info iconThis preview shows pages 1–11. Sign up to view the full content.

View Full Document Right Arrow Icon
1 Exercise Email a short summary of you so your professor can get to know you better: Name, company, job/role/title, most interesting SE area, any architecting experience? What are two important objectives you have for this class.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Software Architecture in  Practice Part Two: Creating an Architecture 2nd Ed. Len Bass, Paul Clements, Rick Kazman
Background image of page 2
3 Chapter 4: Understanding Quality Attributes ABC:  business considerations determine  qualities that must be accommodated in a  system’s architecture. Systems are frequently redesigned  not because  they’re functionally deficient - the replacements  are often functionally identical - but  because  they are difficult to maintain, port, or scale, or  are too slow, or have been compromised by  network hackers .
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 Functionality, Architecture, and  Quality Attributes Functionality  and  quality attributes  are  orthogonal . Achieving quality attributes must be  considered throughout design,  implementation, and deployment . Satisfactory results depend on  getting the  big picture  (architecture)    (implementation)  right .
Background image of page 4
5 Functionality, Architecture, and  Quality Attributes Ex:  Performance  depends partially on how much communication is necessary among  components  (Arch) what functionality has been allocated to each  component  (Arch) how shared resources are allocated  (Arch) the choice of algorithms to implement selected  functionality  (Non-arch) how these algorithms are coded  (Non-arch)
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
6 Key Message Architecture is critical to deliver quality  requirements , and these qualities should be  designed in  and can be  evaluated  at the  architectural level. Architecture , by itself,  is unable to achieve  qualities  - attention must be paid to the details. Within  complex  systems,  quality attributes can  never  be achieved in isolation .  The  achievement of one will have an effect,  positive  or negative,  on others.
Background image of page 6
7 Classes of Quality Attributes Qualities of the system availability, modifiability, performance,  security, testability, and usability. Business qualities target market, rollout schedule, legacy  integration. Architectural qualities completeness, buildability
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
8 Quality Attribute Scenarios
Background image of page 8
9 A QA-specific Requirement Source of stimulus  - generating entity Stimulus  - arriving condition needing  consideration Environment  - system condition Artifact  - part of or entire system  Response  - activity caused by the stimulus Response measure  - measurable results that  tests the requirements
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
10 Performance  (p. 82)   Performance
Background image of page 10
Image of page 11
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 45

ArchitectureBasedonBassCH4-6 - Exercise Email a short...

This preview shows document pages 1 - 11. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online