Home > Store

Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures

Register your product to gain access to bonus material or receive a coupon.

Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures


  • Sorry, this book is no longer in print.
Not for Sale


  • Copyright 2005
  • Dimensions: 7" x 9-1/4"
  • Pages: 736
  • Edition: 1st
  • Book
  • ISBN-10: 0-201-77595-6
  • ISBN-13: 978-0-201-77595-2

"Designing Software Product Lines with UML is well-written, informative, and addresses a very important topic. It is a valuable contribution to the literature in this area, and offers practical guidance for software architects and engineers."
—Alan Brown
Distinguished Engineer, Rational Software, IBM Software Group

"Gomaa's process and UML extensions allow development teams to focus on feature-oriented development and provide a basis for improving the level of reuse across multiple software development efforts. This book will be valuable to any software development professional who needs to manage across projects and wants to focus on creating software that is consistent, reusable, and modular in nature."
—Jeffrey S Hammond
Group Marketing Manager, Rational Software, IBM Software Group

"This book brings together a good range of concepts for understanding software product lines and provides an organized method for developing product lines using object-oriented techniques with the UML. Once again, Hassan has done an excellent job in balancing the needs of both experienced and novice software engineers."
—Robert G. Pettit IV, Ph.D.
Adjunct Professor of Software Engineering, George Mason University

"This breakthrough book provides a comprehensive step-by-step approach on how to develop software product lines, which is of great strategic benefit to industry. The development of software product lines enables significant reuse of software architectures. Practitioners will benefit from the well-defined PLUS process and rich case studies."
—Hurley V. Blankenship II
Program Manager, Justice and Public Safety, Science Applications International Corporation

"The Product Line UML based Software engineering (PLUS) is leading edge. With the author's wide experience and deep knowledge, PLUS is well harmonized with architectural and design pattern technologies."
—Michael Shin
Assistant Professor, Texas Tech University

Long a standard practice in traditional manufacturing, the concept of product lines is quickly earning recognition in the software industry. A software product line is a family of systems that shares a common set of core technical assets with preplanned extensions and variations to address the needs of specific customers or market segments. When skillfully implemented, a product line strategy can yield enormous gains in productivity, quality, and time-to-market. Studies indicate that if three or more systems with a degree of common functionality are to be developed, a product-line approach is significantly more cost-effective.

To model and design families of systems, the analysis and design concepts for single product systems need to be extended to support product lines. Designing Software Product Lines with UML shows how to employ the latest version of the industry-standard Unified Modeling Language (UML 2.0) to reuse software requirements and architectures rather than starting the development of each new system from scratch. Through real-world case studies, the book illustrates the fundamental concepts and technologies used in the design and implementation of software product lines.

This book describes a new UML-based software design method for product lines called PLUS (Product Line UML-based Software engineering). PLUS provides a set of concepts and techniques to extend UML-based design methods and processes for single systems in a new dimension to address software product lines. Using PLUS, the objective is to explicitly model the commonality and variability in a software product line.

Hassan Gomaa explores how each of the UML modeling views—use case, static, state machine, and interaction modeling—can be extended to address software product families. He also discusses how software architectural patterns can be used to develop a reusable component-based architecture for a product line and how to express this architecture as a UML platform-independent model that can then be mapped to a platform-specific model.

Key topics include:

  • Software product line engineering process, which extends the Unified Development Software Process to address software product lines
  • Use case modeling, including modeling the common and variable functionality of a product line
  • Incorporating feature modeling into UML for modeling common, optional, and alternative product line features
  • Static modeling, including modeling the boundary of the product line and information-intensive entity classes
  • Dynamic modeling, including using interaction modeling to address use-case variability
  • State machines for modeling state-dependent variability
  • Modeling class variability using inheritance and parameterization
  • Software architectural patterns for product lines
  • Component-based distributed design using the new UML 2.0 capability for modeling components, connectors, ports, and provided and required interfaces
  • Detailed case studies giving a step-by-step solution to real-world product line problems

Designing Software Product Lines with UML is an invaluable resource for all designers and developers in this growing field. The information, technology, and case studies presented here show how to harness the promise of software product lines and the practicality of the UML to take software design, quality, and efficiency to the next level. An enhanced online index allows readers to quickly and easily search the entire text for specific topics.

Sample Content

Online Sample Chapter

Developing Software Lines: Why Bother?

Downloadable Sample Chapter

Download the Sample Chapter related to this title.

Table of Contents





1. Introduction.

Software Reuse.

Software Product Lines.

Modeling Requirements Variability in Software Product Lines: Feature Modeling.

Modeling Design Variability in Software Product Lines.

Reusable Design Patterns.

Modeling Single Systems with UML.

COMET: A UML-Based Software Design Method for Single Systems.

Modeling Software Product Lines with UML.

UML as a Standard.

Related Texts.


2. Design Concepts for Software Product Lines.

Object-Oriented Concepts.

Information Hiding.

Relationships between Classes.

Dynamic Modeling.

Sequential and Concurrent Applications.

Software Architecture and Components.


3. Software Product Line Engineering.

Evolutionary Software Product Line Engineering Process.

Software Product Line Engineering Phases.

Forward and Reverse Evolutionary Engineering.

Integration of PLUS with the Spiral Model.

Integration of PLUS with Unified Software Development Process.

Requirements, Analysis, and Design Modeling in Software Product Lines.

Software Product Line Scoping.



4. Use Case Modeling for Software Product Lines.

The Use Case Model in Single Systems.

The Use Case Model for Software Product Lines.

Identifying Use Cases.

Documenting Product Line Use Cases.

Example of a Use Case Description.

Modeling Variability in Use Cases.

Modeling Small Variations.

Modeling Variability with the Extend Relationship.

Modeling Variability with the Include Relationship.

Use Case Development Strategies.


5. Feature Modeling for Software Product Lines.

Introduction to Feature Analysis.

Commonality/Variability Feature Analysis.

Features and Use Cases.

Feature Modeling with UML.

Feature Groups.

Advanced Feature Modeling with UML.


6. Static Modeling in Software Product Lines.

Modeling Commonality and Variability in Product Lines.

Static Modeling of the Software Product Line Problem Domain.

Static Modeling of the Software Product Line Scope.

Static Modeling of Entity Classes.

Modeling Application Classes and Objects.


7. Dynamic Interaction Modeling for Software Product Lines.

Dynamic Modeling in Single Systems.

Evolutionary Dynamic Modeling in Software Product Lines.

Kernel First Approach.

Software Product Line Evolution Approach.

Message Sequence Numbering on Interaction Diagrams.

Example of Evolutionary Dynamic Analysis for the Microwave Oven Product Line.


8. Finite State Machines and Statecharts for Software Product Lines.

Finite State Machines for Kernel and Single Systems.

Hierarchical Statecharts.

Finite State Machines and Statecharts for Software Product Lines.

Inherited State Machines in Software Product Lines.

Parameterized State Machines in Software Product Lines.

Comparison of Approaches.

Kernel First Approach: State-Dependent Dynamic Analysis.

Software Product Line Evolution Approach.

Dynamic Analysis with Communi


Untitled Document This is a book about software product lines (known in Europe as software product families), which are families of software systems that have some commonality and some variability. The goal of developing software product lines is software reuse-from reuse of software requirements through reuse of software code. The promise of large scale software reuse has been a goal of the software industry since the dawn of software engineering in the late sixties. However, it has proved an elusive goal.

Software reuse is a subject that most of the larger corporations are facing. To reuse software is to improve productivity (less new software has to be built) and quality (presumably the existing software has been tested and errors have been corrected). Various technologies have been proclaimed as the solution to the software reuse problem, from subroutines to modular software to object-oriented programming to component-based programming. Each of these technologies made a contribution but the overall result in general has been much less than hoped. A major problem with these technologies is that the emphasis is on code reuse. Numerous studies have indicated that coding is only around 20% of the total cost of software development; hence improvements in coding will only be of limited value. Much greater payoff is likely from reuse of software requirements and architectures, which is the goal of software product lines.

I have long been an advocate of large scale software reuse. In a book I wrote together with Martin Griss and Patrik Jonsson on product line engineering in 1997, we addressed architecture, process and organization for software reuse. Product line engineering is about reuse of all artifacts, such as software requirements, analysis, designs including architectures, and test-not just code reuse.

Hassan Gomaa's book is taking a step forward. In particular, he follows the distinction between use cases and features made by Martin Griss in a 1998 paper: use cases are user oriented, with the objective of determining the functional requirements of the product line, whereas features are reuser oriented with the objective of organizing the results of a product line commonality and variability analysis. Following this distinction, Gomaa describes how features can be determined from the product line use case model, by analyzing kernel, optional, and alternative use cases, as well as use case variation points. He uses this analysis as a basis for describing product line commonality by means of common features, and product line variability by means of optional and alternative features, as well as feature groups that constrain how related features can be used by a product line member.

The book also describes how software architectural patterns for product lines can be used as a starting point for developing a reusable software architecture. In addition, it describes how commonality and variability can be modeled in component-based software architectures using the new UML 2.0 notation for composite structure diagrams.

Hassan clearly has a command of how to tie feature-based analysis and use case analysis together. I feel that this is the strongest part of the work, and is an area that is sorely lacking in most UML treatments.

Ivar Jacobson
April 2004


Download the Index file related to this title.


Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020