Risk Themes Discovered through Architecture Evaluations

Authors:
Len Bass;Robert Nord;William Wood;David Zubrow
Affiliations:
Carnegie Mellon University, USA;Carnegie Mellon University, USA;Carnegie Mellon University, USA;Carnegie Mellon University, USA
Venue:
WICSA '07 Proceedings of the Sixth Working IEEE/IFIP Conference on Software Architecture
Year:
2007

Citing 0
Cited 6

Identifying and Understanding Architectural Risks in Software Evolution: An Empirical Study

PROFES '08 Proceedings of the 9th international conference on Product-Focused Software Process Improvement
Middleware Architecture Evaluation for Dependable Self-managing Systems

QoSA '08 Proceedings of the 4th International Conference on Quality of Software-Architectures: Models and Architectures
The software architect as the guardian of system performance and scalability

LMSA '09 Proceedings of the 2009 ICSE Workshop on Leadership and Management in Software Architecture
Software Architecture Evaluation in Global Software Development Projects

OTM '09 Proceedings of the Confederated International Workshops and Posters on On the Move to Meaningful Internet Systems: ADI, CAMS, EI2N, ISDE, IWSSA, MONET, OnToContent, ODIS, ORM, OTM Academy, SWWS, SEMELS, Beyond SAWSDL, and COMBEK 2009
Best practices for writing and managing performance requirements: a tutorial

ICPE '12 Proceedings of the 3rd ACM/SPEC International Conference on Performance Engineering
RCDA: Architecting as a risk- and cost management discipline

Journal of Systems and Software

Quantified Score

Hi-index	0.00

Visualization

Abstract

The output of 18 software architecture evaluations are analyzed to find patterns in the 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 relationship between the domain of a system being evaluated and the risk themes associated with the development of that system. 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.