Difference between revisions of "Architecture Quality Attributes"

From Suhrid.net Wiki
Jump to navigationJump to search
Line 25: Line 25:
 
* Meaningless to say System is modifiable, reusable etc. How do we justify it ?
 
* Meaningless to say System is modifiable, reusable etc. How do we justify it ?
 
* Quality Attributes are best characterised via scenarios.
 
* Quality Attributes are best characterised via scenarios.
 +
* SEI format for QA scenarios:
 +
** Source of stimulus
 +
** Stimulus
 +
** Environment
 +
** Artefact
 +
** Response
 +
** Response Measure

Revision as of 05:26, 20 March 2012

Intro

  • Qualities that must be accommodated in a systems architecture over and above basic functionality.
  • Categories of quality attributes:
    • Observable attributes. e.g:
      • Performance
      • Usability
      • Functionality
      • Security
      • Availability
    • Unobservable attributes. e.g:
      • Modifiability
      • Reusability
      • Testability
      • Portability
      • Certifiability
    • Business attributes.e.g:
      • Time to market
      • Overall cost
      • Longevity
      • Backward compatibility

Quality Attribute Scenarios

  • Meaningless to say System is modifiable, reusable etc. How do we justify it ?
  • Quality Attributes are best characterised via scenarios.
  • SEI format for QA scenarios:
    • Source of stimulus
    • Stimulus
    • Environment
    • Artefact
    • Response
    • Response Measure