It specifies information the developers must collect and mechanisms for controlling requirements changes.
它规约了开发人员必须收集的信息和控制需求变更的机制。
The DOORS solution can help manage requirements and requirements changes with improved ease and flexibility.
DOORS解决方案可以帮助管理需求与需求更改，同时使操作变得更加轻松和灵活。
However, in retrospect we wish we'd taken the time to set up Rational ClearQuest to manage requirements changes.
然而，追溯我们所希望的，我们已经花费时间建立了RationalClearQuest来管理需求的变更。
We were able to track the requirements changes with Rational RequisitePro, but they had an impact on the system beyond that.
我们能够使用Rationalrequisitepro来跟踪需求，但是他们对整个系统带来了影响。
If the project cannot include requirements changes, the solution meets the initial analysis but not the current customer requirements.
如果项目不能包含需求变更，那么解决方案仅满足了最初的分析，而不满足当前的客户需求。
Be sure that customers and management understand the scheduling impacts, inherent risks, and costs of significant requirements changes.
确保用户和管理者理解项目时间计划，潜在的风险和重大需求改变的价值。
Requirements changes due to stakeholder input can be processed within the already existing solution framework, reducing risk and delays.
由涉众输入引起的需求变更会在已经建好的现有解决方案框架中处理，减少了风险和延迟。
If you want to avoid this, along with having to constantly rewrite code to keep pace with the requirements changes, start a CCB or the equivalent.
如果你想避免这一点，避免跟着需求的变更不断地被迫重写代码，那就请启用一个CCB或者类似的东西。
There are also times at which a downward trend needs to be observed, where fewer requirements changes have to be processed to bring the project to a close.
而在另一些时期则可以观察到下降趋势，那时需要处理的需求变化很少，于是项目得以结束。
If requirements changes do not correctly flow between the systems, this is probably because the requirement has been modified in both systems in the same synchronization period.
如果需求更改在系统之间没有得到适当的流动，那么这可能是因为需求在同一个同步化期间在两个系统中得到了同时更改。
The AAL implements specific abstractions built on the . NET that enables teams developing large-scale applications to succeed in an environment of rapid development and customer requirements changes.
能使团队在一个要求快速开发和消费者需求会发生变化的环境下成功开发大型应用。
They comprise an early warning system to ensure that the impact of changes to requirements across product versions are analyzed and dealt with as needed.
它们包括一个早期报警系统，以此来确保变化对需求的影响可以跨过产品版本被分析，并在需要的时候被处理。
These reports can take your requirements, changes, and test results, and then provide you with a comprehensive lifecycle view for software delivery.
这些报告可以您的需求，变化以及测试结果，然后向您提供一个软件交付的综合性生命周期的见解。
If yes, how flexible are these custom built models to absorb changes in business requirements?
如果是，这些自定义构建模型吸收业务要求中的变化的灵活性如何？
When an element of the requirements chain changes, all the trace relationships are marked as suspect, as shown in Figure 28.
当需求链的某个元素发生变化时，所有的跟踪关系都会标记成可疑，如图28所示。
These tools should increase your efficiency to deliver products on time as well as help you manage changes in requirements.
这些工具将提高您的工作效率以便按时交付产品，并帮助您管理需求的更改。
There might be changes in business requirements or feature functionality that require changes to the database schema as well.
可能的原因是业务需求或特性功能发生了变化，因此也要求更改数据库架构。
Its components may have to be changed due to deficiencies found in the authentication algorithms or to changes in requirements for system authentication.
由于发现了认证算法中存在的缺点，或者由于系统认证需求的变化，有时候需要更改认证框架的组件。
For instance, your development team should not receive changes to requirements that are already in implementation.
例如，您的开发团队不会接受已经确定需求的改变。
Updating models to reflect new requirements lets developers at either site see the impact of changes to requirements at a glance.
更新模型以反映新的需求使得在每个站点的开发者都可以看到更改对需求造成的影响。
However, if any requirements for the output PDF changes, the styled elements can be customized to meet those needs.
然而，如果输出pdf有任何的需求变更，那么就可以通过定制风格化元素来满足这些需求。
On the IT side, there is no formal transformation mechanism to convert requirements and their evolving changes into executable structured programs.
在IT方面，没有正式的转换机制将需求及其不断的更改转换为可执行的结构化程序。
The first third of this paper presents the scope we set for the changes, including the requirements we focused on.
本文的前三分之一介绍了我们为变更所设置的范围，包括我们所关注的需求。
Finally, we conclude by stressing the versatility of the solution with respect to changes in requirements, as well as input and output data formats.
最后，涉及到修改需求以及输入输出数据格式的问题时，我们强调了该解决方案的通用性。
Management of all user definitions, events, requests, updates, changes, and requirements must be tested thoroughly.
必须彻底测试所有用户定义、事件、请求、更新、更改和需求的管理。
Let's consider two methods for maintaining traceability of changes to requirements across multiple product releases.
让我们考虑一下跨多个产品发布版本来维护对需求变化的可追溯性的两种方法。
Now, merge these changes into the original requirements document.
现在，将这些变更合并到原始的需求文档之中。
Those with extremely stable requirements, with no changes expected on the order of years.
有严格的稳定性需求，数年之内没有更改计划的项目。
Late changes in requirements may come from the business people, and developers should implement the requirements.
后期需求更改可能来自于业务人员，并且开发人员应该实现那些需求。
Late changes in requirements may come from the business people, and developers should implement the requirements.
后期需求更改可能来自于业务人员，并且开发人员应该实现那些需求。
应用推荐