Evaluating Software Architectures: Methods and Case Studies

Front Cover
Addison-Wesley, 2002 - Computers - 323 pages
1 Review
The first practical guide to evaluating software and system architectures!

-- Quick, low-cost techniques for optimizing any architecture in advance.

-- Ensuring maximum performance, security, reliability, and maintainability.

-- Step-by-step guidance and detailed practical examples based on realistic artifacts.

The foundation of any software system is its architecture. Using this book, you can evaluate every aspect of architecture in advance, at remarkably low cost -- identifying improvements that can dramatically improve any system's performance, security, reliability, and maintainability. As the practice of software architecture has matured, it has become possible to identify causal connections between architectural design decisions and the qualities and properties that result downstream in the systems that follow from them. This book shows how, offering step-by-step guidance, as well as detailed practical examples -- complete with sample artifacts reflective of those that evaluators will encounter. The techniques presented here are applicable not only to software architectures, but also to system architectures encompassing computing hardware, networking equipment, and other elements. For all software architects, software engineers, developers, IT managers, and others responsible for creating, evaluating, or implementing software architectures.

From inside the book

What people are saying - Write a review

Review: Evaluating Software Architectures: Methods and Case Studies

User Review  - Scott - Goodreads

Architecture Trade off Analysis Method (ATAM). This is a great book for direction in the evaluation of Software Architectures. The older method SAAM (Scenario Based Analysis Method) is added to the ... Read full review

Contents

What Is Software Architecture?
1
Evaluating a Software Architecture
19
1 Approximate Cost of a MediumSize ATAMBased Evaluation
39
Copyright

27 other sections not shown

Common terms and phrases

References to this book

All Book Search results »

About the author (2002)

Paul Clements is a senior member of the technical staff at the SEI, where he works on software architecture and product line engineering. He is the author of five books and more than three dozen papers on these and other topics.

Rick Kazman is a senior member of the technical staff at the SEI. He is also an Associate Professor at the University of Hawaii. He is the author of two books, editor of two more, and has written more than seventy papers on software engineering and related topics.

Mark Klein is a senior member of the technical staff at the SEI. He is an adjunct professor in the Masters of Software Engineering program at Carnegie Mellon and a coauthor of A Practitioner's Handbook for Real-time Analysis: Guide to Rate Monotonic Analysis for Real-Time Systems (Kluwer Academic Publishers, 1993).



020170482XAB01162003

Bibliographic information