◇ Feasibility Analysis Report: Description The implementation of the software development project is technically, economic and social factors, and commented on various possible implementations of the development goals to choose from, explain the selected The reason for the implementation plan. Http://blog.9cbs.net/bergn/Articles/227879.aspx01 Feasibility Analysis Report ◇ Project Development Plan: Develop a specific plan for the software project implementation, including the responsible persons of each part of the work, progress, development The budget of funds, the hardware and software resources required. http://blog.9cbs.net/bergn/Articles/227875.aspx02 Project Development Plan ◇ Software Demand Manual (Software Specifications): Detailed descriptions of the function, performance, user interface and operational environment of the developed software. It is written under the conditions of the user and the developer to obtain a joint understanding of software requirements and reach an agreement. It is also the basis for implementing development work. The specification should give data logic and data acquisition requirements to prepare for generating and maintaining system data files. http://blog.9cbs.net/bergn/Articles/227871.aspx03 Software Demand Manual ◇ Summary Design Manual: This manual is a summary of the actual phase of work, it should illustrate the functional allocation, module division, overall structure of the program, input Output and interface design, operation design, data structural design, and error processing design, etc., provides the basis for detailed design. http://blog.9cbs.net/bergn/Articles/227868.aspx04 Profile Design Manual ◇ Detailed Design Manual: Heavy descriptions of how each module is implemented, including implementation algorithms, logic flows, and more. Http://blog.9cbs.net/bergn/Articles/227867.aspx05 Detailed Design Manual ◇ User Operation Manual: This manual describes the software's functionality, performance, and user interface. User users have a specific understanding of how to use this software. Providing the operator provides specific details of the various operating conditions of the software, especially the specific details of the operation method. Http://blog.9cbs.net/bergn/Articles/227865.aspx06 User Operation Manual ◇ Test Plan: To do integrated testing and acceptance testing, you need to organize test and formulate implementation plans. The plan should include the content, progress, condition, personnel, test case selection principle, and the range of deviations allowed by the test results. 07 Test Program ◇ Test Analysis Report: After the test work is completed, the test plan shall be submitted to the test plan, and the test results should be submitted, and the conclusions of tests are proposed. Http://blog.9cbs.net/bergn/Articles/227864.aspx08 Test Analysis Report ◇ Development Progress Month Report: The report of the project submitted to the management department on the monthly report, the report should include progress plans and The actual implementation of the comparison, stage results, the problems encountered and the solution, and the plan for next month. Http://blog.9cbs.net/bergn/Articles/227859.aspx09 Development Progress Mun Report ◇ Project Development Summary Report: After the software project development is completed, it should be compared with the project implementation plan, summarize the actual implementation, such as progress, results , Resource utilization, costs, and investment have, in addition, it is necessary to make an evaluation of development work and summarize experiences and lessons. 10 Development Progress Months http://blog.9cbs.net/bergn/articles/227857.aspx ◇ Software Maintenance Manual: mainly includes software system description, program module description, operating environment, support software instructions, maintenance process, Easy to maintain the maintenance of the software. Http://blog.9cbs.net/bergn/Articles/227855.aspx11 Software Maintenance Manual ◇ Software Issues Report: Point out the registration of software issues, such as dates, discovers, state, and problem modules, etc., provide preparation for software modification Documentation.
Http://blog.9cbs.net/bergn/Articles/227851.aspx12 Software Issues Report ◇ Software Modification Report: After the software product is put into operation, it is found that there is a problem that it needs to be corrected, change, etc., the problem, modification Considering and the impact of the modification make detailed description, submit approval. http://blog.9cbs.net/bergn/Articles/227847.aspx13 Software Modify Report Note that the above file is encoded. Then, for document numbers: 01 ~ 20: Leave a standardized document 21 ~ 50: leave a non-standardized supplement document 51 ~ 99: leave the auxiliary document, or refer to the document
