Software systems architecture : working with stakeholders using viewpoints and perspectives / Nick Rozanski, Eoin Woods.
Material type: TextPublication details: Upper Saddle River, NJ ; London : Addison-Wesley, c2005.Description: xx, 546 p. : ill. ; 25 cmContent type:- text
- unmediated
- volume
- 0321112296 (hbk.) :
- 005.3 ROZ 22
Enhanced descriptions from Syndetics:
Software Systems Architecture is a practitioner-oriented guide to designing and implementing effective architectures for information systems. It is both a readily accessible introduction to software architecture and an invaluable handbook of well-established best practices. It shows why the role of the architect is central to any successful information-systems development project, and, by presenting a set of architectural viewpoints and perspectives, provides specific direction for improving your own and your organization's approach to software systems architecture.
With this book you will learn how to
Design an architecture that reflects and balances the different needs of its stakeholders Communicate the architecture to stakeholders and demonstrate that it has met their requirements Focus on architecturally significant aspects of design, including frequently overlooked areas such as performance, resilience, and location Use scenarios and patterns to drive the creation and validation of your architecture Document your architecture as a set of related views Use perspectives to ensure that your architecture exhibits important qualities such as performance, scalability, and securityThe architectural viewpoints and perspectives presented in the book also provide a valuable long-term reference source for new and experienced architects alike.
Whether you are an aspiring or practicing software architect, you will find yourself referring repeatedly to the practical advice in this book throughout the lifecycle of your projects.
A supporting Web site containing further information can be found at www.viewpoints-and-perspectives.info
Includes bibliographical references and index.
Table of contents provided by Syndetics
- Preface
- Acknowledgments
- About the Authors
- 1 Introduction
- Stakeholders, Viewpoints, and Perspectives
- The Structure of This Book
- Who Should Read This Book
- Conventions Used
- I Architecture Fundamentals
- 2 Software Architecture Concepts
- Software Architecture
- Architectural Elements
- Stakeholders
- Architectural Descriptions
- Interrelationships between the Core Concepts
- Summary
- Further Reading
- 3 Viewpoints and Views
- Architectural Views
- Viewpoints
- Interrelationships between the Core Concepts
- The Benefits of Using Viewpoints and Views
- Viewpoint Pitfalls
- Our Viewpoint Catalog
- Summary
- Further Reading
- 4 Architectural Perspectives
- Quality Properties
- Architectural Perspectives
- Applying Perspectives to Views
- Consequences of Applying a Perspective
- Interrelationships between the Core Concepts
- The Benefits of Using Perspectives
- Perspective Pitfalls
- Our Perspective Catalog
- Summary
- Further Reading
- 5 The Role of the Software Architect
- The Architecture Definition Process
- The Role of the Architect
- Interrelationships between the Core Concepts
- Architectural Specializations
- The Organizational Context
- The Architect's Skills
- The Architect's Responsibilities
- Summary
- Further Reading
- II The Process of Software Architecture
- 6 Introduction to the Software Architecture Process
- 7 The Architecture Definition Process
- Guiding Principles
- Process Outcomes
- The Process Context
- Supporting Activities
- Architecture Definition Activities
- Process Exit Criteria
- Architecture Definition in the Software Development Lifecycle
- Summary
- Further Reading
- 8 Scope, Concerns, Principles, and Constraints
- Business Goals and Drivers
- Architectural Scope
- Architectural Concerns
- Architectural Principles
- Other Architectural Constraints
- Checklist
- Summary
- Further Reading
- 9 Identifying and Engaging Stakeholders
- Selection of Stakeholders
- Classes of Stakeholders
- Examples
- Proxy Stakeholders
- Stakeholder Groups
- Stakeholders' Responsibilities
- Checklist
- Summary
- Further Reading
- 10 Identifying and Using Scenarios
- Types of Scenarios
- Uses for Scenarios
- Identifying and Prioritizing Scenarios
Excerpt provided by Syndetics
Author notes provided by Syndetics
Nick Rozanski is an enterprise technical architect at Marks and Spencer, where he focuses on integration and workflow. During his more than twenty years of experience he has worked for companies such as Logica, Capgemini, and Sybase. His technology experience covers enterprise application integration, relational databases, and object-oriented software development. He is also an experienced technical instructor and certified internal project auditor.
Eoin Woods is a principal consultant at Züehlke Engineering in London, where he works as a consultant software architect focusing on trading and investment management companies in the financial markets. He has worked in the software engineering field for fifteen years with a number of companies, including Ford Motor Company, Groupe Bull, InterTrust Technologies, and Sybase.