A primary benefit of tracking Product Line Requirements in the same Technical Specification is that a Column based side-by-side comparison for specific Values of each Requirement across the entire Product Line is a natural outcome.
Columns can be selected and placed to meet the specific needs of a target audience and the Column layout can be saved for later retrieval. Also, access to edit a Product Line Application Configuration can be controlled per Configuration as necessary.
Other Configurations can be defined to manage Subject Matter Expert recommended values, and benchmark or trade-study values for similar products.
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
| File | MIME type | Size (KB) | Language | Download | |
|---|---|---|---|---|---|
| Product_Line_Requirements_Management_-_Michael_Sutherland_(paper).pdf | application/pdf | 136.91 KB | English | DOWNLOAD! |
Provides definitions
Abstract
Product development organizations use design reuse strategies to build common subsystems for the complex systems they develop and the many customers these systems are delivered to. Sub-systems are designed with an Architecture that will allow for strategic reuse. A base design for a sub-system is designed, with
some reasonable modifications for specific Applications, to meet the requirements of the systems the subsystem will be incorporated into. This paper provides details on a strategy for
Requirement Management across Product Lines that has successfully been deployed within a large Product Development and Manufacturing organization.