
Software Systems Architecture
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
With this book you will learn how to
Design and communicate an architecture that reflects and balances the different needs of its stakeholders
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
Reflecting new standards and developments in the field, this new edition extends and updates much of the content, and
Adds a "system context viewpoint" that documents the system's interactions with its environment
Expands the discussion of architectural principles, showing how they can be used to provide traceability and rationale for architectural decisions
Explains how agile development and architecture can work together
Positions requirements and architecture activities in the project context
Presents a new lightweight method for architectural validation
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.
More details
Other editions
Additional editions

Persons
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.
Content
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
System requirements
File format: ePUB
Copy protection: Watermark-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Use a reading software that can process the file format ePUB: e.g., Adobe Digital Editions or FBReader – both free (see eBook Help).
- Tablet/Smartphone (Android; iOS): Before downloading, install the free app Adobe Digital Editions (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (not Kindle).
The file format ePUB works well for novels and non-fiction books – i.e., „flowing” text without complex layout. On an e-reader or smartphone, line and page breaks automatically adjust to fit the small displays.
This eBook uses Watermark-DRM, a „soft” copy protection. This means that there are no technical restrictions to prevent illegal distribution. However, there is a personalised watermark embedded in the eBook that can be used to identify the purchaser of the eBook in the event of misuse and to provide evidence for legal purposes.
For more information, see our eBook Help page.