从一个需求类型中删除一个属性。
创建一个需求类型和属性定义。
用户定义他们的需求类型的能力。
The ability for users to define their own requirement types.
需求类型及其关系一起被称为追溯策略。
The requirement types and their relationship together are referred to as the traceability strategy.
如何弄清需求类型的词汇？
需求类型(编辑)的权限。
追溯需求的必备条件是需求类型的清晰定义。
The prerequisite for tracing requirements is a clear definition of requirement types.
RM工具使你易于创建需求类型并赋予属性。
RM tools allow you to easily create requirement types and give them attributes.
您可以根据需求类型或者位置来筛选您的需求。
You can filter your requirements by requirement type or location.
根据您的需求，需求类型可以当作模版来使用。
A requirement type serves as a template for your requirements.
从导入的需求类型创建新的Composer需求。
Create new composer requirements from imported requirement types.
如图10所示，有6种基本需求类型与用例项目关联。
As shown in Figure 10, there are six basic types of requirements associated with a use-case project.
明确的追溯要求您手动地建立两个需求类型之间的关系。
Explicit traceability requires you to manually establish a relationship between two requirement types.
每个项目都有关联的文档类型、需求类型以及需求属性。
Each project has associated document types, requirement types, and requirement attributes.
利用标签sdp创建一个称为软件开发计划的新需求类型。
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).
它还包括了需要的可传递构件，以及合适的文件以及需求类型。
It also includes required deliverables, along with appropriate document and requirement types.
不同的项目需要不同的需求类型和/或为追溯定义的不同关系。
Different projects require different requirements types and/or different relationships defined for traceability.
Meta - data，如属性类型，需求类型、文档类型。
Meta-data, such as attribute types, requirement types, document types These items are not accessible through the RPX.
一旦分离开来，经过分割的需求类型将会节省工程的时间和开销。
Once separated, dissected requirement types can save your project time and money.
可以添加定制需求类型、需求属性、定制文件夹以及数据库视图。
You can add custom requirement types, requirement attributes, custom folders, and database views.
特殊的需求类型(例如，与时间或计划有关等等)由语言扩展项处理。
Specific types of requirements (for example, related to timing or scheduling, etc.) are handled by language extensions.
它们可以在不同的需求与工件之间进行应用，也可以映射到需求类型中。
They can be applied across requirements and artifacts and can also map to requirement types.
对于一个通用的集成，用户可以将任意的记录类型与需求类型联系起来。
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.
从纯粹的传统(说明性的)需求方法到基于用例的方法引入了新的需求类型。
Moving from a purely traditional (declarative) requirements approach to a use-case based approach introduces new requirement types.
在管理员项中，点击“Import”按钮以导入需求以及它们的需求类型。
On the administrator tab, click the "Import" button to import requirements and their requirement types.
这些需求类型除了彼此之间的关联外，还可以与相关的业务模型元素建立关联。
As well as relating these requirement types to each other, they can be related to the business model elements where they are relevant.
利用标签EXP创建一个称为期望的新需求类型，然后创建表1中显示的属性。
Create a new requirement type called expectation with the tag exp, and then create the attributes shown in Table 1.
拓扑模型中这些松散结合关系为单元和可利用需求类型之间提供了最大的灵活度。
These are loosely coupled together in the topology models to provide utmost flexibility between the unit and the available requirement types.
计划鼓励你考虑和规约你需要的需求类型，它反过来确保需求编写的一致性与可读性。
A plan encourages you to think about and specify requirement types you will need, which in turn helps to ensure consistency and readability for written requirements.
应用推荐