Contextual design: defining customer-centered systems
Contextual design: defining customer-centered systems
A survey on software architecture analysis methods
IEEE Transactions on Software Engineering
Software Architecture in Practice
Software Architecture in Practice
Balancing Agility and Discipline: A Guide for the Perplexed
Balancing Agility and Discipline: A Guide for the Perplexed
A Framework for Classifying and Comparing Software Architecture Evaluation Methods
ASWEC '04 Proceedings of the 2004 Australian Software Engineering Conference
Why software fails [software failure]
IEEE Spectrum
Using domain knowledge to boost software architecture evaluation
ECSA'10 Proceedings of the 4th European conference on Software architecture
Beyond ATAM: Early architecture evaluation method for large-scale distributed systems
Journal of Systems and Software
| Hi-index | 0.00 |
The output of 18 software architecture evaluations is analyzed. The goal of the analysis is to find patterns in the important quality attributes and risk themes identified in the evaluations. The major results are*A categorization of risk themes. *The observation that twice as many risk themes are risks of ''omission'' as are risks of ''commission''. *A failure to find a relationship between the business and mission goals of a system and the risk themes from an evaluation of that system. *A failure to find a correlation between the domain of a system being evaluated and the important quality attributes for that system. *A wide diversity of names used for various quality attributes. The results of this investigation have application to practitioners by suggesting activities on which developers should put greater focus. They also have application to researchers by suggesting further areas of investigation.