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.

Practice

1. What is the main purpose of requirements change management in a software project?

easy

A. To write code faster

B. To handle changes in project needs systematically

C. To avoid all changes during development

D. To reduce the number of team members

Solution

1. Step 1: Understand the role of requirements change management

   It is designed to manage changes in project needs to keep the project organized and on track.

2. Step 2: Compare options with this purpose

   Only To handle changes in project needs systematically describes handling changes systematically, which matches the purpose.

3. Final Answer:

   To handle changes in project needs systematically -> Option B

4. Quick Check:

   Purpose = Handle changes systematically [OK]

Hint: Focus on managing changes, not avoiding or speeding coding [OK]

Common Mistakes:

• Thinking it prevents all changes
• Confusing it with coding speed
• Assuming it reduces team size

2. Which of the following is a correct step in the requirements change management process?

easy

A. Ignoring change requests until project end

B. Deleting all documentation after changes

C. Implementing changes without approval

D. Analyzing the impact of requested changes

Solution

1. Step 1: Identify correct process steps

   Requirements change management includes analyzing the impact of changes before deciding.

2. Step 2: Evaluate each option

   Only Analyzing the impact of requested changes correctly describes analyzing impact; others describe poor practices.

3. Final Answer:

   Analyzing the impact of requested changes -> Option D

4. Quick Check:

   Step = Analyze impact [OK]

Hint: Analyze changes before approval or implementation [OK]

Common Mistakes:

• Skipping analysis step
• Implementing without approval
• Ignoring requests

3. Consider this scenario: A team receives a change request. They document it, analyze its impact, and approve it. What is the next step?

medium

A. Implement the approved change

B. Delete the original requirements

C. Ignore the change request

D. Restart the project from scratch

Solution

1. Step 1: Review the process steps completed

   The team has documented, analyzed, and approved the change request.

2. Step 2: Identify the logical next step

   After approval, the next step is to implement the change to update the project.

3. Final Answer:

   Implement the approved change -> Option A

4. Quick Check:

   After approval = Implement change [OK]

Hint: After approval, implement changes promptly [OK]

Common Mistakes:

• Ignoring approved changes
• Deleting original requirements unnecessarily
• Restarting project without cause

4. A project team failed to document a change request before implementation. What problem is most likely to occur?

medium

A. No impact on the project

B. The change will be approved faster

C. Clear communication and tracking will be lost

D. The project will automatically finish early

Solution

1. Step 1: Understand the role of documentation in change management

   Documentation ensures clear communication and tracking of changes.

2. Step 2: Analyze consequences of missing documentation

   Without documentation, communication breaks down and tracking is lost, causing confusion.

3. Final Answer:

   Clear communication and tracking will be lost -> Option C

4. Quick Check:

   Missing documentation = Lost communication [OK]

Hint: Always document changes to keep communication clear [OK]

Common Mistakes:

• Assuming faster approval without documentation
• Believing project finishes early automatically
• Ignoring impact of missing documentation

5. A software project has multiple overlapping change requests. How should the team manage these to avoid confusion and errors?

hard

A. Prioritize, analyze dependencies, and communicate clearly

B. Implement all changes immediately without review

C. Reject all changes to keep original plan

D. Ignore communication and focus on coding

Solution

1. Step 1: Identify best practices for managing multiple changes

   Prioritizing changes, analyzing how they affect each other, and clear communication are key.

2. Step 2: Evaluate options against best practices

   Only Prioritize, analyze dependencies, and communicate clearly follows these steps; others cause confusion or ignore process.

3. Final Answer:

   Prioritize, analyze dependencies, and communicate clearly -> Option A

4. Quick Check:

   Manage multiple changes = Prioritize + Analyze + Communicate [OK]

Hint: Handle multiple changes by prioritizing and clear communication [OK]

Common Mistakes:

• Implementing without review
• Rejecting all changes blindly
• Ignoring communication importance