Jednym z moich niedawnych nabytków jest bardzo wartościowa książka, jednak nie jest to podręcznik analizy i modelowania, a opis wieloletnich doświadczeń autorów w tworzeniu i dokumentowaniu architektury oprogramowania.
The authors have structured this edition around the concept of architecture influence cycles. Each cycle shows how architecture influences, and is influenced by, a particular context in which architecture plays a critical role. Contexts include technical environment, the life cycle of a project, an organization?s business profile, and the architect?s professional practices. The authors also have greatly expanded their treatment of quality attributes, which remain central to their architecture philosophy?with an entire chapter devoted to each attribute?and broadened their treatment of architectural patterns.
If you design, develop, or manage large software systems (or plan to do so), you will find this book to be a valuable resource for getting up to speed on the state of the art. (Źródło: Software Architecture in Practice (3rd Edition) (SEI Series in Software Engineering): Len Bass, Paul Clements, Rick Kazman: 9780321815736: Amazon.com: Books)
Autorzy opisują wszystkie aspekty architektury, od jakości, przez wydajność, cykl życia do jej biznesowych aspektów. Książka moim zdaniem jest bardzo dobrym źródłem wiedzy dla kierowników projektów, dla analityków także, ale raczej z perspektywy tego co projekt i dokumentacja architektury powinny zawierać.
Software Architecture in Practice (3rd Edition)
October 5, 2012
Len Bass (Author), Paul Clements (Author), Rick Kazman (Author)
ISBN-13: 978-0321815736 ISBN-10: 0321815734 Edition: 3rd
