Static evaluation of software architectures
Authors:
- M. LindvallMLM. Lindvall
- D. MuthigDMD. Muthig
- M. NaabMNM. Naab
- 1 January 2006
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 15345351,p. 10 pp.-294
Abstract
The software architecture is one of the most crucial artifacts within the lifecycle of a software system. Decisions made at the architectural level directly enable, facilitate, hamper, or interfere with the achievement of business goals, functional and quality requirements. Architecture evaluations play an important role in the development and evolution of software systems since they determine how adequate the architecture is for its intended usage. This paper summarizes our practical experience with using architecture evaluations and gives an overview on when and how static architecture evaluations contribute to architecture development. We identify ten distinct purposes and needs for static architecture evaluations and illustrate them using a set of industrial and academic case studies. In particular, we show how subsequent steps in architecture development are influenced by the results from architecture evaluationsKeywords
This publication has 9 references indexed in Scilit:
- Experimenting with Software Architecture Flexibility Using an Implementation of the Tactical Separation Assisted Flight Environment2005
- Comparing design alternatives from field-tested systems to support product line architecture design2005
- Hierarchical reflexion models2004
- A method for module architecture verification and its application on a large component-based systemInformation and Software Technology, 2003
- Model-Driven Product Line Architectures2002
- Software reflexion models: bridging the gap between design and implementationIEEE Transactions on Software Engineering, 2001
- PuLSE1999
- The 4+1 View Model of architectureIEEE Software, 1995
- Reverse engineering and design recovery: a taxonomyIEEE Software, 1990