Checklist Impact Analysis for Change Request (CR)
Changes in the requirement is one of the greatest challenge in Software system life cycle. Impact analysis is an essential part of this change management. Without adequate analysis it is not possible to confidently determine the extent, complexity and cost of proposed changes to a software system. This gives the upper management the option to make informed decisions regarding the inclusion or rejection of proposed changes. The lack of coherent impact analysis can also hinder the process of ensuring that all system components affected by a change are updated.
Implications of the Proposed Change:
o Check whether any existing requirements in the baseline that conflict with the proposed change.
o Check whether any other pending requirement changes that conflict with the proposed change.
o What are the consequences of not making the change?
o What are possible adverse side effects or other risks of making the proposed change?
o Will the proposed change adversely affect performance requirements or other quality attributes?
o 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?
o Is the proposed change feasible within known technical constraints and current staff skills?
o Will the proposed change place unacceptable demands on any computer resources required for the development, test, or operating environments?
o Must any tools be acquired to implement and test the change?
o How will the proposed change affect the sequence, dependencies, effort, or duration of any tasks currently in the project plan?
o Will prototyping or other user input be required to verify the proposed change?
o How much effort that has already been invested in the project will be lost if this change is accepted?
o Will the proposed change cause an increase in product unit cost, such as by increasing third-party product licensing fees?
o Will the change affect any marketing, manufacturing, training, or customer support plans?
System Elements Affected by the Proposed Change
o Identify any user interface changes, additions, or deletions required.
o Identify any changes, additions, or deletions required in reports, databases, or data files.
o Identify the design components that must be created, modified, or deleted.
o Identify hardware components that must be added, altered, or deleted.
o Identify the source code files that must be created, modified, or deleted.
o Identify any changes required in build files.
o Identify existing unit, integration, system, and acceptance test cases that must be modified or deleted.
o Estimate the number of new unit, integration, system, and acceptance test cases that will be required.
o Identify any help screens, user manuals, training materials, or other documentation that must be created or modified.
o Identify any other systems, applications, libraries, or hardware components affected by the change.
o Identify any third party software that must be purchased.
o Identify any impact the proposed change will have on the projects software project management plan, software quality assurance plan, software configuration management plan, or other plans.
o Quantify any effects the proposed change will have on budgets of scarce resources, such as memory, processing power, network bandwidth, real-time schedule.
o Identify any impact the proposed change will have on fielded systems if the affected component is not perfectly backward compatible.
Effort Estimation for a Requirements Change
|
Effort |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TOTAL ESTIMATED EFFORT |
Procedure:
1. Identify the subset of the above tasks that will have to be done.2. Allocate resources to tasks.
3. Estimate effort required for pertinent tasks listed above, based on assigned resources.
4. Total the effort estimates.
5. Sequence tasks and identify predecessors.
6. Determine whether change is on the projects critical path.
7. Estimate schedule and cost impact.
Impact Analysis Report Template
Change Request ID: ______________
Title: ______________________________________________________
Description: ______________________________________________________
______________________________________________________
Analyst: __________________________
Date Prepared: __________________________
Prioritization Estimates:
Relative Benefit: (1-9)
Relative Penalty: (1-9)
Relative Cost: (1-9)
Relative Risk: (1-9)
Calculated Priority: (relative to other pending requirements)
Estimated total effort: ___________ labor hours
Estimated lost effort: ___________ labor hours (from discarded work)
Estimated schedule impact: ___________ days
Additional cost impact: ___________ dollars
Quality impact: _______________________________________________ _______________________________________________
Other requirements affected: ____________________________________________________
____________________________________________________
Other tasks affected: ____________________________________________________
____________________________________________________
Integration issues: ____________________________________________________
Life cycle cost issues: ____________________________________________________
Other components to examine ____________________________________________________
for possible changes: ____________________________________________________
Subscribe to this comment's feed
| < Prev | Next > |
|---|
