Enjoy fast, free delivery, exclusive deals, and award-winning movies & TV shows with Prime
Try Prime
and start saving today with fast, free delivery
Amazon Prime includes:
Fast, FREE Delivery is available to Prime members. To join, select "Try Amazon Prime and start saving today with Fast, FREE Delivery" below the Add to Cart button.
Amazon Prime members enjoy:- Cardmembers earn 5% Back at Amazon.com with a Prime Credit Card.
- Unlimited Free Two-Day Delivery
- Streaming of thousands of movies and TV shows with limited ads on Prime Video.
- A Kindle book to borrow for free each month - with no due dates
- Listen to over 2 million songs and hundreds of playlists
- Unlimited photo storage with anywhere access
Important: Your credit card will NOT be charged when you start your free trial or if you cancel during the trial period. If you're happy with Amazon Prime, do nothing. At the end of the free trial, your membership will automatically upgrade to a monthly membership.
Buy new:
-32% $54.39$54.39
Ships from: Amazon Sold by: Gold Stone Online
Save with Used - Like New
$11.82$11.82
Ships from: Amazon Sold by: Word Wizards Store
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Software Architecture in Practice (SEI Series in Software Engineering) 3rd Edition
There is a newer edition of this item:
Purchase options and add-ons
The award-winning and highly influential Software Architecture in Practice, Third Edition, has been substantially revised to reflect the latest developments in the field. In a real-world setting, the book once again introduces the concepts and best practices of software architecture―how a software system is structured and how that system’s elements are meant to interact. Distinct from the details of implementation, algorithm, and data representation, an architecture holds the key to achieving system quality, is a reusable asset that can be applied to subsequent systems, and is crucial to a software organization’s business strategy.
The authors have structured this edition around the concept of architecture influence cycles. Each cycle shows how architecture influences, and is influenced by, a particular context in which architecture plays a critical role. Contexts include technical environment, the life cycle of a project, an organization’s business profile, and the architect’s professional practices. The authors also have greatly expanded their treatment of quality attributes, which remain central to their architecture philosophy―with an entire chapter devoted to each attribute―and broadened their treatment of architectural patterns.
If you design, develop, or manage large software systems (or plan to do so), you will find this book to be a valuable resource for getting up to speed on the state of the art.
Totally new material covers
- Contexts of software architecture: technical, project, business, and professional
- Architecture competence: what this means both for individuals and organizations
- The origins of business goals and how this affects architecture
- Architecturally significant requirements, and how to determine them
- Architecture in the life cycle, including generate-and-test as a design philosophy; architecture conformance during implementation; architecture and testing; and architecture and agile development
- Architecture and current technologies, such as the cloud, social networks, and end-user devices.
- ISBN-109780321815736
- ISBN-13978-0321815736
- Edition3rd
- PublisherAddison-Wesley Professional
- Publication dateSeptember 25, 2012
- LanguageEnglish
- Dimensions6.18 x 1.5 x 9.41 inches
- Print length624 pages
Frequently bought together

Similar items that may deliver to you quickly
Editorial Reviews
About the Author
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.
Product details
- ASIN : 0321815734
- Publisher : Addison-Wesley Professional; 3rd edition (September 25, 2012)
- Language : English
- Hardcover : 624 pages
- ISBN-10 : 9780321815736
- ISBN-13 : 978-0321815736
- Item Weight : 2.26 pounds
- Dimensions : 6.18 x 1.5 x 9.41 inches
- Best Sellers Rank: #1,214,485 in Books (See Top 100 in Books)
- #276 in Software Design & Engineering
- #1,444 in Software Development (Books)
- #4,804 in Business Technology
- Customer Reviews:
About the authors

My latest book is Deployment and Operations for Software Engineers which I wrote with John Klein. It grew out of my belief that there is a body of knowledge that modern software engineers should know but that isn't currently taught in software engineering curricula. This body of knowledge includes information about the environment in which an application will execute as well as information about how to exploit that information. This book is an attempt to facilitate the offering of a course that covers this material. Between the book and the instructor slides, a potential instructor has the material necessary to offer a course to their students covering this material.The slides are available at
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cmudevops_DOSE-2Dslides&d=DwMFaQ&c=dWz0sRZOjEnYSN4E4J0dug&r=eK3ZfAl3wnQAY_LLWki5ZQ&m=MrYsSnQg5BblcdiUM74vNmUbajRbW_RyOApsnV7izkE&s=G7NEEjzDGaJqX1E3uLp1r-fqCvWS_2akj7CcmedLNHI&e=

Discover more of the author’s books, see similar authors, read book recommendations and more.

Rick Kazman is a Professor at the University of Hawaii and a Visiting Scientist (and former Senior Member of the Technical Staff) at the Software Engineering Institute of Carnegie Mellon University. His primary research interests are software architecture, design and analysis tools, software visualization, and software engineering economics. He also has interests in human-computer interaction and information retrieval. Kazman has created several highly influential methods and tools for architecture analysis, including the SAAM (Software Architecture Analysis Method), the ATAM (Architecture Tradeoff Analysis Method) and the Dali architecture reverse engineering tool. He is the author of over 100 papers, and co-author of several books, including Software Architecture in Practice, and Evaluating Software Architectures: Methods and Case Studies.
Kazman received a B.A. (English/Music) and M.Math (Computer Science) from the University of Waterloo, an M.A. (English) from York University, and a Ph.D. (Computational Linguistics) from Carnegie Mellon University. How he ever became a software engineering researcher is anybody’s guess. When not architecting or writing about architecture, Kazman may be found cycling, playing the piano, gardening, practicing Tae Kwon Do, or (more often) flying back and forth between Hawaii and Pittsburgh.
Customer reviews
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
Learn more how customers reviews work on AmazonCustomers say
Customers find the book's information quality great for software architects. They say it's useful and practical for students and professionals. However, some readers feel the book is extremely dense. Opinions are mixed on readability, with some finding it easy and understandable, while others say it's too abstract.
AI-generated from the text of customer reviews
Customers find the book great for software architects. They say it's a good reference for already experienced architects and a good overview for class. Readers also mention it covers different aspects of architecture in depth, is thorough, and has enough detail so that they can put it into practice.
"This is the best book about architectural principles and practices...." Read more
"...I consider it a must have for software architect. It haves enough detail so that you can put it in practice and have it as a reference always...." Read more
"This book is certainly a good reference for already experienced architects, and maybe a god overview for less senior people...." Read more
"Great book for software architects. I also took the SEI online course for which this book is the textbook. Material is thorough and presented well." Read more
Customers find the book useful, practical, and a great introduction to a huge topic. They say the lessons still apply in the age of micro-services.
"...Throughout the course, these chapters were extremely useful when building the architecture of an online collaboration system...." Read more
"Great introduction to a huge topic...." Read more
"...Even in the age of micro-services, the large scale lessons still apply." Read more
"Great book, full of useful information.... practical and the book layout is great. This book will last for a few years and in IT that is long LOL." Read more
Customers find the book has improvements and editorial changes that make it easier to read. They also say it's an excellent edition, with much new content that an experienced architect would find valuable. Readers mention the book has a technology update that is a plus.
"...It has improvements in the updated content and editorial changes that makes the book easier to read, more self-explanatory." Read more
"Excellent edition with much new content that an experienced architect would find valuable...." Read more
"It's really simple to read and understand the concepts, and have a technology update that is a plus over the previous versions." Read more
Customers find the book easy and understandable, with clear explanations. They say it's a good base text about software architecture focused on real-life scenarios. However, some readers feel the book is too abstract, lacks technical depth, and is too pedagogical.
"...It also helps the book is an easy and understandable read." Read more
"...the implications of software architecture and the importance of quality attribute analysis. I consider it a must have for software architect...." Read more
"...through more abstract concepts and thoughts, the text is full of useless contemplation and even bare repetition...." Read more
"...Material is thorough and presented well." Read more
Customers find the book extremely dense. They say the first three chapters are rather dense, as they basically resume the whole book.
"...The first 3 chapters are rather dense because they basically resume the whole book. Do not be discuraged, everything will be fine chapter 4 and on." Read more
"...However, I find it far too verbose and far to thick. It would be good if the authors shrunk it to half of its size...." Read more
"The book is extremely dense...." Read more
-
Top reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
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 !! :-)
On the other hand, whenever they walk the reader through more abstract concepts and thoughts, the text is full of useless contemplation and even bare repetition. Maybe, for these more difficult and dry topics, the authors were hoping that the reader would understand eventually after the 5th bad explanation. Sorry, but I would prefer one or two really good explanation.
Top reviews from other countries
A qualidade do livro também é excelente, boa impressão e capa dura!
Je vous le conseille








