|
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:
-
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;
-
Proceed with the detailed definition of the scope of the CN already raised
-
(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.
-
Close CN if implementation is correct.
-
Perform further analysis if the CN has not been implemented correctly.
|
|