A Framework for Software Product Line Practice, Version 5.0
The product development activity depends on the three outputs described abovethe product line scope, the core assets, and the production planplus the product description for each individual product. The following figure illustrates these relationships.
Once more, the rotating arrows indicate iteration and intricate relationships. For example, the existence and availability of a particular product may well affect the requirements for a subsequent product. As another example, building a product that has previously unrecognized commonality with another product already in the product line will create pressure to update the core assets and provide a basis for exploiting that commonality for future products.
The inputs for the product development activity are as follows:
- the product description for a particular product, often expressed as a delta or variation from some generic product description contained in the product line scope (such a generic description is, itself, a core asset)
- the product line scope, which indicates whether it's feasible to include the product under consideration in the product line
- the core assets from which the product is built
- the production plan, which details how the core assets are to be used to build the product
Product builders use the core assets, in accordance with the production plan, to produce products that meet their respective requirements. Product builders also have an obligation to give feedback on any problems or deficiencies encountered with the core assets, so the core asset base remains healthy and viable.