The product baseline is the one where the defect was identified, and should span all the engineering tools that are used in a project or program. Once performing role reproduces the problem, defect planning will go into the resolution stage.

Pre-conditions:

• Defect triaged and assigned

Post-conditions:

• Defect resolution planning starts

Steps

1. Reproduce the defect in a test rig

a. Reproduce a specific version of the product where the problem is occurring

b. Run manual tests to validate the defect and find reproducible usage pattern for isolating the error

2. Reproduce the defect in a simulation or debug environment

a. In any applicable engineering tool(s), select a proper configuration to set the product context for the work about to be performed. This can either be the product baseline where the defect was identified (e.g. AMR.S (GC) Mobile US.2013-06-01), or the relevant maintenance stream of a specific product variant (e.g. AMR.S (GC) Mobile US 2013.FP1, which is a Fix Pack of a Mobile US variant of the AMR product).

b. Select debugging or simulation environment with necessary parameters

c. Identify and isolate the defect

d. Trace the defect to a higher level of abstraction. For example, if a defect is isolated to a specific design/code operation, trace up to the related design state transition, or trace up to a related requirement or use case.

3. Document impact analysis

a. Add links between design/code and the defect

b. Add a comment to the defect with recommendation on how to resolve it

c. [Optional]Add a comment to the defect with recommendation on any test case updates

d. [Optional] Add a comment to the defect with recommendation on any requirement updates e. Complete this phase of the Task, and assigns the defect back to the Project Manager to start planning a future fix.