如果将一种文档类型用于多种目的，那么应该为每种目的提供一个样例。
If you use a document type for multiple purposes, you should provide a sample for each purpose.
用例实现和软件体系结构文档将转化为详细的设计文档。
The use case realizations and the software architecture document translate into detailed design documents.
在该例中，所有信息都是通过访问适当的文档来检索的。
In the example, all information is retrieved by accessing the appropriate documents.
在许多情况下，更新用例和相关的文档要比修改代码本身花费更多的时间。
In many cases, updating the use cases and related documentation took longer than the code fix itself.
此外，你可以从用例产生用户文档。
Furthermore, you can derive user documentation from use cases.
我们同意这个文档应该包括用例和非功能需求(可靠性、可用性等等)。
We agreed that this document would consist of both use cases and nonfunctional requirements (reliability, usability, and so on).
测试人员：测试人员能够创建/更新/删除测试用例、测试结果，并查看产品/版本、功能规范和产品文档。
Testers: Testers will be able to create/update/delete the testcases, test results, and view the product/builds, functional specifications, and product documentation.
一个具体的用例就是处理会计系统中的文档。
One concrete use case is the handling of documents in an accounting system.
清单6显示了一个样例执行历史文档。
PDO库：找到关于在PHP 中访问数据库的所有这些用例的优秀文档等资源。
The PDO library: Find excellent documentation about all of these use cases for accessing databases in PHP and more.
因此，我们要解决的问题是识别和冲突，以及结合多种文档的用例。
So the problems to address are recognition and collision, with the use case being combining multiple documents.
让我们以一个简单的WSDL文档为例。
一般情况下，只有等到用例良好地创建完成之后，这些文档才可以利用。
Typically, this documentation is not available until after use case creation is well underway.
清单4是这类文档的一个样例。
交互图是用于交流在用例实现团队会议中出现的设计思想的非正式文档。
Interaction diagrams are informal documents used to communicate design ideas that come up during the use-case realization team sessions.
下一步是为爬行器提供一个样例通知文档。
The next step is to make a sample announcement document available to the crawler.
在图2 中显示的内容是被粘贴到每个用例作为模板的文档窗口。
The content shown in Figure 2 was pasted into each use case's documentation window to serve as a template.
此文档并不会提供各个用例的概述和最佳实践。
This document is not intended to provide an overview on use cases and their best practices.
您是否会奢侈地创建传统的需求文档、用例等等？
Do you have the luxury of creating a traditional requirements document, use cases, and so on?
以清单4中的XHTML文档为例。
RUP推荐分为三类文档：一个前景文档，多个用例文档和一个补充规约文档，最后一种描述了不能根据用例描述的需求。
RUP recommends three categories: a vision document, use-case documents, and a supplementary specification document describing requirements that do not warrant use cases.
让用例带动用户文档。
用例：改变文档字体的颜色。
在我们的样例应用程序中，数据对象将被系列化为xml文档，然后保存到数据库中。
In our sample application, the data object will be serialized into XML document and then saved into the database.
这个样例业务组件是一个文档库。
本系列的第1部分包含一个代码样例，展示了如何用内存中的另一个文档替换永久xml文档。
Part 1 of this article series included a code sample that showed how to replace a persistent XML document with another document held in memory.
该例表明，BICS文档可以使用URL(可能是一个模式的位置)引用约束。
A BICS document can reference a constraint that USES a URL (perhaps the location of a schema) as in this example.
在此样例应用程序中，您可以使用客户机端脚本确认文档的删除。
In this sample application, you can use a client-side script to confirm the removal of a document.
识别文件，比如样例、多媒体和办公文档。
Identify files, such as samples, multimedia, and office documents.
RUP的文档显示了从业务用例模型到业务对象模型和系统用例模型的演进；我们发现这是非常正确和有帮助的。
The RUP documentation shows the evolution from business use-case model to business object model and system use-case model; we found this to be quite accurate and helpful.
应用推荐