GB/T 8567-2006 "Computer Software Documentation Specification" Development Progress Monthly Report (DPMR)

illustrate:

The purpose of the monthly development progress report is to report the progress and situation of the project development to the relevant management department in time, so as to discover and deal with the problems in the development process in time. Generally, the monthly development progress report is prepared monthly by the project team. If the scale of the software system to be developed is relatively large, the entire engineering project is divided into several sub-project teams to undertake, and the monthly development progress report will be based on the sub-project team. Prepare monthly for the unit.

 

 

 

 

 

1 Introduction

1.1 Identification

This paragraph shall contain the complete identification of the systems and software to which this document applies, including, if applicable , identification numbers, titles, acronyms, version numbers, release numbers.  

1.2 System overview

This paragraph should briefly describe the purpose of the systems and software to which this document applies. It should describe the general nature of the system and software; outline the history of system development, operation, and maintenance; identify the project's investors, acquirers, users, developers, and support agencies; identify current and planned operational sites; and list other relevant documentation.

1.3 Documentation overview

This paragraph shall outline the purpose and content of this document and describe the confidentiality and privacy requirements associated with its use.

Should state:

a. The name and identifier of the software system under development;

b. Subproject name and identifier;

c. Signature of the person in charge of the sub-project;

d. The signature of the writer of this monthly report;

e. The serial number of the current monthly report and the year and month of the report.

2 Reference documents

This chapter should list the numbers, titles, revisions, and dates of all documents referenced in this document. The source of all documentation not available through normal supply channels should also be identified.

3 Project progress and status

3.1 Progress

列出本月内进行的各项主要活动,并且说明本月内遇到的重要事件,这是指一个开发阶段(即软件生存周期内各个阶段中的某一个,例如需求分析阶段)的开始或结束,要说明阶段的名称及开始(或结束)的日期。

3.2状态

说明本月的实际工作进度与计划相比,是提前了、按期完成了或是推迟了?如果与计划不一致,要说明原因及准备采取的措施。

4资源耗用与状态

4.1资源耗用

主要说明本月份内耗用的工时与机时。

4.1.1工时

分为三类:

a.管理用工时。包括在项目管理(制订计划、布置工作、收集数据、检查汇报工作等)方面耗用的工时;

b.服务工时。包括为支持项目开发所必须的服务工作及非直接的开发工作所耗用的工时;

c.开发用工时。要分各个开发阶段填写。

4.1.2机时

说明本月内耗用的机时,以小时为单位,说明计算机系统的型号。

4.2状态

说明本月内实际耗用的资源与计划相比,是超出了、相一致、还是不到计划数?如果与计划不一致,说明原因及准备采取的措施。

5经费支出与状态

5.1经费支出

5.1.1支持性费用

列出本月内支出的支持性费用,一般可按如下七类列出,并给出本月支持费用的总和:

a.房租或房屋折旧费;

b.工资、奖金、补贴;

c.培训费。包括教师的酬金及教室租金;

d.资料费。包括复印及购买参考资料的费用;

e.会议费。召集有关业务会议的费用;

f.旅差费;

g.其他费用。

5.1.2设备购置费

列出本月内实际支出的设备购置费,一般可分如下三类:

a.购买软件的名称与金额;

b.购买硬设备的名称、型号、数量及金额;

c.已有硬设备的折旧费。

5.2状态

说明本月内实际支出的经费与计划相比较,是超过了、相符合、还是不到计划数?如果与计划不一致,说明原因及准备采取的措施。

6下个月的工作计划

7建议

本月遇到的重要问题和应引起重视的问题及因此产生的建议。

8注解

本章应包含有助于理解本文档的一般信息(例如背景信息、词汇表、原理)。本章应包含为理解本文档需要的术语和定义,所有缩略语和它们在文档中的含义的字母序列表。

附录

附录可用来提供那些为便于文档维护而单独出版的信息(例如图表、分类数据)。为便于处理,附录可单独装订成册。附录应按字母顺序(A,B)编排。

Guess you like

Origin http://10.200.1.11:23101/article/api/json?id=326801307&siteId=291194637