The utility model can meet use requirements of some special devices.
可以满足一些特殊设备的使用要求。
White dryer placement is appropriate, whether the environment temperature to meet the use requirements.
干燥机摆置是否适当，环境温度是否满足使用要求。
You can use these samples as a basis for your own deployment plan requirements.
您可以使用这些示例作为您自己的部署计划需求的基础。
Use cases are an excellent way to capture business requirements.
用例是捕获业务需求的一个优秀的方法。
Requirements, and similarly use cases, are not just text.
需求和类似的用例，并不仅仅是文本。
As such, use cases should participate in the management of all system requirements.
同样地，用例应当参与到所有系统需求的管理之中。
As much as you can, use known solutions to meet reliability and performance requirements.
你应尽量采用那些已知的方案以满足可靠性与性能需求。
We use a spreadsheet to keep track of the requirements.
我们使用电子数据表来保持对需求的跟踪。
In this case, you can grow hardware requirements based on actual service use.
在这种情况下，可以根据实际的服务使用来增加硬件需求。
For most use cases, the embedded rule engine can not meet the complex business requirements.
在大多数使用案例中，嵌入的规则引擎不能满足复杂的业务需求。
This exercise readdresses how to gather requirements and create use cases from them.
该练习再次重述了如何收集需求并由它们来创建用例。
There are numerous requirements gathering methodologies, but the most common method is use case modeling.
虽然有众多的需求收集方法，但是最普通的方法是用例建模。
For this example, I use a simple requirements, analysis, design, and development flow.
对于本例而言，我使用了一种最简单的要求、分析、设计和开发流程。
You can use this architecture for other systems that have similar business and it requirements.
您也可以将这种体系结构应用于包含类似的业务及IT需求的系统中。
These principles apply to requirements, too — particularly to use cases.
这些原则对需求同样适用，尤其是用例。
Of course, you are free to use any other technique to describe your requirements.
当然，你也可以使用别的技术来描述你的需求。
We first describe the scenario, requirements, and a few use cases.
我们首先介绍场景、需求和几个使用案例。
For most use cases, the embedded rule engine cannot meet complex business requirements.
对于大多数用例，嵌入的规则引擎无法满足复杂的业务需求。
Also, you can use the traceability function to determine the impact of changes on requirements.
同样，您可以使用追溯功能确定变更对需求的影响。
The content models are generally hard to use for complex requirements.
对于复杂需求通常很难使用内容模型。
Gathering requirements using use cases can be tricky.
使用用例来收集需求可能比较棘手。
These utilities are fast, have relatively small memory requirements, and are easy to use.
这些实用程序速度快，内存需求较小，且易于使用。
To model and track the requirements related to the use of the application in production.
建模和追踪产品程序使用相关的需求。
For example, for the requirements gathering and management stage, we'll use IBM Rational RequisitePro.
例如，对于需求搜集和管理阶段，可以使用IBMRationalRequisitePro。
The client must meet these requirements to use the component.
客户必须满足这些要求才能使用组件。
You can now use the process decomposition structure to drive how requirements are specified.
您现在可以使用流程分解结构来驱动需求指定的方式。
Business users who validate your requirements can feel quite comfortable with a use case-based approach.
确认你的需求的业务用户，会对基于用例的方法感到非常舒服。
They are the minimum requirements to use XWT and data binding.
它们是使用XWT和数据绑定的最低要求。
These links trace the use cases to the use case requirements.
这些连接跟踪用例一直到用例请求。
You can use online sources or books as per the requirements of your instructor.
你可以用在线资源或者书籍作为指导资料。
应用推荐