- Paperback: 432 pages
- Publisher: Addison-Wesley Professional; 1 edition (November 14, 1999)
- Language: English
- ISBN-10: 0321643348
- ISBN-13: 978-0321643346
- Product Dimensions: 7.5 x 0.9 x 9.4 inches
- Shipping Weight: 1.6 pounds (View shipping rates and policies)
- Average Customer Review: 6 customer reviews
- Amazon Best Sellers Rank: #6,618,451 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Applied Software Architecture (paperback) 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
"Rebound" by Kwame Alexander
Don't miss best-selling author Kwame Alexander's "Rebound," a new companion novel to his Newbery Award-winner, "The Crossover,"" illustrated with striking graphic novel panels. Pre-order today
Customers who viewed this item also viewed
What other items do customers buy after viewing this item?
From the Inside Flap
Software architecture is a recently emerged technical field, but it's not a new activity; there have always been good designers who create good software architectures. However, now the consensus is that what these designers do is qualitatively different from other software engineering activities, and we've begun figuring out how they do it and how we can teach others to do it.
Software architecture is not just a new label for an old activity; software architects today face new challenges. They are asked to produce increasingly complex software. Using the latest technologies, but these technologies are changing faster than ever. And they are asked to produce better quality software with a shorter time-to-market. Instead of seeing the architecture as necessarily complicated by these staggering requirements, we need to realize that the architecture is our most powerful tool in meeting them.
This book is a practical guide to designing, describing, and applying software architecture. The book began as a study of software architecture in industry, specifically at our company--Siemens. The study told us how practitioners define software architecture, what problems they are trying to solve with it, and how and why they choose particular architectural solutions.
We examined how architects design systems so that today's technology can be replaced with tomorrow's. We saw how the experts abstracted the essential aspects of their real-time, safety-critical reliability and performance requirements so that they could make good architectural decisions consistently. We also saw how good architecture descriptions improved the development process, making it easier to develop high-quality software in a shorter time. We saw how managers' understanding of the architecture was critical in organizing and scheduling the project. We saw how developers depended on the architecture to define interfaces and boundaries between their component and others, and to target maintenance activities.
This book also grew from our experience with software architecture as we applied the principles and techniques we saw the experts use. The description techniques helped uncover architectural problems in existing systems. The design principles guided us in defining architectures for new systems and for proposing solutions to problems in existing systems. Road Map
Part I of this book provides important background information for understanding what we mean by software architecture, and how we structure the architecture design tasks. In Part II we define the architecture design tasks, and use a running example to show how they are applied to the design of a software architecture. The example system, IS2000, is an image acquisition and processing system. We don't provide its complete architecture design, but instead describe one of its subsystems in detail. The Additional Reading section at the end of each chapter in Parts I and II dives references to sources of more information on software architecture.
Part III contains detailed descriptions of four industrial systems. These systems come from our original industrial study and they represent the state-of-the-art in software architecture. Each chapter in Part III gives a broad overview of the software architecture of a case study; These studies don't have the same level of detail as IS2000. The four systems are
Safety Vision--A half-million lines of code (LOC) instrumentation and control system for nuclear power plants Healthy Vision--A million LOC embedded patient monitoring system Central Vision--A half-million LOC centralized patient monitoring system Comm Vision--A multimillion LOC telecommunications system
The architects of these systems faced and solved some of the most difficult challenges confronting today's architects: designing large-scale, real-time, safety-critical, highly reliable systems.
In Part IV, we examine the software architect's role, describing what an architect must do beyond the software architecture design.
A Glossary and a Quick Reference to the architecture design tasks and artifacts are included at the end of the book. The four Quick Reference architecture views can also be found on the front and back endpapers.
We have selected the Unified Modeling Language (UML) to describe the software architecture, supplemented by tables or other notations when appropriate. We chose UML because it expresses well most of what we were trying to capture, and it is widely understood. Although the architecture notation is not the essential contribution of this book, we believe that a common notation and a common agreement about what is described will further the field of software architecture by improving our ability to communicate.
The main thing you'll learn from this book is a new way to tackle the problem of architecture design. You will learn what the issues are, when they should be addressed, and how they can be addressed. This book will increase your ability to recognize good solutions. Even if it does not change your eventual architectural solutions, it will help you arrive at those solutions more quickly. Guide to the Reader
There are a couple of different ways you can read this book. To get a general overview, we recommend you read Parts I and IV. For managers or others who are interested in understanding what software architecture is and how it is used, this is sufficient.
Project managers, system architects, software developers, testers, and those who want a better understanding of the four software architecture views should read, in addition, at least some of Part II. You can get this overview by reading Part II; you may skip the sections that cover the example system. Thus, read the first few pages of Part II, then the first and last sections of chapters 3 through 7. Skip Chapter 2 and Sections 3.2 through 3.7, 4.2, 5.2, 6.2, and 7.2.
After this overview, you will be well prepared to read the case studies. This is an option for students of software architecture or others who want to see the architecture of a range of applications. As you would expect, the case studies are all independent, so you can pick any or all to read. Read the introductory pages of Part III to find out more about the characteristics of each case study.
The final option is to read the whole book. This is, of course, what we recommend for software architects and all others who want a thorough understanding of software architecture. However, we don't expect you to digest Part III all at once, The case studies can be read over time, as the need or interest arises. 0201325713P04062001 --This text refers to an out of print or unavailable edition of this title.
From the Back Cover
"Designing a large software system is an extremely complicated undertaking that requires juggling differing perspectives and differing goals, and evaluating differing options. Applied Software Architecture is the best book yet that gives guidance as to how to sort out and organize the conflicting pressures and produce a successful design." -- Len Bass, author of Software Architecture in Practice.
Quality software architecture design has always been important, but in today's fast-paced, rapidly changing, and complex development environment, it is essential. A solid, well-thought-out design helps to manage complexity, to resolve trade-offs among conflicting requirements, and, in general, to bring quality software to market in a more timely fashion.
Applied Software Architecture provides practical guidelines and techniques for producing quality software designs. It gives an overview of software architecture basics and a detailed guide to architecture design tasks, focusing on four fundamental views of architecture--conceptual, module, execution, and code. Through four real-life case studies, this book reveals the insights and best practices of the most skilled software architects in designing software architecture. These case studies, written with the masters who created them, demonstrate how the book's concepts and techniques are embodied in state-of-the-art architecture design. You will learn how to:
- create designs flexible enough to incorporate tomorrow's technology;
- use architecture as the basis for meeting performance, modifiability, reliability, and safety requirements;
- determine priorities among conflicting requirements and arrive at a successful solution; and
- use software architecture to help integrate system components.
Anyone involved in software architecture will find this book a valuable compendium of best practices and an insightful look at the critical role of architecture in software development.
Author interviews, book reviews, editors picks, and more. Read it now
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
It gives a systematic introduction to several high-level notations, describing the conceptual, executable, structural (or module), and code views. Most of the notation is well-formed UML, and the authors take care to add semantic notes to every part of the graphical notation. They supplement the standard notations with a few text-based extensions. These capture requirements, archtiectural decisions, risks and risk mitigation, and other operating features of a living software project.
One real asset is the related set of brief case studies at the end of the book, three separate products with a common conceptual base. This book is aging, it dates back to 1999 - five years, as I write this. That's old in the "architecture" literature, and the authors fail to apply the "product line" notion. I take this book for its good, though, and lack of one buzzword is a small enough fault.
The book uses a process-and-pipe model pervasively for architectural description. It's a good tool, but other tools are good for other purposes, and their omission is a problem here.
Still, the book is competent on the whole. Its sustained product-line example ties the whole together, and it focusses on practice intead of mainfestos and brand-name methodologies. There's a lot of good here, and you can pick out out easily.
This book answers your questions by proposing both a technique and a language (UML extended), that will help you list the different factors affecting your project, infer the right design decisions, and document them throughout the project. For those with an analytical mind, the architecture process itself is decomposed and re-engineered. No consultant talk here : everything is explained, both in words and figures, using real world examples.
Some will regret that the application field used for the demonstration is too narrow, since only real time applications are used, and there is no reference to database architecture or e-business ! But for those of the embedded world, such a book was awaited, and browsing (too) quickly through various application fields would have contented no one, anyhow.
It is still a long reading, if you want to study all examples in depth - fortunately, you can start your own design after the first case study.
Lastly, using UML throughout the project eases the communication with the development engineers, and it really helps when your team tackles detailed design.
The organisational, product and technical factors affecting the development of a product are called out and the authors provide a means to systematically identify and classify each of these factors. The attempt to satisfy each factor inevitably leads to issues which must be addressed. By providing an issue card format that records the general solution and associated strategies, each issue can be comprehensively addressed. In fact new issues may be raised as a result of the adoption of a strategy and these new issues can be addressed in the same way.
To me this clear linkage between the factors that affect the product development, the issues that arise, and the strategies that address them, is the most outstanding attribute of this book. My only quibble is that the examples given do not encompass business sofware development.
Overall I heartily recommend this book as an excellent way of making sure that you are addressing the issues in your projects.
The best practices are simply case studies that really impart no wisdom to the reader (or, at least, to this reader).
I tried to "get something" out of this book several times, and read it fully twice. However, I'm convinced that there really isn't much there.