Task: Configuration Control
Configuration Control is the process of systematically controlling any changes to uniquely identified elements in the Requirements, Design and Product baselines.
Disciplines: Configuration and Change Management
Relationships
Main Description

Within the sphere of control of RDE, this means controlling changes that are directly contained or indirectly referenced from the RDE processes. These can occur as the result of the agreement tasks or during development when either suppliers or stakeholder want to request changes.

Configuration Control

Configuration Control

Steps
Identify each problem on a Problem Report (PR) and allocate a unique identification.
Identify the need.
Identify the need to perform a change directly onto a Change Note (CN) and allocate a unique identifier (in practise it is normally a number)
Update change notes (CN).

Determine whether to proceed with:

  1. Transitioning a PR into a CN (and allocate a unique number to the CN) and define in detail the exact changes on the CN or;
  2. Proceed with the detailed definition of the scope of the CN already raised
  3. (Due to either a change in need by the user, or a mismatch between any of the baselines (PR))
Perform Impact Analysis.
Perform Impact Analysis and document the specifics of the need for change (On a uniquely identified Change Note (CN))
Review the proposed (detailed) changes on the CN.
Decide whether to implement the CN.
Also figure out at what point in time in the Requirements, Design and Product Baselines.
Implement the proposed change(s) or not.
Check that the proposed and agreed changes have been implemented as defined.
  1. Close CN if implementation is correct.
  2. Perform further analysis if the CN has not been implemented correctly.