[Original] Software Configuration Management

 

[Original] Software Configuration Management

1. What is Software Configuration Management?


The following are some standard definitions: (1) ISO/IEC 12207 (1995) Information technology-software survival process: the configuration management process is the process of implementing management and technical procedures throughout the software life cycle. It identifies and defines software items in the system and develops baselines; it controls the modification and release of software items; records and reports application for the status and modification of software items, ensures the integrity, coordination and correctness of software items, and controls the storage, loading and delivery of software items.

(2) ISO 9000-3 (1997) Quality Management and Quality Assurance Standards-Part 1: ISO 3rd: 9001 guidelines for use in computer software development, supply, installation and maintenance: software Configuration Management is a management discipline that provides technical and management guidance on the development and support of configuration items. Configuration Management applications depend on the project scale, complexity, and risk.

(3) W. Babich: Software Configuration Management can coordinate software development to minimize confusion. Software Configuration Management is a technology that identifies, organizes, and controls modifications. It aims to improve productivity most effectively.

(4) GB/T 11457 (1995) Software Engineering terminology: Software Configuration Management is the process of marking and determining configuration items in the system, control the projection and change of these items throughout the lifecycle of the system, record and report the configuration status and change requirements, and verify the integrity and correctness of the configuration items.

Summary configuration management is designed to maintain product history, identify and locate unique product versions, and control changes during product development and release through a series of technologies, methods, and means, this makes management Systematic, effectively reduces repetitive work, and ensures the quality and efficiency of products.

 

Ii. Main content of Software Configuration Management:

1. Version Management

1.1 Software configuration item ):Meaning: system components generated during the software life cycle that should be included in the scope of management. Including various management documents and technical documents, source and target code, and various data required for running (configuration management resource objects ). Form: In a General Software Configuration Management System, the most basic software configuration items are stored and managed in the form of disk files. Version 1.2 is the basis of Configuration Management:All historical records of each software configuration item should be recorded, and information such as who created the software configuration item and who modified the configuration item and why, and the retrieval and Information Query of these software configuration item versions. 1.3 version tree:You can manage different evolution directions of software systems. 1.4 version management of software configuration items-Number of versionsRecords the tree structure information of a time-marked configuration item version evolution. 2. Configuration support 2.1 Software Configuration ):The combination, structure, and relationship definitions of all software configuration items in different periods. 2.2 System ModelingDefine the configuration to indicate the entire system or its subsystems. 2.3 dependency TracingFor example, find the version of the design document corresponding to a source file version. 2.4 Impact AnalysisAnalyze the changes to one part of the system that may affect other parts. 3. Change management 3.1 Changes: source and process of software version EvolutionSource: demand changes, added features, modification errors ...... Lifecycle: request, approval, implementation, verification, review, and termination. 3.2 Change ControlRecord and control every modification to software configuration items. 3.3 change trackingWhich step has the lifecycle changed? If a bug has been changed, how can we find out the cause. 3.4 change propagationHelps spread modifications to one version of the product to other versions. 4. Build) 4.1 construct and reconstruct the system (build)Helps developers correctly and quickly construct and reconstruct any version of the product. 4.2 software release management (Release)Provide different versions for different users to avoid confusion. 4.3 deployment)Helps deploy the entire system in a distributed environment. 5. Process Support 5.1 Process Control 5.2 predefined process templates and customizable process instancesYou can define the process and ensure that each step defined in the process is executed by authorized personnel in the correct order. 5.3 key concepts in Process SupportIncluding roles, working groups, tasks, and triggers. 6. Team support 6.1 workspace managementDifferent developers have independent workspace that does not affect each other. 6.2 Concurrent DevelopmentMultiple developers can develop a project at the same time. 6.3 remote DevelopmentDevelopers can physically distribute data in distant locations. 7. Status reportDependency report impact report structure report change status report difference report history report access control report conflict detection report 8. Audit Control8.1 verification Software Configuration Management Process 8.2 verification of integrity of all configuration items managed by the system 8.3 basic audit control is to record all activities executed during the configuration management process and provide retrieval mechanisms-> logs