Publicado el 31 de Diciembre de 2011 por Addison Wesley.
4 estrellas
(1 reseña)
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.
New in Edition 2:
We have introduced a new viewpoint, which we call the Context viewpoint. This describes the relationships, dependencies, and interactions between the system and its environment (the people, systems, and external entities with which it interacts). It extends, formalizes, and standardizes the relatively brief discussion of scope and context that used to be in Chapter 8.
We have expanded the discussion of different aspects of the role of architecture in Part …
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.
New in Edition 2:
We have introduced a new viewpoint, which we call the Context viewpoint. This describes the relationships, dependencies, and interactions between the system and its environment (the people, systems, and external entities with which it interacts). It extends, formalizes, and standardizes the relatively brief discussion of scope and context that used to be in Chapter 8.
We have expanded the discussion of different aspects of the role of architecture in Part II.
We have revised most of the viewpoint and perspective definitions, particularly the Functional and Concurrency views and the Performance and Scalability perspective.
We have revised and extended the Bibliography and the Further Reading sections in most chapters.
We have updated the book to align with the concepts and terminology in the new international architecture standard ISO 42010 (which derives from IEEE Standard 1471).
We have updated our UML modeling advice and examples to reflect the changes introduced in version 2 of UML.
I've used this book for several years while teaching software architecture to master students in computer science at TU Delft. The book is based on extensive experience from the authors working for large IT organizations. The book encodes years of experience in a systematic set of (UML-like) diagrams reflecting the basic premises of the book: Software systems are built to meet architectural properties desired by stakeholders, and are realized by means of viewpoints and crosscutting perspectives. The distance to the world of students is quite large, making it less suitable for teaching.
