With an understanding of the integrated tools and their artifacts it is critical to define how they will be organized
in the tools to support product line engineering. For example, your organization may create products for the automotive
industry, you need to decide will a project area in DOORS Next Generation be used for capturing requirements for a
product variant. Or, will a project area be used for a larger context and attributes and tags will be used.
Mapping the key terms introduced earlier like "platform", "product", "variant", "system", "sub-system", and "component"
into the tool organization is a critical part of adopting PLE . Below are some sample information model mappings.
DOORS Next Gen (DNG)
|
DNG Element
|
PLE Element
|
|
Project Area
|
Platform
|
|
Artifact Types
|
Features, Functions, Business Requirements, System Requirements, Component
Requirements, Design Specifications
|
|
Attributes
|
Use for classification of variants
|
|
Collection
|
Use for attribute selection of variants
|
|
Stream
|
Create one per product variant
|
Rational Team Concert (RTC)
|
RTC Element
|
PLE Element
|
|
Project Area
|
Platform
|
|
Plans
|
Connect to RQM test plans
|
|
Streams
|
Create one per variant
|
|
Components
|
Define directory structure to share with third party suppliers
|
|
Baselining
|
Create stream baseline and promote to RELM
|
|
Dashboards
|
Connect dashboards to reporting tools (RPE, Insight)
|
|
Work Items
|
Connect suppliers to work items for notification of delivery
|
|
Team Area
|
People need to participate on multiple teams and different roles
|
|
Workflow & Process Configuration
|
Drive process enforcement using RMC and RTC work items
|
Rational Quality Manager (RQM)
|
RQM Element
|
PLE Element
|
|
Project Area
|
Platform
|
|
Test Plans
|
Quality Goals
|
|
Test Cases
|
Versioning with copy before VVC; create test types => functional,
diagnostic, environmental
|
|
Snapshots
|
Publish to RELM
|
|
Categories
|
Categorize test artifacts with variant tags
|
|
