Rational RequisitePro software is an easy-to-use requirements management tool.
RationalRequisitePro是一种非常容易使用的需求管理工具。
The Company may use requirements and field conditions, is designed to accommodate customer demand.
本公司可根据使用要求和现场条件，设计适合客户需求的产品。
1in this article, I use requirements engineering "as a short form for business requirements engineering."
1在这该文章中，我使用需求工程，作为业务需求工程一个简称。
For modest use requirements, Dillo may provide a good compromise between a fully featured browser and the austerity of Lynx.
对于要求不太高的使用需求来说，Dillo是介于功能完善的浏览器和只有少量开销的Lynx之间的折中方案。
The diagram below shows how the roles of project manager, architect and test lead use requirements to accelerate their tasks.
下面显示的图向您展示了项目管理员，结构师和测试领导等角色是怎样使用需求来促进开发任务的。
Organizations that use requirements templates, which reflect tested procedures for producing quality requirements, can help in this regard.
组织机构使用可以反映生产质量需求的测试程序的需求模板，在这个方面有所帮助。
As we also noted earlier, attributes provide supplemental information that helps you understand and use requirements specifications more effectively.
也如我们前面注意到的，属性提供了补充信息，使你更加有效地理解和使用需求规约。
Chapter 9, "Managing the requirements," touches on a broad array of techniques by which project leaders can use requirements to keep a project healthy.
第9章，“管理需求”，简略提到项目经理使用需求来保持项目健康的技巧。
As you work on performance management issues, it's a good idea to use requirements management techniques to help you determine the impact of the problem on the business.
在处理性能管理问题时，最好使用需求管理技术来帮助确定问题对业务的影响。
As the generalization of topographic data, thematic data generalization needs the support of generalization knowledge to satisfy the use requirements and reflect the main geographic nature.
与地形数据综合一样，专题数据综合需要依据一定的综合规则来保障数据综合围绕应用的需求、反映主要地理特征。
JD: Which one to use really depends on your requirements.
JD：选择使用哪一个，其实取决于你的需求。
Requirements-based testing is the primary way of validating an application or system, and it applies to both traditional and use case requirements.
基于需求的测试是确认一个应用软件或系统的主要方式，它既适用于传统需求也适用于用例需求。
If you decide to use traditional, declarative requirements, then the guidelines should explain how to write them.
如果你决定使用传统的声明式需求，则指南应当解释如何编写需求。
Here's one more tip for writing good requirements: Use a consistent document format.
还有一个写好需求的技巧：使用一致的文档格式。
Once specified, those use cases contain the software requirements.
一旦具体化，这些用例就会包含软件需求。
To satisfy these non-functional requirements we use the WS response template pattern.
为了满足这些非功能需求，我们将使用WS响应模板模式。
You can also use placeholders when associating requirements with an artifact.
在将需求与工件联系起来之时，您也可以使用占位符。
I recommend the use of a requirements repository that will tie into use cases, design, and code, to provide traceability through the project.
我建议使用需求存储库，该存储库将与用例、设计和代码紧密结合，以在项目进行的整个过程中提供可跟踪性。
Capturing business requirements using use cases.
利用用例获取业务需求。
Provide bi-directional relationships between risks and other project lifecycle artifacts, e.g., requirements, use cases, etc.
为风险以及其他项目生命周期产物之间提供双向关系，例如需求，用例等。
Traditional development captures requirements in use cases.
传统开发通过用例来捕获需求。
The approach you use depends on the requirements of your user interface (UI).
所使用的方法取决于用户界面（UI）的需求。
By providing a user's view of what the system should do, use cases are requirements.
用例即需求，它从用户的角度来说明系统应该提供的功能。
The section talks about what use cases are used for, and finally shows how to check requirements against use cases.
该部分讨论用例是用于什么的，并且最后介绍如何根据用例检查需求。
You should be able to use surveys to uncover requirements that are not otherwise clearly generated.
您应该能够通过各种调查来发现需求，否则将无法清楚地得到这些需求。
Create your templates for the use cases, or requirements document, or whatever metaphor you use to capture requirements, but make sure they have two distinct sections that map to these two processes.
创建自己的用例模板或需求文档或任何用于捕获需求的工具，但要确保具有映射到这两个流程的两个不同部分。
This article described the use case and requirements of the composite business process that you'll implement in the subsequent parts.
本文描述了您将在后续部分中实现的组合业务流程的用例和需求。
Figure 2: Balance the use of components with addressing requirements.
图2：平衡需求处理组件的使用。
Move away from large text documents to visual representations, and use scenario-based requirements definitions (see Figure 5).
从大型文本文件转移至可视代表，并使用基于场景的需求定义(参见图5)。
Move away from large text documents to visual representations, and use scenario-based requirements definitions (see Figure 5).
从大型文本文件转移至可视代表，并使用基于场景的需求定义(参见图5)。
应用推荐