Software Architecture in Practice
Published on 12. February 1998
Book
Hardback
480 pages
978-0-201-19930-7 (ISBN)
Description
This book introduces the concepts and practice of software architecture-what a system is designed to do, and on how its components are meant to interact with each other. An architecture is an abstract view, distinct from the details of implementation, algorithm, and data representation. Its creation is the first step in designing a system with properties desired by customers, end users, developers, maintainers, and other interested parties. The authors cover here not only essential technical topics for specifying and validating a system, but, for the first time, emphasize the importance of the business context in which large systems are designed. Enhancing both technical and organizational discussions, key points are illuminated by substantial case studies undertaken by the authors and the Software Engineering Institute.
More details
Language
English
Place of publication
Boston
United States
Publishing group
Pearson Education (US)
Target group
College/higher education
Dimensions
Height: 243 mm
Width: 166 mm
Thickness: 35 mm
Weight
951 gr
ISBN-13
978-0-201-19930-7 (9780201199307)
Copyright in bibliographic data and cover images is held by Nielsen Book Services Limited or by the publishers or by their respective licensors: all rights reserved.
Schweitzer Classification
Other editions
New editions
Len Bass | Paul Clements | Rick Kazman
Software Architecture in Practice
Book
04/2003
2nd Edition
Addison Wesley
€65.60
Article exhausted; check for reprint
Persons
Len Bass is a senior member of the technical staff at the Software Engineering Institute (SEI). He has written or edited five books and numerous papers on software engineering and other topics. He has extensive experience in architecting real-world development projects.
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.
0201199300AB01162003
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.
0201199300AB01162003
Content
(Each chapter concludes with a Summary, For Further Reading and/or Discussion Questions.)
Preface.
Reader's Guide.
Acknowledgments.
I. ENVISIONING ARCHITECTURE.
1. The Architecture Business Cycle.
Where Do Architectures Come From?
Software Processes and the Architecture Business Cycle.
What Makes a "Good" Architecture?
2. What Is Software Architecture?
What Software Architecture Is and What It Isn't.
Architectural Styles, Reference Models, and Reference Architectures.
Other Viewpoints.
Why Is Software Architecture Important?
Architectural Structures.
3. A-7E: A Case Study in Utilizing Architectural Structures.
Relationship to the Architecture Business Cycle.
Requirements and Qualities.
Architectural Approach.
Architecture for the A-7E Avionics System.
II. CREATING AND ANALYZING AN ARCHITECTURE.
4. Quality Attributes.
Architectures and Quality Attributes.
Architectural Means for Achieving Qualities.
5. Moving From Qualities to Architecture: Architectural Styles.
Introducing Architectural Styles.
Organizing Architectural Styles.
Refinements of Styles.
Using Styles in System Design.
Achieving Quality Goals with Architectural Styles.
6. Unit Operations.
Introducing Unit Operations.
Applying Unit Operations to User-Interface Software.
Ramifications of Addressing Quality Attributes.
7. The World Wide Web: A Case Study in Interoperability.
Relationship to the Architecture Business Cycle.
Requirements and Qualities.
Architectural Approach.
Architectural Solution.
Architecture Business Cycle Today.
8. CORBA: A Case Study of an Industry Standard Computing Infrastructure.
Relationship to the Architecture Business Cycle.
Requirements and Qualities.
Architectural Approach.
Architectural Solution.
The Web and CORBA.
9. Analyzing Development Qualities at the Architectural Level: The Software Architecture Analysis Method.
The How and Why of Analyzing Software Architecture.
Overview of Software Architecture Analysis Method.
A Small Example of SAAM Application.
SAAM Applied to a Financial Management System.
SAAM Applied to a Revision-Control System.
Observations on SAAM.
10. Architecture Reviews.
Costs and Benefits.
Review Techniques.
The Review Practice.
11. Air Traffic Control: A Case Study in Designing for High Availability.
Relationship to the Architecture Business Cycle.
Requirements and Qualities.
Architectural Approach.
Architectural Solution.
Assessing the Architecture for Maintainability.
III. MOVING FROM ARCHITECTURES TO SYSTEMS.
12. Architecture Description Languages.
Architecture Description Languages Today.
Capturing Architectural Information in an ADL.
How Do ADLs Help System Development?
Choosing an ADL.
An Example of an ADL.
13. Architecture-Based Development.
Forming the Team Structure.
Creating a Skeletal System.
Exploiting Patterns in Software Architecture.
Ensuring Conformance to an Architecture.
Building Domain-Specific Languages.
14. Flight Simulation: A Case Study in Architecture for Integrability.
Relationship to the Architecture Business Cycle.
Requirements and Qualities.
Architectural Approach.
Architectural Solution.
Achievement of Goals.
IV. REUSEING ARCHITECTURES.
15. Product Lines: Reusing Architectural Assets within an Organization.
Creating Products and Evolving a Product Line.
Organizational Implications of a Product Line.
Component-Based Systems.
16. CelsiusTech: A Case Study in Product Line Development.
Relationship to the Architecture Business Cycle.
Requirements and Qualities.
Architectural Approach.
17. Communitywide Reuse of Architectural Assets.
Reference Architectures.
Open Systems.
The Process of Engineering an Open System.
Standards.
18. The Meteorological Anchor Desk System: A Case Study in Building a Web-Based System from Off-the-Shelf Components.
Relationship to the Architecture Business Cycle.
Requirements and Qualities.
Architectural Approach.
Architectural Solution.
19. Software Architecture in the Future.
The Architecture Business Cycle Revisited.
Architecture and Legacy Systems.
Achieving an Architecture.
From Architecture to System.
Acronyms.
References.
Bibliography.
Index. 0201199300T04062001
Preface.
Reader's Guide.
Acknowledgments.
I. ENVISIONING ARCHITECTURE.
1. The Architecture Business Cycle.
Where Do Architectures Come From?
Software Processes and the Architecture Business Cycle.
What Makes a "Good" Architecture?
2. What Is Software Architecture?
What Software Architecture Is and What It Isn't.
Architectural Styles, Reference Models, and Reference Architectures.
Other Viewpoints.
Why Is Software Architecture Important?
Architectural Structures.
3. A-7E: A Case Study in Utilizing Architectural Structures.
Relationship to the Architecture Business Cycle.
Requirements and Qualities.
Architectural Approach.
Architecture for the A-7E Avionics System.
II. CREATING AND ANALYZING AN ARCHITECTURE.
4. Quality Attributes.
Architectures and Quality Attributes.
Architectural Means for Achieving Qualities.
5. Moving From Qualities to Architecture: Architectural Styles.
Introducing Architectural Styles.
Organizing Architectural Styles.
Refinements of Styles.
Using Styles in System Design.
Achieving Quality Goals with Architectural Styles.
6. Unit Operations.
Introducing Unit Operations.
Applying Unit Operations to User-Interface Software.
Ramifications of Addressing Quality Attributes.
7. The World Wide Web: A Case Study in Interoperability.
Relationship to the Architecture Business Cycle.
Requirements and Qualities.
Architectural Approach.
Architectural Solution.
Architecture Business Cycle Today.
8. CORBA: A Case Study of an Industry Standard Computing Infrastructure.
Relationship to the Architecture Business Cycle.
Requirements and Qualities.
Architectural Approach.
Architectural Solution.
The Web and CORBA.
9. Analyzing Development Qualities at the Architectural Level: The Software Architecture Analysis Method.
The How and Why of Analyzing Software Architecture.
Overview of Software Architecture Analysis Method.
A Small Example of SAAM Application.
SAAM Applied to a Financial Management System.
SAAM Applied to a Revision-Control System.
Observations on SAAM.
10. Architecture Reviews.
Costs and Benefits.
Review Techniques.
The Review Practice.
11. Air Traffic Control: A Case Study in Designing for High Availability.
Relationship to the Architecture Business Cycle.
Requirements and Qualities.
Architectural Approach.
Architectural Solution.
Assessing the Architecture for Maintainability.
III. MOVING FROM ARCHITECTURES TO SYSTEMS.
12. Architecture Description Languages.
Architecture Description Languages Today.
Capturing Architectural Information in an ADL.
How Do ADLs Help System Development?
Choosing an ADL.
An Example of an ADL.
13. Architecture-Based Development.
Forming the Team Structure.
Creating a Skeletal System.
Exploiting Patterns in Software Architecture.
Ensuring Conformance to an Architecture.
Building Domain-Specific Languages.
14. Flight Simulation: A Case Study in Architecture for Integrability.
Relationship to the Architecture Business Cycle.
Requirements and Qualities.
Architectural Approach.
Architectural Solution.
Achievement of Goals.
IV. REUSEING ARCHITECTURES.
15. Product Lines: Reusing Architectural Assets within an Organization.
Creating Products and Evolving a Product Line.
Organizational Implications of a Product Line.
Component-Based Systems.
16. CelsiusTech: A Case Study in Product Line Development.
Relationship to the Architecture Business Cycle.
Requirements and Qualities.
Architectural Approach.
17. Communitywide Reuse of Architectural Assets.
Reference Architectures.
Open Systems.
The Process of Engineering an Open System.
Standards.
18. The Meteorological Anchor Desk System: A Case Study in Building a Web-Based System from Off-the-Shelf Components.
Relationship to the Architecture Business Cycle.
Requirements and Qualities.
Architectural Approach.
Architectural Solution.
19. Software Architecture in the Future.
The Architecture Business Cycle Revisited.
Architecture and Legacy Systems.
Achieving an Architecture.
From Architecture to System.
Acronyms.
References.
Bibliography.
Index. 0201199300T04062001