Software Architecture in Practice (3rd Edition) und über 1,5 Millionen weitere Bücher verfügbar für Amazon Kindle. Erfahren Sie mehr
EUR 47,95
  • Alle Preisangaben inkl. MwSt.
Nur noch 13 auf Lager (mehr ist unterwegs).
Verkauf und Versand durch Amazon.
Geschenkverpackung verfügbar.
Menge:1
Ihren Artikel jetzt
eintauschen und
EUR 7,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
Dieses Bild anzeigen

Software Architecture in Practice (SEI Series in Software Engineering) (Englisch) Gebundene Ausgabe – 25. September 2012


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 47,95
EUR 41,61 EUR 65,51
44 neu ab EUR 41,61 6 gebraucht ab EUR 65,51

Wird oft zusammen gekauft

Software Architecture in Practice (SEI Series in Software Engineering) + Documenting Software Architectures: Views and Beyond (SEI Series in Software Engineering) + Evaluating Software Architectures: Methods and Case Studies (SEI Series in Software Engineering)
Preis für alle drei: EUR 151,85

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

  • Gebundene Ausgabe: 589 Seiten
  • Verlag: Addison Wesley; Auflage: 3rd revised edition. (25. September 2012)
  • Sprache: Englisch
  • ISBN-10: 0321815734
  • ISBN-13: 978-0321815736
  • Größe und/oder Gewicht: 16,9 x 3,5 x 24,3 cm
  • Durchschnittliche Kundenbewertung: 3.5 von 5 Sternen  Alle Rezensionen anzeigen (2 Kundenrezensionen)
  • Amazon Bestseller-Rang: Nr. 41.861 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

Über den Autor und weitere Mitwirkende

Len Bass is a Senior Principal Researcher at National ICT Australia Ltd (NICTA). He joined NICTA in 2011 after twenty-five years at the Software Engineering Institute (SEI) at Carnegie Mellon University. He is the coauthor of two award-winning books in software architecture, including Documenting Software Architectures: Views and Beyond, Second Edition (Addison-Wesley, 2011), as well as several other books and numerous papers in computer science and software engineering on a wide range of topics. Len has almost fifty years' experience in software development and research in multiple domains, such as scientific analysis systems, embedded systems, and information systems. Paul Clements is the Vice President of Customer Success at BigLever Software, Inc., where he works to spread the adoption of systems and software product line engineering. Prior to this position, he was Senior Member of the Technical Staff at the SEI, where, for 17 years, he lead or co-lead projects in software product line engineering and software architecture documentation and analysis. Other books Paul has coauthored include Documenting Software Architectures: Views and Beyond, Second Edition (Addison-Wesley, 2011) and Evaluating Software Architectures: Methods and Case Studies, (Addison-Wesley, 2002), and Software Product Lines: Practices and Patterns (Addison-Wesley, 2002). In addition, he has also published dozens of papers in software engineering reflecting his long-standing interest in the design and specification of challenging software systems. Paul was a founding member of the IFIP WG2.10 Working Group on Software Architecture. Rick Kazman is a professor at the University of Hawaii and a Visiting Scientist (and former Senior Member of the Technical Staff) at the SEI. He is a coauthor of Evaluating Software Architectures: Methods and Case Studies, (Addison-Wesley, 2002). Rick's primary research interests are software architecture, design and analysis tools, software visualization, and software engineering economics. He is also interested in human-computer interaction and information retrieval. Rick was one of the creators of several highly influential methods and tools for architecture analysis, including the SAAM (Software Architecture Analysis Method), the ATAM (Architecture Tradeoff Analysis Method), the CBAM (Cost-Benefit Analysis Method), and the Dali architecture reverse engineering tool.

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

Kundenrezensionen

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

Die hilfreichsten Kundenrezensionen

11 von 14 Kunden fanden die folgende Rezension hilfreich Von jensa am 15. Dezember 2012
Format: Kindle Edition Verifizierter Kauf
I would give five starts for the content so far, but I decided to give only two stars because the formatting of the e-book edition is really sub-standard. Right at the start of the first chapter, the quotation is printed with one character per page over many pages. Going on, formatting switches between left-aligned and justified which is hard to read because the text looks different in each section. Some sections are indented so much that there are only a few words per line, so the text looks like a small column over pages. I wonder how this could pass quality checks by the publisher because it looks like someone converted the text and did not check the result before selling it on Amazon.

All in all, I would advice every programmer or software architect to buy the book, but not the e-book.
2 Kommentare 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
0 von 1 Kunden fanden die folgende Rezension hilfreich Von Bebe Aischa Sarwar Sahebjan am 13. September 2014
Format: Gebundene Ausgabe Verifizierter Kauf
I like it! This book has everything what i need and i recommend it to anyone else who want to know something about SE!
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: 22 Rezensionen
29 von 30 Kunden fanden die folgende Rezension hilfreich
Mandatory reading for the Software Architect!!! 18. Oktober 2012
Von T. Anderson - Veröffentlicht auf Amazon.com
Format: Gebundene Ausgabe Verifizierter Kauf
It was hard to imagine this book getter any better than it already was. I guess that was because I never expected so many changes. This is the most I have ever seen a new edition of a book change. If you own the second edition, you will definitely want this new one. It is almost like another book.

The big case studies are gone. They have been replaced with a ton of new material. If you don't own the first and second editions of the book, you can get the case studies on the publisher's web site.

Below are the chapters in this third edition.

Part One. Introduction
1. What Is Software Architecture?
2. Why Is Software Architecture Important?
3. The Many Contexts of Software Architecture

Part Two. Quality Attributes
4. Understanding Quality Attributes
5. Availability
6. Interoperability
7. Modifiability
8. Performance
9. Security
10. Testability
11. Usability
12. Other Quality Attributes
13. Architectural Tactics and Patterns
14. Quality Attribute Modeling and Analysis

Part Three. Architecture in the Life Cycle
15. Architecture in Agile Projects
16. Architecture and Requirements
17. Designing an Architecture
18. Documenting Software Architectures
19. Architecture, Implementation, and Testing
20. Architecture Reconstruction and Conformance
21. Architecture Evaluation
22. Management and Governance

Part Four. Architecture and Business
23. Economic Analysis of Architectures
24. Architecture Competence
25. Architecture and Software Product Lines

Part Five. The Brave New World
26. Architecture in the Cloud
27. Architectures for the Edge
28. Epilogue

To show you just how much the book has changed I have included the table of contents to the second edition below.

Pt. One. Envisioning Architecture
Ch. 1. The Architecture Business Cycle
Ch. 2. What Is Software Architecture?
Ch. 3. A-7E Avionics System: A Case Study in Utilizing Architectural Structures

Pt. Two. Creating an Architecture
Ch. 4. Understanding Quality Attributes
Ch. 5. Achieving Qualities
Ch. 6. Air Traffic Control: A Case Study in Designing for High Availability
Ch. 7. Designing the Architecture
Ch. 8. Flight Simulation: A Case Study in an Architecture for Integrability
Ch. 9. Documenting Software Architectures
Ch. 10. Reconstructing Software Architectures

Pt. Three. Analyzing Architectures
Ch. 11. The ATAM: A Comprehensive Method for Architecture Evaluation
Ch. 12. The CBAM: A Quantitative Approach to Architecture Design Decision Making
Ch. 13. The World Wide Web: A Case Study in Interoperability

Pt. Four. Moving From One System to Many
Ch. 14. Software Product Lines: Re-using Architectural Assets
Ch. 15. CelsiusTech: A Case Study in Product Line Development
Ch. 16. J2EE/EJB: A Case Study of an Industry-Standard Computing Infrastructure
Ch. 17. The Luther Architecture: A Case Study in Mobile Applications Using J2EE
Ch. 18. Building Systems from Off-the-Shelf Components
Ch. 19. Software Architecture in the Future

This book has been my go to book for most of my software architecture career. It is what taught me about quality attributes, tactics, and scenarios. It provided my first introduction to the Architecture Tradeoff Analysis Method (ATAM), the Quality Attribute Workshop (QAW), the Cost Benefit Analysis Method (CBAM), Active Reviews for Intermediate Designs (ARID), and the Attribute-Driven Design (ADD) method. In this new edition of the book they introduce the lightweight architecture evaluation. It is a slimmed-down version of ATAM. It is intended to be used on lower ceremony projects.

This new version has a ton of new material. One of the biggest changes is that the quality attributes covered now have their own chapter. There is a new chapter for Availability, Interoperability, Modifiability, Performance, Security, Testability, and Usability.

There is a new chapter dedicated to the technical, project, business, and professional contexts of software architecture. This chapter shows how architecture supports and is informed by other forces and activities in the different contexts.

Part four, Architecture and Business, contains three chapters dedicated to showing the relationships between the architecture and the business.

There is a new chapter on architecturally significant requirements and how to solicit those requirements from the goals set down by the business. This chapter introduces a new method for eliciting and documenting business goals in order to discover architecturally significant requirements. The new method is called Pedigreed Attribute eLicitation Method or PALM for short.

There is a new chapter on individual and organizational architectural competence. The chapter covers the technical duties of a software architect, the non-technical duties of a software architect, and the knowledge areas of the software architect. It also provides a framework for organizational architectural competence.

Part three, Architecture in the Life Cycle, shows how architecture relates to agile projects, shows how to elicit architecturally significant requirements, shows how to design the architecture and document the architecture, also how to test the architecture. Part three also covers how to reconstruct an architecture and evaluate an architecture.

One of my favorite new additions was chapter 27, Architectures for the Edge. An Edge dominant system is one that depends on the input of their users for success. Edge architectures that exist today are Wikipedia, YouTube, Facebook, and Twitter. It was just a really interesting read.

I could go on and on about the value of the content in this book. The bottom line is that if you are a software architect, or want to be one, this is mandatory reading, period.
3 von 3 Kunden fanden die folgende Rezension hilfreich
Excellent structure to evaluate software architecture 27. August 2013
Von Pete the Geek - Veröffentlicht auf Amazon.com
Format: Gebundene Ausgabe Verifizierter Kauf
As a software designer and engineer for over 1/4 century, I am always on the look-out for a process which claims to separate high-quality from low-quality. Software is not a tangible, 3-dimensional, manufactured product, but software has "quality". Initially someone at work started pushing this new "quality" rating methodology for software......distributed or centralized.

I have dedicated the last several years to wrestling with "quality".....everywhere in my life but particularly at work with software. When I heard "Architecture Quality Attributes" I was intrigued and bought the book. Each AQA is broken down into Concerns and Common Tactics. Thinking back over the last 1/4 century....they all rang true. Quality in technical design and quality in technical management all come together here. Buy this book.

My only peeve......why such a half-hearted writeup Probabilty Statistics, Fault-tree Analysis, and FMEA ? There is a dis-organized and scattered treatment through out the book. Page 84 (3rd edition) discusses AND gates, OR gates, etc etc...and then statistics shows up again from pages 255 - 259. In today's distributed environment, probability statistics is very revealing. The more components bolted together to create a network, the more OR-gates you have that could fail and make your network inoperable. This is the Achilles heel of distributed environments.

Ironically, that entire concept is hidden from the reader of this book. Even on page 256, at the very bottom, the authors give a formula for "probability of failure". In fact, the formula is EXACTLY WRONG !! The formula shown is the formula for "probability of success". ( probabilty of failure + probability of success = 1 ). Oh well.

Perhaps, I thought chuckling to myself as I put the book down, this is why the young kids keep buying more and more servers whenever they run into capacity constraints.......page 256 assures them that each component approaches zero chance of failing as time approaches infinity and the component is left in service longer and longer and longer....... DOH !! :-)
3 von 3 Kunden fanden die folgende Rezension hilfreich
Not that good 8. Mai 2014
Von Giovani Salvador - Veröffentlicht auf Amazon.com
Format: Kindle Edition Verifizierter Kauf
Lots of what to do and not how to achieve. It does not contain technical depth. Some tactics are very succint. For a kindle edition, the price is high, compared to the quality of the book
20 von 28 Kunden fanden die folgende Rezension hilfreich
Great content, but almost unreadable layout 3. Januar 2013
Von jensa - Veröffentlicht auf Amazon.com
Format: Kindle Edition
I would give five starts for the content so far, but I decided to give only two stars because the formatting of the e-book edition is really sub-standard. Right at the start of the first chapter, the quotation is printed with one character per line over many pages. Going on, formatting switches between left-aligned and justified which is hard to read because the text looks different in each section. Some sections are indented so much that there are only a few words per line, so the text looks like a small column over pages. I wonder how this could pass quality checks by the publisher because it looks like someone converted the text and did not check the result before selling it on Amazon.

All in all, I would advice every programmer or software architect to buy the book, but not the e-book.
1 von 1 Kunden fanden die folgende Rezension hilfreich
Very good and comprehensive explanation of good (the best) practices in ... 15. Dezember 2014
Von Maciek - Veröffentlicht auf Amazon.com
Format: Kindle Edition Verifizierter Kauf
Very good and comprehensive explanation of good (the best) practices in a software development. I recommend that book for the beginners and for the experienced professionals as well.
Waren diese Rezensionen hilfreich? Wir wollen von Ihnen hören.