Abstract : Architectural decisions have a great impact on the consequent quality of software systems. As a result, it is important to evaluate how a software architecture meets its quality demands. Though much focus has been placed on modeling and describing the software architecture as a design artifact, we found that relatively little is known about the current experience with software architecture evaluation. This report details the results of two workshops on software architecture evaluation, held at the Software Engineering Institute (SEI) on November 9-10, 1995 and May 9-10,1996. The purpose of the workshops was to determine the state of industrial practice in the evaluation of software architectures with respect to a set of desired quality attributes, and to uncover recommendations for best practices. In this report, we summarize the findings of the two workshops, define a set of dimensions to characterize various software architecture evaluation techniques, and make concrete recommendations for implementing architecture evaluation practices.
[1]
Sallie M. Henry,et al.
Software Structure Metrics Based on Information Flow
,
1981,
IEEE Transactions on Software Engineering.
[2]
Frank J. Sisti,et al.
Software Risk Evaluation Method Version 1.0.
,
1994
.
[3]
Philippe Kruchten,et al.
The 4+1 View Model of Architecture
,
1995,
IEEE Softw..
[4]
Pierre N. Robillard,et al.
A Software System Evaluation Framework
,
1995,
Computer.
[5]
Fred P. Brooks,et al.
The Mythical Man-Month
,
1975,
Reliable Software.
[6]
N. Chapman,et al.
Performance engineering
,
1997
.
[7]
Leonard J. Bass,et al.
SAAM: a method for analyzing the properties of software architectures
,
1994,
Proceedings of 16th International Conference on Software Engineering.
[8]
Leonard J. Bass,et al.
Scenario-Based Analysis of Software Architecture
,
1996,
IEEE Softw..