Programming Books C Java PHP Python Learn more Browse Programming Books
  • List Price: $74.99
  • Save: $25.26 (34%)
Only 3 left in stock (more on the way).
Ships from and sold by
Gift-wrap available.
Design and Use of Softwar... has been added to your Cart
FREE Shipping on orders over $35.
Condition: Used: Good
Comment: Wear to the cover and some pages, no writing or highlighting inside!!! ITEM SHIPS FBA FROM AMAZON!!! BUY WITH CONFIDENCE!!! GET IT FAST!!!
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

Design and Use of Software Architectures: Adopting and Evolving a Product-Line Approach Paperback – May 29, 2000

ISBN-13: 978-0201674941 ISBN-10: 0201674947 Edition: 1st

Buy New
Price: $49.73
30 New from $25.51 33 Used from $0.01
Amazon Price New from Used from
"Please retry"
$25.51 $0.01

Frequently Bought Together

Design and Use of Software Architectures: Adopting and Evolving a Product-Line Approach + Software Product Lines: Practices and Patterns
Price for both: $109.71

Buy the selected items together

Shop the new
New! Introducing the, a hub for Software Developers and Architects, Networking Administrators, TPMs, and other technology professionals to find highly-rated and highly-relevant career resources. Shop books on programming and big data, or read this week's blog posts by authors and thought-leaders in the tech industry. > Shop now

Product Details

  • Paperback: 368 pages
  • Publisher: Addison-Wesley Professional; 1 edition (May 29, 2000)
  • Language: English
  • ISBN-10: 0201674947
  • ISBN-13: 978-0201674941
  • Product Dimensions: 9.2 x 7.4 x 0.7 inches
  • Shipping Weight: 1.5 pounds (View shipping rates and policies)
  • Average Customer Review: 4.0 out of 5 stars  See all reviews (4 customer reviews)
  • Amazon Best Sellers Rank: #1,276,037 in Books (See Top 100 in Books)

Editorial Reviews

From the Back Cover

In the ever-changing world of software development, organizations are gradually realizing the need for an explicit software architecture for their systems. And software engineers are potentially faced with the challenge of developing multiple, inter-related systems whilst pressured by financial and lead-time constraints. It is thus essential to establish a well-defined design method in order to build high-quality, reliable, and easily maintainable individual or families of systems - the question is how to approach this?

This book provides an achievable answer. The author proposes a method for designing software architectures, and product line architectures, which is based on his experience in industry and research,

The first part of the book introduces the design method, examining its three key phases - functionality-based architecture design, architecture assessment and architecture transformation - in detail. The second half of the book explores the concept of software product lines, incorporating elements of architectural design, component-based software engineering and reuse. It takes you through the process of designing, developing and evolving a product-line approach, including the development of software architecture and components for the family, instantiation of family members and evolution of assets. It also examines the pros and cons of a number of organizational models that can be applied when putting a software product line approach in to practice.

If you are a software architect or engineer involved in designing software systems architectures, this book will give you the resources you need for success.

· features real-life case studies covering control and real-time systems, networking, and telecommunications industry examples to illustrate how the method and processes work in practice
· provides a systematic approach that employs both qualitative and quantitative techniques for assessments
· contains key chapters on approaches to component development, and use of object-oriented frameworks as components in software product lines
· includes sections that can be read as stand-alone, depending on your level of knowledge and experience and your specific area of interest.


About the Author

 Jan Bosch is Professor of Software Engineering at the University of Karlskrona/Ronneby, Sweden. He is a key member of the RISE and ARCS groups, through which he has been involved in extensive research in the software architecture area, in conjunction with a number of companies in industry. He has also authored many articles and conference proceedings and given workshops and tutorials at a number of international conferences

More About the Author

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

Customer Reviews

4.0 out of 5 stars
Share your thoughts with other customers

Most Helpful Customer Reviews

36 of 39 people found the following review helpful By Mike Tarrani HALL OF FAMETOP 50 REVIEWER on April 30, 2001
Format: Paperback
This book provides an interesting and comprehensive approach to designing software architectures. The author crystalized four concepts that have greatly influenced on my thinking: (1)focus on quality attributes during the design and evaluation, (2) a rich set of evaluation techniques, (3) dimensional views of the architecture design, and (4) a realistic approach to reusability.
The author's treatment of quality attributes provides a good foundation for the design process. The author's method of linking quality attributes to quality requirements is plain good practice and bears careful reading. Traceability in any engineering or design effort is essential and the approach proposed needs to be included early in the life cycle.
There are major four evaluation techniques covered in the book: Scenario-based that examines software qualities within the context of scenarios; simulation techniques that model the architecture in a simulation environment; mathematical modeling that uses statistics, probability and other techniques to predict qualities such as reliability, etc.; and experienced-based reasoning (see Brooks' Mythical Man Month for a good explanation of that!).
Among the most powerful concepts presented is dimensional views, which decompose the architecture into component and system views; business, organization, process and technology views; and development, usage and evolution views. This approach ensures that an architecture's design proceeds in accordance with findings from a thorough analysis, and that all factors be considered and incorporated into the design. If you are a proponent of SEI's Architecture Trade-off Analysis Method (ATAM) you will see some similarities.
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
15 of 17 people found the following review helpful By wiredweird HALL OF FAMETOP 500 REVIEWER on July 5, 2004
Format: Paperback Verified Purchase
I had much higher hopes for this book. The idea of software architecture is finally coming into its own as a field of study. That includes the levels above individual software systems, including highly configurable systems and whole corporate product families. The subtitle, "Adopting and evolving a product line approach," looked promising.
A few things early on left me skeptical. Section I.4.1, for example, discusses quality factors of an architecture. The approach is completely retrospective, though. It only looks backwards at what emerged in a system, not forwards into how a system should be designed. I agree with section I.5.5 that some quality requirement X will be implemented across some set of system modules. Summing that quality's presence across all modules to add up to X is a positively dangerous mis-statement. The strength of a chain is in all of its links, but is not the sum of the link strengths - the strength of a system's security is not increased by adding yet more insecure modules.
The treatment of "software science" metrics is deplorably shallow. If you must use that approach, it's best to use a wide variety of indicators with different sensitivities, ideally indicators that don't depend on the programming language. The author stops with one metric, a graph-theoretic number that would be nearly impossible to apply to XSLT, Prolog, UI specification systems, database schemata, and so on. "Experience-based assessment" proposes the use of external assessment teams, without suggesting any way of guaging that team's ability. The discussion of processes vs. threads, with respect to program reliability misses the most critical point: that processes normally have hardware memory protection and threads don't.
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
0 of 2 people found the following review helpful By M. Bjerke on April 10, 2006
Format: Paperback
I had this book for a class at post graduate school. The material in the book is good, but it is unfortunate how difficult reading the book is. I think the reason for this is the translation from another language.

Aside from the english of the book, the arguments presented are down so in a very logical progression and made very well.
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 17 people found the following review helpful By ws__ on March 27, 2002
Format: Paperback
This book is certainly not for beginners. You already have to know a lot about software architecture to meaningfully read it.
It is very abstract, elegant and bright. The reading style is still amazingly light. If you are in the know you are delighted to read about it in such an elegant way. If you are not in the know you will have trouble to develop a concrete idea and to digest all those different aspects on so few pages.
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

What Other Items Do Customers Buy After Viewing This Item?