---
title: "Change management, CMMI and CMDB"
subject: "Information System"
chapter: 6
key: "semester_8/information_system:change-management-cmmi-cmdb"
source: https://www.bctengineer.com/q/semester_8/information_system/change-management-cmmi-cmdb
site: BCT Engineering
---

# Change management, CMMI and CMDB

Information System · Chapter 6: Implementations of Information Systems

- Asked in: 2073 Magh, 8 marks
- Video: [What is a Configuration Management Database (CMDB)? Explained with Example](https://www.youtube.com/watch?v=AOdYQpMxn6c) — AssetLoom
- Answer checked by Claude Opus 5.5 (high effort) on 2026-10-14
- Page: https://www.bctengineer.com/q/semester_8/information_system/change-management-cmmi-cmdb
- Whole chapter: https://www.bctengineer.com/md/semester_8/information_system/chapter-6

## Question

What is change management in the context of any IS implementation? How closely is it associated and CMMI concepts and with Configuration Management Database (CMDB) functionalities?

## Short answer

Change management is a structured process to control changes, minimizing disruption. It aligns with CMMI process areas like Configuration Management, ensuring controlled, documented changes. A CMDB stores configuration items and relationships, enabling impact analysis before changes and accurate updates afterward.

## Answer

#### Change management in IS implementation
**Change management** is the structured process of planning, approving, implementing and reviewing changes (to software, hardware, procedures and people) so that disruption and risk are minimised. During IS implementation it covers (a) the *organisational/people side*: communication, training, handling resistance; and (b) the *technical side*: change requests, impact analysis, approval, testing, release and rollback.

Typical steps: raise a change request, assess impact and risk, approve (change advisory board), schedule, implement and test, record, and review.

#### Relation with CMMI
**CMMI (Capability Maturity Model Integration)** is a framework to improve the maturity of an organisation's processes in five levels: Initial, Managed, Defined, Quantitatively Managed, Optimizing.
- Change management is a core part of CMMI process areas such as **Configuration Management** (change control of baselines), **Requirements Management** (managing requirement changes) and **Organizational Performance Management** (deploying process improvements).
- A higher maturity level means changes are controlled, documented, measured and improved, not done ad hoc.
- CMMI gives the process discipline (what to do); change management is how changes are handled within it.

#### Relation with CMDB
A **Configuration Management Database (CMDB)** stores information about configuration items (CIs) such as servers, applications, network devices, licences and documents, and the relationships between them.
- Before a change, the CMDB shows which CIs and services are affected (**impact analysis**).
- After the change, the CMDB is updated so that records stay correct.
- It supports baselines, version control, audit and rollback.
- It is a main tool of ITIL's change and configuration management.

```text
 Change request -> Impact analysis (CMDB)
        -> Approval -> Implement/Test
        -> Update CMDB -> Review (CMMI)
```

## Check yourself

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

1. During IS implementation, change management covers:
   A. Only technical changes
   B. Both the organisational/people side and the technical side such as change requests, impact analysis, approval, testing and rollback
   C. Only training
   D. Only hardware
   Answer: B. It covers both the people side and the technical side. (Key point: Two sides)

2. Which lists the five CMMI maturity levels in order?
   A. Initial, Managed, Defined, Quantitatively Managed, Optimizing
   B. Basic, Advanced, Expert, Master, Final
   C. Defined, Initial, Managed, Optimizing, Quantitative
   D. Planned, Done, Tested, Released, Closed
   Answer: A. CMMI levels are Initial, Managed, Defined, Quantitatively Managed and Optimizing. (Key point: CMMI levels)

3. How is change management related to higher CMMI maturity?
   A. Changes become ad hoc
   B. Changes are controlled, documented, measured and improved
   C. Changes are banned
   D. Changes are hidden
   Answer: B. Higher maturity means controlled, documented, measured changes. (Key point: CMMI relation)

4. What is the role of the CMDB before a change?
   A. It shows which CIs and services are affected (impact analysis)
   B. It approves the change
   C. It writes code
   D. It trains users
   Answer: A. The CMDB supports impact analysis by showing affected configuration items; it is updated after the change. (Key point: CMDB role)

## Related in Information System

- [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
- [Knowledge management and KM triangle](https://www.bctengineer.com/question.md?key=semester_8%2Finformation_system%3Aknowledge-management-hierarchy) — Information System, chapter 4

## Related in other subjects

- [Issues modern configuration management must address](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Asurvival-of-fittest) — Software Engineering, chapter 10
- [Short note: change management](https://www.bctengineer.com/question.md?key=semester_5%2Fsoftware_engineering%3Achange-management) — Software Engineering, chapter 10
- [SQL: create and use bank database](https://www.bctengineer.com/question.md?key=semester_6%2Fdatabase_management_system%3Asql-create-database-bank) — Database Management System, chapter 3
- [ER diagram: hospital management](https://www.bctengineer.com/question.md?key=semester_6%2Fdatabase_management_system%3Aer-hospital) — Database Management System, chapter 2
