Requirements change management in Software Engineering - Step-by-Step Execution

Concept Flow - Requirements change management

Identify Change Request

↓

Analyze Impact & Feasibility

↓

Review & Approve/Reject

↓

Update Requirements

↓

Implement Change

↓

Verify & Validate

↓

Close Change Request

This flow shows how a change request is identified, analyzed, approved or rejected, implemented, and finally verified before closing.

Execution Sample

Software Engineering

1. Receive change request
2. Analyze impact
3. Approve or reject
4. If approved, update requirements
5. Implement and verify change

This sequence outlines the main steps taken when managing a requirements change.

Analysis Table

Step	Action	Decision/Result	Next Step
1	Receive change request	Request logged	Analyze impact
2	Analyze impact and feasibility	Impact assessed	Review and approve/reject
3	Review and approve/reject	Approved	Update requirements
4	Update requirements documents	Requirements updated	Implement change
5	Implement change	Change implemented	Verify and validate
6	Verify and validate change	Change verified	Close change request
7	Close change request	Request closed	End process

💡 Process ends after change request is closed following verification.

State Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	Final
Change Request Status	None	Logged	Analyzed	Approved	Updated	Implemented	Verified	Closed

Key Insights - 3 Insights

Why is it important to analyze impact before approving a change?

Analyzing impact helps understand how the change affects the project scope, cost, and schedule, preventing unexpected problems. This is shown in step 2 of the execution_table.

What happens if a change request is rejected during review?

If rejected, the change is not implemented and stakeholders are notified. This is implied in step 3 where the decision can be 'No' leading to notifying stakeholders instead of updating requirements.

Why must verification happen after implementation?

Verification ensures the change works as intended and does not cause issues. Step 6 in the execution_table shows verification before closing the request.

Visual Quiz - 3 Questions

Look at the execution_table, what is the status of the change request after step 4?

A Verified

B Implemented

C Updated

D Closed

💡 Hint

Check the 'Change Request Status' in variable_tracker after step 4.

At which step does the decision to approve or reject the change happen?

A Step 2

B Step 3

C Step 5

D Step 6

💡 Hint

Look at the 'Decision/Result' column in execution_table for step 3.

If a change request is rejected, which step would be skipped?

A Update requirements

B Analyze impact

C Receive change request

D Verify and validate

💡 Hint

Rejected changes do not proceed to updating requirements as shown in the concept_flow diagram.

Concept Snapshot

Requirements change management:
1. Identify and log change request
2. Analyze impact and feasibility
3. Review and approve or reject
4. If approved, update requirements
5. Implement and verify change
6. Close request after validation

Full Transcript

Requirements change management is a process to handle changes in project requirements. It starts by receiving a change request, then analyzing its impact on the project. Next, the change is reviewed and either approved or rejected. Approved changes lead to updating the requirements documents, implementing the change, and verifying it works correctly. Finally, the change request is closed. This process helps keep the project on track and avoids surprises by carefully managing changes step-by-step.