---
title: "Short note: change management"
subject: "Software Engineering"
chapter: 10
key: "semester_5/software_engineering:change-management"
source: https://www.bctengineer.com/q/semester_5/software_engineering/change-management
site: BCT Engineering
---

# Short note: change management

Software Engineering · Chapter 10: Configuration Management

- Asked in: 2068 Chaitra, 2.5 marks; year not given, 3 marks
- Answer checked by Claude Opus 5.5 (high effort) on 2026-10-14
- Page: https://www.bctengineer.com/q/semester_5/software_engineering/change-management
- Whole chapter: https://www.bctengineer.com/md/semester_5/software_engineering/chapter-10

## Question

Write a short note on change management.

## Short answer

Change management controls modifications through a formal process: a change request is validated, impact is analyzed, and a change control board approves or rejects it. Approved changes are implemented, tested, and checked in to create a new version. This prevents uncontrolled changes, preserves history, and aids impact estimation.

## Answer

**Change management** (change control) is the configuration management process that makes sure every change to a software system is requested, analysed, approved, made and recorded in a controlled way. Its aim is to allow necessary changes while keeping the system stable and costs under control.

**Change control process** (Sommerville and Pressman):
1. **Change request:** a user or developer submits a **change request form (CRF)** describing the change.
2. **Validation and analysis:** the request is checked to see if it is valid and not a duplicate. Its impact, cost and risk are analysed.
3. **Decision:** a **change control board (CCB)** or change control authority approves or rejects it, considering cost, benefit and schedule.
4. **Engineering change order:** an approved change is assigned to a developer with a description of the work.
5. **Implement:** the developer **checks out** the affected items, makes the change, and the change is reviewed and tested.
6. **Check in and baseline:** the changed items are checked in, a new version is created, and the CRF is closed.

```text
Change request --> Analyse impact/cost --> CCB
                                           |
                    +----------------------+
                    |                      |
                Rejected               Approved
             (inform user)                 |
                                 Check out, modify
                                           |
                                  Review and test
                                           |
                                 Check in, new version
```

**Example:** a customer asks for SMS alerts in a banking app. The CCB estimates 10 person-days, approves it for the next release, and the change is tracked until it is tested and released.

**Benefits:** prevents uncontrolled changes, keeps a history of who changed what and why, and helps estimate the effect of changes.

## Check yourself

The answer's key points as multiple-choice questions, with the correct option and why.

1. What is the aim of change management?
   A. Prevent all changes
   B. Allow any change quickly
   C. Allow necessary changes while keeping the system stable and costs under control
   D. Replace testing
   Answer: C. Changes are requested, analysed, approved, made and recorded in a controlled way. (Key point: Aim of change management)

2. What does the change control board (CCB) do?
   A. Writes the code
   B. Approves or rejects change requests considering cost, benefit and schedule
   C. Tests the change
   D. Submits change requests only
   Answer: B. The CCB makes the decision after impact analysis. (Key point: Role of CCB)

3. Which order is correct after a change request is approved?
   A. Check in, then check out, then modify
   B. Modify, then analyse, then request
   C. Check out items, modify, review and test, then check in to create a new version
   D. Release, then modify
   Answer: C. The developer checks out, changes, review/tests, and checks in creating a new version. (Key point: Process order)

## Related in other subjects

- [Importance of change management](https://www.bctengineer.com/question.md?key=semester_8%2Finformation_system%3Achange-management-importance-tactics) — Information System, chapter 6, asked 2×
- [CSFs and change management](https://www.bctengineer.com/question.md?key=semester_8%2Finformation_system%3Acritical-success-factors-change-mgmt) — Information System, chapter 6
- [Change management, CMMI and CMDB](https://www.bctengineer.com/question.md?key=semester_8%2Finformation_system%3Achange-management-cmmi-cmdb) — Information System, chapter 6
- [Change in form of ownership](https://www.bctengineer.com/question.md?key=semester_7%2Forganization_and_management%3Aownership-change-examples) — Organization and Management, chapter 4