Scribd
Upload
53 views

Implications of The Proposed Change: Impact Analysis Checklist For Requirements Changes

The document provides a checklist for analyzing the implications and impact of proposed requirement changes for a project. It identifies areas to examine such as conflicting requirements, risks, effects on schedules and tasks, and system elements affected like the user interface, source code, and documentation. It also includes templates for estimating the effort required to implement the change for different tasks, and for reporting the results of the impact analysis.

Uploaded by

Javed Nehal
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
53 views

Implications of The Proposed Change: Impact Analysis Checklist For Requirements Changes

The document provides a checklist for analyzing the implications and impact of proposed requirement changes for a project. It identifies areas to examine such as conflicting requirements, risks, effects on schedules and tasks, and system elements affected like the user interface, source code, and documentation. It also includes templates for estimating the effort required to implement the change for different tasks, and for reporting the results of the impact analysis.

Uploaded by

Javed Nehal
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

Impact Analysis Checklist for Requirements Changes

Implications of the Proposed Change

• Identify any existing requirements in the baseline that conflict with the proposed change.
• Identify any other pending requirement changes that conflict with the proposed change.
• What are possible adverse side effects or other risks of making the proposed change?
• Will the proposed change adversely affect performance requirements or other quality attributes?
• 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?
• Is the proposed change feasible within known technical constraints and current staff skills?
• How will the proposed change affect the sequence, dependencies, effort, or duration of any tasks currently in
the project plan?
• Will prototyping or other user input be required to verify the proposed change?
• How much effort that has already been invested in the project will be lost if this change is accepted?

System Elements Affected by the Proposed Change

• Identify any user interface changes, additions, or deletions required.


• Identify any changes, additions, or deletions required in reports, databases, or data files.
• Identify the design components that must be created, modified, or deleted.
• Identify hardware components that must be added, altered, or deleted.
• Identify the source code files that must be created, modified, or deleted.
• Identify any changes required in build files.
• Identify existing unit, integration, system, and acceptance test cases that must be modified or deleted.
• Estimate the number of new unit, integration, system, and acceptance test cases that will be required.
• Identify any help screens, user manuals, training materials, or other documentation that must be created or
modified.
• Identify any other systems, applications, libraries, or hardware components affected by the change.
• Identify any third party software that must be purchased.
• Identify any impact the proposed change will have on the project’s software project management plan,
software quality assurance plan, software configuration management plan, or other plans.
• Quantify any effects the proposed change will have on budgets of scarce resources, such as memory,
processing power, network bandwidth and real-time schedule.
• 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
(Man Hours) Task
Update the SRS or requirements database with the new requirement
Create new design components
Modify existing design components
Develop new user interface components
Modify existing user interface components
Develop new source code
Modify existing source code
Perform unit and integration testing after implementation
Write new functional, system and acceptance test cases
Modify existing system and acceptance test cases
Develop new reports
Modify existing reports
Modify various project plans
Update other documentation
Perform rework following reviews and testing
Recertify product as being safe, secure, and compliant with standards.
Other additional tasks
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 project’s 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: _______________________________________

You might also like