13 Documents required for software development

In the software project development process, should write according to the software development request 13 kind of document, the document preparation request has the pertinence, the accuracy, the clarity, the completeness, the flexibility, the traceability!

1. Feasibility Analysis Report

This paper illustrates the feasibility of the implementation of the Software development Project on the technical, economic and social factors, and discusses the reasons for the selected embodiments in order to reasonably meet the various possible implementation options for the development goals.

2. Project Development Plan

A specific plan for the implementation of the software project should include the responsible personnel for each part of the work, the progress of development, the budget for development funds, the hardware and software resources required.

3. Software Requirement Specification (software specification)

The function, performance, user interface and operating environment of the software developed are described in detail. It is written under the condition that both the user and the developer have a common understanding and agreement on the software requirements, and it is the basis of the implementation of the development work. The specification should give the data logic and the requirements of the collection, in order to generate and maintain the system data files ready.

4. Summary Design Manual

The manual is a summary of the actual stage of the work, it should explain the function allocation, module division, the overall structure of the program, input and output and interface design, operation design, data structure design and error processing design, to provide a basis for detailed design.

5. Detailed design Instructions

It focuses on how each module is implemented, including implementation algorithms, logical processes, and so on.

6. User Operation manual

This manual provides a detailed description of the software's functionality, performance, and user interface, giving the user a specific understanding of how to use the software, providing the operator with knowledge of the various operating conditions of the software, in particular the specifics of the operating method.

7. Test Plan

In order to do the integration test and acceptance test, we need to develop an implementation plan for how to organize the test. The plan should include the content of the test, progress, conditions, personnel, the selection of test cases, the allowable deviation range of the test results, etc.

8. Test Analysis Report

After the completion of the test work, the test plan should be submitted a description of the implementation of the test results are analyzed, and put forward the test of the concluding comments.

9. Monthly Development Progress

The monthly report of the software personnel to the management of the project progress report, which should include the progress plan and actual implementation of the comparison, phase results, problems encountered and solutions, and next month's plan.

10. Project Development Summary Report

After the completion of software project development, should be compared with the project implementation plan, summarize the actual implementation of the situation, such as progress, results, resource utilization, cost and input of manpower, in addition, also need to evaluate the development work, summed up the experience and lessons.

11. Software Maintenance Manual

Mainly includes software system description, program module description, operating environment, support software Description, maintenance process description, easy to maintain the software.

12. Software Problem Report

It points out the registration of software problems, such as date, discovery person, status, problem belongs to the module, to provide preparation documents for software modification.

13. Software Modification Report

After the SOFTWARE PRODUCT is put into operation, it is found that it needs to be amended, changed and so on, the existing problems, modification considerations and the impact of the changes should be described in detail and submitted for approval.

13 Documents required for software development