Example of Product Line Management Using Streams
The following illustration shows the streams structure for the development of a product-line that has three products.
Initial stream—Contains project and tracker templates that follow naming conventions, and defined configuration management permissions.
Motorcycle product-line release-1.0 stream–Contains all possible features for the first motorcycle release. For example, 250cc, 350cc, EV, ABS, and regions.
Transformed stream—Contains the product-line stream that is transformed for a particular product.
Product release stream—Contains motorcycle products. For example, Jupiter EV Release-1.0, Jupiter Gas Release-1.0, and Falcon EU ABS Release-1.0.
Change flow
Changes flow from the product-line release stream to the transformed stream and then to the product release stream.
Every stream derives structure and configuration from the stream whose changes flow into it.
Stream roles
Initial stream—Project creation, tracker configuration and template source.
Release stream—Configuration for a particular release of a product, library, or product-line.
Product-line stream—150% configuration containing items for multiple products.
Transformed stream—100% product configuration.
Product stream—Tailored configuration for a product.
Change-flow direction
Changes flow from the baseline of a source stream to a target stream
Benefits
This architecture supports:
Reuse
Controlled divergence
Parallel development
Variant-specific customization
Was this helpful?