The project workbook is not so much a separate document as i

The project workbook is not so much a separate document as it is a structure imposed on the documents that the project will be producing anyway.

All the documents of the project need to be part of this （71）. This includes objectives ,external specifications , interface specifications , technical standards , internal specifications and administrative memoranda（备忘录）.

Technical prose is almost immortal. If one examines the genealogy （手册） of a customer manual for a piece of hardware or software , one can trace not only the ideas , but also many of the very sentences and paragraphs back to the first （72） proposing the product or explaining the first design. For the technical writer, the paste-pot is as mighty as the pen.

Since this is so, and since tomorrow’s product-quality manuals will grow from today’s memos, it is very important to get the structure of the documentation right. The early design of the project （73） ensures that the documentation structure itself is crafted, not haphazard. Moreover, the establishment of a structure molds later writing into segments that fit into that structure.

The second reason for the project workbook is control of the distribution of （74）. The problem is not to restrict information, but to ensure that relevant information gets to all the people who need it.

The first step is to number all memoranda, so that ordered lists of titles are available and h worker can see if he has what he wants. The organization of the workbook goes well beyond this to establish a tree-structure of memoranda. The （75） allows distribution lists to be maintained by subtree, if that is desirable.

（71）A.structure B.specification C.standard D.objective

（72）A.objective B.memoranda C.standard D.specification

（73）A.title B.list C.workbook D.quality

（74）A.product B.manual C.document D.information

（75）A.list B.document C.tree-structure D.number

【答案】A  B  C  D  C

【解析】

项目工作手册不是单独的一篇文档，它是对项目必须产出的一系列文档进行组织的一种结果。

项目的所有文档都必须是该结构的一部分。这包括目标，外部规范说明，接口规范，技术标准，内部规范和管理备忘录（备忘录）。

技术说明几乎是必不可少的。如果某人就硬件和软件的某部分,去查看一系列相关的用户手册。他发现的不仅仅是思路,而且还有能追溯到最早备忘录的许多文字和章节,这些备忘录对产品提出建议或者解释设计。对于技术作者而言,文章的剪裁粘贴与钢笔一样有用。基于上述理由,再加上“未来产品”的质量手册将诞生于“今天产品”的备忘录,所以正确的文档结构非常重要。事先将项目工作手册设计好,能保证文档的结构本身是规范的,而不是杂乱无章的。另外,有了文档结构,后来书写的文字就可以放置在合适的章节中。使用项目手册的第二个原因是控制信息布。控制信息发布并不是为了限制信息,而是确保信息能到达所有需要它的人的手中项目手册的第一步是对所有的备忘录编号,从而每个工作人员可以通过标题列表来检索是否有他所需要的信息。还有一种更好的组织方法,就是使用树状的索引结构。而且如果需要的话,可以使用树结构中的子树来维护发布列表。