1·Individual reports can be found in the Project Documentation section.
单独的报告可以在Project Documentation部分中找到。
2·Establish key performance metrics and appropriate project documentation.
建立关键绩效度量指标和适宜的项目文档。
3·In fact, a comment I received on that series said that it was better documentation for Spring than the project documentation!
实际上，关于该系列我收到过这样的评论：它比Spring的项目文档还要棒！
4·The team then cuts and pastes graphics from the slides to create formal project documentation, including requirements specifications.
然后团队从幻灯片上剪切并粘贴图形，创建正式的项目文档，包括需求规范。
5·Closure will include the development of the index and location of project documentation using the configuration management system.
收尾包括利用配置管理系统为项目文件编制一份索引指明位置。
6·To generate this project documentation just, open a command window and navigate to the AddressBookDeployment directory of the workbench.
要生成项目文档，请打开命令窗口并导航到工作台的AddressBookDeployment目录。
7·You guessed it: This article shows you how automation can streamline the process (and reduce the misery) of generating project documentation.
您猜对了：本文将向您展示如何运用自动化来简化项目文档的生成过程，从而减轻这方面的负担。
8·Trac is a Web-based software project-management tool that includes a wiki for managing project documentation and notes (see Resources for a link).
Trac是一个基于Web的软件项目管理工具，其中包括一个用于管理项目文档和笔记的wiki(请参阅参考资料)。
9·It provides a single portal for all project documentation, code, and artifacts, so the support team can have access to all of the development information through this software.
它为所有的项目文件，代码及工件提供了单个的端口，这样支持团队就可以通过该软件访问所有的开发信息了。
10·And forget about emailing around the various versions of your specification, because FogBugz also includes a full-featured wiki for authoring and reviewing project documentation.
不用再发邮件通知文档规范不同版本之间的变化了，因为FogBugz还包括有一个全功能的wiki，可帮助你撰写、查看项目文档。