Change requirement type color and style.
更改需求类型颜色和风格。
The requirement type must first be defined.
需求类型必须首先定义。
Delete an attribute from a requirement type.
从一个需求类型中删除一个属性。
Create expectation as a new requirement type.
创建期望作为一个新的需求类型。
Create a requirement type and attribute definitions.
创建一个需求类型和属性定义。
Create Software Development Plan as a new requirement type.
创建软件开发计划(Soft ware Development Plan)作为一个新的需求类型。
You can filter your requirements by requirement type or location.
您可以根据需求类型或者位置来筛选您的需求。
A requirement type serves as a template for your requirements.
根据您的需求，需求类型可以当作模版来使用。
One requirement type can trace to more than one other requirement type.
一个需求类型可以追溯到超过一个的其他需求类型。
Type a title for the association window for the requirement type and record type.
在联系窗口中为需求类型与记录类型输入一个标题。
Whenever you document a requirement it must belong to a specific requirement type.
不论您什么时候编制一个需求，它都必须属于一个具体的需求类型。
For instance, the same requirement type can be associated with one or more unit type.
例如，同一个需求类型可以与一个或者更多的单元类型相关联。
Table 1: Attributes for the expectation requirement type in IBM Rational RequisitePro
表1：IBMRationalRequisitePro 中期望需求类型的属性
The requirement type will be of the RequisitePro document type default requirement type.
需求种类将会成为RequisitePro文件种类的默认需求种类。
And for a custom integration, user can associate any record type with any requirement type.
对于一个通用的集成，用户可以将任意的记录类型与需求类型联系起来。
You can configure how requirements are selected, either by either requirement type or by view.
您可以配置怎样选择需求，或者根据需求类型选择，或者根据视图来选择。
The requirement attributes will be set to the default values as defined in the requirement type.
需求属性将会被设置成，在需求种类中定义的默认值。
In RequisitePro project, the ClearQuest admin should add corresponding attributes for each requirement type.
在RequisitePro项目中，ClearQuest管理员应该为每一个需求类型添加相应的属性。
Scenario is not a standard requirement type in RequisitePro, so you need to add it as a new requirement type.
在RequisitePro中场景不是一个标准的需求类型，所以你需要增加它成为一个新的需求种类。
Create a new requirement type called expectation with the tag exp, and then create the attributes shown in Table 1.
利用标签EXP创建一个称为期望的新需求类型，然后创建表1中显示的属性。
Taking the following as a sample, you can assign the "Read" and "Update" permission for requirement type of 'System User Stories'.
拿接下来的部分做个例子，您可以为“系统用户事例”的需求类型分配“读取”和“更新”许可权。
In case of new requirements, the document's default requirement type will be assigned (regardless of the original requirement type).
对于一个新的需求，文件的默认需求种类会被指定(不考虑初始的需求种类)。
In addition to the requirement type, a hierarchy — or more generally, a set of valid relationships between requirement types — must be defined.
除了需求类型以外，层次——或更一般的说法，需求类型之间的一组有效的关系——必须要定义。
Administrators also control access to project documents and requirements by assigning document type and requirement type permissions to user groups.
管理员还可以通过给用户组分配文档类型和需求类型权限来控制项目文档和需求的访问。
An instance of a requirement type can trace to multiple instances of another requirement type (and vice versa based on the trace-from relationship).
需求类型的实例可以追溯到另一个需求类型的多个实例(而反过来基于追溯来的关系)。
This relationship defines which requirement type traces to, or is traced from, 5 which other requirement type. There is some complexity to be aware of
该关系确定了需求类型追溯到哪个需求类型，或从其他哪个需求类型追溯而来5 。
Create a new requirement type called Software Development Plan with the tag SDP. Then create the following attribute (in addition to others you might need).
利用标签sdp创建一个称为软件开发计划的新需求类型。
Therefore, if you are using RequisitePro to manage only one requirement type, you can move responsibility for requirements management to Rational Quality Manager.
因此，如果您正在使用RequisitePro以管理只有一种的需求类型，那么您可以将需求管理的重任迁移至Rational Quality Manager。
To facilitate this method, I propose the addition of a new attribute for every requirement type whose requirements might be used on releases with multiple versions.
为了改进这种方法，我建议对每一个需求类型增加一个新的属性，这些需求可以被基于多版本的发行版本使用。
To facilitate this method, I propose the addition of a new attribute for every requirement type whose requirements might be used on releases with multiple versions.
为了改进这种方法，我建议对每一个需求类型增加一个新的属性，这些需求可以被基于多版本的发行版本使用。
应用推荐