Input: for the problem/modification identification and classification phase shall be at PTR for corrective and/or emergency types of requests. The SCR shall be input for adaptive, perfective, or emergency types of requests.
Process: if a modification to the software (not supportive data elements in a file) is required, the following determinative activities shall occur with the "Problem/modification, classification, and prioritization" process:
- Assign an identification number;
- Classify the type of maintenance;
- Analyze the modification to determine whether to accept, reject or further evaluate;
- Make a preliminary estimate of the modification size/magnitude;
- Prioritize the modification; and
- Assign a PTR or SCR to a block of modifications schedule for implementation.
Control: The PTR and SCR and its process determinations shall be uniquely identified and entered into a repository. See vocabulary slides for definition of a repository.
Output: The output of this process shall be the validated PTR or SCR and the process determinations that were stored in a repository. The repository shall contain the following items:
- Statement or problem or software change;
- Problem or change evaluation;
- Classification of the type of maintenance required;
- Initial priority;
- Verification data;
- Initial estimate of resources required to modify the existing system.
Metrics:
- The number of omissions on the PTR or SCR.
- Number of PTR or SCR submittals
- Number of duplicate PTRs or SCRs.
- Time expended for problem validation.
Factors to consider: The correctness of the information submitted and if the PTR or SCR will make the software program harder or easier to maintain in the future.
