Programming Books C Java PHP Python Learn more Browse Programming Books
Software Systems Architecture and over one million other books are available for Amazon Kindle. Learn more
Buy Used
$2.53
+ $3.99 shipping
Used: Good | Details
Sold by tacoma_goodwill
Condition: Used: Good
Comment: All pages are intact, and the spine and cover are also intact. May have some usage wear, missing or damaged dust jacket, stickers, cover creases, bumped corners, bent pages, remainder mark, previous owner label or name, inscription, notes, underlining and/or highlighting. Text only; no CDs, InfoTrac, Access Codes, Activation Keys, or other inclusions, unless otherwise noted.
Access codes and supplements are not guaranteed with used items.
Have one to sell? Sell on Amazon
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See this image

Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives Hardcover – April 30, 2005

ISBN-13: 978-0321112293 ISBN-10: 0321112296 Edition: 1st

Used
Price: $2.53
18 New from $18.96 27 Used from $2.53 1 Collectible from $109.08
Amazon Price New from Used from
Kindle
"Please retry"
Hardcover
"Please retry"
$18.96 $2.53
NO_CONTENT_IN_FEATURE

Hero Quick Promo
12 Days of Kindle Book Deals
Load your library with Amazon's editors' picks, $2.99 or less each today only. Learn more

Product Details

  • Hardcover: 576 pages
  • Publisher: Addison-Wesley Professional; 1 edition (April 30, 2005)
  • Language: English
  • ISBN-10: 0321112296
  • ISBN-13: 978-0321112293
  • Product Dimensions: 7.5 x 1.5 x 9.5 inches
  • Shipping Weight: 2.2 pounds
  • Average Customer Review: 4.8 out of 5 stars  See all reviews (26 customer reviews)
  • Amazon Best Sellers Rank: #706,882 in Books (See Top 100 in Books)

Editorial Reviews

From the Back Cover

Software Systems Architectureis 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 atwww.viewpoints-and-perspectives.info



About the Author

Nick Rozanski is an enterprise technical architect at Marks and Spencer, where he focuses on integration and workflow. During his more than twenty years of experience he has worked for companies such as Logica, Capgemini, and Sybase. His technology experience covers enterprise application integration, relational databases, and object-oriented software development. He is also an experienced technical instructor and certified internal project auditor.

Eoin Woods is a principal consultant at Züehlke Engineering in London, where he works as a consultant software architect focusing on trading and investment management companies in the financial markets. He has worked in the software engineering field for fifteen years with a number of companies, including Ford Motor Company, Groupe Bull, InterTrust Technologies, and Sybase.




More About the Authors

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

4.8 out of 5 stars
5 star
22
4 star
3
3 star
0
2 star
1
1 star
0
See all 26 customer reviews
It is a very thorough and well written book.
R. C. Rathore
Anybody who has read the SEI books needs to read this one as well.
Mr. R. Van Schelven
This book is a "must have" for every software architect.
Amazon Customer

Most Helpful Customer Reviews

35 of 38 people found the following review helpful By uniq on August 28, 2005
Format: Hardcover
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." ([...] 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.
Read more ›
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
20 of 22 people found the following review helpful By Peter Eeles on January 3, 2006
Format: Hardcover
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.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
21 of 24 people found the following review helpful By T. Anderson TOP 1000 REVIEWERVINE VOICE on June 1, 2005
Format: Hardcover Verified Purchase
SECOND EDITION REVIEW:
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.
Read more ›
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
6 of 7 people found the following review helpful By paulsm on August 17, 2005
Format: Hardcover
This very readable book covers covers a lot of ground. It's a great introduction for those interested in software architecture; it's also a got a lot of great insights and useful information for practicing s/w architects.

Two of the main benefits this book has over other architecture books are:

a) it's one of the more up-to-date (Spring/2005) texts available on the subject

b) it's agnostic: giving equal coverage to all of the main schools, rather than focusing on just one.

One (relatively) unique idea in this book is the notion of "views" (as in Hofmeister or Krutchen) vs "perspectives"; perspectives being issues such as "security" that tend to cut *across* views.

Another thing I really liked was the emphasis on "architecture" as fundamentally driven by, and created for - the *stakeholders*.

This book is a great buy: it contains a lot of interesting, useful and important ideas and information about the art and science of software architecture.

Very, very highly recommended!
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again

Most Recent Customer Reviews