Standardization of Computer Software documentation

01 Feasibility Analysis Report
Http://blog.csdn.net/bergn/articles/227879.aspx
Bytes ------------------------------------------------------------------------------------------
02 Project Development Plan
◇ Project Development Plan: formulate a specific plan for the software project implementation plan, it should include the person in charge of each part of the work, the development progress, the development budget, the required hardware and software resources.
Http://blog.csdn.net/bergn/articles/227875.aspx
Bytes ------------------------------------------------------------------------------------------
03 Software Requirement Specification
◇ Software Requirement Specification (Software Specification): describes the functions, performance, user interface, and operating environment of the software. It is written under the conditions that both users and developers have a common understanding of the software requirements and reach an agreement. It is also the basis for the implementation of development work. This manual should provide data logic and data collection requirements to prepare for the production and maintenance of system data files.
Http://blog.csdn.net/bergn/articles/227871.aspx
Bytes ------------------------------------------------------------------------------------------
04 summary Design Manual
◇ Summary Design Manual: This manual is the work result of the actual phase. It should describe the function allocation, module division, Program The overall structure, input and output, interface design, operation design, data structure design, and error handling design provide the basis for detailed design.
Http://blog.csdn.net/bergn/articles/227868.aspx
Bytes ------------------------------------------------------------------------------------------
05 Detailed Design Manual
◇ Detailed design description: describes how each module is implemented, including implementation Algorithm And logical processes.
Http://blog.csdn.net/bergn/articles/227867.aspx
Bytes ------------------------------------------------------------------------------------------
06 User Manual
◇ User operation manual: This Manual describes the functions, performance, and user interface of the software in detail, so that you can get a detailed understanding of how to use the software, provide the operator with relevant knowledge about the various running conditions of the software, especially the detailed operation methods.
Http://blog.csdn.net/bergn/articles/227865.aspx
Bytes ------------------------------------------------------------------------------------------
07 test plan
◇ Test plan: to do a good job of integration test and acceptance test, we need to formulate an implementation plan for how to organize the test. The plan should include the testing content, progress, conditions, personnel, selection principles of test cases, and allowable deviation range of test results.
Http://blog.csdn.net/bergn/articles/227864.aspx
Bytes ------------------------------------------------------------------------------------------
08 Test Analysis Report
◇ Test Analysis Report: after the test is completed, a description of the execution of the test plan should be submitted, the test results should be analyzed, and the test conclusions and opinions should be put forward.
Http://blog.csdn.net/bergn/articles/227861.aspx
Bytes ------------------------------------------------------------------------------------------
09 monthly Development Progress Report
◇ Monthly Development Progress Report: This monthly report is a monthly project progress report submitted by software personnel to the management department, the report should include the comparison of the progress plan and actual implementation, the results of the phase, the problems encountered and solutions, and the plans for the next month.
Http://blog.csdn.net/bergn/articles/227859.aspx
Bytes ------------------------------------------------------------------------------------------
10 monthly Development Progress Report
◇ Project Development Summary Report: after the software project is developed, it should be compared with the project implementation plan to summarize the actual implementation status, such as progress, results, resource utilization, cost and invested manpower, in addition, the development work should be evaluated to sum up experience and lessons.
Http://blog.csdn.net/bergn/articles/227857.aspx
Bytes ------------------------------------------------------------------------------------------
11 software maintenance manual
◇ Software maintenance manual: This manual mainly includes software system description, program module description, operating environment, support software description, and maintenance process description to facilitate software maintenance.
Http://blog.csdn.net/bergn/articles/227855.aspx
Bytes ------------------------------------------------------------------------------------------
12 software Issue Report
◇ Software Issue Report: indicates the registration status of software problems, such as the date, detected person, status, module of the problem, and provides the preparation documents for software modification.
Http://blog.csdn.net/bergn/articles/227851.aspx
Bytes ------------------------------------------------------------------------------------------
13 software modification report
◇ Software modification Report: after the software product is put into operation, problems such as correction and modification are discovered, the existing problems, modification considerations, and the impact of the changes should be described in detail and submitted for approval.
Http://blog.csdn.net/bergn/articles/227847.aspx
Bytes ------------------------------------------------------------------------------------------

Note that the above files are encoded at the beginning.
Then, for the document number:
01 ~ 20: left to the canonicalized document
21 ~ 50: reserved for non-normalized supplementary documents
51 ~ 99: Leave it to the auxiliary document or reference document