5 Part 5: V-Modell Reference Work Products
5.3 Products
5.3.4 Configuration and Change Management
5.3.4.3 Problem Report / Change Request
Process module: Problem and Change Management
Responsible: Change Request Manager (when using process module Problem and Change Management)
Activity: Preparing Problem Report/Change Request
Work Product Attributes: external
Purpose
Problem report and change request are the documented wish to solve a problem, execute a modification or introduce an improvement. They may be initiated by various factors, e.g. changes of requirements or faults within the system.
Problem reports or change requests may be prepared by each stakeholder, e.g. »Software Developer or »User, or introduced as »External Product from the outside of the project. The Project Manual specifies when problem reports and change requests must be prepared in order to initiate and implement a change.
Is generated by
Project Manual, Project Plan (see product dependency 4.13)
Depends on
Change Decision, Change Status List, Problem/Change Evaluation, Project Plan (see product dependency 5.29)
5.3.4.3.1 Identification and Classification
This subject describes the identified problem and change request in detail. It should document all information - e.g. unambiguous identification of the subject matter of the problem, requesting agency and urgency - which is required in order to reproduce the problem or replicate the change request. Every change request shall be categorized and classified, e.g., with respect to the type of change, change priority and completion.
Exemplary Product Content
The change request may include the following:
Identification
- Identificator of request
- Project identification
- Identification of the subject matter (configuration) to which the report or request refers
- Date of receipt
- Requesting agency (name, telephone, email)
- Related other requests
Classification
- Categorization of change (fault (in request, design, coding, process/procedure), problem, change of requirement, extension, improvement)
- Urgency as seen from point of view of the requesting agency (e.g., critical, very important, important, desirable)
- Desired date of completion
5.3.4.3.2 Opportunity/Problem Description
Based on the description of the actual state in the previous subject, the »Opportunity/Problem Description indicates the reason for the change, e.g., technical problems, scarcity of resources or organisational conflicts. The rationale may also decribe opportunities and benefits of the desired change and potential damage which may occur if the changes are not executed.
If the request refers to a deviation of the system behavior from the specified requirements or to the change of a requirement, this requirement must be indicated.
5.3.4.3.3 Suggested Solution
If the requesting agency has any concrete concepts for implementing the desired state, these should be presented here. The effects of the implementation should also be described.