newseasonhw2015 Hier klicken Jetzt Mitglied werden lagercrantz Cloud Drive Photos Professionelle Fotografie2 Learn More blogger UrlaubundReise Shop Kindle Shop Kindle Autorip SummerSale
Software Architecture in Practice (2nd Edition) und über 1,5 Millionen weitere Bücher verfügbar für Amazon Kindle. Erfahren Sie mehr
Gebraucht kaufen
EUR 5,77
+ EUR 3,00 Versandkosten
Gebraucht: Sehr gut | Details
Verkauft von betterworldbooks__
Zustand: Gebraucht: Sehr gut
Kommentar: Frueheres Bibliotheksbuch. Sehr guter Zustand fuer ein gebrauchtes Buch, minimale Abnutzungserscheinungen. 100%ige Kostenrueckerstattung garantiert Ueber eine Million zufriedene Kunden! Ihr Einkauf unterstuetzt world literacy!
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
Dieses Bild anzeigen

Software Architecture in Practice (SEI Series in Software Engineering) (Englisch) Gebundene Ausgabe – 9. April 2003

3 Kundenrezensionen

Alle Formate und Ausgaben anzeigen Andere Formate und Ausgaben ausblenden
Amazon-Preis Neu ab Gebraucht ab
Kindle Edition
"Bitte wiederholen"
Gebundene Ausgabe
"Bitte wiederholen"
EUR 14,90 EUR 2,78
4 neu ab EUR 14,90 9 gebraucht ab EUR 2,78

Dieses Buch gibt es in einer neuen Auflage:

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



Produktinformation

  • Gebundene Ausgabe: 512 Seiten
  • Verlag: Addison Wesley; Auflage: 2. A. 2003. (9. April 2003)
  • Sprache: Englisch
  • ISBN-10: 0321154959
  • ISBN-13: 978-0321154958
  • Größe und/oder Gewicht: 16,5 x 3,4 x 24,1 cm
  • Durchschnittliche Kundenbewertung: 3.7 von 5 Sternen  Alle Rezensionen anzeigen (3 Kundenrezensionen)
  • Amazon Bestseller-Rang: Nr. 145.795 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
  • Komplettes Inhaltsverzeichnis ansehen

Mehr über die Autoren

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

Produktbeschreibungen

Synopsis

The first edition of this book established itself as the leading book on this topic of growing importance. It was critically acclaimed (recipient of the Software Development Magazine Productivity Award) and widely embraced by customers. The second edition maintains the goals of the first edition: to define and explain software architecture, and to demonstrate, through real-world case studies, its importance for software system design. The added goals of the second edition are to bring the content up-to-date with significant developments in the understanding and practice of software architecture in the past five years. These developments include advances in architecture analysis, design, reconstruction, and documentation--advances in which the authors, through their work at the Software Engineering Institute (SEI), have played a direct and prominent role.

Über den Autor und weitere Mitwirkende

Len Bass is a senior member of the technical staff at the Software Engineering Institute (SEI). He has written or edited five books and numerous papers on software engineering and other topics. He has extensive experience in architecting real-world development projects. Paul Clements is a senior member of the technical staff at the SEI, where he works on software architecture and product line engineering. He is the author of five books and more than three dozen papers on these and other topics. Rick Kazman is a senior member of the technical staff at the SEI. He is also an Associate Professor at the University of Hawaii. He is the author of two books, editor of two more, and has written more than seventy papers on software engineering and related topics.

Alle Produktbeschreibungen

Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?

Kundenrezensionen

3.7 von 5 Sternen
5 Sterne
0
4 Sterne
2
3 Sterne
1
2 Sterne
0
1 Sterne
0
Alle 3 Kundenrezensionen anzeigen
Sagen Sie Ihre Meinung zu diesem Artikel

Die hilfreichsten Kundenrezensionen

8 von 8 Kunden fanden die folgende Rezension hilfreich Von Sicheneder am 28. Oktober 2003
Format: Gebundene Ausgabe Verifizierter Kauf
Das Buch habe ich mir gekauft, da während meiner Arbeit immer wieder folgende Fragestellungen aufgetreten sind:
Wie sieht gute Architektur aus?
Wie fügen sich Altbestände von Software in die Architekturbeschreibung ein?
Wie gehe ich vor, wenn nur noch Software aber keine Beschreibung der zugrunde liegenden Architektur vorhanden ist?
Wie soll Softwarearchitektur dokumentiert werden?
All diese Fragen (und noch mehr) werden beantwortet. Das Buch bietet keine Patentlösungen an beschreibt aber strukturierte Vorgehensweisen und zeigt (meist unausgesprochene) Anforderungen an Softwarearchitekturen auf.
Der Schreibstil ist recht trocken, so daß man sich ordentlich durchbeißen muß, will man es ganz lesen. Das Buch ist jedoch so aufgebaut, daß man auch einzelne Kapitel unabhängig lesen kann. Dennoch ist es keine leichte Kost und liest sich auch nicht mal so nebenbei.
Die angeführten Beispiele sind nicht unbedingt alle intuitiv verständlich aber sie zeigen, daß man auch große Projekte, bewaffnet nur mit guter Architektur und strukturiertem Vorgehen, ohne die modernen Hilfsmittel von heute (Entwicklungsumgebungen, CaseTools etc.), bewältigen kann. Sie belegen eindruckvoll, daß alle technischen Hilfsmittel Selbstdisziplin, Erfahrung und Struktur nicht ersetzen können (bestenfalls unterstützen).
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
5 von 7 Kunden fanden die folgende Rezension hilfreich Von Dr. Gernot Starke am 27. Oktober 2006
Format: Gebundene Ausgabe Verifizierter Kauf
The SEI'guys give a broad and excellent overview of software architecture - no doubt. Good read, nice samples.

As a longstanding software practicioner I nevertheless asked myself: What's the advice? What shall I do in practice? This book does imho not provide sufficient answers, it lacks advice and "best practices".

The best part imho is the coverage of scenarios for nonfunctional requiements: The authors offer some strategies or tactics to achieve attributes like performance or availability in software architectures. Their ideas are systematic and really useful.

I did not like the parts on architecture documentation: The approach (which is detailed in Paul Clements' book on "Documenting Software Architectures") is way beyond practicability - much to "meta-level", even the examples are not really understandable. I seriously doubt that their documentation approach would fit any budget-driven commercial software project - it might work in unlimited-funds-available situations (which I never had the chance to meet in practice...).

Summary: A must-have-book for serious architects, but do not expect too much "practical" advice - use it as foundation or background material.
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen
Von Nix Sam am 21. Januar 2013
Format: Gebundene Ausgabe Verifizierter Kauf
The authors present a broad and comprehensive overview of software architecture, still book is very basic in terms of standardization of architecture.

Case-studies do not contain business architecture, even the basic BPM are not available. The corresponding information and technology architecture are either not availbale or not arranged in sequential and structured way.

Its a architecture book for foundation and reference but do not serve the purpose of helping the professionals to achieve Enterprise IT Architecture.

It would be great if this book acts as a tool to lead to enterprise architecture complaint to open standards framework.
Kommentar War diese Rezension für Sie hilfreich? Ja Nein Feedback senden...
Vielen Dank für Ihr Feedback. Wenn diese Rezension unangemessen ist, informieren Sie uns bitte darüber.
Wir konnten Ihre Stimmabgabe leider nicht speichern. Bitte erneut versuchen

Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)

Amazon.com: 18 Rezensionen
34 von 40 Kunden fanden die folgende Rezension hilfreich
A Bible for Software Architects 25. November 2003
Von Amazon Customer - Veröffentlicht auf Amazon.com
Format: Gebundene Ausgabe
Being a Software Architect, I can certainly appreciate the work that the authors of this book (L. Bass, P. Clements, R Kazman) have put into this book. Software Architecture in Practice is probably the best book that I have read on the theory and practice of architecture design and software engineering. There is no fair way for me to review this book as it is PACKED with useful information from beginning to the very end. It has a combination of high-level architectural concepts tailored with best software engineering practices. It is not a complete book on software engineering, but it wasn't meant to be - it's meant to cover a very specific topic in software engineering and it does so extremely well. It is a text in which the concepts architecting software applications, evaluating architectures thru various methods, and case studies of major leaps in software architecture have been very well described; depicted and well evaluated. The book is written from an architect's point of view, and it shows how an architect or a group of architects can make or break an organization, and what they need to do in order to be successful. The authors of this book explain why simply architecting something is not good enough and lots of work needs to be done before and after the architectural phase to ensure the quality and the success of the project. This aspect of the book is simply priceless.
The author start by describing software architecture as:
"The Software Architecture of a program or computing system is the structure or structures of the system, which compromise software elements, the externally visible properties of those elements, and the relationships between them."
Throughout the book, the author used this definition to describe various aspects of architecture. One of the methods/techniques that the author uses is called the Architecture Business Cycle (ABC). ABC is method of realizing the "things" that influence the architect and in-turn the architecture - known as the circle of influences. This concept, ABC, is used for all the case studies mentioned in this book:

· A case study on a system that have extreme safety requirements - the Air traffic control.
· A case study on a system with high level of distribution of its subsystems - A flight simulator
· A case study in which it was essential for the organization to be able to share documents instantaneously.
· A case study on an organization where one architecture lead to a product line of applications
· A case study on the need to standardization of architectural approaches across organizations and the community - J2EE and the EJB.
For each case study, the authors depict its ABC and give the reader the reason, business reason, that this project got started to begin with. The reader then walks thru a series of decision-making steps that led to the architecture that was finally chosen. The drivers of the project, the business reason, the architect[s], and the organization are all linked and the authors go into a GREAT DETAIL on how this link can influence the final design.
Architecture Tradeoff Analysis Method or ATAM is a new topic that is added to the second edition of the book. ATAM is a structured method of evaluating architectures.
"It results in a list of risks that the architecture will not meet its business goals"
The authors start by describing the roles and responsibilities of people involved in ATAM, and the output artifacts that ATAM will produce when completed:
· A Concise presentation of the Architecture
· Articulation of the business goals
· Quality requirements in terms of collection of scenarios
· Mapping of architectural decisions to quality requirements
· A set of identified sensitivity and tradeoff points
· A set of risks and non-risks
· A set of risk themes.
The process of ATAM is depicted next in which there are a total of 4 phases:
1) Partnership and preparation: the key project decision makers informally meet to work out the details of the ATAM process.
2) Evaluation phase - the long evaluation process of the architecture with the same project decision makers as in previous phase
3) Evaluation phase, continued - this time the stakeholders are present
4) Follow up - the stakeholders and the evaluation team meets again to follow up.
The process is described very well and examples forms are shown in the book that can be used for your evaluation process. The great thing about this chapter and how it's written is the way that the ATAM process is presented. It is almost like a checklist that the architects need to follow. Very easy to read and follow. The inputs of every phase are clearly identified, and the description of the output is depicted rather clearly. The chapter ends with yet another case study that shows the "theory" just presented. The authors close the chapters by having the following comments about this book:
· ATAM is not an evaluation of Requirements, but only the architecture
· ATAM is not a code evaluation
· ATAM does not actually involved system testing
· ATAM is not a practice instrument, but identifies possible areas of risk within the architecture.
The ATAM is followed by another very well written topic on CBAM (Cost Benefit Analysis Method). This chapter is also new in this edition, but I will leave the details of this chapter for the reader. I like the ATAM method more than the CBAM, because it seems simpler to me.
All and all, the authors in this book did a fantastic job in writing this book. This book is packed with useful information for architects, project leads, and even technical managers.
15 von 17 Kunden fanden die folgende Rezension hilfreich
Good software architecture book 7. Juni 2003
Von Erik Gfesser - Veröffentlicht auf Amazon.com
Format: Gebundene Ausgabe
My recent software engineering graduate course on software architecture relied mainly on this SEI text, along with several of the many SEI white papers posted on the SEI site, and such texts as Buschmann's Pattern Oriented Software Architecture (POSA) and Stelting/Maassen's Applied Java Patterns. Since the second edition of the text was available just two weeks after the start of the course, I decided not to purchase the first edition, and instead purchased the second edition. However, having used both editions for the course, I must say that the second edition is superior to the first even when only taking the architectural view notation into account (it uses UML rather than a cryptic, proprietary notation used in the first edition, although at this high of a level in modeling, UML sometimes disappoints as well). The addition of content from some SEI white papers to the text is also a benefit of the second edition. The text, regardless of the edition, is well written and very understandable.
8 von 9 Kunden fanden die folgende Rezension hilfreich
Soon to appear in an undergraduate software course... 21. Juli 2003
Von Kris L. Holt - Veröffentlicht auf Amazon.com
Format: Gebundene Ausgabe Verifizierter Kauf
The second edition of the book makes a good journeyman's guidebook, which the first edition didn't since software architecture was still a mystique. The second edition, which has been heavily revamped, makes it clear that software architecture is a mature discipline.
I used the first edition, along with SEI technical papers in a graduate-level software architecture introductory course. After reading the first edition, I still wasn't sure what a software architect should do. The second edition makes it clear. I think a lot of the technical papers that I read are now chapters in the book. Some new chapters are simply great: Understanding Quality Attributes, Achieving Qualities, Designing the Architecture, Documenting Software Architectures, the ATAM, and the CBAM.
I really liked the replacement of ADL with UML, the de facto standard, with all of its warts and blemishes.
For criticism, this book was history as soon as it hit the presses. You'd still need to read SEI technical papers to be current. One of the chapters discusses the performance problems with remote entity beans and makes no reference to EJB 2.0 spec local entity beans with no performance hit on every cross-bean call. Likewise, the final chapter on "The Future" wasn't so bold as to prognosticate on OMG's current work on MDA, but they may be alluding to it with "Moving from architecture to code."
Still more fun to read than a harlequin romance novel and readable in four days.
3 von 3 Kunden fanden die folgende Rezension hilfreich
Good Foundation Book 19. Mai 2008
Von Thomas Sprimont - Veröffentlicht auf Amazon.com
Format: Gebundene Ausgabe Verifizierter Kauf
This is a solid work on SEI's ADD methodology. The authors fully document the ADD methodology in terms of incorporating this into your practice. Clear text, diagrams, and illustrations depict how you bridge the gap between theory and practice.

If you're looking to use, or enhance, how to leverage your use architecture, I recommend this book. ADD is a method that values the business intent of the software, and constructs a method that delivers value to the customer.

There are some weak chapters, which prevent me from giving a 5-star rating. For example, Chapter 10 addresses reverse engineering an architecture. The focus was on a point exercise that is not useful in either theory or practice. Other case studies in the book (there are a few) were not helpful as they did not have the keys to turn the theory into practice. For example Chapter 16 addressed a J2EE/EJB study; however it was very high-level and omitted important details to be used in practice. However, the case study of an avionics system (Chapter 3) was good; it provided insight in how to apply theoretical concepts.

I recommend this book for those organizations looking for a solid value-add approach to improving your architectures both technically, and in customer value.
1 von 1 Kunden fanden die folgende Rezension hilfreich
Excellent book on the meaning of software architecture 3. Juli 2011
Von mobiusklien - Veröffentlicht auf Amazon.com
Format: Taschenbuch
In the beginning part of this book, the authors make a compelling case that software architecture is required for success. They also make it clear that there is not ONE GOOD software architecture, that in fact is based upon requirements. And that key insight is the most important fulcrum of the book. Every other incredible nugget of common sense stems from this core principle of requirements and qualities.
The tools and techniques in this book are superb ground work for designing better systems. The case studies are deep and illustrate the concepts incredibly well. This is a must have for every architect, or aspiring architect.
the authors are relevant and real.
Waren diese Rezensionen hilfreich? Wir wollen von Ihnen hören.