Configuration items

baseline

Configure status reporting

CCB: change Control Board configuration control board

A data medium and the data recorded thereon.

Permanent and readable by humans or machines, used to describe something human-readable.

In software engineering, documentation is often used to describe any written or graphical information that describes, defines, specifies, reports, or certifies activities, requirements, processes, or results.

Specific classification of software project documents

Important aspects and quality requirements

Project Cycle

Detailed classification: 14 types of documents

Assets generated during software development

Use a set of feature information

six types

Baseline: A specific point at the end of each development phase of the software life cycle, also called a milestone

At the milestone, the phase work has ended and formal phase products have been formed, so that the originally continuous development work is divided at these points, which is more conducive to testing and affirming the results of the phase work, and is also conducive to change control.

With the baseline provisions, it is prohibited to cross a milestone to modify the work results of another development stage, and it is considered that some completed stage results of the established milestones have been frozen.

Configuration status description and reporting

Task: Effectively record the information required for report management configuration. The purpose is to provide the current status of configuration items in a timely and accurate manner for relevant personnel to understand, so as to strengthen configuration management work.

Task: Verify the consistency of configuration items against configuration flags.

Software development practice shows that configuration items are marked to achieve change control and version control. If no checks or verifications are done, confusion can still occur.

Determine how to name the configuration item and what information to use to describe the configuration item

The oversight organization for configuration item changes.

Task: Evaluate and approve proposed changes to configuration items, and oversee the implementation of approved changes.

member:

Configuration items

Configuration ID

important content

Configuration ID

Configuration flags

Steps to establish a configuration management system

Git

SVN.

1. Development library

2. Controlled library

3. Product library

Configuration item change flow chart

In principle, configuration items under control are not allowed to be modified, but this is not absolute. If changes must be made for various reasons, you can submit a change request.

After the change request is approved by the joint review and the responsible leader, the configuration item is allowed to be checked out from the library. After the change is completed and reviewed, the change can be confirmed to be correct before it can be re-entered into the library to restore it to a controlled state.

Whether the development of configuration items has been successfully completed.

Whether the configuration items have reached the specified performance and functions

Whether the operation and supporting documents of the configuration items have been completed and meet the requirements.

Review formal test documents, review verification and validation reports based on test data; review all approved changes, review changed documents, and spot-check design review reports; conduct reviews to ensure that all tests have been performed; conduct additional sampling tests based on functional and performance requirements .

Whether each built configuration item conforms to the corresponding technical documentation.

Whether the configuration item corresponds to the information in the configuration status report

Review system specifications for completeness;

Compare architectural design and detailed design components for consistency;

Review the module list to determine compliance with approved coding standards;

Review the format and completeness of manuals (such as user manuals, operation manuals) and compliance with system function descriptions.