Documenting Software Architectures: Views and Beyond und über 1,5 Millionen weitere Bücher verfügbar für Amazon Kindle. Erfahren Sie mehr
EUR 38,35
  • Statt: EUR 38,36
  • Sie sparen: EUR 0,01
  • Alle Preisangaben inkl. MwSt.
Nur noch 3 auf Lager (mehr ist unterwegs).
Verkauf und Versand durch Amazon.
Geschenkverpackung verfügbar.
Menge:1
Documenting Software Arch... ist in Ihrem Einkaufwagen hinzugefügt worden
Ihren Artikel jetzt
eintauschen und
EUR 16,00 Gutschein erhalten.
Möchten Sie verkaufen?
Zur Rückseite klappen Zur Vorderseite klappen
Anhören Wird wiedergegeben... Angehalten   Sie hören eine Probe der Audible-Audioausgabe.
Weitere Informationen
Alle 2 Bilder anzeigen

Documenting Software Architectures: Views and Beyond (SEI Series in Software Engineering) (Englisch) Gebundene Ausgabe – 5. Oktober 2010


Alle 2 Formate und Ausgaben anzeigen Andere Formate und Ausgaben ausblenden
Amazon-Preis Neu ab Gebraucht ab
Kindle Edition
"Bitte wiederholen"
Gebundene Ausgabe
"Bitte wiederholen"
EUR 38,35
EUR 38,35 EUR 58,05
56 neu ab EUR 38,35 6 gebraucht ab EUR 58,05

Hinweise und Aktionen

  • Beim Kauf von Produkten ab 40 EUR erhalten Sie eine E-Mail mit einem 10 EUR Gutscheincode, einlösbar auf ausgewählte Premium-Beauty-Produkte. Diese Aktion gilt nur für Produkte mit Verkauf und Versand durch Amazon.de. Für weitere Informationen zur Aktion bitte hier klicken.

  • Sparpaket: 3 Hörbücher für 33 EUR: Entdecken Sie unsere vielseitige Auswahl an reduzierten Hörbüchern und erhalten Sie 3 Hörbücher Ihrer Wahl für 33 EUR. Klicken Sie hier, um direkt zur Aktion zu gelangen.


Wird oft zusammen gekauft

Documenting Software Architectures: Views and Beyond (SEI Series in Software Engineering) + Software Architecture in Practice (SEI Series in Software Engineering) + Vorgehensmuster für Softwarearchitektur: Kombinierbare Praktiken in Zeiten von Agile und Lean
Preis für alle drei: EUR 110,79

Die ausgewählten Artikel zusammen kaufen
Jeder kann Kindle Bücher lesen — selbst ohne ein Kindle-Gerät — mit der KOSTENFREIEN Kindle App für Smartphones, Tablets und Computer.


Produktinformation


Mehr über die Autoren

Entdecken Sie Bücher, lesen Sie über Autoren und mehr

Produktbeschreibungen

Über den Autor und weitere Mitwirkende

Paul Clements is a Senior Member of the Technical Staff at the Carnegie Mellon Software Engineering Institute (SEI), where he has worked since 1994 leading or coleading projects in software product-line engineering and software architecture documentation and analysis. Besides this one, Clements is the coauthor of two other practitioner-oriented books about software architecture: Software Architecture in Practice (Addison-Wesley, 1998; Second Edition 2003) and Evaluating Software Architectures: Methods and Case Studies (Addison-Wesley, 2001). He also cowrote Software Product Lines: Practices and Patterns (Addison-Wesley, 2001) and was coauthor and editor of Constructing Superior Software (Sams, 1999). In addition, Clements has authored dozens of papers in software engineering, reflecting his longstanding interest in the design and specification of challenging software systems. In 2005 and 2006 he spent a year as a visiting faculty member at the Indian Institute of Technology in Mumbai. He received a Ph.D. in computer sciences from the University of Texas at Austin in 1994. He is a founding member of the IFIP Working Group on Software Architecture (WG2.10). Felix Bachmann is a Senior Member of the Technical Staff at the SEI, working in the Architecture Centric Engineering Initiative. He is coauthor of the Attribute-Driven Design Method, a contributor to and instructor for the ATAM Evaluator Training course, and a contributor to the book Software Architecture in Practice, Second Edition. Before joining the SEI, he was a software engineer at Robert Bosch GmbH in corporate research, where he worked with software development departments to address the issues of software engineering in small and large embedded systems. Len Bass is a Senior Member of the Technical Staff at the SEI. He has coauthored two award-winning books in software architecture as well as several other books and numerous papers in a wide variety of areas of computer science and software engineering. He has been a keynote speaker or a distinguished lecturer on six continents. He is currently working on applying the concepts of ultra-large-scale systems to the smart grid. He has been involved in the development of numerous different production or research software systems, ranging from operating systems to database management systems to automotive systems. He is a member of the IFIP Working Group on Software Architecture (WG2.10). David Garlan is a Professor of Computer Science and Director of Software Engineering Professional Programs in the School of Computer Science at Carnegie Mellon University (CMU). He received his Ph.D. from CMU in 1987 and worked as a software architect in industry between 1987 and 1990. His interests include software architecture, self-adaptive systems, formal methods, and cyber-physical systems. He is considered to be one of the founders of the field of software architecture and, in particular, formal representation and analysis of architectural designs. In 2005 he received a Stevens Award Citation for fundamental contributions to the development and understanding of software architecture as a discipline in software engineering. James Ivers is a Senior Member of the Technical Staff at the SEI, where he works in the areas of software architecture and program analysis. He received a Master of Software Engineering from CMU in 1996 and has worked for and with a variety of development organizations, from start-up to multinational corporations. He has written numerous papers, contributed to the development of an international standard for distributed simulations, and has recently been working in a public-private collaboration to draft security recommendations for the smart grid. Reed Little is a Senior Member of the Technical Staff at the SEI. He applies more than 35 years of experience in computer simulation, software architecture, software product lines, man-machine interface, artificial intelligence, and programming language design to various aspects of applied research and hands-on customer assistance for large (more than three million lines of code) software systems. Paulo Merson has more than 20 years of software development experience. He works for the SEI in the areas of software architecture, service-oriented architecture, and aspect-oriented software development. He is also a practicing software architect in industry. One of his assignments at the SEI is to teach a two-day course in "Documenting Software Architectures" for industry and government practitioners. His speaking experience also includes tutorials at various conferences, such as SD Best Practices, Dr. Dobb's Architecture & Design World, and JavaOne. Prior to joining the SEI, he was a Java EE consultant. Paulo holds a B.Sc. in Computer Science from University of Brasilia, and a Master of Software Engineering from CMU. Robert Nord is a Senior Member of the Technical Staff in the Research, Technology, and System Solutions Program at the SEI, where he works to develop and communicate effective methods and practices for software architecture. He is coauthor of the practitioner-oriented book Applied Software Architecture (Addison-Wesley, 2000) and lectures on architecture-centric approaches. He is a member of the IFIP Working Group on Software Architecture (WG2.10). Judith Stafford is a Senior Lecturer at Tufts University and a Visiting Scientist at the SEI. Before joining the faculty at Tufts University, she was a Senior Member of the Technical Staff at the SEI in the Product Lines Systems Program, working in the Software Architecture Technologies Initiative. She has authored several book chapters on the topic of software architecture analysis, software architecture support for software component composition, and software architecture documentation. Stafford has been an organizer and program committee member for several conferences and workshops, and a guest editor on several leading software engineering journal special issues. She received her Ph.D. and M.S. degrees in Computer Science from the University of Colorado at Boulder. She is a member of the IEEE Computer Society, ACM SIGSOFT and SIGPLAN, and the IFIP Working Group on Software Architecture (WG2.10).

In diesem Buch (Mehr dazu)
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Hier reinlesen und suchen:

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: 17 Rezensionen
14 von 15 Kunden fanden die folgende Rezension hilfreich
The Best Just got Better.... 25. Oktober 2010
Von T. Anderson - Veröffentlicht auf Amazon.com
Format: Gebundene Ausgabe Verifizierter 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.
2 von 2 Kunden fanden die folgende Rezension hilfreich
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!
1 von 1 Kunden fanden die folgende Rezension hilfreich
Providing Structure for the Messy World of Architecture 13. April 2012
Von Perpetual Dreamer - Veröffentlicht auf Amazon.com
Format: Gebundene Ausgabe Verifizierter Kauf
Some of us have been practicing software modeling since the early days of Rational Rose (about 20 years ago!) And still we find this business of describing a system's architecture to be vexing. Just give us some rules! Ah, but it's not so simple. Our job as architects and designers is not to just fill out a template. It's to wrap our brains around requirements, ponder solutions, innovate, and sort it all out for ourselves and others. This book feels like modeling 5.0 or something like that. It's an evolutionary next step in the art and craft of communicating software architectures. Paul Clements and team have done a good job of proposing a framework for exploring and communicating designs. It's kind of easy to remember (three views). Yet they recognize that this problem doesn't have a formulaic solution. I might complain that the book doesn't actually work through a complete example--rather, it is rich with tiny examples of each view and style. The comprehensive example is online. Based on personal experience, I might add that this approach needs the support of modern presentation techniques. Audiences--even highly technical ones--may not warm up to a purely views-based presentation. All in all, I highly recommend this book to all software practitioners.
3 von 4 Kunden fanden die folgende Rezension hilfreich
Continues to impress 30. Mai 2011
Von Bob Savage - Veröffentlicht auf Amazon.com
Format: Gebundene Ausgabe Verifizierter 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.
9 von 13 Kunden fanden die folgende Rezension hilfreich
What is software architecture vs software design? 4. November 2011
Von gyas - Veröffentlicht auf Amazon.com
Format: Gebundene Ausgabe
What is software architecture vs software design? Ugh, hate that a book about software architecture fails to answer this basic question, despite a rambling multi-page attempt. Here is the most succinct definition I've read: software architecture is the plan for realizing non-functional requirements, software design is the plan for realizing functional requirements; this definition should be included in the next version of this book.

If this book had a real-world example non-functional spec (please, no trivial web-book-store examples) and the resulting SAD, I'd rate it 4.5 stars.

Otherwise the book is ok, except for a few mislabeled UML drawings. If you read this book you should also read a book or two on systems engineering (INCOSE handbook?) where the methodology for documenting system architectures is well-defined and mature.
Waren diese Rezensionen hilfreich? Wir wollen von Ihnen hören.