Quantifying the value of architecture design decisions: lessons from the field

Authors:
Mike Moore;Rick Kazman;Mark Klein;Jai Asundi
Affiliations:
NASA Goddard Space, Flight Center;Carnegie Mellon University;Carnegie Mellon University;University of Texas, Dallas
Venue:
Proceedings of the 25th International Conference on Software Engineering
Year:
2003

Citing 4
Cited 7

Experience with performing architecture tradeoff analysis

Proceedings of the 21st international conference on Software engineering
Quantifying the costs and benefits of architectural decisions

ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Software Engineering Economics

Software Engineering Economics
A Cost-Value Approach for Prioritizing Requirements

IEEE Software

UML Profiles for Design Decisions and Non-Functional Requirements

SHARK-ADI '07 Proceedings of the Second Workshop on SHAring and Reusing architectural Knowledge Architecture, Rationale, and Design Intent
Systematic approaches to understanding and evaluating design trade-offs

Journal of Systems and Software
Model Driven Development with non-functional aspects

EA '09 Proceedings of the 2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design
A cost-benefit framework for making architectural decisions in a business context

Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 2
An evaluation and decision method for ICT architectures for cross-organizational business process coordination

Information Systems and e-Business Management
Decision-making techniques for software architecture design: A comparative survey

ACM Computing Surveys (CSUR)
Evaluation of IT portfolio options by linking to business services

DEECS'06 Proceedings of the Second international conference on Data Engineering Issues in E-Commerce and Services

Quantified Score

Hi-index	0.00

Visualization

Abstract

This paper outlines experiences with using economic criteria to make architecture design decisions. It briefly describes the CBAM (Cost Benefit Analysis Method) framework applied to estimate the value of architectural strategies in a NASA project, the ECS. This paper describes the practical difficulties and experiences in applying the method to a large real-world system. It concludes with some lessons learned from the experience.