Book description
"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.
Table of contents
- Copyright
- Praise for Designing Software Product Lines with UML
- The Addison-Wesley Object Technology Series
- The Component Software Series
- Foreword
-
Preface
- Overview
- What This Book Provides
- The PLUS Advantage
- Intended Audience
- Ways to Read This Book
-
Annotated Table of Contents
- Chapter 1: Introduction
- Chapter 2: Design Concepts for Software Product Lines
- Chapter 3: Software Product Line Engineering
- Chapter 4: Use Case Modeling for Software Product Lines
- Chapter 5: Feature Modeling for Software Product Lines
- Chapter 6: Static Modeling in Software Product Lines
- Chapter 7: Dynamic Interaction Modeling for Software Product Lines
- Chapter 8: Finite State Machines and Statecharts for Software Product Lines
- Chapter 9: Feature/Class Dependency Modeling for Software Product Lines
- Chapter 10: Architectural Patterns for Software Product Lines
- Chapter 11: Software Product Line Architectural Design: Component-Based Design
- Chapter 12: Software Application Engineering
- Chapter 13: Microwave Oven Software Product Line Case Study
- Chapter 14: Electronic Commerce Software Product Line Case Study
- Chapter 15: Factory Automation Software Product Line Case Study
- Appendix A: Overview of the UML Notation
- Appendix B: Catalog of Software Architectural Patterns
- Contact
- Acknowledgments
-
I. Overview
-
1. Introduction
- 1.1. Software Reuse
- 1.2. Software Product Lines
- 1.3. Modeling Requirements Variability in Software Product Lines: Feature Modeling
- 1.4. Modeling Design Variability in Software Product Lines
- 1.5. Reusable Design Patterns
- 1.6. Modeling Single Systems with UML
- 1.7. COMET: A UML-Based Software Design Method for Single Systems
- 1.8. Modeling Software Product Lines with UML
- 1.9. UML as a Standard
- 1.10. Related Texts
- 1.11. Summary
- 2. Design Concepts for Software Product Lines
-
3. Software Product Line Engineering
- 3.1. Evolutionary Software Product Line Engineering Process
- 3.2. Software Product Line Engineering Phases
- 3.3. Forward and Reverse Evolutionary Engineering
- 3.4. Integration of PLUS with the Spiral Model
-
3.5. Integration of PLUS with Unified Software Development Process
- 3.5.1. Unified Software Development Process
- 3.5.2. How PLUS Relates to USDP
- 3.5.3. Inception
- 3.5.4. Elaboration—Iteration #1: Kernel First
- 3.5.5. Elaboration—Iteration #2: Product Line Evolution
- 3.5.6. Construction—Iteration #1: Construction of the Kernel Components
- 3.5.7. Transition—Iteration #1: Testing of the Kernel System
- 3.5.8. Further Iterations of Product Line Engineering
- 3.5.9. The Unified Process with Software Application Engineering
- 3.6. Requirements, Analysis, and Design Modeling in Software Product Lines
- 3.7. Software Product Line Scoping
- 3.8. Summary
-
1. Introduction
-
II. Requirements, Analysis, and Design Modeling for Software Product Lines
-
4. Use Case Modeling for Software Product Lines
- 4.1. The Use Case Model in Single Systems
- 4.2. The Use Case Model for Software Product Lines
- 4.3. Identifying Use Cases
- 4.4. Documenting Product Line Use Cases
- 4.5. Example of a Use Case Description
- 4.6. Modeling Variability in Use Cases
- 4.7. Modeling Small Variations
- 4.8. Modeling Variability with the Extend Relationship
- 4.9. Modeling Variability with the Include Relationship
- 4.10. Use Case Development Strategies
- 4.11. Summary
- 5. Feature Modeling for Software Product Lines
- 6. Static Modeling in Software Product Lines
-
7. Dynamic Interaction Modeling for Software Product Lines
- 7.1. Dynamic Modeling in Single Systems
- 7.2. Evolutionary Dynamic Modeling in Software Product Lines
- 7.3. Kernel First Approach
- 7.4. Software Product Line Evolution Approach
- 7.5. Message Sequence Numbering on Interaction Diagrams
- 7.6. Example of Evolutionary Dynamic Analysis for the Microwave Oven Product Line
- 7.7. Summary
-
8. Finite State Machines and Statecharts for Software Product Lines
- 8.1. Finite State Machines for Kernel and Single Systems
- 8.2. Hierarchical Statecharts
- 8.3. Finite State Machines and Statecharts for Software Product Lines
- 8.4. Inherited State Machines in Software Product Lines
- 8.5. Parameterized State Machines in Software Product Lines
- 8.6. Comparison of Approaches
- 8.7. Kernel First Approach: State-Dependent Dynamic Analysis
- 8.8. Software Product Line Evolution Approach
- 8.9. Dynamic Analysis with Communicating State-Dependent Objects
- 8.10. Summary
- 9. Feature/Class Dependency Modeling for Software Product Lines
-
10. Architectural Patterns for Software Product Lines
- 10.1. Categorization of Software Patterns
-
10.2. Software Architectural Structure Patterns
- 10.2.1. Layers of Abstraction Architectural Pattern
- 10.2.2. Kernel Architectural Pattern
- 10.2.3. Client/Server Architectural Pattern
- 10.2.4. Broker Architectural Pattern
- 10.2.5. Client/Agent/Server Architectural Pattern
- 10.2.6. Centralized Control Architectural Pattern
- 10.2.7. Distributed Control Architectural Pattern
- 10.2.8. Hierarchical Control Architectural Pattern
- 10.2.9. Implications of Control Patterns
- 10.2.10. Communicating Components Architectural Pattern
-
10.3. Software Architectural Communication Patterns
- 10.3.1. Asynchronous Message Communication Pattern
- 10.3.2. Bidirectional Asynchronous Message Communication Pattern
- 10.3.3. Synchronous Message Communication with Reply Pattern
- 10.3.4. Asynchronous Message Communication with Callback Pattern
- 10.3.5. Synchronous Message Communication without Reply Pattern
- 10.3.6. Broker Communication Patterns
- 10.3.7. Discovery Pattern
- 10.3.8. Group Message Communication Patterns
- 10.3.9. Negotiated Communication Patterns
- 10.3.10. Product Line Implications of Communication Patterns
- 10.4. Software Architectural Transaction Patterns
- 10.5. Documenting Software Architectural Patterns
- 10.6. Applying Software Architectural Patterns
- 10.7. Summary
-
11. Software Product Line Architectural Design: Component-Based Design
- 11.1. Software Architecture Issues
- 11.2. Configurable Architectures and Software Components
- 11.3. Steps in Designing Distributed Applications
- 11.4. Design of Software Architecture
- 11.5. Design of Component-Based Software Architecture
- 11.6. Separation of Concerns in Component Design
- 11.7. Aggregate and Composite Subsystems
- 11.8. Component Structuring Criteria
- 11.9. Design of Server Components
- 11.10. Distribution of Data
- 11.11. Design of Component Interfaces
- 11.12. Design of Components
- 11.13. Summary
-
12. Software Application Engineering
- 12.1. Phases in Software Application Engineering
- 12.2. Software Application Engineering with the USDP
- 12.3. Application Deployment
- 12.4. Tradeoffs in Software Application Engineering
-
12.5. Example of Software Application Engineering
- 12.5.1. Feature Model for the Microwave Oven Application
- 12.5.2. Use Case Model for the Microwave Oven Application
- 12.5.3. Static Model for the Microwave Oven Application
- 12.5.4. Dynamic Model for the Microwave Oven Application
- 12.5.5. Feature/Class Dependency for the Microwave Oven Application
- 12.5.6. Software Architecture for the Microwave Oven Application
- 12.6. Summary
-
4. Use Case Modeling for Software Product Lines
-
III. Case Studies
-
13. Microwave Oven Software Product Line Case Study
- 13.1. Problem Description
- 13.2. Use Case Modeling
- 13.3. Feature Modeling
- 13.4. Static Modeling
- 13.5. Dynamic Modeling
-
13.6. Software Product Line Evolution
- 13.6.1. Impact Analysis of the Beeper Feature
- 13.6.2. Impact Analysis of the Multi-Line Display Feature
- 13.6.3. Impact Analysis of the Display Language Feature
- 13.6.4. Impact Analysis of the Light Feature
- 13.6.5. Impact Analysis of the Turntable Feature
- 13.6.6. Impact Analysis of the Minute Plus Feature
- 13.6.7. Impact Analysis of the Power Level and Multi-level Heating Features
- 13.6.8. Impact Analysis of the TOD Clock Feature
- 13.6.9. Impact Analysis of the Recipe Feature
- 13.6.10. Impact Analysis of the Statechart for Microwave Oven Control
- 13.6.11. Impact Analysis of the Statechart for Oven Timer
- 13.7. Feature/Class Dependency Analysis
-
13.8. Design Modeling
- 13.8.1. Component-Based Software Architecture
- 13.8.2. Architectural Communication Patterns
- 13.8.3. System Deployment
- 13.8.4. Product Line Evolution: Optional and Variant Components
- 13.8.5. Product Line Evolution: Component Communication
- 13.8.6. Product Line Architecture and Component Interfaces
- 13.8.7. Design of Composite Components
- 13.9. Software Application Engineering
-
14. Electronic Commerce Software Product Line Case Study
- 14.1. Problem Description
- 14.2. Use Case Modeling
- 14.3. Feature Modeling
- 14.4. Static Modeling
- 14.5. Dynamic Modeling
-
14.6. Software Product Line Evolution
- 14.6.1. Dynamic Modeling for Create Requisition
- 14.6.2. Dynamic Modeling for Confirm Delivery
- 14.6.3. Dynamic Modeling for Send Invoice
- 14.6.4. Dynamic Modeling for Prepare Purchase Order
- 14.6.5. Dynamic Modeling for Deliver Purchase Order
- 14.6.6. Dynamic Modeling for Check Customer Account
- 14.6.7. Dynamic Modeling for Bill Customer
- 14.7. Feature/Class Dependency Analysis
- 14.8. Design Modeling
- 14.9. Software Application Engineering
-
15. Factory Automation Software Product Line Case Study
- 15.1. Problem Description
- 15.2. Use Case Modeling
- 15.3. Feature Modeling
- 15.4. Static Modeling
- 15.5. Dynamic Modeling
-
15.6. Software Product Line Evolution
- 15.6.1. Communication Diagrams for High-Volume Manufacturing Use Cases
- 15.6.2. Communication Diagrams for Workflow and Work Order Use Cases
- 15.6.3. Dynamic Modeling of High-Volume Manufacturing
- 15.6.4. Statechart for Line Workstation Controller
- 15.6.5. Communication Diagrams for Manufacture High-Volume Part Use Cases
- 15.6.6. Dynamic Modeling of Flexible Manufacturing Use Cases
- 15.6.7. Statechart for Part Agent
- 15.6.8. Communication Diagrams for Flexible Manufacturing Use Cases
- 15.6.9. Dynamic Modeling for Flexible Workstation Control
-
15.7. Feature/Class Dependency Analysis
- 15.7.1. Common Feature and Kernel Classes
- 15.7.2. Optional Features and Classes
- 15.7.3. Alternative High-Volume Manufacturing Features and Feature/Class Dependencies
- 15.7.4. Alternative Flexible Manufacturing Features and Feature/Class Dependencies
- 15.7.5. Alternative Factory Monitoring Feature and Feature/Class Dependencies
- 15.8. Design Modeling
- 15.9. Software Application Engineering
- A. Overview of the UML Notation
-
B. Catalog of Software Architectural Patterns
- B.1. Software Architectural Structure Patterns
-
B.2. Software Architectural Communication Patterns
- B.2.1. Asynchronous Message Communication Pattern
- B.2.2. Asynchronous Message Communication with Callback Pattern
- B.2.3. Bidirectional Asynchronous Message Communication Pattern
- B.2.4. Broadcast Pattern
- B.2.5. Broker Forwarding Pattern
- B.2.6. Broker Handle Pattern
- B.2.7. Discovery Pattern
- B.2.8. Negotiation Pattern
- B.2.9. Subscription/Notification Pattern
- B.2.10. Synchronous Message Communication with Reply Pattern
- B.2.11. Synchronous Message Communication without Reply Pattern
- B.3. Software Architectural Transaction Patterns
- Glossary
- Bibliography
-
13. Microwave Oven Software Product Line Case Study
Product information
- Title: Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures
- Author(s):
- Release date: July 2004
- Publisher(s): Addison-Wesley Professional
- ISBN: None
You might also like
book
Applying Use Case Driven Object Modeling with UML: An Annotated e-Commerce Example
is a practical, hands-on guide to putting use case methods to work in real-world situations. This …
book
Designing Software Architectures: A Practical Approach
will teach you how to design any software architecture in a systematic, predictable, repeatable, and cost-effective …
book
UML for Database Design
The Unified Modeling Language (UML), the standard graphical notation for modeling business and software application needs, …
book
Object-oriented Programming Using C++ and Java
This book offers contemporary, comprehensive and in-depth coverage of all the concepts of object-oriented technologies, with …