Change Request Tickets
In a maintenance project whenever we receive a change request ticket from the customer, it is first analyzed by the developer. The developer determines whether it is a bug or an enhancement. Sometimes it can be neither. In such cases it is identified as an issue in user understanding. Once an issue is identified as a bug or enhancement then it is logged in the CR log for prioritization.
Impact analysis is done to help users think through the full impact of a proposed change request ticket. As such, it is an essential part of the evaluation process for a maintenance project. More than this, it gives the ability to spot problems before they arise, so that we can develop contingency plans to handle issues smoothly. It includes answering the following questions (and more):
- Identifying any existing requirements in the baseline that conflict with the proposed change.
- What are possible adverse side effects or other risks of making the proposed change?
- Will the change affect any system component that affects critical properties such as safety and security, or involve a product change that triggers recertification of any kind?
- How will the proposed change affect the sequence, dependencies, effort, or duration of any tasks currently in the project plan?
- Will the proposed change adversely affect performance requirements or other quality attributes?
Once the Impact analysis is done we estimate the effort to fix the change request in the system. This estimate includes the code changes, testing and other activities such as deployment and release.