PLM Scenario 1

a4 Locate requirements in change request context

Pre conditions:
Activity assigned to SE in a single repository
CR identified and in focus in a single repository
SE has authority across multiple service providers (and hence repositories)

Requirements exist in an ALM and a PLM repository

Post conditions:
CR associated with context and relevant existing requirements in the CR repository
Association is underwritten by the SE
Activity is noted as complete

Steps

(Step 1) Systems Engineer: Understand CR

1. Select the CR (Should)
2. Record CR has been picked(Should)
3. Open CR and explore and understand its description (Must)
4. Comment and reject as not relevant to the SE (Wont)
5. Open a timed or event based collaboration issue with priority for this CR with contributors and associated information (Wont)
6. Pursue the collaboration issue to close (Wont)

(Step 2) Systems Engineer: Understand CR Context

1. Identify context from CR attributes e.g product family, product release, prevailing versions and variants (Must)
2. Validate responsponsibility for CR in context (Wont)
3. Open a timed or event based collaboration issue with priority for this CR with contributors and associated information (Wont)
4. Pursue the collaboration issue to close (Wont)
5. Validate and record the context of CR in the CR (Should)
6. Record that the CR has an identified context (Should)
7. Comment and reject as invalid context (Wont)
8. Comment and reject as lacking authority or responsibility for CR in this context (Wont)

(Step 3) Systems Engineer: Locate requirements from product context

1. Locate the requirements collection or baseline from the context (Must)
2. Open a timed or event based collaboration issue with priority for this CR with contributors and associated information (Wont)
3. Pursue the collaboration issue to close (Wont)
4. Validate the pedigree of the baseline to the context (Could)
5. Record the location of the existing requirements baseline (Should)
6. Comment as unable to locate requirements and notify PM (Wont)

(Step 4) Systems Engineer: Record the association between the CR, context and the located requirements

1. Create and store a link between the CR, its context and the baseline or collection of requirements
2. Mark activity complete (Should)

Issues at 17/12:

Multiple requirements repositories not addressed yet