"This new edition is brighter, shinier, more complete, more pragmatic, more focused than the previous one, and I wouldn't have thought it possible to improve on the original. As the field of software architecture has grown over these past decades, there is much more to be said, much more that we know, and much more that we can reflect upon of what's worked and what hasn't-and the authors here do all that, and more." -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: * Coverage of architectural styles such as service-oriented architectures, multi-tier architectures, and data models * Guidance for documentation in an Agile development environment * Deeper treatment of documentation of rationale, reflecting best industrial practices * Improved templates, reflecting years of use and feedback, and more documentation layout options * A new, comprehensive example (available online), featuring documentation of a Web-based service-oriented system * Reference guides for three important architecture documentation languages: UML, AADL, and SySML
Documenting Software Architectures
und über 1,5 Millionen weitere Bücher verfügbar für Amazon Kindle. Erfahren Sie mehr
| |||||||||||||||
Kurzbeschreibung
Wird oft zusammen gekauft
Produktinformation
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
Ist der Verkauf dieses Produkts für Sie nicht akzeptabel? |
Produktbeschreibungen
Synopsis
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.
-- Dieser Text bezieht sich auf eine andere Ausgabe:
Gebundene Ausgabe
.
Buchrückseite
"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 -- Dieser Text bezieht sich auf eine andere Ausgabe: Gebundene Ausgabe .
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
In diesem Buch
(Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Kundenrezensionen
Es gibt noch keine Kundenrezensionen auf Amazon.de
5 Sterne
4 Sterne
3 Sterne
2 Sterne
1 Sterne
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com:
4.8 von 5 Sternen
12 Rezensionen
11 von 11 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen
The Best Just got Better....
25. Oktober 2010
Von T. Anderson
- Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe|Von Amazon bestätigter Kauf
This book is the bible of documenting software architectures. It is a mandatory read for all software architects. It should also be read by the various stakeholders who have invested in a software architect so they have some idea about what their investment should be accomplishing.
This version includes a lot of new content. It includes new architectural styles for SOA, database models, and multi-tier architectures.
The authors have expanded the epilogue which is the comparison of Views and Beyond to other documenting approaches. It now includes comparisons to ISO/IEC 42010 - ANSI/IEEE Std 1471-2000, the RUPs 4+1, Rozanski and Woods Viewpoint Set, agile projects, and DoDAF.
The book now includes 3 appendixes. One on UML, SysML, and AADL. Each is an overview of the language.
They have improved templates based on experience gained since the first version of the book.
The book's example is now on line. It documents a Web-based service-oriented system.
This book shows you how to communicate with your stakeholders and how to address quality attribute requirements like no other book out there. I am not saying it is the best book out there, I am saying it accomplishes what it tries to teach. It creates a view of a great method of documenting architecture. It then provides a cross reference with some other great methods of documenting software architecture in the epilogue I mentioned above.
It is a must read for any architect that takes there job serious. It will add a wealth of knowledge to your arsenal of tools.
This version includes a lot of new content. It includes new architectural styles for SOA, database models, and multi-tier architectures.
The authors have expanded the epilogue which is the comparison of Views and Beyond to other documenting approaches. It now includes comparisons to ISO/IEC 42010 - ANSI/IEEE Std 1471-2000, the RUPs 4+1, Rozanski and Woods Viewpoint Set, agile projects, and DoDAF.
The book now includes 3 appendixes. One on UML, SysML, and AADL. Each is an overview of the language.
They have improved templates based on experience gained since the first version of the book.
The book's example is now on line. It documents a Web-based service-oriented system.
This book shows you how to communicate with your stakeholders and how to address quality attribute requirements like no other book out there. I am not saying it is the best book out there, I am saying it accomplishes what it tries to teach. It creates a view of a great method of documenting architecture. It then provides a cross reference with some other great methods of documenting software architecture in the epilogue I mentioned above.
It is a must read for any architect that takes there job serious. It will add a wealth of knowledge to your arsenal of tools.
3 von 3 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen
Continues to impress
30. Mai 2011
Von Bob Savage
- Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe|Von Amazon bestätigter Kauf
This is one of those books about which it is difficult to say enough good things. I found the first edition very influential on my on thinking to say nothing of enlightening. Impressively, the authors have improved this second edition, for example moving the comprehensive sample documentation online, thus making room for more of the lucid and rational explanation of documentation practices that made the first edition so useful.
I usually include a discussion of who would benefit from a reading in my reviews. Anybody who thinks they might be producers or consumers of software architecture documentation owes it to themselves to get a copy of this book now. Others might think they have no need for this book, but still should read it. This includes Business Analysts, who, this book makes clear, are stakeholders of software architectures. BAs will also their thinking sharpened on how to develop useful documentation and use graphical notation in a precise and meaningful fashion.
This book is on my short list of classics of software engineering. It is a book I return to often. Reading this second edition, even after being fully familiar with the first, was still a richly satisfying experience. I cannot recommend this book enough.
I usually include a discussion of who would benefit from a reading in my reviews. Anybody who thinks they might be producers or consumers of software architecture documentation owes it to themselves to get a copy of this book now. Others might think they have no need for this book, but still should read it. This includes Business Analysts, who, this book makes clear, are stakeholders of software architectures. BAs will also their thinking sharpened on how to develop useful documentation and use graphical notation in a precise and meaningful fashion.
This book is on my short list of classics of software engineering. It is a book I return to often. Reading this second edition, even after being fully familiar with the first, was still a richly satisfying experience. I cannot recommend this book enough.
1 von 1 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen
Practical and understandable
7. Juli 2011
Von Randy Rice
- Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe
As a software tester, I rely heavily on system documentation. Unfortunately, documentation is often missing, obsolete, or never created in the first place.
Also, I have a great appreciation for software architects and the work they produce. As a former developer, I used to struggle with the best ways to express system architecture diagrams. After all, there are so many methods available to document systems - UML being a major one, but there are others.
When I started reading this book, I was struck by its practicality, beautiful simplicity, and integration between authors. Everything I read in this book is written in a clear and understandable way. The authors understand that different audiences will read this book, so they give graphical (of course) guidance in which chapters are most applicable to architects, stakeholders and novices.
This book covers the basics, such as module views and module styles, component and connector views, allocation views and styles. Part two of the book goes beyond the basics and gets into issues regarding levels of detail, deciding among alternatives, documenting interfaces and documenting behavior. Part three is devoted to building the architecture documentation.
There are appendices devoted to UML, SysML and AADL to show how architectural documentation is shown in each of these.
It would be tempting to say that this book is needed for new technologies, such as SOA and the cloud, which is true, but too narrow. Actually, this book can be applied to any technology or approach - traditional, agile, iterative, or anything. That's because the one thing people ask for and struggle with is documentation. This is especially true for architectural documentation.
Read this book and apply the things in it and you will stand out on projects - in a good way. And, of course, that's a good thing!
Also, I have a great appreciation for software architects and the work they produce. As a former developer, I used to struggle with the best ways to express system architecture diagrams. After all, there are so many methods available to document systems - UML being a major one, but there are others.
When I started reading this book, I was struck by its practicality, beautiful simplicity, and integration between authors. Everything I read in this book is written in a clear and understandable way. The authors understand that different audiences will read this book, so they give graphical (of course) guidance in which chapters are most applicable to architects, stakeholders and novices.
This book covers the basics, such as module views and module styles, component and connector views, allocation views and styles. Part two of the book goes beyond the basics and gets into issues regarding levels of detail, deciding among alternatives, documenting interfaces and documenting behavior. Part three is devoted to building the architecture documentation.
There are appendices devoted to UML, SysML and AADL to show how architectural documentation is shown in each of these.
It would be tempting to say that this book is needed for new technologies, such as SOA and the cloud, which is true, but too narrow. Actually, this book can be applied to any technology or approach - traditional, agile, iterative, or anything. That's because the one thing people ask for and struggle with is documentation. This is especially true for architectural documentation.
Read this book and apply the things in it and you will stand out on projects - in a good way. And, of course, that's a good thing!
›
Gehen Sie zu Amazon.com, um alle 12 Rezensionen zu sehen
4.8 von 5 Sternen
Waren diese Rezensionen hilfreich?
Wir wollen von Ihnen hören.
Kunden diskutieren
|
Das Forum zu diesem Produkt
Fragen stellen, Meinungen austauschen, Einblicke gewinnen Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
|
Ähnliche Foren
|
||||||||||||||||||||||||||||||||||
Lieblingslisten
|
|
Ähnliche Artikel finden
Ihr Kommentar
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
|
