The main content of software configuration management:

The main content of software configuration management:

1. Version Management
1.1 Software configuration items (software config item):
Meaning: A variety of system components that should be included in the scope of management within the software life cycle.
Includes a variety of administrative and technical documentation, source and target code, and various data required to run (configuration-managed resource objects).
Morphology: In the usual software configuration management system, the most basic software configuration items are stored and managed in the form of disk files.
1.2 Version management is the foundation of configuration management:
All history of each software configuration item should be recorded and recorded by whom the software configuration item was created, by whom and when, and for what reason, as well as search and information queries for the versions of these software configurations.
1.3 Version Tree:
The different evolutionary directions of software systems can be managed.
1.4 Version management of software configuration items--Number of versions
Records a tree structure information with a time-stamped configuration item version evolution.

2. Configuration support
2.1 Software configurations (software configuration):
The combination, structure, and relationship definition of all software configuration items at different times.
2.2 System Modeling
A configuration is defined to represent the entire system or subsystem within it.
2.3 Dependency Tracking
For example, find the version of the design document that corresponds to a source file version.
2.4 Impact Analysis
Analyze what other parts may be affected by the modification of one part of the system.

3. Change Management
3.1 Change: Source and process of software version evolution
Source: Demand Change, add functionality, modify errors ...
Lifecycle: request, approve, implement, validate, audit, end.
3.2 Change Control
Records and controls every modification to a software configuration item.
3.3 Change Tracking
A change in the life cycle to which step.
If a bug that has been changed appears again, how to find out why.
3.4 Change Propagation
Help propagates changes to one version of the product to other versions.

4. Construction Management (build)
4.1 System construction and re-construction (Build)
Help developers to construct and reconstruct any version of the product correctly and quickly.
4.2 Software Release Management (release)
Provide different versions for different users to avoid confusion.
4.3 Software Deployment Management (Deployment)
Help deploy the entire system in a distributed environment.

5. Process Support
5.1 Process Control
5.2 Pre-defined process templates and customizable process examples
You can define the process and ensure that each step defined in the process is executed in the correct order by the authorized person.
5.3 Key Concepts in process support
Include: Roles, workgroups, tasks, trigger mechanisms, and so on.

6. Team Support
6.1 Workspace Management
Different developers have independent workspaces that are not mutually impacting.
6.2 Parallel development
Support multiple developers to develop a project at the same time.
6.3 Remote Development
Developers can be physically distributed over far distances.

7. Status Report
Dependency reporting
Impact Report
Construction Report
Change Status Report
Variance Report
Historical reports
Access Control reports
Conflict Detection Report

8. Audit control
8.1 Verifying the Software configuration management process
8.2 Verifying the integrity of all configuration items managed by the system
8.3 Basic Audit control is the recording of all activities performed during the configuration management process and provides a retrieval mechanism-log