Delete an attribute from a requirement type.
从一个需求类型中删除一个属性。
Create a requirement type and attribute definitions.
创建一个需求类型和属性定义。
You can filter your requirements by requirement type or location.
您可以根据需求类型或者位置来筛选您的需求。
Table 1: Attributes for the expectation requirement type in IBM Rational RequisitePro
表1：IBMRationalRequisitePro 中期望需求类型的属性
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中显示的属性。
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.
管理员还可以通过给用户组分配文档类型和需求类型权限来控制项目文档和需求的访问。
To increase the support of Rational RequisitePro for branch or merge scenarios, add two additional attributes to every requirement type that will be affected by branch or merge action.
为了增加RationalRequisitePro对于分支或者合并场景的支持力度，您需要向每一种需求类型添加两个附加的属性，分支或者合并操作会影响到这些需求类型。
To increase the support of Rational RequisitePro for branch or merge scenarios, add two additional attributes to every requirement type that will be affected by branch or merge action.
为了增加RationalRequisitePro对于分支或者合并场景的支持力度，您需要向每一种需求类型添加两个附加的属性，分支或者合并操作会影响到这些需求类型。
应用推荐