Software Architecture Evaluation with ATAM in the DoD System Acquisition Context

Abstract : Many modern defense systems rely heavily on software to achieve system functionality. Because software architecture is a major determinant of software quality, it follows that software architecture is critical to the quality of a software-intensive system. For a Department of Defense (DoD) acquisition organization, the ability to evaluate software architectures can have a favorable impact on the delivered system. This technical note explains the basics of software architecture and software architecture evaluation in a system-acquisition context. It also sets the context for applying software architecture evaluation based on the Architecture Tradeoff Analysis Method(sm) (ATAM(sm)) in the DoD acquisition environment. Future versions of this technical note will expand upon this conceptual approach and provide additional details drawn from real experiences.

[1]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[2]  John Bergey,et al.  The DoD Acquisition Environment and Software Product Lines , 1999 .

[3]  Paul Clements,et al.  Recommended Best Industrial Practice for Software Architecture Evaluation. , 1997 .

[4]  Paul Clements,et al.  Software Product Lines A New Paradigm for the New Century , 1999 .

[5]  Linda M. Northrop,et al.  A Framework for Software Product Line Practice , 1999, ECOOP Workshops.

[6]  Mark Klein,et al.  Experience with performing architecture tradeoff analysis , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[7]  P ? ? ? ? ? ? ? % ? ? ? ? , 1991 .

[8]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.