In short
- Definition: The discipline of identifying, versioning and controlling all configuration items of a system so that its state is known and reproducible.
- Goal: Make every environment consistent, traceable and recoverable.
- Example S.M.A.R.T. requirement: 100% of infrastructure and settings stored as code, with zero unapproved drift found in weekly scans.
1. Definition
As a non-functional requirement, configuration management describes the discipline of identifying, versioning and controlling every configuration item of a system, so that its state is always known and can be reproduced [1], [2], [3].
If an environment cannot be rebuilt from version control, it is not under configuration management.Key takeaway
Configuration items include source code, infrastructure definitions, application settings, database schemas, secrets references and documentation. Modern teams store most of them as code in version control and apply them through automated pipelines.
Configuration drift happens when an environment is changed by hand and no longer matches its recorded definition. Good configuration management detects and prevents it.
2. Goal
The goal is consistent, traceable and recoverable environments: every change is known, approved and can be undone.
Without it, environments drift apart, bugs appear only in production, and recovery after a failure depends on someone remembering what was changed by hand.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Items under version control | % of configuration items | 100% of infrastructure and settings | Inventory compared to repositories |
| Unapproved drift | Findings per scan | 0 | Weekly drift detection |
| Environment rebuild time | Hours | < 4 h from scratch | Periodic rebuild test |
| Change traceability | % of changes linked to a ticket | 100% | Pipeline and repository logs |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Infrastructure: “All infrastructure and application settings shall be stored as code in version control and deployed only through the pipeline; weekly scans shall find no unapproved drift.”
- Recovery: “A complete test environment shall be rebuildable from version control in under 4 hours, verified each quarter.”
- Traceability: “Every production change shall be linked to an approved ticket and a version tag.”
5. Questions to Ask Stakeholders
- Which items must be under configuration control?
- Who may change production configuration, and how?
- How are secrets managed and referenced?
- How fast must an environment be rebuilt from scratch?
- How will drift be detected and corrected?
- How long must change history be kept?
6. Common Pitfalls
- Allowing manual hotfixes in production. They create drift. Route even urgent fixes through the pipeline.
- Storing secrets in repositories. Use a secrets manager and keep only references in version control.
- Forgetting data and schemas. Database migrations and reference data are configuration too.
7. Related NFRs
- Deployment — automated deployment relies on versioned configuration.
- Disaster Recovery — rebuilding environments needs complete configuration.
- Auditability and Control — change history supports audits.
- Maintainability — known, reproducible states make fixes safer.
8. FAQ
Describing servers, networks and services in files kept in version control, then applying them automatically.
The gap that appears when an environment is changed outside the controlled process and no longer matches its definition.
No. It covers code, settings, schemas and documents used by all teams.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [4] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| FAQ | Frequently asked questions | List of common questions with their answers. | [5] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [3] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Data migration | Moving data from one system or format to another. | [6] |
| Database | Organized store of data that software can query and update. | [7] |
| Deployment | Installing a new version of software in the environment where people use it. | [8] |
| Infrastructure as code | Defining servers and networks in versioned files instead of configuring them by hand. | [2] |
| Log | Time-stamped record of events written by software, used for troubleshooting and audit. | [9] |
| Pipeline (CI/CD) | Automated sequence of steps that builds, tests and deploys each code change. | [10] |
| Production environment | The live system that real users use, as opposed to test environments. | [11] |
| Schema | Formal description of how data is structured. | [12] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [13] |
| Version control | System that records every change to files so versions can be compared and restored. | [14] |
10. Sources and Further Reading
- [1] “Software configuration management.” Wikipedia. https://en.wikipedia.org/wiki/Software_configuration_management (accessed Nov. 18, 2026).
- [2] “Infrastructure as code.” Wikipedia. https://en.wikipedia.org/wiki/Infrastructure_as_code (accessed Nov. 18, 2026).
- [3] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [4] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [5] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [6] “Data migration.” Wikipedia. https://en.wikipedia.org/wiki/Data_migration (accessed Nov. 19, 2026).
- [7] “Database.” Wikipedia. https://en.wikipedia.org/wiki/Database (accessed Nov. 19, 2026).
- [8] “Software deployment.” Wikipedia. https://en.wikipedia.org/wiki/Software_deployment (accessed Nov. 19, 2026).
- [9] “Logging (computing).” Wikipedia. https://en.wikipedia.org/wiki/Logging_(computing) (accessed Nov. 19, 2026).
- [10] “CI/CD.” Wikipedia. https://en.wikipedia.org/wiki/CI/CD (accessed Nov. 19, 2026).
- [11] “Deployment environment.” Wikipedia. https://en.wikipedia.org/wiki/Deployment_environment (accessed Nov. 19, 2026).
- [12] “Database schema.” Wikipedia. https://en.wikipedia.org/wiki/Database_schema (accessed Nov. 19, 2026).
- [13] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [14] “Version control.” Wikipedia. https://en.wikipedia.org/wiki/Version_control (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @isawred; inline photo by @nicknice, both on Unsplash.




