Chapter 1: Introduction
Chapter 2: Software Architecture Concepts
Chapter 3: Viewpoints and Views
Chapter 4: Architectural Perspectives
Chapter 5: The Role Of The Software Architect
Chapter 6: Introduction to the Software Architecture Process
Chapter 7: The Architecture Definition Process
Chapter 8: Concerns, Principles, and Decisions
Chapter 9: Identifying and Engaging Stakeholders
Chapter 10: Identifying and Using Scenarios
Chapter 11: Using Styles and Patterns
Chapter 12: Producing Architectural Models
Chapter 13: Creating the Architectural Description
Chapter 14: Evaluating the Architecture
Chapter 15: Introduction to the Viewpoint Catalog
Chapter 16: The Context Viewpoint
Chapter 17: The Functional Viewpoint
Chapter 18: The Information Viewpoint
Chapter 19: The Concurrency Viewpoint
Chapter 20: The Development Viewpoint
Chapter 21: The Deployment Viewpoint
Chapter 22: The Operational Viewpoint
Chapter 23: Achieving Consistency Across Views
Chapter 24: Introduction to the Perspective Catalo
Chapter 25: The Security Perspective
Chapter 26: The Performance and Scalability Perspective
Chapter 27: The Availability and Resilience Perspective
Chapter 28: The Evolution Perspective
Chapter 29: Other Perspectives
Chapter 30: Working As A Software Architect
Appendix: Other Viewpoint Sets

About the Author

Nick Rozanski has worked in IT since 1980 for several large and small systems integrators, including Logica, Capgemini, and Sybase, and end user organizations including Marks and Spencer and Barclays Global Investors. He has taken senior roles on a wide range of programs in finance, retail, manufacturing, and government. His technology background includes enterprise application integration, package implementation, relational database, data replication, and object-oriented software development. He is also an experienced technical instructor and certified internal project auditor.

Eoin (pronounced “Owen”) Woods is a lead system architect in the equities technology group of a major European investment bank with architecture and design responsibility for a number of the organization’s key systems. Prior to this, he led the application architecture group at Barclays Global Investors and has worked as a software engineer for Group Bull, Sybase, InterTrust, and Zuhlke, as well as through his own consultancy company, Artechra.

Table of Contents

About the Author