Establish and maintain the plan for performing the requirements development process.
建立和维护执行需求开发过程的计划。
Train the people performing or supporting the requirements development process as needed.
需要培训人员执行和支持需求开发过程。
Establish and maintain an organizational policy for planning and performing the requirements development process.
为计划和执行需求开发过程建立和维护一个组织策略。
Place designated work products of the requirements development process under appropriate levels of configuration management.
在适当的配置管理水平下，指定需求开发过程的产品位置。
Assign responsibility for performing the process, developing the work products, and providing the services of the requirements development process.
为执行过程、开发工作产品指定责任，并提供需求开发过程的服务。
Provide adequate resources for performing the requirements development process, developing the work products, and providing the services of the process.
为执行需求开发过程、开发工作产品提供充足的资源，并提供过程的服务。
Objectively evaluate adherence of the requirements development process against its process description, standards, and procedures, and address noncompliance.
客观评价坚持需求开发过程中违反她的进程描述、标准、步骤和不符合的位置。
This process forces the developer to concentrate on the functional requirements outside of the development paradigm to be used.
这个过程迫使开发者将重点集中在所使用的开发模式外部的功能需求之上。
A critical best practice for avoiding scope creep, therefore, is to facilitate the change of requirements at any stage of the development process.
因此，防止范围渐变的一个关键最佳实践是，在开发过程的任一阶段都能够方便地进行需求更改。
Once design patterns caught on, patterns began to appear in other areas of software development like process, requirements analysis, and so on.
一旦模式变得流行起来，模式就开始出现在软件开发的其它领域，如过程，需求分析等等。
Just look at requirements, task management or development process management.
看一看需求，任务管理或是开发流程管理。
Since development is an iterative process, requirements definition does not end in the initial project-definition phase.
由于开发是个迭代的过程，所以需求定义并没有终止在初始的项目定义阶段。
These incomplete requirements call for a flexible modeling process and for techniques which are appropriate for evolutionary development.
这些不完整的需求需要灵活的建模过程和适合于进化开发的技术。
Inclusion of the client meant that we were able to capture many of the real requirements early enough so that the scope was clear, helping to avoid problems later in the development process.
让客户参与设计过程意味着，我们能够在早期捕捉到许多真实的需求，从而明确设计范围，帮助避免在开发过程的后期才发现问题。
For a development team, part of the requirements process is to analyze the problem being solved.
对于开发团队来说，需求处理部分就是分析待解决的问题。
In an age when development teams routinely work in domains that are foreign to them, however, the traditional SRS may fall short as a requirements gathering process.
但是，在开发小组在他们不熟悉的领域进行日常工作的时代，传统的SRS作为需求收集过程可能有所欠缺。
Because requirements gathering is the foundation of the development cycle, an ineffective or ill-chosen requirements gathering process greatly increases the probability that your project will fail.
因为需求收集是开发周期的基础，一个无效或选择欠妥的需求分析过程极大的增加了项目失败的可能性。
The choice of requirements gathering process to implement depends on the greater context of the development project.
实现需求收集过程的选择依赖于开发项目更大的环境。
This means that the requirements process needs to be tightly integrated with, and executed to the same timetable of, the iterative development of the solution.
这意味着需求过程需要被紧密的集成，按照与解决方案的迭代式开发同样的时间表运行。
The requirements gathering process you choose to implement can have an enormous impact on the success of your software development project.
为实现所选择的需求收集过程极大的影响着软件开发项目的成功。
As a requirements gathering process, Feature-Driven development is very flexible, lending itself to change management throughout the development cycle.
作为一种需求收集过程，“功能驱动开发”非常灵活，它有助于在开发周期中更改管理。
The development of use cases for a project is generally seen as a way of facilitating the requirements gathering process, thereby speeding up application development.
一个项目用例的开发通常被看作是促进需求收集过程的一种方法，从而加速应用软件的开发。
MDA's repeatable set of practices is well-suited to today's iterative development requirements, because MDA enhances predictability of the development process and the delivered solution itself.
MDA的可重复的实践集是适合当今迭代开的发需求的，因为MDA提高了开发过程和要交付的解决方案本身的可预见性。
Designing SOA solutions with a business focus links business requirements and the it development process at the enterprise level.
通过采用以业务为中心的方法设计SOA解决方案，可在企业级别将业务需求与IT开发流程联系起来。
We view business process models as a way for the business to communicate requirements to IT in the context of SOA and business-driven development.
我们将业务流程模型视为一种业务部门与IT部门在SOA和业务驱动开发的上下文中沟通的方法。
Business process support for the value chain includes management of business strategy requirements, and enterprise architecture (for both product development and product delivery).
支持价值链的业务处理过程包括：业务策略需求的管理、以及企业架构(产品的开发和交付)。
It is not developed within the process but is a necessary input for the development of compliance requirements.
它不是由过程开发出的，而是所必需的针对法规遵循需求开发的输入。
IllustrationSuppose you are the manager of an it department whose software development staff needs more agility in its process to meet market requirements.
插图设想您是一个IT部门的经理，该部门的软件开发职员在满足市场需求的过程中需要更多灵活性。
Traditional requirements engineering, the first step in the software development process, determines the functional and nonfunctional needs or conditions that must be met for a new product or system.
作为软件开发流程中的第一步，传统需求工程确定新产品或系统所必须满足的功能性和非功能性需求或条件。
The Rational Unified Process defines UCM as "Rational Software's approach to managing change in software system development, from requirements to release.
Rational统一过程将 UCM定义为 "在软件系统开发（从需求到发布）的过程中管理变更的Rational 软件的方法。
应用推荐