Software architects could be the main category targeted by the book, but both software developers and software development project managers could get their share of knowledge that applies to their daily work. I will recommend this book to every software developers. In addition, the book provides very interesting content of how to consider a software architecture. I think that this objective is broadly achieved. This book states that its goal is to answer the following question: “How do you document an architecture so that others can successfully use it, maintain it, and build a system from it?”. Three appendixes present some techniques that can be used to describe the architecture (UML, SysML and AADL) My favorite content is a section that deals with the ontology of architecture decisions. A second part discusses in a more detailed fashion the process of documenting architecture. “Documenting Software Architectures” starts by explaining the concepts of architecture views and styles. There are also many pointers and quotes in the margins that allow you or your brain to navigate further from the current content. The book provides a reading guide for the different categories of readers (architect, novice and stakeholders). It is both easy to read and well-structured. The first thing that I liked about this book on documenting software architectures is that the authors know how to write.
0 Comments
Leave a Reply. |