- Hardcover: 560 pages
- Publisher: Addison Wesley; 1 edition (26 Sep 2002)
- Language English
- ISBN-10: 0201703726
- ISBN-13: 978-0201703726
- Product Dimensions: 23.4 x 15.8 x 3.2 cm
- Average Customer Review: 3.3 out of 5 stars See all reviews (3 customer reviews)
- Amazon Bestsellers Rank: 732,842 in Books (See Top 100 in Books)
- See Complete Table of Contents
Documenting Software Architectures
and over one million other books are available for Amazon Kindle .
Learn more
| ||||||||||||||||||||
Did you know you can trade in your old books for an Amazon.co.uk Gift Card to spend on the things you want? Plus, get an extra £5 Gift Certificate when you trade in books worth £10 or more before June 30, 2012. Visit the Books Trade-In Store for more details. |
|
There is a newer edition of this item:
|
Product details |
More About the Authors
Discover books, learn about writers, and more.
Product Description
Product Description
Architecture is crucial to the success of any large software system -- but even a superb architecture will fail if it isn't communicated well. Now, there's a language- and notation-independent guide to capturing architecture so it can be used successfully by every analyst, software designer, and developer. The authors review the diverse goals and uses of software architecture documentation, providing documentation strategies for several common scenarios. They identify the basic unit of software architecture documentation: the viewtype, which specifies the type of information to be provided in an architectural view. For each viewtype -- Modules, Component-and-Connectors, and Allocation -- they offer detailed guidance on documenting what really matters. Next, they demonstrate how to package architecture documentation in coherent, usable form: augmenting architectural views with documentation of interfaces and behavior; accounting for architectural variability and dynamic systems; and more.
From the Back Cover
"This book is of immense value. It should save you months of trials and errors, lots of undeserved hassle, and many costly mistakes that could potentially jeopardize the whole endeavor. It will become an important reference on the shelf of the software architect."
—From the Foreword by Philippe Kruchten, Rational Software Canada
"There is probably no better set of authors to write this book. The material is readable. It uses humor effectively. It is nicely introspective when appropriate, and yet in the end it is forthright and decisive....This is a tour de force on the subject of architectural documentation."
—Robert Glass, Editor-in-Chief, Journal of Systems and Software and Editor/Publisher, The Software Practitioner
For all but the most trivial software systems, you must pay close attention to the architecture—the conceptual glue that holds every phase of a project together for its many stakeholders. Without an architecture that is appropriate for the problem being solved, the project will stumble along or, most likely, fail. Even with a superb architecture, if that architecture is not well understood or well communicated—in other words, well documented—the project cannot be considered a complete success.
Although architecture is now widely recognized as a critical element in software development, there has been little guidance independent of language or notation on how to capture it. Based on the authors' extensive experience, Documenting Software Architectures helps you decide what information to document, and then, with guidelines and examples (in various notations, including UML), shows you how to express an architecture in a form that everyone can understand. If you go to the trouble of creating a strong architecture, you must also be prepared to describe it thoroughly and clearly, and to organize it so that others can quickly find the information they need.
Essential topics for practitioners include:
- Seven rules for sound documentation
- The uses of software architecture documentation, including goals and strategies
- Architectural views and styles, with general introductions and specific examples
- Documenting software interfaces and software behavior
- Templates for capturing and organizing information to generate a coherent package
0201703726B08222002
Inside This Book
(Learn More)
Browse and search another edition of this book.
Browse and search another edition of this book.
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
What Other Items Do Customers Buy After Viewing This Item?
Customer Reviews
Most Helpful Customer Reviews
11 of 12 people found the following review helpful
Format:Hardcover
The book is written primarily for software architects and technical writers (with respect to software architecture). And for that, I like it. The book provides great insight on documenting software architectures and best practices like the "7 rules for sound documentation". I found it especially good on using multiple views and how to write readable and understandable documentation.
I think (experienced) software architects working on complex projects will like this book. I don't think it is suitable for beginners.
7 of 8 people found the following review helpful
Format:Hardcover
Don't get me wrong the book is good, the discussion of numerous views, styles is great and it provokes a lot of structured thinking, it's a book I would recommend.
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...
0 of 4 people found the following review helpful
Format:Hardcover
I didn't find the book very useful...or enjoyable to read. If you are new to architecture you may want to read something with a broader scope. If you are experienced in the field you are probably already familiar with the views and techniques presented.
Would you like to see more reviews about this item?
Were these reviews helpful?
Let us know
Listmania!
Look for similar items by category
- Books > Computing & Internet > Computer Science > Architecture & Microprocessors > Architecture & Logic
- Books > Computing & Internet > Digital Lifestyle > Online Shopping > Amazon
- Books > Computing & Internet > Programming > Software Design, Testing & Engineering > Software Architecture
- Books > Computing & Internet > Programming > Software Design, Testing & Engineering > Software Engineering
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
