by Len Bass, Paul Clements, Rick Kazman, Ken Bass
Amazon Price: $45.95
Availability: Usually ships within 24 hours.
Hardcover - 452 pages (January 1998)
Addison-Wesley Pub Co; ISBN: 0201199300 ;
Dimensions (in inches): 1.46 x 9.55 x 6.57
Amazon.com Sales Rank: 9,228
Book Description
This book introduces the concepts and practices of software architecture-what a software system is designed to do and how that system's components are meant to interact with each other. An architecture is an abstract view distinct from the details of implementation, algorithm, and data representation. Architecture is, increasingly, a crucial part of a software organization's business strategy because it is a reusable asset that can be reapplied to subsequent systems. Reuse leads to the architecture business cycle, allowing an organization to leverage the effort invested in an architecture to enter whole new business areas.
Drawing on their extensive experience building and evaluating architectures, the authors cover the essential technical topics for specifying and validating a system. For the first time in a book, 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 constraints and the opportunities that companies encounter. To that end, key points of both technical and organizational discussions are illuustrated by a selection of "industrial-strength" case studies. These studies, undertaken by the authors and the Software Engineering Institute, describe how successful architectures have led to the fulfillment of demanding requirements and enhanced an organization's position in its business community.
If you design, develop, or manage the building of large software systems, or if you have an interest in acquiring such systems for your corporation or government agency, use this book to quickly get you up to speed on software architecture.
Synopsis
The concepts and practice of software architecture are introduced--what a system is
designed to do and how its components are meant to interact with each other. The authors
cover not only essential technical topics for specifying and validating a system, but, for
the first time, emphasize the importance of the business context in which large systems
are designed. .
About the Authors
Dr. Len Bass is a senior software engineer at the Software Engineering Institute
(SEI). He has written or edited five books and numerous papers on software engineering,
human-computer interaction, and other topics. He headed a group that developed a software
architecture for flight-training simulators that has been adopted as a U.S. Air Force
standard.
Dr. 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 over three dozen papers on software design and real-time systems.
Dr. Rick Kazman is a senior software engineer at the SEI, where he leads the Architecture Tradeoff Analysis initiative, and Adjunct Professor of Computer Science at the University of Waterloo and the University of Toronto. He is the author of more than fifty papers in the areas of software engineering, human-computer interaction, and information retrieval.
