| ||||||||||||||||||
![]() Trade In this Item for up to £19.25
Get an extra £5 when you trade in books worth £10 or more until June 30, 2012. Trade in Documenting Software Architectures: Views and Beyond (SEI Series in Software Engineering) for an Amazon.co.uk gift card of up to £19.25, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Product details
|
—From the Foreword by Grady Booch, IBM Fellow
Software architecture—the conceptual glue that holds every phase of a project together for its many stakeholders—is widely recognized as a critical element in modern software development. Practitioners have increasingly discovered that close attention to a software system’s architecture pays valuable dividends. Without an architecture that is appropriate for the problem being solved, a project will stumble along or, most likely, fail. Even with a superb architecture, if that architecture is not well understood or well communicated the project is unlikely to succeed.
Documenting Software Architectures, Second Edition, provides the most complete and current guidance, independent of language or notation, on how to capture an architecture in a commonly understandable form. Drawing on their extensive experience, the authors first help you decide what information to document, and then, with guidelines and examples (in various notations, including UML), show you how to express an architecture so that others can successfully build, use, and maintain a system from it. The book features rules for sound documentation, the goals and strategies of documentation, architectural views and styles, documentation for software interfaces and software behavior, and templates for capturing and organizing information to generate a coherent package. New and improved in this second edition:
—From the Foreword by Grady Booch, IBM Fellow
Software architecture—the conceptual glue that holds every phase of a project together for its many stakeholders—is widely recognized as a critical element in modern software development. Practitioners have increasingly discovered that close attention to a software system’s architecture pays valuable dividends. Without an architecture that is appropriate for the problem being solved, a project will stumble along or, most likely, fail. Even with a superb architecture, if that architecture is not well understood or well communicated the project is unlikely to succeed.
Documenting Software Architectures, Second Edition, provides the most complete and current guidance, independent of language or notation, on how to capture an architecture in a commonly understandable form. Drawing on their extensive experience, the authors first help you decide what information to document, and then, with guidelines and examples (in various notations, including UML), show you how to express an architecture so that others can successfully build, use, and maintain a system from it. The book features rules for sound documentation, the goals and strategies of documentation, architectural views and styles, documentation for software interfaces and software behavior, and templates for capturing and organizing information to generate a coherent package. New and improved in this second edition:
Suggested Tags from Similar Products(What's this?)Be the first one to add a relevant tag (keyword that's strongly related to this product)
|
I think (experienced) software architects working on complex projects will like this book. I don't think it is suitable for beginners.
BUT, it could have been so much better... (hence only 4 stars)
1. Needs more example models & diagrams, a picture is worth 1000 words.
2. It should be about modelling not documenting, but hey that IS the title of the book!
3. The final section that discusses the views proposed by RUP, siemens, ODP etc are clearly an afterthought as they don't really tell you much and are so 'standalone'.
4. Amazingly there is no discussion of frameworks.
5. The MDA paradigm isn't even touched upon - a major ommission IMHO.
Ultimately though it's the best book I've read on the subject, just left me with half the answer...
|