Deliverable Name | Translations | ![]() |
||||||||||||||
Change Requests |
|
|||||||||||||||
Keywords | ||||||||||||||||
Change Requests, Consequence Analysis, Action | ||||||||||||||||
Description | ||||||||||||||||
A Change Request documents a requested change/addendum to the system. For major changes/additions it contains an analysis of the change why, what and how, and impacts on timelines and resources. It also records what action is taken. During formal tests, Test Protocols can be used instead of Change Requests. The person responsible for Quality Assurance collects and dispatches all change requests. The nature and frequency of that traffic gives an idea of the stability and quality of the system. Changes that effects the requirements of the system should, approved or not, be added to the Requirements Attributes document. |
||||||||||||||||
Approval | ||||||||||||||||
|
Recommended Storage | Timing | Responsibility | ||
\<Client>\<Project>\Xtra\Change Requests\ | Anytime |
|
||
Templates | Important input from | Important input to | ||
|