Configuration Management Processes, Explained

UPI Study › Courses › Software Engineering › Free lessons › Lesson 14.4 Free with a free account

Configuration Management Processes

Software Engineering · Chapter 14: Project Estimation, Configuration, and Change ControlSection 14.4 · lesson 89 of 1036 min · free with a free account

← Scheduling Policies and Configuration Management PlansNext lesson: Configuration Management Tools: Version Control, Build Systems, and CI/CD Pipelines →

Earn 3 college credits for Software EngineeringRecommended for credit by NCCRS · Computer Science 301 · self-paced · one payment, lifetime access
Enroll in Software Engineering · $250 →Download the syllabus (PDF)

In this lesson

Knowing exactly what exists, what changed, and why.

  • Define software configuration management, and the problem it solves
  • Describe the 4 core SCM activities
  • Trace a change through change control - including a rejection
  • Explain why audits matter even when the process is followed

Transcript

Everything said in the video, section by section (782 words). Read along, or search it.

Project Estimation, Configuration, and Change Control

Configuration Management Processes

Software changes constantly, often with several people touching different parts of the same system at once. This section covers the discipline that keeps track of it all, organized around four core activities that work together.

Losing Track of History

Which Version Is Real?

Without a disciplined way to track what version of what item exists, what has changed, and why, a project can quickly lose track of its own history. Nobody is quite sure which version is authoritative. Or whether a given change was ever actually reviewed. Software configuration management, or S C M, is the discipline that provides this control. It governs how a system's items are identified, changed, tracked, and verified, throughout the system's life.

4 Core Activities

4 Questions SCM Answers

S C M organizes its work around four core activities. Together, they answer four different questions. Configuration identification answers, what is under formal control? Change control answers, how does a baselined item change? Status accounting answers, what actually happened, and when? And configuration audits answer, does everything still line up?

Configuration Identification

Naming Items and Setting Baselines

Configuration identification names the specific items that will be placed under formal control. That means source code modules, requirements documents, test plans, and similar artifacts. It also establishes a baseline. That is a formally reviewed, agreed-upon version of an item. The baseline becomes the fixed reference point for everything built or changed afterward. Nothing can be said to have changed, in any meaningful sense, until there is a baseline to change it from.

Change Control

Every Change a Deliberate Decision

Once an item is baselined, further changes go through a formal change control process, rather than happening informally. A proposed change is submitted. Its impact is analyzed. And it is explicitly approved, rejected, or deferred, before any work on it proceeds. That ensures every change to a baselined item is a deliberate, reviewed decision, rather than something that simply happened.

Figure 14.4B

A Baseline Through Change Control

Here is one baseline moving through change control. A change request against baseline version one goes through impact analysis, and then reaches a decision. If it is approved, it is implemented, and a new baseline, version two, is deliberately established. If it is rejected or deferred, baseline version one stays exactly as it was, and the reason is recorded. So a rejected change does not quietly disappear, or get tried again unofficially. Nothing changes without an explicit, recorded decision.

Tracking and Verifying

Status Accounting vs. Audits

Status accounting is the record-keeping behind the other activities. It maintains an accurate, retrievable history of every item's versions, and every change's outcome. What changed, when, why, and under whose approval. Configuration audits are periodic, formal checks. They confirm that what actually exists matches what the records say should exist. And they confirm that change control was genuinely followed for every change since the last audit. An audit does not assume the process worked. It verifies that it did. And its findings often become the input for the next round of change control.

Table 14.4

The 4 Activities at a Glance

Here are the four activities at a glance, with the key output of each. Identification produces a named baseline. Change control produces an approved, rejected, or deferred change. Status accounting produces an accurate change history. And configuration audits produce either verified consistency, or corrective findings.

Apply It

A Shared Document, No History

Let's apply that. Several people edit a shared document, with no version history, and no approval step. Which activities are missing? Change control, because nothing is approved. And status accounting, because there is no history. Eventually, nobody will be able to say which version is right, or who changed what, and why.

Apply It

Careful Change Control, No Audits

Here is another case. A team follows change control carefully for every single request. But it never performs a configuration audit. What could still go undetected? A change that bypassed the process entirely. Or records that no longer match what actually exists. Following a process is not the same as verifying that it was followed. That is exactly the gap audits close.

Key Terms

The Vocabulary of This Section

Let's lock in the key terms. Software configuration management is the discipline of controlling how a system's items are identified, changed, tracked, and verified. Configuration identification names the items under formal control, and establishes baselines. Change control is the formal process of proposing, analyzing, and approving or rejecting changes. Status accounting is the record-keeping that tracks what changed, when, why, and under whose approval. And a configuration audit confirms that actual items match the recorded status, and that change control was genuinely followed.

Key Takeaways

What to Carry Forward

To pull this together. S C M organizes its work around four core activities. Identification, change control, status accounting, and configuration audits. Identification establishes baselines, the fixed reference points that make later change meaningful. Change control requires every change to a baselined item to be explicitly approved, rejected, or deferred. Status accounting keeps the history answerable, rather than reconstructed from memory. And audits verify that the other three activities actually work, rather than assuming they do.

About Software Engineering at UPI Study

Software Engineering (Computer Science 301) is a self-paced online course of 103 video lessons in 15 chapters, from process models and agile to requirements, design, user interfaces, reliability, security and project management. It carries a NCCRS credit recommendation for 3 semester credits.

Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Enroll now → Course details Download the syllabus All Computer Science courses Every course with PRO →

Compare: Software Engineering vs Systems Analysis

Why take it here

Why students take Software Engineering with UPI Study

How professional software gets builtSoftware Engineering covers how teams turn requirements into working, maintainable software: process models, agile, requirements, design, testing, reliability and project management. It is a core course in computer science and software degrees.
Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.
Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.
Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.
Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.
130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Where the credit goes

Universities that work with NCCRS

Software Engineering carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

Thomas Edison State UniversityThomas Edison State UniversitySigned partnerUniversity of the PeopleUniversity of the PeopleSigned partnerCharter Oak State CollegeCharter Oak State CollegeSigned partnerStrayer UniversityStrayer UniversitySigned partnerColumbia Southern UniversityColumbia Southern UniversitySigned partnerIndiana TechIndiana TechSigned partnerPenn StatePenn StateWorks with NCCRSSouthern New Hampshire UniversitySouthern New Hampshire UniversityWorks with NCCRSSUNYSUNYWorks with NCCRS +many more cooperating universitiesFind my college →

Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.

FAQ

Questions students ask us

About Configuration Management Processes

What is software configuration management?
Software configuration management (SCM) is the discipline of controlling how a system's items are identified, changed, tracked, and verified throughout its life. It solves the problem of a project losing track of its own history, where nobody is sure which version is authoritative or whether a change was ever reviewed. SCM matters most when several people change the same system at once.
What are the four core activities of software configuration management?
The four core SCM activities are configuration identification, change control, status accounting, and configuration audits. Identification names the items under formal control and sets baselines. Change control decides how a baselined item may change. Status accounting records what changed, when, why, and under whose approval. Audits confirm that actual items match the records and that change control was followed.
What happens to a rejected change request in change control?
When a change request is rejected or deferred, the current baseline stays exactly as it was and the reason for the decision is recorded. The request does not quietly disappear or get tried again unofficially. If a change is approved instead, it is implemented and a new baseline version is deliberately established, so nothing changes without an explicit, recorded decision.
Why are configuration audits needed if a team follows change control?
Following a process is not the same as verifying that it was followed, and configuration audits close that gap. Without audits, a change that bypassed the process entirely, or records that no longer match what actually exists, could go undetected. Audits verify that the other SCM activities really worked, and their findings often feed the next round of change control.

About the Software Engineering course

How many college credits is Software Engineering?
Software Engineering (Computer Science 301) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
How much does Software Engineering cost and what is included?
$250, paid once, with lifetime access: all 103 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.
Which universities accept UPI Study credits?
UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.
How long does Software Engineering take?
It is self-paced with no deadlines. The 103 lessons total about 11 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.
How are the exams done?
Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.
How do my credits reach my college?
When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

Ready for the full course? Earn 3 credits in Software Engineering.

103 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.

Enroll in Software Engineering →Download the syllabusEvery course with PRO →
Software Engineering
3 credits · NCCRSEnroll →