Programming Books C Java PHP Python Learn more Browse Programming Books
Software Architecture in Practice (2nd Edition) and over one million other books are available for Amazon Kindle. Learn more
Buy Used
$36.71
Condition: Used: Good
Comment: Some visible wear, and minimal interior marks. Unbeatable customer service, and we usually ship the same or next day. Over one million satisfied customers!
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 Architecture in Practice (2nd Edition) Hardcover – April 19, 2003

ISBN-13: 078-5342154955 ISBN-10: 0321154959 Edition: 2nd

Used
Price: $36.71
16 New from $8.00 51 Used from $0.33
Amazon Price New from Used from
Kindle
"Please retry"
Hardcover
"Please retry"
$8.00 $0.33
NO_CONTENT_IN_FEATURE

Holiday Deals in Books
Holiday Deals in Books
Find deals for every reader in the Holiday Deals in Books store, featuring savings of up to 50% on cookbooks, children's books, literature & fiction, and more.

Product Details

  • Hardcover: 560 pages
  • Publisher: Addison-Wesley Professional; 2 edition (April 19, 2003)
  • Language: English
  • ISBN-10: 0321154959
  • ISBN-13: 978-0321154958
  • Product Dimensions: 6.5 x 1.3 x 9.5 inches
  • Shipping Weight: 2.5 pounds
  • Average Customer Review: 3.8 out of 5 stars  See all reviews (16 customer reviews)
  • Amazon Best Sellers Rank: #267,516 in Books (See Top 100 in Books)

Editorial Reviews

From the Back Cover

This award-winning book, substantially updated to reflect the latest developments in the field, 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.

Drawing on their own extensive experience, the authors cover the essential technical topics for designing, specifying, and validating a system. They also emphasize the importance of the business context in which large systems are designed. Their aim is to present software architecture in a real-world setting, reflecting both the opportunities and constraints that companies encounter. To that end, case studies that describe successful architectures illustrate key points of both technical and organizational discussions.

Topics new to this edition include:

  • Architecture design and analysis, including the Architecture Tradeoff Analysis Method (ATAM)
  • Capturing quality requirements and achieving them through quality scenarios and tactics
  • Using architecture reconstruction to recover undocumented architectures
  • Documenting architectures using the Unified Modeling Language (UML)
  • New case studies, including Web-based examples and a wireless Enterprise JavaBeans™ (EJB) system designed to support wearable computers
  • The financial aspects of architectures, including use of the Cost Benefit Analysis Method (CBAM) to make decisions
  • If you design, develop, or manage the building of large software systems (or plan to do so), or if you are interested in acquiring such systems for your corporation or government agency, use Software Architecture in Practice, Second Edition, to get up to speed on the current state of software architecture.



    0321154959B03262003

    About the Author

    Len Bass is a senior member of the technical staff at the Software Engineering Institute (SEI). He has written or edited five books and numerous papers on software engineering and other topics. He has extensive experience in architecting real-world development projects.

    Paul Clements is a senior member of the technical staff at the SEI, where he works on software architecture and product line engineering. He is the author of five books and more than three dozen papers on these and other topics.

    Rick Kazman is a senior member of the technical staff at the SEI. He is also an Associate Professor at the University of Hawaii. He is the author of two books, editor of two more, and has written more than seventy papers on software engineering and related topics.




    More About the Authors

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

    Customer Reviews

    In the beginning part of this book, the authors make a compelling case that software architecture is required for success.
    mobiusklien
    Software Architecture in Practice is probably the best book that I have read on the theory and practice of architecture design and software engineering.
    Amazon Customer
    This text is chock full of "Case Studies" in Architectural design & development methods, but surpringinly sparse in specifics.
    Ibuycrappystuff

    Most Helpful Customer Reviews

    33 of 39 people found the following review helpful By Amazon Customer on November 25, 2003
    Format: Hardcover
    Being a Software Architect, I can certainly appreciate the work that the authors of this book (L. Bass, P. Clements, R Kazman) have put into this book. Software Architecture in Practice is probably the best book that I have read on the theory and practice of architecture design and software engineering. There is no fair way for me to review this book as it is PACKED with useful information from beginning to the very end. It has a combination of high-level architectural concepts tailored with best software engineering practices. It is not a complete book on software engineering, but it wasn't meant to be - it's meant to cover a very specific topic in software engineering and it does so extremely well. It is a text in which the concepts architecting software applications, evaluating architectures thru various methods, and case studies of major leaps in software architecture have been very well described; depicted and well evaluated. The book is written from an architect's point of view, and it shows how an architect or a group of architects can make or break an organization, and what they need to do in order to be successful. The authors of this book explain why simply architecting something is not good enough and lots of work needs to be done before and after the architectural phase to ensure the quality and the success of the project. This aspect of the book is simply priceless.
    The author start by describing software architecture as:
    "The Software Architecture of a program or computing system is the structure or structures of the system, which compromise software elements, the externally visible properties of those elements, and the relationships between them."
    Throughout the book, the author used this definition to describe various aspects of architecture.
    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
    14 of 16 people found the following review helpful By Erik Gfesser VINE VOICE on June 7, 2003
    Format: Hardcover
    My recent software engineering graduate course on software architecture relied mainly on this SEI text, along with several of the many SEI white papers posted on the SEI site, and such texts as Buschmann's Pattern Oriented Software Architecture (POSA) and Stelting/Maassen's Applied Java Patterns. Since the second edition of the text was available just two weeks after the start of the course, I decided not to purchase the first edition, and instead purchased the second edition. However, having used both editions for the course, I must say that the second edition is superior to the first even when only taking the architectural view notation into account (it uses UML rather than a cryptic, proprietary notation used in the first edition, although at this high of a level in modeling, UML sometimes disappoints as well). The addition of content from some SEI white papers to the text is also a benefit of the second edition. The text, regardless of the edition, is well written and very understandable.
    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
    8 of 9 people found the following review helpful By Kris L. Holt on July 20, 2003
    Format: Hardcover Verified Purchase
    The second edition of the book makes a good journeyman's guidebook, which the first edition didn't since software architecture was still a mystique. The second edition, which has been heavily revamped, makes it clear that software architecture is a mature discipline.
    I used the first edition, along with SEI technical papers in a graduate-level software architecture introductory course. After reading the first edition, I still wasn't sure what a software architect should do. The second edition makes it clear. I think a lot of the technical papers that I read are now chapters in the book. Some new chapters are simply great: Understanding Quality Attributes, Achieving Qualities, Designing the Architecture, Documenting Software Architectures, the ATAM, and the CBAM.
    I really liked the replacement of ADL with UML, the de facto standard, with all of its warts and blemishes.
    For criticism, this book was history as soon as it hit the presses. You'd still need to read SEI technical papers to be current. One of the chapters discusses the performance problems with remote entity beans and makes no reference to EJB 2.0 spec local entity beans with no performance hit on every cross-bean call. Likewise, the final chapter on "The Future" wasn't so bold as to prognosticate on OMG's current work on MDA, but they may be alluding to it with "Moving from architecture to code."
    Still more fun to read than a harlequin romance novel and readable in four days.
    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
    2 of 2 people found the following review helpful By Thomas Sprimont on May 19, 2008
    Format: Hardcover Verified Purchase
    This is a solid work on SEI's ADD methodology. The authors fully document the ADD methodology in terms of incorporating this into your practice. Clear text, diagrams, and illustrations depict how you bridge the gap between theory and practice.

    If you're looking to use, or enhance, how to leverage your use architecture, I recommend this book. ADD is a method that values the business intent of the software, and constructs a method that delivers value to the customer.

    There are some weak chapters, which prevent me from giving a 5-star rating. For example, Chapter 10 addresses reverse engineering an architecture. The focus was on a point exercise that is not useful in either theory or practice. Other case studies in the book (there are a few) were not helpful as they did not have the keys to turn the theory into practice. For example Chapter 16 addressed a J2EE/EJB study; however it was very high-level and omitted important details to be used in practice. However, the case study of an avionics system (Chapter 3) was good; it provided insight in how to apply theoretical concepts.

    I recommend this book for those organizations looking for a solid value-add approach to improving your architectures both technically, and in customer value.
    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