Documenting Software Architectures und über 1 Million weitere Bücher verfügbar für Amazon Kindle . Erfahren Sie mehr


oder
Loggen Sie sich ein, um 1-Click® einzuschalten.
oder
Mit kostenloser Probeteilnahme bei Amazon Prime. Melden Sie sich während des Bestellvorgangs an. Erfahren Sie mehr
Alle Angebote
Möchten Sie verkaufen? Hier verkaufen
Documenting Software Architectures: Views and Beyond (SEI Series in Software Engineering)
 
 
Beginnen Sie mit dem Lesen von Documenting Software Architectures auf Ihrem Kindle in weniger als einer Minute.

Sie haben keinen Kindle? Hier kaufen oder eine gratis Kindle Lese-App herunterladen.

Documenting Software Architectures: Views and Beyond (SEI Series in Software Engineering) [Englisch] [Gebundene Ausgabe]

Paul Clements , Felix Bachmann , Len Bass , David Garlan , James Ivers , Reed Little , Paulo Merson , Robert L. Nord
4.3 von 5 Sternen  Alle Rezensionen anzeigen (3 Kundenrezensionen)
Preis: EUR 43,95 kostenlose Lieferung. Siehe Details.
  Alle Preisangaben inkl. MwSt.
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Auf Lager.
Verkauf und Versand durch Amazon.de. Geschenkverpackung verfügbar.
Nur noch 5 Stück auf Lager - jetzt bestellen.
Lieferung bis Mittwoch, 30. Mai: Wählen Sie an der Kasse Morning-Express. Siehe Details.

Weitere Ausgaben

Amazon-Preis Neu ab Gebraucht ab
Kindle Edition EUR 31,63  
Gebundene Ausgabe EUR 43,95  

Wird oft zusammen gekauft

Documenting Software Architectures: Views and Beyond (SEI Series in Software Engineering) + Software Architecture in Practice (SEI Series in Software Engineering) + Effektive Softwarearchitekturen: Ein praktischer Leitfaden
Preis für alle drei: EUR 128,80

Verfügbarkeit und Versanddetails anzeigen

Die ausgewählten Artikel zusammen kaufen


Produktinformation

  • Gebundene Ausgabe: 608 Seiten
  • Verlag: Addison Wesley; Auflage: 2nd revised edition. (5. Oktober 2010)
  • Sprache: Englisch
  • ISBN-10: 0321552687
  • ISBN-13: 978-0321552686
  • Größe und/oder Gewicht: 23,6 x 16 x 3,6 cm
  • Durchschnittliche Kundenbewertung: 4.3 von 5 Sternen  Alle Rezensionen anzeigen (3 Kundenrezensionen)
  • Amazon Bestseller-Rang: Nr. 51.360 in Englische Bücher (Siehe Top 100 in Englische Bücher)
  • Komplettes Inhaltsverzeichnis ansehen

Mehr über die Autoren

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

Produktbeschreibungen

Kurzbeschreibung

"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

Über den Autor

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).

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
Hier reinlesen und suchen:

Vorgeschlagene Tags zu ähnlichen Produkten

 (Was ist das?)
Setzen Sie den ersten relevanten Tag hinzu (ein Schlüsselwort, das mit diesem Produkt in engem Zusammenhang steht).
 

 

Kundenrezensionen

4 Sterne
0
2 Sterne
0
1 Sterne
0
Die hilfreichsten Kundenrezensionen
5 von 5 Kunden fanden die folgende Rezension hilfreich
Von Bücherkeule TOP 1000 REZENSENT
Format:Gebundene Ausgabe
Warning up front: This book is not about teaching hands-on, direct-to-use techniques for documenting software architectures. It is a lengthy, sometimes academically long-winding discussion about what a good documenation is and what techniques might be employed. It is a book to make the reader think, it is not a shop from which you can lift pracical recipes without reading the small print first. But the book does fulfill its promise: It makes you think about the problem. Pretty hard, actually. So read on if this is what you want.

Very few books on software architecture tackle the difficult problem of how a software architecture should be presented. This is a surprising omission given the commonly accepted dictum that architecture is, to a large extent, about communication. The omission may indicate that despite attempts at formalizing software specification (e.g UML, BPMN or various attempts at specifiying templates for architectural documents) no single technique of describing an architecture is sufficient in practice. From my own experience, I think this is not really surprising. Unlike specifications for physical machinery, software is prone to demand a plethora of different views. These range from the creation of the contextual language for a specific software (e.g. the formalisation of measurement in medicine as first step towards building a diagnostic system) over the various clasical views on an architecture all the way to a business perspective whithout which no budget may be available to the project. What makes software architecture documents particularly difficult is the interrelation between various views and the importance of dynamic aspects (which are among the more difficult aspects to capture in documentation). But to my mind, one of the hardest challenges of all, and usually mentioned at best in passing, is the problem of creating the right sort of contextual language up front.

The present book is a laudable attempt at discussing various methods of formally describing a software architecture. That the requiste material is all there can be glimpsed from the table of contents. I wish to make the following remarks: The authors make no attempt at finding a general formal solution to the title-problem of documenting a software architecture. Instead, they discuss the standard persepctives but remain aware throughout that there is no single solution. They take the reader through the various persepctives that need to be serviced by an architect. The authors challange their readers to think further by providing numerous exercises which help show the diversity inherent in the discussion. They do not limit themselves to one technique of documentation but, through their own example, make it plain that documenting an architecture requires different tools and, above all!, a sure command of language. It is this latter distinguishing feature, which is not explicitly mentioned in the book but implicit in the author's own way of presenting their thinking, that should be one of the main conclusions of the book. However, and this is where I have not been quite so happy, they stop short of showing how formal representations tie in with the way we first create the language in which we talk about the problem to be cast in software.

The book is not a book of recipes. It is a book that gets you thinking about the complex problem of writing up an architecture. The focus remains on documenting technical architectures and only implicity touches on the larger problem of how an architecture is, in writing, related to the problem domain it is intended for. I find it a useful restriction that templates for use in projects are not provided - these tend to limit inexperienced architects to given perspectives and in practice may lead you to omitting what may be particular and specific about your architecture. An excellent push in the right direction. Be pushed and then push on.
War diese Rezension für Sie hilfreich?
11 von 15 Kunden fanden die folgende Rezension hilfreich
Von "margull"
Format:Gebundene Ausgabe
Eine gute SW-Architekturdokumentation umfasst verschiedene Aspekte, von der logischen Struktur bis hin zu Konfigurations- und Hardware-spezifischen Sichten. In dem Buch "Documenting Software Architectures" beschreiben die Autoren verschiedene Sichten ("Views"), die sie in 3 Gruppen einteilen: Module Views, Component&Connector Views, und Allocation Views. Bei Bedarf können weitere Views definiert werden, z.B. in spezielle Domänen oder innerhalb von Firmen.
Ihr systematischer Ansatz erlaubt es, alle relevanten Aspekte zu beschreiben. Im Buch werden Vergleiche z.B. zu IEEE 1471 und UML gezogen, wobei sie detailiert Möglichkeiten und Einschränkungen von UML 1.x im Rahmen von Architekturdokumentationen aufzeigen. UML2.0, das besser zur SW-Architektur-Dokumentation geeignet ist, wird nicht behandelt.
War diese Rezension für Sie hilfreich?
7 von 10 Kunden fanden die folgende Rezension hilfreich
Format:Gebundene Ausgabe|Von Amazon bestätigter Kauf
Das momentan immer noch einzige Buch zum Thema "Architekturdokumentation" - mit vielen hilfreichen Tipps für gute Dokumentation. Clements motiviert das (wichtige!) Thema "Architektur aus unterschiedlichen Sichten" sehr gut und ausführlich.

Aber: In der Praxis möchte ich NICHT zuerst mal über die geeigneten Viewpoints und Perspectives forschen, sondern meine konkrete Architektur dokumentieren. Clements versäumt es, mir DAFÜR konkrete Hilfestellung zu geben, leider! Ich möchte auch nicht jedes Mal wieder über mögliche Notationen und Strukturen diskutieren - auch dafür gibt Clements nur sehr ausweichend Hilfestellung...

Den Beispielen merkt man den akademisch/militärischen Hintergrund an - ich fand sie nicht besonders hilfreich. Clements hätte besser daran getan, "einfachere" aber aussagekräftigere Beispiele zu verwenden.

Fazit: Wer sich mit "methodischer Dokumentation von IT-Architekturen" beschäftigt, sollte dieses Buch lesen. Wer allerdings für konkrete Aufgeben direkt anwendbare Hilfe sucht, dem hilft das Buch nicht (dafür gibt es aber frei verfügbare Doku-Templates inklusive Erläuterungen als Abhilfe!)

Wegen der Praxisferne gibt's nur drei Sterne.

Alternative Literaturempfehlung: Dokumentation ist in den Büchern über Software-Architektur ein ungeliebtes Thema - meist wird es ignoriert...
War diese Rezension für Sie hilfreich?
Kundenrezensionen suchen
Nur in den Rezensionen zu diesem Produkt suchen

Kunden diskutieren

Das Forum zu diesem Produkt
Diskussion Antworten Jüngster Beitrag
Noch keine Diskussionen

Fragen stellen, Meinungen austauschen, Einblicke gewinnen
Neue Diskussion starten
Thema:
Erster Beitrag:
Eingabe des Log-ins
 


Aktive Diskussionen in ähnlichen Foren
Kundendiskussionen durchsuchen
Alle Amazon-Diskussionen durchsuchen
   
Ähnliche Foren


Lieblingslisten


Ähnliche Artikel finden


Anhand des Sachgebietes nach ähnlichen Produkten suchen:


Ihr Kommentar


Datenschutzerklärung von Amazon.de Versandbedingungen von Amazon.de Umtausch- & Rücknahme bei Amazon.de