Requirements change management in Software Engineering - Mini Project: Build & Apply

Requirements Change Management

📖 Scenario: You are part of a software development team working on a new app. During the project, the client requests changes to the original requirements. Managing these changes carefully is important to keep the project on track.

🎯 Goal: Build a simple step-by-step checklist for managing requirements changes effectively in a software project.

📋 What You'll Learn

Create a list of initial requirements

Add a variable to track change requests

Write a loop to review each change request

Add a final step to approve or reject changes

💡 Why This Matters

🌍 Real World

Managing changes in project requirements helps teams stay organized and deliver what clients need without confusion.

💼 Career

Understanding requirements change management is essential for roles like project managers, business analysts, and software developers.

1

Create the initial requirements list

Create a list called requirements with these exact items: 'Login functionality', 'User profile', and 'Data export'.

Software Engineering

# Create the list of initial requirements
# Your code here

Hint

Use square brackets [] to create a list and separate items with commas.

2

Add a variable for change requests

Create a list called change_requests with these exact items: 'Add password reset' and 'Include dark mode'.

Software Engineering

requirements = ['Login functionality', 'User profile', 'Data export']
# Create the list of change requests
# Your code here

Hint

Use a list to hold the change requests, just like the requirements list.

3

Review each change request

Write a for loop using request as the variable to go through each item in change_requests. Inside the loop, add each request to the requirements list.

Software Engineering

requirements = ['Login functionality', 'User profile', 'Data export']
change_requests = ['Add password reset', 'Include dark mode']
# Loop through change_requests and add each to requirements
# Your code here

Hint

Use append() to add items to a list inside the loop.

4

Approve or reject changes

Create a dictionary called change_status where keys are the items from change_requests and values are 'Approved' for 'Add password reset' and 'Rejected' for 'Include dark mode'.

Software Engineering

requirements = ['Login functionality', 'User profile', 'Data export']
change_requests = ['Add password reset', 'Include dark mode']
for request in change_requests:
    requirements.append(request)
# Create change_status dictionary with approval decisions
# Your code here

Hint

Use curly braces {} to create a dictionary with key-value pairs.

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