Impact analysis checklist for requirements change)

ArticleDirectory

• System elements affected by changes

Impact analysis checklist for requirements changes

Requirement change impact analysis Checklist

 

Implications of the proposed change implied in the proposed change

O identify any existing requirements in the baseline that conflict with the proposed change.
Identify all requirements in the baseline that conflict with the proposed requirements

O identify any other pending requirement changes that conflict with the proposed change.
Identify the conflict between the current change and the pending demand changes

O what are the consequences of not making the change?
What will happen if no changes are made?

O what are possible adverse side effects or other risks of making the proposed change?
What are the adverse results or risks caused by changes?

O will the proposed change adversely affect performance requirements or other quality attributes?
Will the change affect the performance of the requirement or other quality attributes in turn?

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?
Does a change affect system components, for example, a product change that affects security boundaries or triggers a new certificate change of any type?

O is the proposed change feasible within known technical constraints and current staff skills?
Is the change feasible under the premise of known technical constraints and current personnel skills?

O will the proposed change place unacceptable demands on any computer resources required for the development, test, or operating environments?
Is the change accepted by any computer resource environment (development, test, or operation environment )?

O must any tools be acquired to implement and test the change?
Do I have to use some tools to implement or test changes?

O how will the proposed change affect the sequence, dependencies, effort, or duration of any tasks currently in the Project Plan?
How does the current change affect the work in the current project plan, such as sequence, dependency, results, and stages?

O will prototyping or other user input be required to verify the proposed change?
Can a prototype or other user input be required to check whether the change is correct?

O how much effort that has already been invested in the project will be lost if this change is accepted?
How much investment cost will be lost if you accept this change?

O will the proposed change cause an increase in product unit cost, such as by increasing third-party product licensing fees?
Will changes increase the unit cost ratio of products, for example, adding third-party product license fees?

O will the change affect any marketing, manufacturing, training, or customer support plans?
Will changes affect the marketing, processing, training, and user support plans?

System elements affected by the proposed change system elements affected

O Identify any user interface changes, additions, or deletions required.
Identifies all the changes to the required user interface, add or delete

O identify any changes, additions, or deletions required in reports, databases, or data files.
Identifies all requests for adding, deleting, and modifying reports, databases, and data files.

O Identify the design components that must be created, modified, or deleted.
Identifies all design components that must be created, modified, and deleted

O Identify hardware components that must be added, altered, or deleted.
Identifies hardware components that must be added, changed, and deleted

O identify the source code files that must be created, modified, or deleted.
IdentifiesSource codeFile

O identify any changes required in build files.
Identifies all requests for changes in the architecture file

O Identify existing unit, integration, system, and acceptance test cases that must be modified or deleted.
Identifies existing unit tests, integration tests, system tests, 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.
Estimate the number of new test cases that will be needed

O Identify any help screens, user manuals, training materials, or other documentation that must be created or modified.
Identifies all help interfaces, user manuals, training materials, and other documents that must be modified or created

O identify any other Systems, Applications, libraries, or hardware components affected by the change.
Identify system applications affected by changesProgramLibrary files or hardware components

O Identify any third party software that must be purchased.
Identify which third-party software must be purchased

O 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.
Identifies all project management plans affected by changes, software quality assurance plans, configuration management plans, and 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.
Quantify any impact on the budget of rare resources, such as memory, process volume, network bandwidth, and real-time schedule.

O Identify any impact the proposed change will have on fielded systems if the affected component is not perfectly backward compatible.
Identifies the impact of changes on the implemented system when the affected components are not perfectly backward compatible

Workload Estimation for demand changes

Workload (labor time)	Task
__________	Update SRS or demand data path
__________	Develop or evaluate a prototype
__________	Create a new design component
__________	Modify existing design components
__________	Develop new user interface components
__________	Modify existing user interface components
__________	Develop new user release and help screens
__________	Modify existing user release and help screens
__________	Develop new sourcesCode
__________	Modify existing source code
__________	Purchase or integrate third-party software
__________	Select, purchase, and integrate hardware components; restrict vendors
__________	Develop new unit testing and Integration Testing
__________	Modify existing unit test and integration test
__________	Develop new system test and Acceptance Test Cases
__________	Modify existing system test and Acceptance Test Cases
__________	Modify the driver of Automated Testing
__________	Regression testing at the unit, module, and system level
__________	Develop new reports
__________	Modify an existing report
__________	Develop new database elements
__________	Modify existing database elements
__________	Develop new data files
__________	Modify an existing data file
__________	Modify various project plans
__________	Update other documents
__________	Update requirement update Matrix
__________	Review changed work products
__________	Review and Test
__________	Re-verify whether the security, reliability, and adaptability of the product meet the standards
__________	Other additional tasks
__________	Total workload

Steps:
1. Identify the subset of tasks that must be performed in the preceding task list

2. Allocate resources to tasks

3. Estimate the workload required for related tasks in the preceding task list based on allocated resources.

4. Total workload evaluation

5. Specify the task sequence and precursor (dependency)

6. Check whether the change occurs on the Key Path of the project.

7. Estimate the schedule and cost impact

Impact Analysis Report Template

Change Request ID :_______________

Title:

Description:

 

ANALYST:

Preparation Date:

 

Priority evaluation: