Requirements change management in Software Engineering - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Requirements Change Management?

It is the process of handling changes to software requirements in a controlled way to ensure the project stays on track and meets user needs.

beginner

Why is managing changes in requirements important?

Because uncontrolled changes can cause delays, increase costs, and lead to a product that does not meet user expectations.

intermediate

Name a common step in the requirements change management process.

Evaluating the impact of the change on the project’s scope, schedule, and resources before approval.

intermediate

What role does communication play in requirements change management?

Clear communication ensures all stakeholders understand the change, its reasons, and effects, helping to avoid confusion and resistance.

beginner

How can tools help in managing requirements changes?

Tools can track changes, document decisions, and keep everyone updated, making the process organized and transparent.

What is the first step when a new requirement change is proposed?

A Immediately implement the change

B Evaluate the impact of the change

C Ignore the change

D Delete the original requirement

The first step is to evaluate how the change affects the project before deciding to approve or reject it.

Which of the following is NOT a risk of poor requirements change management?

A Improved team morale

B Increased costs

C Project delays

D Product not meeting user needs

Poor change management usually harms team morale, not improves it.

Who should be involved in decisions about requirement changes?

A Only the project manager

B Only the developers

C All relevant stakeholders

D Only the customers

All relevant stakeholders should be involved to ensure the change is well understood and agreed upon.

What is a common tool feature that supports requirements change management?

A Change tracking

B Automatic coding

C Email spam filtering

D Graphic design

Change tracking helps keep a record of all requirement changes and their status.

Which is a good practice when communicating requirement changes?

A Ignore feedback from stakeholders

B Use technical jargon only

C Avoid telling the team until last minute

D Use clear and simple language

Clear and simple language helps everyone understand the changes and reduces confusion.

Explain the main steps involved in requirements change management.

Think about what happens from when a change is suggested until it is completed.

Describe why uncontrolled changes to requirements can harm a software project.

Consider what happens if changes happen without planning or agreement.