Software Architecture in Practice

Preface. Acknowledgments. Reader's Guide. I. ENVISIONING ARCHITECTURE. 1. The Architecture Business Cycle. 2. What Is Software Architecture? 3. A-7E Avionics System: A Case Study in Utilizing Architectural Structures. II. CREATING AN ARCHITECTURE. 4. Understanding Quality Attributes. 5. Achieving Qualities. 6. Air Traffic Control: A Case Study in Designing for High Availability. 7. Creating the Architecture. 8. Flight Simulation: A Case Study in an Architecture for Integrability. 9. Documenting Software Architectures. 10. Reconstructing Software Architectures. III. ANALYZING AN ARCHITECTURE. 11. The ATAM: A Comprehensive Method for Architecture Evaluation. 12. CBAM: A Quantitative Approach to Architecture Design Decision Making. 13. The World Wide Web: A Case Study in Interoperability. IV. MOVING FROM ONE SYSTEM TO MANY. 14. Software Product Lines: Reusing Architectural Assets. 15. CelsiusTech: A Case Study in Product Line Development. 16. J2EE/EJB: A Case Study of an Industry Standard Computing Infrastructure. 17. The Luther Architecture: A Case Study in Mobile Applications Using J2EE. 18. Building Systems from Off-the-Shelf Components. 19. Software Architecture in the Future. Glossary. References. Index. 0321154959T03252003

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.