Permissions of requirement types (edit).
需求类型(编辑)的权限。
How to clarify the vocabulary of requirement types?
如何弄清需求类型的词汇？
The ability for users to define their own requirement types.
用户定义他们的需求类型的能力。
Create new composer requirements from imported requirement types.
从导入的需求类型创建新的Composer需求。
RM tools allow you to easily create requirement types and give them attributes.
RM工具使你易于创建需求类型并赋予属性。
The prerequisite for tracing requirements is a clear definition of requirement types.
追溯需求的必备条件是需求类型的清晰定义。
Each project has associated document types, requirement types, and requirement attributes.
每个项目都有关联的文档类型、需求类型以及需求属性。
They can be applied across requirements and artifacts and can also map to requirement types.
它们可以在不同的需求与工件之间进行应用，也可以映射到需求类型中。
You can add custom requirement types, requirement attributes, custom folders, and database views.
可以添加定制需求类型、需求属性、定制文件夹以及数据库视图。
The requirement types and their relationship together are referred to as the traceability strategy.
需求类型及其关系一起被称为追溯策略。
Explicit traceability requires you to manually establish a relationship between two requirement types.
明确的追溯要求您手动地建立两个需求类型之间的关系。
On the administrator tab, click the "Import" button to import requirements and their requirement types.
在管理员项中，点击“Import”按钮以导入需求以及它们的需求类型。
However, the schema for topology model does not enforce any strict association between unit and requirement types.
然而，拓扑模型方案并不强制单元与需求之间有任何严格的关联。
Some examples of requirement types in RequisitePro are stakeholder needs, features, use cases, actors, and glossary terms.
在RequisitePro中一些需求类型的例子是涉众需求，特性，用例，参与者，和术语条款。
Moving from a purely traditional (declarative) requirements approach to a use-case based approach introduces new requirement types.
从纯粹的传统(说明性的)需求方法到基于用例的方法引入了新的需求类型。
This allows business rule specifications, service requirements or other requirement types to be expressed in terms of glossary terms.
这样便可以用术语表中的术语表达业务规则、服务需求或其他需求。
As we saw earlier, requirement types might include business needs, features, and functional and non-functional software requirements.
正如我们前面看到的，需求类型可能包括业务需要、特性以及功能性和非功能性的软件需求。
As well as relating these requirement types to each other, they can be related to the business model elements where they are relevant.
这些需求类型除了彼此之间的关联外，还可以与相关的业务模型元素建立关联。
Then, as you collect information from stakeholders, decide which of the requirement types they are describing, and write the requirement.
这样，在你从涉众那里收集信息时，要确定他们描述的是何种需求类型，然后写成需求。
These are loosely coupled together in the topology models to provide utmost flexibility between the unit and the available requirement types.
拓扑模型中这些松散结合关系为单元和可利用需求类型之间提供了最大的灵活度。
In addition to the requirement type, a hierarchy — or more generally, a set of valid relationships between requirement types — must be defined.
除了需求类型以外，层次——或更一般的说法，需求类型之间的一组有效的关系——必须要定义。
For developers who write requirements, the plan describes necessary requirements artifacts, along with requirement types and their respective attributes.
对编写需求的开发人员，该计划描述了必要的需求工件，以及需求类型及相应的属性。
After you have identified all of the requirement types from your various RequisitePro projects, you can create requirements based on these requirement types.
在从多个RequisitePro项目中识别所有的需求类型之后，您可以创建基于这些需求类型的需求。
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.
计划鼓励你考虑和规约你需要的需求类型，它反过来确保需求编写的一致性与可读性。
Add the attribute sureness factor (with a real assigned value) to other requirement types that could depend on expectations (e.g., stakeholder requests, features, etc.).
将属性确信因子(带有一个分配的实数值)添加到依赖于期望的其他需求类型中(例如，涉众请求，特性等)。
Once the project requirements are created, relationships can be defined between different requirement types, providing a means to trace requirements through the project life cycle.
项目需求创建之后，就可以在不同的需求类型之间定义关系，这提供了在项目生命周期中跟踪需求的一种手段。
If you have multiple projects that you want to define, repeat the previous step until all desired requirements and requirement types are imported to Rational requirements Composer.
如果您有想要定义的多个项目，重复以上的步骤直到所有想要的需求和需求类型都导入到RationalRequirements Composer中。
The prefix is used as an identifier for requirements and requirement types in this project when it is referenced as an external project for cross-project traceability (see Listing 3).
当这个项目被当作外部的项目引用或者当进行跨项目跟踪时，这个前缀就可以当作项目需求和需求类型的标识符来使用(请参见列表3)。
The prefix is used as an identifier for requirements and requirement types in this project when it is referenced as an external project for cross-project traceability (see Listing 3).
当这个项目被当作外部的项目引用或者当进行跨项目跟踪时，这个前缀就可以当作项目需求和需求类型的标识符来使用(请参见列表3)。
应用推荐