Configuration management is a management process for establishing and maintaining the consistency of a product performance, functional and physical attributes with its requirements, design and operational information throughout its life. It originated in the United States Department of Defense in the 1950s as a discipline for managing hardware, became formal in the late 1960s through the DoD 480 series of military standards, and was later consolidated into MIL-STD-973 in 1991, which fed into the widely used ANSI-EIA-649 standard. Its purpose is to verify that systems perform as intended with proper documentation and to manage changes to a system in a controlled way that improves reliability and maintainability while reducing cost and risk. Configuration management is now standard practice across the military, IT service management under frameworks such as ITIL, civil engineering projects like roads, bridges, dams and buildings, and industrial engineering generally. This description is adapted from Wikipedia contributors under CC BY-SA 4.0; changes were made. https://creativecommons.org/licenses/by-sa/4.0/
Facts
Core PrincipleHandle changes systematically so that a system maintains its integrity over time. 1 FAQs
What does configuration management actually keep track of?
Configuration items, their identifiers, and baselines such as a working production setup.
IBM describes three things. The first is configuration items, meaning the software or infrastructure initiative, module or API the team will monitor and control. The second is identifiers, the unique serial or version number or other tracking mechanism for each item. The third is baselines, typically the configuration of a working production environment.
Connections
Sources
1. Configuration management (Wikipedia)
Overview, first sentence
CM is the practice of handling changes systematically so that a system maintains its integrity over time.
In Group: Software Requirements and Architecture Practices, Introduction
Configuration management (CM) is a management process for establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational information throughout its life.
View the SourceReader Challenges (0)
No disputes yet. Spotted an error or a better source? Open the first one.
Sign in to dispute this or suggest a correction.