In weniger als einer Minute können Sie mit dem Lesen von Software Systems Architecture: Working with Stakeholders... auf Ihrem Kindle beginnen. Sie haben noch keinen Kindle? Hier kaufen Oder fangen Sie mit einer unserer gratis Kindle Lese-Apps sofort an zu lesen.

An Ihren Kindle oder ein anderes Gerät senden

 
 
 

Kostenlos testen

Jetzt kostenlos reinlesen

An Ihren Kindle oder ein anderes Gerät senden

Jeder kann Kindle eBooks lesen - auch ohne Kindle-Gerät - mit der gratis Kindle Lese-App für Smartphones und Tablets.
Software Systems Architecture: Working with Stakeholders Using Viewpoints and Perspectives (2nd Edition)
 
 

Software Systems Architecture: Working with Stakeholders Using Viewpoints and Perspectives (2nd Edition) [Kindle Edition]

Nick Rozanski , Eóin Woods

Kindle-Preis: EUR 23,94 Inkl. MwSt. und kostenloser drahtloser Lieferung über Amazon Whispernet

Weitere Ausgaben

Amazon-Preis Neu ab Gebraucht ab
Kindle Edition EUR 23,94  
Gebundene Ausgabe EUR 40,95  


Produktbeschreibungen

Kurzbeschreibung

This is the eBook version of the printed book.

Software Systems Architecture, Second Edition is a highly regarded, practitioner-oriented guide to designing and implementing effective architectures for information systems. It is both a readily accessible introduction to software architecture and an invaluable handbook of well-established best practices.

 

With this book you will learn how to

  • Design and communicate an architecture that reflects and balances the different needs of its stakeholders
  • Focus on architecturally significant aspects of design, including frequently overlooked areas such as performance, resilience, and location
  • Use scenarios and patterns to drive the creation and validation of your architecture
  • Document your architecture as a set of related views

 

Reflecting new standards and developments in the field, this new edition extends and updates much of the content, and

  • Adds a “system context viewpoint” that documents the system’s interactions with its environment
  • Expands the discussion of architectural principles, showing how they can be used to provide traceability and rationale for architectural decisions
  • Explains how agile development and architecture can work together
  • Positions requirements and architecture activities in the project context
  • Presents a new lightweight method for architectural validation

 

Whether you are an aspiring or practicing software architect, you will find yourself referring repeatedly to the practical advice in this book throughout the lifecycle of your projects.

Synopsis

Software Systems Architecture is a practitioner-oriented guide to designing and implementing effective architectures for information systems. It is both a readily accessible introduction to software architecture and an invaluable handbook of well-established best practices. It shows why the role of the architect is central to any successful information-systems development project, and, by presenting a set of architectural viewpoints and perspectives, provides specific direction for improving your own and your organization's approach to software systems architecture.With this book you will learn how to *Design an architecture that reflects and balances the different needs of its stakeholders *Communicate the architecture to stakeholders and demonstrate that it has met their requirements *Focus on architecturally significant aspects of design, including frequently overlooked areas such as performance, resilience, and location *Use scenarios and patterns to drive the creation and validation of your architecture *Document your architecture as a set of related views *Use perspectives to ensure that your architecture exhibits important qualities such as performance, scalability, and security The architectural viewpoints and perspectives presented in the book also provide a valuable long-term reference source for new and experienced architects alike.

Whether you are an aspiring or practicing software architect, you will find yourself referring repeatedly to the practical advice in this book throughout the lifecycle of your projects. A supporting Web site containing further information can be found at www.viewpoints-and-perspectives.info


Produktinformation

  • Format: Kindle Edition
  • Dateigröße: 7048 KB
  • Seitenzahl der Print-Ausgabe: 704 Seiten
  • Gleichzeitige Verwendung von Geräten: Bis zu 5 Geräte gleichzeitig, je nach vom Verlag festgelegter Grenze
  • Verlag: Addison-Wesley Professional; Auflage: 2 (25. Oktober 2011)
  • Verkauf durch: Amazon Media EU S.à r.l.
  • Sprache: Englisch
  • ASIN: B0061LAKW0
  • Text-to-Speech (Vorlesemodus): Aktiviert
  • X-Ray:
  • Amazon Bestseller-Rang: #123.971 Bezahlt in Kindle-Shop (Siehe Top 100 Bezahlt in Kindle-Shop)

  •  Ist der Verkauf dieses Produkts für Sie nicht akzeptabel?

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.2 von 5 Sternen  6 Rezensionen
18 von 18 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen My new standard architecture framework 7. Februar 2012
Von W. Alan McBee - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe
I want to start by countering the negative review that is currently viewed as the most helpful here on Amazon. The reviewer did not like that the book did not seem to address most directly what would be needed by "project managers, team leads and most importantly developers."

I'm going to suggest that the reviewer started reading the book with a preconceived notion of what a software architect is, and what software architecture is about. It's no surprise. I'm reading several books on software architecture; all of them confront and try to address what might be a common definition, given that there are so many ambiguous definitions throughout the world.

The authors of this book make clear that ALL of the stakeholders in a software project must be appropriately addressed. That's a huge challenge! From business executives to analysts to even project managers, team leads, and developer, all of them must share a common understanding of the entire system and what will be changed. If the architect is primarily thinking about how to communicate with the development team, then that architect should have her title changed to development lead or chief engineer.

It was by reading this book for the main purpose of understanding what a software architect really is responsible for, that I can now easily distinguish the software architect role from other roles. The responsibility is to everybody that has a material interest in the project.

And how can one possibly communicate appropriately to people whose interest and technical acumen will range as wide as is possible throughout a business? That's exactly what this book explain precisely how to do, in a way that will make sense to the developers, the project managers, the executives, the project managers, the operations staff, the security team... everyone.

It does not (nor does it claim to) teach how to apply software development design patterns to construct a component, nor how to correlate a sequence diagram of a system with its structural diagram, or any of the other concerns that are probably best left to the development leads.

It does, however, consistently encourage and recommends strategies and tactics for keeping the level of abstraction at the right level for the stakeholders to which you are attempting to share that one software system solution. Architecture is not about the world of details (where developers live) -- it's about the world of models which, as a necessity, must remove details that are not necessary for all stakeholders. The model must be correct, but it must also be shared by all. That's the responsibility of the architect.

This book is definitely worth reading if you already believe that software architecture is your field, and feel overwhelmed at trying to grasp the scope of your responsibilities and the ever-changing nature of what an architect's value should be. It has a permanent place on my bookshelf, and I'll be referring to it quite often over my career.
5 von 5 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen The BEST Software Architecture Book Available 2. März 2013
Von T. Anderson - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe|Von Amazon bestätigter Kauf
Some might look at my book collect and think I have hoarding issues. If I had to pick just one Software Architecture book to keep, this would be the one.

This is the second edition of one of the best books written on software systems architecture. If you are in the software development industry, you should read this book. If you are a Software Architect, you must read this book.

This book covers a vast amount of material but it ties it all together in a way that paints a complete picture of what software systems architecture is all about.

The book starts out covering architecture fundamentals. There is a chapter on Software Architecture Concepts, Viewpoints and Views, Architectural Perspectives, and The Role of the Software Architect.

It then presents a process for software architecture and explains all the elements involved with the process. This part of the book contains chapters on The Architecture Definition Process, Concerns, Principles and Decisions, Identifying and Engaging Stakeholders, Identifying and Using Scenarios, Using Styles and Patterns, Producing Architectural Models, and Evaluating the Architecture.

Next is a viewpoint catalog. The part of the book goes into the details of the different viewpoints the authors recommend considering as part of you architectural analysis. The viewpoints include Context, Information, Functional, Concurrency, Information, Development, Deployment, and Operational. Each viewpoint is a separate chapter. This section ends with a chapter that show how to achieve consistency across views.

After the viewpoint catalog the authors present a perspective catalog. Perspectives ensure that quality properties that cross several views are accounted for and analyzed. The perspective catalog includes Security, Performance and Scalability, Availability and Resilience, Evolution, Accessibility, Development Resource, Internationalization, Location, Regulation, and Usability.

The book ends with a chapter that ties everything together and a nice appendix that shows the relationship of the author's Viewpoints and Perspectives to other processes. They include Kruchten 4+1, RM-ODP, Siemens, SEI's Views and Beyond, Garland and Anthony, IAF, Zachman, and TOGAF.

I am lucky they came out with a second edition because my first edition is getting pretty beat up. It has scribbling from tons of different projects in it. The first edition has not left my side since I purchased it and this second edition won't leave my side either.

One of the things I like about this book is that the authors complete the picture. They don't say here is one example of a pitfall, concern, or tactic, they present a nice long list that really helps lead you through the process. Keeping this book handy helps me think of things I am sure to overlook.

Another thing I like about this book is that it is not a reinvention of the wheel. The authors do a great job of incorporating industry best practices that have withstood the test of time, as well as included all the newer elements of software architecture that have come about in recent years.

If you have the first edition, the second edition is worth getting. There is updated information scattered throughout the book as well as a new Context viewpoint. There has been 132 pages added.

I said this about the first version and it still holds true with the second edition... Even if you are not an architect it is a great book to buy so you understand what to expect out of one. I may buy a few extra copies to give out on projects so they understand why I am supposed to be there. Anyone reading this book should have a great and complete understanding of architecture and the value it adds to a project.
1 von 2 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Exceptional Briefing 30. Januar 2013
Von Z - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe|Von Amazon bestätigter Kauf
This was an exceptional review on the entire practice of Architecture. Throughout this work, the authors provide very detailed (yet easy to read) guidance on every element of view-based architecture. This book provides an enterprise perspective of the practice of architecture and outlines all of the things to watch out for at various stages of system design.

I would recommend this book both as a comprehensive briefing as well as a reference book if you are an architect.
6 von 10 Kunden fanden die folgende Rezension hilfreich
3.0 von 5 Sternen Helpful for one part of the Software Architecture problem 23. April 2012
Von Samwell - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe
I started out excited to read this book, and ended up somewhat disappointed. The two biggest challenges in software architecture are keeping that architecture "In Sync" (for some sufficiently confident "In Sync") with

(A) requirements, as they are uncovered or evolve, and
(B) implementation, as it gets built and evolves.

While this book does a fair job on (A), it unfortunately does an inadequate job on (B).

The separation of viewpoints from perspectives is useful (re-named, though not new), the potential pitfalls listed are useful, and including an "Operational" viewpoint is useful for a large class of systems. But the content and boundaries of both viewpoints and perspectives is quite ambiguous e.g. I was surprised to see the authors suggest that replication of application servers would change the Functional view. I would try quite hard to avoid this e.g. limit it to, at most, an annotation on connectors.

Lastly, for the number of "Definitions" included in this book, it was disappointing that those were not consolidated and formalized into a model (beyond the Viewpoints / Perspectives / Stakeholder level).
0 von 2 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Favorite Software Architecture Book 18. Juni 2012
Von Timothy J. Roberts - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe|Von Amazon bestätigter Kauf
This is my favorite software architecture reference.
Its a good mixture of practical and theoretical (deep).
The viewpoint/perspective sections provides a useful set of items to consider when evaluating an architecture.
Waren diese Rezensionen hilfreich?   Wir wollen von Ihnen hören.

Beliebte Markierungen

 (Was ist das?)
&quote;
A good architecture is one that successfully addresses the concerns of its stakeholders and, when those concerns are in conflict, balances them in a way that is acceptable to the stakeholders. &quote;
Markiert von 8 Kindle-Nutzern
&quote;
An architectural tactic is an established and proven approach you can use to help achieve a particular quality property. &quote;
Markiert von 7 Kindle-Nutzern
&quote;
An architectural perspective is a collection of architectural activities, tactics, and guidelines that are used to ensure that a system exhibits a particular set of related quality properties that require consideration across a number of the systems architectural views. &quote;
Markiert von 7 Kindle-Nutzern

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
 

Kundendiskussionen durchsuchen
Alle Amazon-Diskussionen durchsuchen
   


Ähnliche Artikel finden


ARRAY(0xa0f03b88)