Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives | 
 enlarge | Authors: Nick Rozanski, Eoin Woods
Publisher: Addison-Wesley Professional
Category: Book
List Price: $59.99
Buy New: $39.99
You Save: $20.00 (33%)
New (31) Used (11) from $39.99
Rating:  16 reviews
Sales Rank: 30145
Media: Hardcover
Pages: 576
Number Of Items: 1
Shipping Weight (lbs): 2.2
Dimensions (in): 9.3 x 7.2 x 1.3
ISBN: 0321112296
Dewey Decimal Number: 005.3
EAN: 9780321112293
Publication Date: April 30, 2005
Availability: Usually ships in 1-2 business days
Condition: Brand new. Please allow 7 to 10 BUSINESS DAYS for delivery after receipt of order. We cannot ship to post office box addresses.
| |
| Similar Items:
|
| Editorial Reviews:
Product Description
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
|
| Customer Reviews: Read 11 more reviews...
Comprehensive view on the subject of Systems Architecture August 28, 2005
uniq (El Dorado Hills, CA United States)
16 out of 16 found this review helpful
When it comes to the systems or software architecture, I subscribe to Tom Demarco's definition: "An architecture is a framework for the disciplined introduction of change." (http://www.systemsguild.com/GuildSite/TDM/Architecture.html). And while most of the job postings matching "architect" these days talk about the need for writing and testing code, there is a growing awareness in the industry that in order to build a resilient enterprise system an organization must look beyond design patterns and coding idioms. In addition to the technical challenges, building large enterprise system requires effort of many professionals during an extended period of time. This brings other non-technical risks into the picture.
This is one of the better books covering many issues that comprise System Architecture discipline in the light of their personal experience. The authors introduce us to an approach for partitioning architecture using Viewpoints (behavioral characteristics, e.g. Functional, Information, Concurrency, Development, Deployment, Operational) and Perspectives (nonfunctional aspects, e.g. Security, Performance and Scalability, Availability and Resilience, Evolution).
The first half of the book describes the discipline of Application Software Architecture, the second half contains two catalogs, one for Viewpoints and the other for Perspectives. Both catalogs describe concerns, artifacts (models), problems and pitfalls when focusing on a viewpoint or perspective.
I would qualify this book as a companion and reference for a beginner through intermediate level. It gives an excellent overview of what a system architect has to go through day in and day out to achieve success. The book contains a wealth of advice on what to pay and not pay attention to in any particular stage of the architectural development. The authors clearly speak from personal experience. Their examples are always to the point, although a bit sketchy with respect to details on techniques and artifacts and how to develop and use them. Considering the site of the volume, the authors did an excellent job balancing width and depth of coverage: trying to cover such a vast discipline in detail in a 500+-page book is not possible.
Every IT architect should read this book January 3, 2006
Peter Eeles
8 out of 8 found this review helpful
My reason for buying this book was to hear what the authors had to say about handling cross-cutting architectural concerns (such as security), which they refer to as "perspectives". The authors offer refreshing insights into how such concerns should be interwoven with the architecture views/viewpoints with which many architects will already be familiar when documenting their software architectures.
But now that I've finally finished reading the book (500+ pages) I have to say that this book is so much more. This is essentially a "book of 2 halves". The first half discusses fundamental architecture concepts, and various elements of the architecture process. However, the second half of the book is dedicated to a catalog of viewpoints and a catalog of perspectives. These sections are, I think, the most valuable, and offer probably the best overview of different architectural concerns (such as concurrency, deployment, operations, security, availability etc.) I've come across. And the whole book is liberally sprinkled with pragmatic advice, and examples, based on the authors' experiences.
In summary, the book makes a great "handbook" for both novice and experienced architects.
Simply Excellent June 1, 2005
T. Anderson (PA USA)
13 out of 15 found this review helpful
This is an awesome book for Architects. It ties together the SEI books Software Architecture in Practice, 2nd Edition and Documenting Software Architectures: Views and Beyond in its own way making Architecture very understandable.
I am not going to blabber about each chapter I will just say they are all excellent and complete. Go to the book's site for more info on the details of the book. http://www.viewpoints-and-perspectives.info/
I have over 10 years of experience as a software architect. This book is an excellent addition to my library. It is an easy read with tons of info in it.
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.
Brings many things together July 13, 2006
PAT BAILEY (Grand Rapids, MI United States)
5 out of 5 found this review helpful
I was impressed with this book's unique perspective of blending the business and technical needs into a single focus, and it continued to maintain the human considerations. It does an excellent job of describing how to support business decisions through architecture at a macro level in a style where "the rubber hits the road."
If you are a systems analyst or a software development manager, this shouldn't be on your book shelf - it should be on your desk for regular reference.
explains the job of a system architect July 2, 2006
W Boudville (Terra, Sol 3)
4 out of 4 found this review helpful
The authors give the reader detailed and useful suggestions about designing a software system. It should be made clear that this is not a programming book. Coding particulars are at a finer level outside the book's scope.
The book is addressed to the software architect. Which can be rather a vague job role. One merit of the book is that it can be used to define what a software architect does. While the authors might not claim to encompass everything in your job description, perhaps what is given here is your core responsibility.
So the text shows how to identify and use scenarios, to build sets of scenarios. And yet be able to construct inherently different scenarios. A vital feature of making the scenarios is how it involves the stakeholders very early in the design. Vital in preventing misunderstandings about undesigned or unneeded functionalities, before they get built into the system.
Then, given a system, the text explains how to document it using UML. The latter is extremely useful. Both for programmers who might have to design to it, and for the stakeholders. The visual nature of UML helps make it understandable to both parties.
|
|
|
