您可以从已经存在的工件中创建需求。
RM工具使你易于创建需求类型并赋予属性。
RM tools allow you to easily create requirement types and give them attributes.
捕获需求、创建需求文档和管理需求。
Capturing requirements, creating requirements documents, and managing requirements.
首先，因为门户全是关于用户界面的，所以创建需求的业务人员对这些需求的关心要多于传统项目。
First, because portals are all about user interfaces, the business people creating requirements care much more about these requirements than a traditional project.
在第一次迭代后的每一次中，我们通过深入钻研具体功能领域(用例)来创建需求的深度视角，因而为每个迭代建立一个SRS。
During each iteration after the first, we create the depth view of requirements by doing deep dives into specific functional areas (use cases), thus building an SRS for each iteration.
业务分析员应该推广需求；但是，对于简洁性，我们将会创建一个简单的需求。
Requirements should be populated by the business analyst; for simplicity, however, we will create a sample requirement.
第一，它强制企业尽早考虑外观问题，并为他们提供一个论坛来创建这些需求。
First, it forces the business to think about look and feel issues early and provides them a forum to create these requirements.
在这个阶段，动态业务应用的需求比创建它们所需的设计实践更清晰。
At this stage, the requirements for Dynamic Business Applications are clearer than the design practices needed to create them.
此方法将允许他们快速地创建满足其情景需求的应用程序。
This approach would allow them to rapidly create applications that meet their situational needs.
现在你就可以根据需求创建用例与角色之间的联系了。
Now you can create associations between use cases and actors according to the requirements.
然后我们将描述基本的模式设计范式，并将探索创建满足项目需求的作用域设计方面的考虑因素和最佳实践。
Then we'll describe basic schema design patterns and explore considerations and best practices for creating scope designs that fit the needs of your projects.
现在您能够根据演进的需求创建各种分析配置，并且根据那些配置方便地运行分析。
You are now able to create various analysis configurations based on your evolving needs, and conveniently run analyses based on those configurations.
清单7显示一个无序列表，它根据这些需求创建主导航内容的结构。
Listing 7 shows the unordered list created to structure the content for the primary navigation based on these requirements.
测试人员直接根据说明用例的功能需求创建测试脚本。
The tester creates test scripts directly from the functional requirements that illustrate the use case.
我们需要创建符合特定基础结构需求的脚本。
You need to create scripts to match specific infrastructure needs.
毕竟，您已经创建了需求，对它们进行了分类，并将它们放在了需求管理系统中；为什么需要在门户研讨会上再一次讨论它们呢？
After all, you have already created the requirements, categorized them, and placed them into your requirements management system; why do you need to discuss them again in the portal workshop?
私有云的常见需求是创建标准的镜像、虚拟化和自动化。
With a private cloud, there needs to be support for creating standardized images, virtualization and automation.
谁创建项目需求，团队中的哪个人需要使用这些需求？
Who creates project requirements, and who on the team needs to have access to these requirements?
项目需求创建之后，就可以在不同的需求类型之间定义关系，这提供了在项目生命周期中跟踪需求的一种手段。
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.
这些人没有去创建有需求的读者，但却提供给了他们有用的东西。
These guys did not create the waiting audience, but they do provide for it.
添加第二种步骤，以证实您在早期创建的需求中添加的主题。
Add a second step to verify that the subjects you added in the requirement that you created earlier are listed.
根据他们的义务，他们可以读取和回应注释，创建和更新支持工件，创建和更新需求。
According to their responsibilities, they can read and respond to comments, create and update supporting artifacts, create and update requirements.
您是否会奢侈地创建传统的需求文档、用例等等？
Do you have the luxury of creating a traditional requirements document, use cases, and so on?
需求也可以通过RPX创建。
例如，以创建功能需求(如为企业内的应用程序对用户访问进行重新验证)为例。
As an example, consider common capability needs such as user access revalidation for applications within an enterprise.
看看这种策略能否发现需求的突然增加，从而创建更多的实例以满足这些需求。
Check how the policy detects sudden increases in the demand and results in the creation of additional instances to fill in the demand.
于是我们发现了更高的需求，于是创建了更多的实例来满足这种需求。
Higher demand would be detected and more instances would be created to fill that demand.
接下来用户就可以根据模型创建对需求的跟踪链接，这种链接能自动提供跟踪、影响分析以及覆盖文档等功能。
Users then create traceability links from the model to the requirements, automatically providing traceability, impact analysis and coverage documentation.
新创建的需求并不是原始需求的拷贝，而是应用默认值的新实例。
The newly created requirements are not copies of the original requirements but new instances with applied default values.
利用标签EXP创建一个称为期望的新需求类型，然后创建表1中显示的属性。
Create a new requirement type called expectation with the tag exp, and then create the attributes shown in Table 1.
应用推荐