Difference between revisions of "Attribute Driven Design"
From Suhrid.net Wiki
Jump to navigationJump to search (→Intro) |
(→Intro) |
||
| Line 7: | Line 7: | ||
* Output of ADD is first levels of module decomposition. | * Output of ADD is first levels of module decomposition. | ||
* System is described as a set of containers for functionality and interactions between them. | * System is described as a set of containers for functionality and interactions between them. | ||
| + | |||
| + | = Input to ADD = | ||
| + | |||
| + | * Functional requirements - typically expressed as use cases. | ||
| + | * Quality requirements - must be expressed as system specific quality scenarios. | ||
| + | * Design constraints. | ||
| + | |||
| + | == ADD Steps == | ||
Revision as of 01:57, 7 April 2012
Intro
- ADD takes as input a set of QA scenarios and uses knowledge about relation between quality attribute achievement and architecture in order to design the architecture.
- ADD is an approach to defining a software architecture that bases the decomposition process on the quality attributes that the software has to fulfill.
- Recursive decomposition process where at each stage, tactics and architectural patterns are chosen.
- ADD is started after requirements analysis - where the QA drivers are thought to be well understood.
- Output of ADD is first levels of module decomposition.
- System is described as a set of containers for functionality and interactions between them.
Input to ADD
- Functional requirements - typically expressed as use cases.
- Quality requirements - must be expressed as system specific quality scenarios.
- Design constraints.
