Transfer from S8S8, I feel that I will use it, so I archive here.
-------------------------------------------------- ---
Teach you how to do project development summary report I introduction 1.1 Writing purposes Description Writing this project development summary report, pointing out the expected reading range. 1.2 Background Description: a. The name of this project and the name of the software system developed; b. This software task makes a computing center for the developer, user, and install this software. I. 3 Define the definition of the specimen used in this document and the original phrase of the first letter of the foreman. 1.4 References list the references to be used, such as: a. The approved planned task book or contract of the project, the approval of the superior organ; b. Other published files belonging to this item; c. The documents, materials, information, including the software development criteria they want are included in this document. List the title, file number, publishing date, and publishing units of these files, indicating that the source of these files can be obtained. 2 Real Development Results 2.1 Product Description The final product, including: a. The names of each program in the program system, the hierarchical relationship between them, the amount of the program, the number of stored media, and the number of procedures, B. B. Which versions of the program system share, the respective version numbers and the differences between them; Name of each file; d. Each database established. If the development of the configuration management plan is developed, it is necessary to compare with this plan. 2.2 The main functions and performances list the main functions and performances actually have actual features and performance in this software product, and the feasibility study report, project development plan, and function. Ask for the content of the specification, indicating that the original development goal is reached, not fully reached, or more. 2.3 Basic flow Use the figure to give the actual basic processing flow of the program system. 2.4 Scientific Progress The comparison of the progress of the original plan and the actual progress, clearly stated that the actual progress is in advance, or is delayed, and the main reasons are analyzed. 2.5 Fees list comparisons for the original plan fees and actual expenses, including: a. Time, in the month of the month, and statistics on different levels; b. Computer usage time, distinguishably CPU time and other device times; C. Other expenditures such as material consumption, travel fees. It is clear that the funds are exceeded, or it is sailed, and the main reasons are analyzed. 3 Development Work Evaluation 3.1 The evaluation of production efficiency gives actual production efficiency, including: a. The average production efficiency of the program, that is, the number of rows produced per month; b. The average production efficiency of the document is the number of thousands of words produced per month; and the number of original plan is listed as contrast. 3.2 Evaluation of Product Quality Description The error incidence in the program preparation inspected in the test, namely the number of error instructions (or the number of statements) in each dry strip instruction (or statement). If the development of quality assurance plans or configuration management plans are developed in the development, they should be compared to these programs. 3.3 Evaluation of technical methods gives the evaluation of the techniques, methods, tools and means used in the development. 3.4 Analysis of the cause of error given the cause analysis of errors in the development. 4 Experience and lessons list the most important experience and lessons from this development work and recommendations for future project development work.
