Basic Terms of Software Configuration Management

Configuration
Management refers to the discipline used to control a series of changes in the system.
A series of technologies, methods, and means have been used to maintain the product history, identify and locate the unique version of the product, and
Control Changes in the Development and release phases, and ensure the quality and efficiency of production by managing and reducing repetitive work in an orderly manner.
Unlike configuration management, Software Configuration Management uses computers as the carrier (regardless of tools and products), not only maintains
Status, historical records, storage, recovery, and product manufacturing are also supported. Software Configuration Management is a concept involved in software engineering.
For ease of description, the following are some terms related to Software Configuration Management (mainly Software Configuration Management ).
Plan specification GB/T
12505-90.
(1) Project entrust
Organization)
A project entrusting Organization refers to the organization or
Individual.
(2)
Project undertaking
Organization)
A project organizer refers to an organization or individual that develops, purchases, or selects software products for the project entrusting unit.
(3) Software Development Organization
Development Organization)
A Software Development Organization is an organization or individual directly responsible for software development, directly or indirectly entrusted by a project.
(4)
User)
A user is an organization or individual who uses software to complete a computing, control, or data processing task.
(5)
Software)
Software refers to computer Program And related data and documents, including solidified programs.
IEEE
The definition is as follows: computer programs, methods, rules, relevant documents, and running on computers
Required data.
It can be seen that the software is no longer just a program and a user manual, but contains a large number of programs, documents and
Data.
(6)
Software
Object)
A software object is any entity that is generated during project progress and can be controlled by Software Configuration Management. Each
Each software object has a unique identifier, an object entity that contains actual information, and a group used to describe its own characteristics.
Properties and relationships, as well as mechanisms used to perform relational operations and message transmission with other objects.
Software objects can be divided into source objects (Source
Object) and the derived object (derived object ),
According to its content structure, it can be divided into atomic object and composite object (derived
Object), according to its
The structure can be divided into atomic object and Composite
Object), according to the software
The time (state) at which a message is sent can be divided into mutable object and immutable object.
Object ).
(7)
Configuration)
Configuration refers to the implementation of software or hardware (that is, the product stated in the technical documentation) in configuration management.
) Those features and physical features.
(8)
Critical Software)
Important Software refers to the software that may affect personal safety and cause major economic or social losses.
(9)
Software Life
Cycle)
Software life cycle refers to the process of developing a software system to meet the application requirements.
The computer software system is put into operation by multiple workers until the software system is "retired. System Analysis and software
Definition, software development and system operation and maintenance 3
Phase. The software development stage is generally divided into requirement analysis,
Summary design, detailed design, coding and unit testing, assembly and integration testing, system testing, installation and acceptance 6
Phase.

(10)
Software Development
Library)
A software development library is used to store software development tasks in a certain stage of the software life cycle.
A library of computer-readable and manual-readable information.
(11)
Configuration item)
A configuration item refers to an entity in a configuration. It satisfies a final use function and can be imaged on a given reference point.
Id. In GB/T
11457-1995 another definition of configuration items in software engineering terms: For configuration management purposes
As a unit to view the hardware and/or software components, to meet the final application function and is specified for configuration management
Hardware/software, or their collection.
Software Configuration Management objects are software configuration items, which are information items generated during software engineering. Follow
ISO9000-3
The software configuration can be:
-Documents and data related to contracts, processes, plans, and products;
- Source code , Target Code , And executable code;
-Related products, including software tools, available software in the database, purchased software, and software provided by users.
All the items that make up the preceding information constitute a software configuration, and each of the items is called a software configuration.
Configuration items, which is the basic unit of configuration management. During software development, the earliest software configuration item is the system software specification.
As the software development process deepens, software configuration items also increase rapidly.
Software configuration items can be divided into two categories:
-Software benchmark-a group of software configuration items (documents and other software products) officially reviewed and approved
This is the basis for the next step of software development, and can only be changed through formal change control accumulation. For example, Set
Reporting is the basis of coding, and design reports can be used as software benchmarks.
-Non-benchmark configuration items-a group of software configuration items not officially reviewed and approved.
This allows you to divide software configuration items from the following perspectives.
A software system is divided into several configuration items, which are determined by the development policies determined by the Project Manager. For more information, see
NASA
The software configuration item Division Principle (NASA Software Configuration
Management
Guidebooks, 1995). Each software or set meets one of the following conditions and can be viewed as a software configuration item:
-The software set is independently designed, implemented, and tested;
-This software set is critical to overall performance, or has high risks or is related to system security;
-This Software Collection is extremely complex, involves high-tech, or has strict performance requirements;
-The software set has a direct interface with the software provided by other existing software projects or other institutions;
-It is expected that the software set will have more modifications than the conventional one after it becomes a runable software;
-This software set includes all functions in a specific range, such as application software and operating system;
-The software set is installed on a computer platform different from other parts of the system;
-The software set is designed to be reusable.
The following describes the name/number of a software configuration item.
Each component/component identifier of the software must be unique for tracking and reporting software configuration items
Status. Generally, each software configuration item must be assigned an identifier name or symbol.
The identifier is attached with a descriptor. NASA-CM-GDBK
The following is an example of a flag:
Software configuration items can be identified as FS (flight software for
And the components of the flight software, such
The flight execution program can be identified as fs_ex, indicating that it is a FS
The second-level component of the software configuration item.
The component (subroutine) can be numbered fs_ex_001 and fs_ex_002.
.
Therefore, you can compile the code according to the "Model codes_subsystem/Device Configuration codes_development phase codes_software Product Classification
# _ Configuration item number "principle to name and number each software configuration item and its components, subroutines and Related Description documents.
In the individual life cycle of software, it generally includes planning, analysis and evaluation, design, testing, Operation/maintenance, etc.
Status. Correspondingly, Software Configuration Management can be divided into design, test, controlled, and running states.
Status. The controlled status indicates that the software configuration management item is in the configuration management status.
(12) software controlled
Library)
A software controlled database is a product released as a stage at the end of a stage of the software life cycle.
Library of computer-readable information and manual-readable information related to the development work. Software Configuration Management refers
So the software controlled library is also called the Software Configuration Management Library.
(13)
Software product inventory
Library)
A software product library is used to store final products and deliver them to users after the system test phase of the software life cycle ends.
The Library of software installed on site or on site. The software product library can be set up and maintained on the subsystem and system layer respectively. If the software
If the product in the product library needs to be changed, some products should be locked in the product library, and the corresponding software configurations in the software controlled library should be summarized.
The change control procedures in the controlled database can be performed until the changes are completed and confirmed that they can complete the specified functions and performance.
Store it in the software product library again.
(14)
Configuration
Management)
Configuration Management is a technical and administrative discipline for managing and monitoring the following items. Configure
Feature and physical features of the item are identified and written as documents; changes to these features are controlled; changes have been processed
Record and report the process and implementation status, and verify the compliance with the required requirements.
(15)
Interface
Control)
Interface Control describes all the functions of two or more configuration item interfaces provided by one or more departments.
Process of features and physical features. Before implementing these features and physical features, make sure the modifications made to them
Reviewed and approved.
(16)
Version)
A version is the identified instance of a configuration item ). It can also be said that the source object quality cannot be changed
The new relatively stable pattern (configuration) formed after passing the inspection is called the software version.
Each software object can have a version group, and they have a specific relationship with each other.
Generally, the version Group of the software object is in a tree structure.
(17)
Version
Control)
Version control is used to establish different versions of a configuration item during the software life cycle.
The software objects involved in the software engineering process must be identified. You may need to do more before the object becomes a baseline.
Frequent changes may also be required after the baseline is changed.
(18)
Release)
Release refers to the process by which products of the software phase are submitted in the next phase at the end of each phase of the software period.
It also refers to the process of submitting the final product that is spent at the end of the system test phase to the user. This process is also called delivery.
(Delivery ).
(19)
Baseline)
A baseline is a configuration item that is officially marked, fixed, and officially approved at a specific time of its lifecycle.
Version. It can also be said that baseline is a specific point at the end of each development phase in the software life cycle, also known as a milestone. Only yuzheng
Software Configuration protocols obtained from technical review and formal technical review of software configurations
And the formal text of the software configuration can become a baseline. Its role is to make the division of work in various stages more clear, so that the original
Continuous work is broken at these points to facilitate testing and validation of stage results.
Once a software configuration item becomes a baseline, it is stored in the project database (also known as the project information library or software warehouse ).
Library. When a software organization member wants to modify the baseline configuration item, copy it from the project database
Dedicated workspace for this engineer (such as clearcase
. This activity is recorded in a notebook.
In short, baselines are a very important concept of Software Configuration Management. In a sense, it is developed in Software
It is a reference point and measurement point in the development schedule, and is stable for subsequent development.
. The baseline is actually frozen for some configurations.

(20)
Software
Configuration)
Software configuration refers to the various forms (machine readable or manual) generated by a software product at each stage of the software life cycle.
A collection of documents, programs, and data of various versions. Each element in the set is called the software.
Configuration item.
The output information of the software engineering process is as follows:
3
Type: computer program, which describes the documents of computer programs (including technical documents)
Files and user documents), data structure. All information items (documents, reports, procedures,
Tables and data) constitute the software configuration. Software configuration is all information generated when software development progresses to a certain time point.
It reflects and describes the status of the software development stage.
The software configuration can be divided into the following two types.
-Materials that cannot be directly executed. Such as written documents, program lists, test data, and test results.
-Materials that can be executed directly. Such as the target code and database information. They can be processed by computers and stored in
Storage medium.
(21) Functional baseline (Functional
Baseline)
Function baseline refers to the system design specifications that have been officially reviewed and approved at the end of the system analysis and software definition phase
Description of the specifications of the development system in the manual; or the specification is signed and approved by both parties after the project entrusting organization and the project undertaking organization
The specification of the software development system as stipulated in the agreement or contract; or the application of a lower-level, with the consent of the higher-level or
Description of the specifications of the software development system as defined in the project task book directly issued by the superior. Function baseline is initially approved
Feature configuration ID.
(22) allocation baseline (allocated
Baseline)
Baseline Allocation refers to the description of Software Requirement Specifications that have been formally reviewed and approved at the end of the software requirement analysis phase. Minute
A configuration baseline is the allocation configuration identifier originally approved.
(23) Product baseline
Baseline)
Product baselines refer to the software products that have been officially reviewed and approved at the end of the software assembly and system testing phase
Specifications of all configuration items. The product baseline is the initial product configuration identifier.
(24) Baseline Management
Configuration
Management)
Baseline configuration management refers to the process of establishing a baseline that has been officially reviewed and approved and serves as the basis for further development.
Some (such as software design and code) software work products should have baselines established at pre-identified points and
Strictly control the change process. These baselines provide control and stability when dealing with customers.
(25) Baseline Management
Management)
Baseline management refers to the use of technical and administrative management in configuration management to specify and modify these documents.
Documentation, which officially identifies and establishes baselines at specific times.
(26) software baseline Audit
Baseline
Audit)
Software baseline audit refers to the inspection of the structure, content, and facilities of the software baseline library to check whether the baseline is compliant.
The document that describes the baseline.
(27) software baseline Library
Baseline Library)
A software baseline library is a repository that stores configuration items and connection records.
(28) Configuration Management Database System (Configuration
Management Library System)
The Configuration Management Library System is a tool and procedure for accessing the content of the software baseline library.
(29) Configuration
Unit)
A Configuration unit is a configuration item that can be placed in the configuration management database system and retrieved from the database.
(30) Process Capability baseline
Baseline)
Process Capability baseline is recorded in documents. In a typical environment, it is usually possible to implement
Description of the range of results.
(31) configuration control group/Committee
Control
Board)
Configuration control group/Committee refers to a group of change personnel responsible for evaluation and approval of configuration items to ensure that all changes are
Is reviewed.
(32) Configuration
Identification)
The configuration identifier is an element of Software Configuration Management. It is determined by the configuration items selected for the system and the physical features that record their functions.
Technical documents of approved configuration items are composed of instructions, diagrams, tables, etc. For convenience
Software configuration items are controlled and managed to avoid confusion. You need to name them. This is the task of configuration identification.
The purpose of the configuration mark is to provide a traceable means for the software behavior and change results of the changed configuration item to avoid
Software development behaviors can be carried out in an uncontrolled and chaotic manner, which also facilitates the gradual completion of software development work in baseline mode.
(33) Change management
Management)
Change management is an element of Software Configuration Management, including evaluation, coordination, approval, or disapproval, and formal Configuration
Configuration item changes and other activities.
The main purpose of change management is to control and coordinate software developers with different responsibilities for effective communication so that software development
Personnel will not fight independently in an unordered environment, leading to insurmountable bottlenecks in the development efficiency of the team. Software survival period
All the software configurations in the software are the true representatives of software products and must be accurate. In the software engineering process
Changes must cause software configuration changes. Such changes must be strictly controlled and managed to keep the changes Information and
Deliver accurate and clear information to the next step of the software engineering process.
(34) configuration status statistics (Configuration
Status
Accounting)
Configuration status statistics are an element of Software Configuration Management. They consist of records and report information required for effective management. This
The information includes the approved configuration identification table, the configuration status to be changed, and the audited change status.
The purpose of status statistics is to present the software through quantified data and reports based on version control and process management.
The status of the development progress.
(35) configuration review
Auditing)
Configuration audit is an element of Software Configuration Management. It checks software products based on requirements, standards, or contract agreements.
The purpose of configuration review is to measure the acceptance of both the user and the development team (for example, software contract signed with the user)
Same), through the function audit and physical audit, the software implementation process and software functional integrity and correctness
Line inspection review. Configuration review ensures that the Software Configuration Management system works correctly and that the configuration item Function after testing meets the requirements
.
Configuration audit is divided into informal audit and formal audit.
Informal audits are conducted at critical stages of the software life cycle. For example, configuration is usually required before starting system design.
Audit, verify the integrity and correctness of the Requirement Specification configuration. Take formal review before the software concert customer.
Formal review includes two types: functional and physical. Function configuration review (FCA) is based on the test method, test
Evaluate the test process and test report to identify whether the actual performance of the software configuration items meets the requirements defined in the design document. Things
Configuration review (PCA) is a formal test of the concert version of the configuration item to identify whether the version is consistent with the determined Technology
Be consistent with the documentation and ensure that all approved changes have been completed in the software Concert version, including all required software
Items, Data, work procedures and documents.
Software Configuration Management
The four key elements are configuration identification, change management, configuration review, and configuration status statistics.
(36) Development Configuration Management (developmental configuration)
Management)
Development Configuration management refers to the use of technical and administrative management to specify and control the software and its related technical documents,
They define the constantly evolving configurations of a software work product during development. Development Configuration Management is free of direct control by developers
. Configuration items placed under development configuration management are not baselines, although they may be baseline at some points of Development
And placed under baseline configuration management.
(37) Key
Process
Area)
A group of related activities can achieve a set of goals that are crucial to building process capabilities when these activities are completed together.
Each key process domain has been defined on a single maturity level. CMU-SEI
Determine that they are some major components,
Used to help identify the software process capabilities of an organization and understand the improvements made for higher maturity levels. Software Configuration
Management is level 2 in CMM (Software Capability Maturity Model)
.
Common Software Configuration Management Abbreviations:
CI configuration item
SCM Software
Configuration Management Software Configuration Management
SCMP Software Configuration Management Plan
Software Configuration Management Plan
Cr change request
SCN specification change notice
Notes for changes
FCA functional configuration audit function configuration review
Gui Graphical User
Interface graphical user interface
PCA physical configuration audit physical configuration review
VDD version
Description document
ECP Engineering Change proposal project Change proposal
CPCI
Computer Program configuration item computer program configuration item
Csci Computer Software
Configuration item computer software configuration item
Sccb software configuration control board
Software configuration control group/Committee