Table of contents
1. Classification of software documents
2. Four levels of document quality
2. Internal Documentation (Level 2)
3. Working documents (Level 3 documents)
4. Formal documents (Level 4 documents)
1. Definition of configuration management
2. Six main activities of configuration management
Preface
This article mainly records key notes on the test points of information document management and configuration management of project management.
1. Classification of software documents
1. Development documents
Describe the development process itself, including feasibility study report and project mission statement; requirements specification; functional specification; design specification, including program and data specifications; development plan; software integration and testing plan; quality assurance plan; security and Test information.
2. Product documentation
Describes the products of the development process; includes training manuals; reference manuals and user guides; software support manuals; product manuals and informational advertising.
3.Manage documents
Record project management information, including records of progress and progress changes at each stage of the development process; records of software changes; definition of responsibilities of the development team; project plan, project phase report; configuration management plan.
2. Four levels of document quality
Level 1.1 Documentation
It is suitable for developers who need less than one person-month to develop their own programs. The documentation should include a program listing, development records, test data, and a program introduction.
2. Internal Documentation (Level 2)
Can be used for specialized programs that do not share resources with other users. Level 2 documentation also includes sufficient comments in the program listing to help users install and use the program.
3. Working documents (Level 3 documents)
Suitable for programs jointly developed by several people within the same unit, or programs that can be used by other units.
4. Formal documents (Level 4 documents)
Suitable for software products that are to be officially released for general use, critical programs or programs with repetitive management applications (such as payroll calculations) require Level 4 documentation.
3. Configuration management
1. Definition of configuration management
Configuration management is formally defined as the application of technical and managerial guidance and monitoring methods to identify and describe the functional and physical characteristics of configuration items, control changes to these characteristics, record and report change processing and implementation status, and verify compliance with specified requirements. Compliance.
Software configuration management: It is about the management of software assets. What are software assets? Source code, design documents and other documents, executable programs, automatic test scripts, compilers and other tools and environments...all in the software Anything used or generated during the development process that is valuable and worthy of preservation are software assets. Software configuration management is about the management of these contents.
2. Six main activities of configuration management
3. Configuration items
Configuration items: project plans, requirements documents, design documents, source code, executable code, test cases, and various data required to run the software. They enter configuration management after being reviewed and inspected.
Some documents that cannot be modified after they are generated (such as measurement reports, meeting minutes, and work reports) cannot be used as configuration items. Configuration items can be modified.
Configuration items can be divided into two categories: baseline configuration items and non-baseline configuration items.
Baseline configuration items: including all design documents and source programs, etc.
Non-baseline configuration items: including various plans and reports of the project.
The operation permissions of all configuration items are strictly managed by the CMO (Configuration Administrator). The basic principle is: baseline configuration items are open to developers for reading; non-baseline configuration items are open to PM, CCB (Control Change Board) and related personnel. .
The code is as follows (example):
import numpy as np
import pandas as pd
import matplotlib.pyplot as plt
import seaborn as sns
import warnings
warnings.filterwarnings('ignore')
import ssl
ssl._create_default_https_context = ssl._create_unverified_context
Summarize
This article mainly records key notes on the test points of information document management and configuration management of project management.