Based on the information provided by engineers working on requirements and design, the role performing this task determines the use of a particular component baseline across the overall product line. Results are provided to Project and Product managers for review and approval.

This task can be performed in parallel with the work systems and software engineers are performing to implement change or defect resolution. In fact, it is a recommended practice to analyze component dependencies as early as possible in your process, to enable the flexibility of delivering necessary changes or fixes right after they have been completed in the original product variant.

Pre-conditions:

• Defect reproduced in a single product variant
• Change approved for a single product variant

Post-conditions:

• Impact to other product variants in a product line determined

Steps

1. Set up and initiate the work needed to complete this task 

a. Open the task and read the description

b. Mark the task to Start Working, and save the task

c. Send a comment in the Task to lead engineers in key disciplines (e.g. requirements, design) to explore what artifacts might be impacted 

2. Trace component usage

a. Find usage of the component baseline in a product line

b. Once presented with a list of product variants that depend on the component baseline in question, capture the list in the appropriate format 

3. Report on component usage

a. Add component usage information to the Task

b. Notify project and/or product managers of the list of product variants dependent on the component baseline in question

c. Close the Task