Project Development Summary Report

Project Development Summary Report
I Introduction
1.1 Writing Purpose
Describes the purpose of preparing the project development summary report and points out the expected scope of reading.
1.2 Background
Note:
A. Name of the project and the name of the developed software system;
B. The task initiator, developer, user, and computing center where the software is installed.
I .3 Definition
Lists the definitions of specialized terms used in this document and the original phrases of the foreign acronyms.
1.4 references
List the reference materials to be used, such:
A. approved plans and tasks or contracts and approvals from higher authorities for this project;
B. Other published documents of the project;
C. Documents and materials referenced everywhere in this document, including the software development standards to be used. Lists the titles, document numbers, publication dates, and publishing units of these files, indicating the sources where these files are available.
2. Actual development results
2.1 Products
Describe the final product, including:
A. the names of various programs in the Program System, the hierarchical relationship between them, the program volume of each program, the form and quantity of storage media in kilobytes;
B. the versions of the program system, their respective versions, and their differences;
C. Name of each file;
D. Each database created. If a configuration management plan has been developed during development, it should be compared with this plan.
2.2 Main functions and performance
The main functions and performance of the software product are listed one by one. The feasibility study report, project development plan, and functional requirements are compared. find the relevant content of the manual, indicating that the original development goal has been reached, not fully met, or exceeded.
2.3 Basic Process
The following figure shows the basic process of the Program System.
2.4 progress
The comparison between the original plan progress and the actual progress shows whether the actual progress is in advance or delayed. The main reasons are analyzed.
2.5 cost
Compare the original plan cost with the actual expenditure cost, including:
A. labor hours, in the unit of month, are measured at different levels;
B. the time used by the computer to differentiate the CPU time and the time of other devices;
C. Other expenses such as material consumption and delivery cost.
Clearly state whether the funds have been exceeded or saved, and analyze the main reasons.
3 Development Evaluation
3.1 Production Efficiency Evaluation
The actual production efficiency is provided, including:
A. Average production efficiency of the program, that is, the number of lines produced per month;
B. Average file production efficiency, that is, the number of thousand words produced each month;
Compare the number of original plans.
3.2 Product Quality Evaluation
This section describes the incidence of errors detected in programming during testing, that is, the number of error commands (or statements) in each dry instruction (or statement ). If a quality assurance plan or configuration management plan has been developed in development, it should be compared with these plans.
3.3 evaluation of technical methods
Evaluate the technologies, methods, tools, and means used in development.
3.4 error Cause Analysis
Analyze the causes of errors in development.
4. Experience and Lessons Learned
List the most important experiences and lessons learned from this development work and the suggestions for future project development work.