Software Development Process Documentation

Graduating six months, from the beginning of the internship, to do Android development one year, combined with their own, feel that the development report is very necessary, but for various reports to distinguish is very confusing. On the Internet to see in the software project development process, the requirement to write 13 types of documents, combined with the situation encountered in the development of their own projects, to collate this article, a developer's perspective to see the 13 kinds of reports

Document		Executive person		Details
Feasibility Analysis Report		Product Manager		The implementation of the project is technically, economically and socially feasible, available as a possible implementation of options and the pros and cons of implementing the scheme.
Project Development Plan		Product Manager		The implementation programme develops specific plans, which 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.
Software Requirement Specification (software specification)		Product Manager		The function, performance, user interface and operating environment of the software developed are described in detail. This document must be detailed, clear, avoid unclear requirements, development costs wasted. I dropped a lot of pits here.
Overview Design Manual		Development staff		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.
Detailed design Instructions		Development staff		It focuses on how each module is implemented, including implementation algorithms, logical processes, and so on.
User Operating Manual		Product Manager		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.
Test Plan		Test QA Staff		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.
Test Analysis Report		Test personnel		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.
Development progress Report		Development staff		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.
Project Development Summary Report		Product Manager		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.
Software Maintenance Manuals		Development staff		Mainly includes software system description, program module description, operating environment, support software Description, maintenance process description, easy to maintain the software.
Software Problem Report		Test personnel		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.
Software Modification Report		Development staff		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. At present, we are through a number of management sites, by testers to send bugs, developers accept the repair. Zen Road