需求文本被清晰地标注。
记住需求文本与属性值有一个完整的拷贝。
Bear in mind that this is a complete copy of the requirement text and the attribute values.
要记住当您引入文件时，只可引入需求文本。
Keep in mind that when you import documents, only the requirement text will be imported.
对于一个已存在的需求，只有需求文本会被改变。
In case of an existing requirement, only the requirement text would be changed.
表格中包括需求号、需求文本、以及各种属性，例如优先级和身份等。
The table contained the requirement ID, the requirement text, as well as the various attributes, such as priority and status.
这个boolean值可以使您用下列任何一种方法在一个文档外部对需求文本进行更改。
The Boolean value enables you to change requirement text outside of a document in any of these ways.
表2显示了一段需求文本摘录，其中的identification服务与所有主体关联。
Table 2 shows an excerpt from a requirements document in which the identification service is associated with all the principals.
为了版本控制的目的，这种评审活动只应该发生在需求分析师要对需求文本进行评审的时候，或者之后。
The review activity should occur on or after a specific date on which the text of the requirements is to be reviewed by a requirements analyst for versioning purposes.
如图11所示，选择Vision文档中的需求文本(我们选择“产品特性”一节中描述的第一个特性的文本)。
As shown in Figure 11, select the requirement text in the Vision document (we chose the text for the first feature outlined in the Product Features section).
本方法首先对中文需求文本进行初步句法和语义分析处理，然后通过对得到的结果进行分析，自动生成问卷来完善类图中的建模元素。
This method generates questionnaires based on the result of the initial semantic analysis of requirement text, which helps to refine the modeling elements.
当一个需求分析师因为版本控制的目的要评审需求文本时间时候，我们会为每一个需求定义一个新的的VersioningReviewdate属性。
We define the meaning of the versioning review date for each requirement as the date on which the text of the requirement is subject to review by a requirements analyst for versioning purposes.
您还可以打开其他的工件，例如一个用例文件，并强调显示文本以提取一项需求，如图13所示。
You can also open other artifacts, such as a use case document, and highlight text to extract a requirement, as Figure 13 illustrates.
需求和类似的用例，并不仅仅是文本。
由于用户密码是在网络上以正文文本格式传输的，因此这并不能满足安全身份验证的需求。
With users' passwords traveling over the network in plain text, you do not meet the requirement for secure authentication.
在需求定义过程中会广泛使用文本文件。
Text documents are still widely used in the requirements definition process.
利益关系人也可以通过一个在线的协作环境，在需求探索过程中使用直观的文本和可视化标记。
Stakeholders in the requirements process bring their expertise together using intuitive rich requirements text and visual notations in a collaborative, web-based environment.
两家公司都确信对于能够显示电子文本设备的需求将会爆炸般增长。
Both firms are betting that demand for devices dedicated to displaying electronic text will grow explosively.
范例包含了视频文件，业务用例文件；用例描述，描述性文本；包含一个或者多个其他需求工件的报告。
Examples include vision documents, business case documents; report mock-ups; use case descriptions; declarative text; reports containing one or more other requirement artifacts.
您的日常需求工作将会一直围绕工件进行，而它正是文本文件、草图、图形以及类似最常见的形式。
Your daily requirements work will revolve around these artifacts, which is our general term for text documents, sketches, images, and the like.
正如我们在前一个迭代中所做的那样，我们要添加文本标签，以识别需求中的元素，然后将需求与文本注释联系起来。
As we did in previous iterations, we add text labels to identify elements that are subject to requirements and then attach requirements to text annotations.
用例文本和关系图描述用户对需求的理解。
Use case text and diagrams describe the users' understanding of the requirements.
因而，规则包含某个“用户需求”的正式和可实现的表达，通常使用自然语言(例如英语)以文本形式进行陈述。
A rule thus embodies a formal, implementable expression of some "user requirement," usually stated in textual form using a natural language (for example, English).
从大型文本文件转移至可视代表，并使用基于场景的需求定义(参见图5)。
Move away from large text documents to visual representations, and use scenario-based requirements definitions (see Figure 5).
用户可以从定义了文本的任何地方(需求文档、电子邮件、模型内容等等)调用它。
It can be invoked by users from any location that defines text (requirements documents, emails, model content, and so on).
编写方案文本，而非功能需求。
这允许您扩展InfoSphereWarehouse的文本分析功能，以满足特定的需求。
This lets you extend the text analysis capabilities of InfoSphere Warehouse to meet your specific requirements.
图4代表了Composer工具中需求的多格式文本。
Figure 4 represents rich text from a requirement in the composer tool.
在第1部分中，您已经学到了如何将DocBookXML文档转换成满足电子邮件发布苛刻需求的文本格式。
In Part 1, you learned how to convert DocBook XML documents to a text format that satisfies the stringent requirements of E-mail publishing. This required three steps.
默认地，AjaxTags可以处理XML、HTML和纯文本内容，这应该可以满足大多数的用户需求。
AjaxTags deals with XML, HTML, and plain text content by default, which should cover most user needs.
文本或blob等可变大小字段也是如此，其中表大小的增长可以远超过需求。
This is also true with variable size fields, such as text or blob, where the table size can grow much larger than needed.
应用推荐