CMM (Configuration Management-Configuration Management)

No configuration management is available for large and small projects or IT companies.

First, let's define it in a simple language.
Configuration Management is the product (configuration item) of the software development process. It also carries out system control over the changes to these identified software configuration items to ensure the integrity and traceability of software products. That is to say, you can ensure that these items are properly saved and you can view the change process.

2. Let's look at the terms in configuration management:
A. configuration items (configuration items ):
It is the items marked and managed hierarchically according to certain rules. These items are the product of the development process (documents, reports, Code, etc, some management features are granted by configuration management rules, such as different access permissions and different controlled levels.
B. Baseline)
A status that is under formal control through review, signing, and other activities. This process is called "baseline ". Each baseline is the benchmark for the next development. At the end of a software development phase, the added and modified baseline content of the previous baseline forms the next baseline. The change columns of each baseline are strictly controlled and must be changed through the change process.
C, version)
A version is the identifier, add, modify, or delete of a configuration item in a certain stage. The version is identified by the version number.

3. Configuration Management activities:
X. Schedule Configuration Management:
A. configuration item ID:
Select Configuration items (some management process documents and some intermediate tables can be left blank and strictly managed) and divide these configuration items (by document/Code or by different modules, for different types of documents, perform standardized identification (such as segment ID identification, the identification is not a simple process, such as release version, public library version, compile the intermediate test version), and then organize it according to a certain directory structure.
B. configuration control: (permission management/Change Control)
Configuration items can be divided into several levels:
1. Baseline-based.
2. managed and controlled.
3. Controlled
Each configuration item has certain access permissions, and the access to the configuration item is controlled according to the permission,
Each baseline change must go through a certain change process, and each CR has a certain State to ensure the correctness of the change.

C. Release status:
Regularly publish the latest status and changes of baseline configuration items.

D. Configuration audit:
Before the end of the phase meeting, baseline audits should be conducted regularly by QA and the CMO of the backup or other project teams, and backups should be audited.

E. Backup recovery management:
Regularly back up the configuration library as planned

E. Software release (depending on the specific circumstances of different IT companies, whether it is regarded as the responsibility of Configuration Management)