We've been working on projects, and the documentation generated in the middle of the project is a "contract" that is delivered to the customer and is an inheritable outcome of the project as a whole. People in the project may feel they are aware of the whole project, and there is no need to bother writing documents that few people read. But what you write down is what you actually do, and what you don't write down is always verbal.
The following is a list of the documents to be produced in the process of an IT project, for your reference:
1 stage: Project proposal, feasibility study report, "can be researched and approved"
2 tender Stage: "Tender Specification", "Technical Answer book".
3 Requirement Analysis Stage: User requirement specification, software specification
4 Overall design phase: "Master Design Manual"
5 Overview Design phase: "Summary Design Manual"
6 Detailed design stage: "Detailed design Specification-database" "Detailed design Manual-Backstage" "Detailed design Specification-interface" "Detailed design specification-front desk"
7 Integrated Deployment phase: Integrated deployment scenario-host, integrated deployment scenario-database
8 Integrated Test phase: "System test Plan" "Uat Test Report" "Test Analysis Report" "Acceptance Test Report" "Performance test Report"
9 cutting on-line stage: "On-line cutting plan" "on-line cutting program"
10 Commissioning and handover phase: "Trial Operation Report"
11 Preliminary examination Stage: "Preliminary Examination Application" "Completion Settlement Report" "First verification book"
12 Final inspection stage: Final inspection application, final report of completion
Software development process Document List "Go"