Difference between revisions of "Architecture Lifecycle Issues"
From Suhrid.net Wiki
Jump to navigationJump to search (Created page with "= Architecture Based Process = * Establish business case for the system. e.g. Product cost, time to market. * Understand the requirements ** Use cases, prototypes ** Quality att...") |
|||
Line 11: | Line 11: | ||
* Implement product based on the architecture. | * Implement product based on the architecture. | ||
* Ensure that implementation conforms with architecture. | * Ensure that implementation conforms with architecture. | ||
+ | |||
+ | == Process Recommendations == | ||
+ | |||
+ | * Architecture should be a product of a single architect or a small group of architects with a single leader. | ||
+ | * Arch should have both functional reqs and an articulated, prioritized list of quality attributes. | ||
+ | * Arch should be well documented with atleast one static view and one dynamic view. | ||
+ | * Arch should be circulated to all stakeholders who should actively review. | ||
+ | * Arch should be analysed for quantitative measures and formally evaluated for qualitative properties. | ||
+ | * Should lend itself to incremental implementation via creation of a skeletal system. |
Revision as of 08:39, 13 April 2012
Architecture Based Process
- Establish business case for the system. e.g. Product cost, time to market.
- Understand the requirements
- Use cases, prototypes
- Quality attributes
- Commonality & variability from previous/future systems - domain analysis.
- Develop the architecture - use tactics, styles.
- Document the architecture - using variety of views and ADL.
- Analyse or evaluate the architecture.
- Implement product based on the architecture.
- Ensure that implementation conforms with architecture.
Process Recommendations
- Architecture should be a product of a single architect or a small group of architects with a single leader.
- Arch should have both functional reqs and an articulated, prioritized list of quality attributes.
- Arch should be well documented with atleast one static view and one dynamic view.
- Arch should be circulated to all stakeholders who should actively review.
- Arch should be analysed for quantitative measures and formally evaluated for qualitative properties.
- Should lend itself to incremental implementation via creation of a skeletal system.