Most regulations are expressed as requirements.
大多数规章都被表示为需求。
These modules can be added as requirements to the Makefile.PL.
可以将这些模块作为需求添加到 Makefile.PL。
As requirements change, the related architecture must be updated.
当需求变更时，相关的结构必须被更新。
Speakize is one of those functions you will be tweaking as requirements change.
Speakize是这些功能之一，您可以根据需要进行修改。
They are always trying to design the system at the same time as requirements are being gathered.
他们一直尝试在收集需求的同时设计系统。
You need to consider performance requirements, as well as requirements like guaranteed message delivery.
您需要考虑性能需求以及有保证的邮件传递之类的需求。
They allow you to dynamically move both CPU and RAM resources between partitions, as requirements evolve.
它们允许根据需求的变化在分区之间动态地转移CPU和RAM资源。
None (which is a placeholder for values that do not qualify as requirements as defined by the default types)
None （无，充当占位符，容纳那些不符合默认类型定义的需求的值）
Note that policies may also often be expressed as requirements but they are also frequently expressed as rules.
注意，策略也可能常常被表示为需求，但是它们也是经常被表示为规则。
The provider teams employ the service mocks as prototypes and the service tests as requirements to implement the services.
提供程序团队采用服务模拟作为原型，并将服务测试作为要求，从而实现服务。
CLASP also has an impact on a few key traditional software engineering activities, such as requirements specification.
CLASP在一些关键的传统软件工程活动里有影响，例如需求分析。
However, to obtain good requirements, requires several activities such as requirements engineering or change management.
然而，为了获得良好的需求，我们需要做很多工作，像需求工程或者变更管理等等。
XMLSpy and other graphical schema capture tools are excellent as requirements capturing tool for some of the following reasons.
由于以下原因，XMLSpy和其他图形化模式捕捉工具很适合作为需求捕捉工具。
An application is transitioned to a support team with few of the development artifacts, such as requirements, designs and tests.
一个程序会转化为拥有少量开发构件的支持团队，例如需求，设计和测试。
Requirement creep often caused by changing business needs As requirements change, SA usually changes to accommodate business changes
需求渐变通常由不断变化的业务需求导致当需求改变时，情景应用程序通常会更改，以适应业务改变
The article elaborates many aspects in detail, such as requirements analysis, system design, system realizes and system test etc.
本文从需求分析、系统设计、系统实现和系统测试等多方面进行了详细阐述。
Using the annotations in the process model as requirements, the developer codes the necessary rules and rules service implementation.
当需要的时候使用流程模型中的注释，开发人员对必要的规则及规则服务实现进行编码。
Projects that are best suited for test assertions as requirements are those where the end users of the application are themselves technical.
最适合将测试断言作为需求的项目是应用程序的最终用户自己掌握技术的项目。
For example, all content belonging to one specific discipline, such as requirements or change management, can be found in one method package.
例如，所有属于一个特定规程，比如需求或变更管理，的内容可以在一个方法包中被找到。
Materials such as requirements, system architecture, and data structures are not restricted to a single project and are intended to be reused.
需求、系统体系结构和数据体系结构等资料并不限制到单个项目，要进行重用。
Problems in these areas require technical resolution much earlier in the project, and the underlying needs should have been captured as requirements.
这个领域中的问题需要在这个项目的早期就确定技术问题，同时潜在的需求也应该捕获作为需求。
By employing many of the same principles and concepts they already use to write code, developers can effectively serve as requirements engineers.
通过应用许多与他们编写代码时相同的原则和概念，开发人员可以有效地担当起需求工程师的职责。
Software testing must be integrated with the other parts of software development, especially disciplines such as requirements management and change management.
软件测试必须与软件开发的其他部分结合起来，特别是像需求管理和变更管理这样的规程。
The rules architect has to make sure that all rules are captured using techniques—such as requirements gathering—through numerous interviews with business users.
规则架构师必须确保通过与业务用户进行大量访谈并使用一些技术（如需求收集）来捕获所有规则。
It begins as early as requirements management and spans over architecture, implementation, test, quality assurance, documentation - until your service is operational.
它从需求管理开始，延伸至架构，实现，测试，质量控制，文档——直到你的服务正式运行。
Activities such as requirements gathering, project organization and planning, staffing, estimation, monitoring, and reporting all occur in both types of projects.
诸如需求搜集、项目组织和管理、人员安排、评估、监控和报告等等活动都出现在这两种类型的项目中。
Often, as work items such as requirements come off the stack for implementation in the current iteration, an equal or greater number of work items are added back to the stack.
通常，随着需求条目从本次迭代中的执行栈中移除，相等数量的或者更大数量的工作条目就会被添加回这个栈中。
The primary benefit of using a rules engine over ordinary coding techniques is that rules engines allow efficient and controlled change of business rules as requirements change.
与普通的编码技术相比，使用规则引擎的主要好处是，在需求发生变化时，规则引擎可以高效地控制对业务规则的修改。
Reuse of both knowledge and technical assets - such as requirements and business rules documents, design artifacts, and technical code created during transformation activities.
重用知识与技术资产——比如在转型活动中产生的需求及业务规则文档、设计制品及技术代码等。
Reuse of both knowledge and technical assets - such as requirements and business rules documents, design artifacts, and technical code created during transformation activities.
重用知识与技术资产——比如在转型活动中产生的需求及业务规则文档、设计制品及技术代码等。
应用推荐