Software Product Lines Collection
This collection includes two decades of SEI work on software product lines.
Software Engineering Institute
A software product line is a set of software-intensive systems that share a common, managed set of features satisfying the specific needs of a particular market segment or mission and that are developed from a common set of core assets in a prescribed way.
Software product lines are emerging as a viable and important development paradigm allowing companies to realize order-of-magnitude improvements in time to market, cost, productivity, quality, and other business drivers. Software product line engineering can also enable rapid market entry and flexible response, and provide a capability for mass customization.
Product lines can help organizations overcome the problems caused by resource shortages. Organizations of all types and sizes have discovered that a product line strategy, when skillfully implemented, can produce many benefits—and ultimately give the organizations a competitive edge. Example organizational benefits include:
- Improved productivity
- Increased quality
- Decreased cost
- Decreased labor needs
- Decreased time to market
- Ability to move into new markets in months, not years
This collection includes two decades of SEI work on software product lines.
This document describes the activities and practices in which an organization must be competent before it can benefit from fielding a product line of software systems.
The Arcade Game Maker product line is an example product line created to support learning about and experimenting with software product lines in the classroom.
This report describes the experience of a company that builds large, complex, embedded, real-time shipboard command-and-control systems as a product line.
Presented: June 2005
Presented at the SEI Army Software Product Line Workshop, February 12, 2009.
A Product Line Architecture for Army Aviation Diagnostics and Maintenance: Views and Evolution (SATURN 2007)
This presentation was given at the 2007 SATURN workshop, held in Pittsburgh.
This 2004 report presents the results of a study that focused on how product line organizations create products.
This report describes the architecture reconstruction process that was followed when the SEI performed architecture reconstructions on three small automotive motor systems.
This report presents a vision for software product lines as an acquisition focus and suggests extensions to current Department of Defense policy and practices to increase the awareness of and receptivity to product line acquisition.
This 2000 report provides background information to inform other reports in an SEI-published series of reports designed to provide concise and usable information about product line acquisition practices.
Bottom-Up Software Product Line Design A Case Study Emphasizing the Need for Stakeholder Commitment (SATURN 2009)
This 2009 presentation describes a software product line architecture (PLA) intended to increase reuse while ensuring faster time to market for new applications within the robotics domain.
Business Process Lines to Develop Service-Oriented Architectures through the Software Product Lines paradigm
This presentation on business process lines to service-oriented architecture through the software product lines paradigm was delivered by five members of the University of Bari in 2008.
This report documents NUWC's approach for measurement by describing the Goal-Driven Software Measurement approach and providing early results of the measurement program.
This case study describes a DoD weapon system development effort and compares the current way of developing software systems to the product line approach.
A presentation from the Large Scale track at SATURN 2012, May 7-11, 2012, St Petersburg, FL.
Combining Product Line Engineering and Service Oriented Architecture in Health Care Infrastructure Systems: Experience Report
This 2008 presentation was delivered by Jörg Bartholdt, Bernd Franke, C. Schwanninger, and Michael Stal of Siemens AG.
This 2001 report is a case study of the Control Channel Toolkit (CCT), a software asset base for a software product line of ground-based spacecraft command and control systems built under the direction of the NRO.
This 2001 report describes the approach a DoD organization used to develop alternative acquisition strategies and analyzes the pros and cons of each.
Some basics of software product line practice, the challenges that make product line acquisition unique, and three basic acquisition strategies are all part of this white paper.
This 2009 report describes a technique for formulating the production strategy of a production system.
This presentation provides an overview of the SCAMPI appraisal method.
This 1999 report provides guidelines for an organization that is developing a CONOPS document.
This 2002 technical report provides guidance for creating, using, and evaluating a production plan, which is a description of how core assets are to be used to develop a product in a product line.
This 2000 report provides guidance for DoD organizations for mining legacy systems to obtain core assets that will fit into a previously defined software architecture for a product line.
This TSP Symposium 2014 presentation introduces software product line development, essential activities and underlying practices, and costs and benefits of adoption.
In this 2005 presentation, Linda M. Northrop of the Software Engineering Institute (SEI) provides an introduction to software product line acquisition.
This 1996 report introduces an approach that will help managers make resource allocation decisions.
This report highlights the mutual benefits of combining systematic reuse approaches from product line development with flexible approaches for implementing business processes in a service oriented architecture.
MAP and OAR Methods: Techniques for Developing Core Assets for Software Product Lines from Existing Assets
This 2002 report describes the MAP and OAR methods, the activities that each involves, and examples of applying them.
This 2003 report characterizes the status of measurement associated with the operation of a software product line, suggests a small set of measures to support its management, and provides guidance for those establishing measurement activities within a software product line.
This 2000 report outlines four basic steps that are required to successfully mine assets.
This presentation from SATURN 2011 codifies the the architecture knowledge required for evoloving products in a given viewpoint.
Presented at the SEI Army Software Product Line Workshop, February 12, 2009
This 2005 report provides an end-to-end view of the activities that are needed to support the automatic derivation of products within a software product line.
This 1999 paper presents the basics of product line practices and reports the results of two DoD product line workshops in which important issues and successful practices were shared.
This 2006 report chronicles the decisions a program manager might face in considering the adoption of a product line approach.
This bibliography lists SEI and non-SEI resources that have informed the SEI Product Lines efforts. Examples cover diverse domains and show the kind of improvements you can achieve using a product line approach.
Three diagnostic tools for understanding an organization's readiness for and initial approach to software product lines
This 2004 report introduces a variant of the Factory Pattern called the Adoption Factory pattern that provides a generic roadmap to guide a manageable, phased product line adoption strategy.
This presentation introduces the concept of strategic, planned reuse and a new way of conducting one's software business.
This 2003 presentation on Software Product Lines in Acquisition was delivered by Grady Campbell of the Software Engineering Institute (SEI) in January 2003.
This book provides a framework of specific practices, with detailed case studies, to guide the implementation of product lines in your organization.
This presentation on Software Product Lines: Reuse That Makes Business Sense was delivered by Linda M. Northrop of the Software Engineering Institute (SEI) in April 2006.
This report expands on the testing practice area described by Clements and Northrop. Test-related activities that can be used to form the test process for a product line organization are described.
This technical note examines three key DoD acquisition policies and regulations, along with their implications for launching a product line.
This report offers a case study of organizations that have adopted a software product line approach for developing a family of software-intensive systems.
This 2005 report describes the concepts needed when creating core assets with included variability. These concepts provide guidelines to core asset creators on how to model the variability explicitly, so it is handled consistently throughout the product line and managing the variability becomes feasible.