Hence, the development approach that is followed is not the classic "waterfall" scenario, where requirements gathering is followed by analysis and design, leading to the implementation of the system.
因此，随后的开发方法不是典型的“瀑布”方案，在瀑布方案中，收集需求之后进行分析和设计，并进行系统的实现。
This transformation approach is the most costly, and requires careful assessment to ensure the solution aligns with future requirements.
该转换方法的成本开销最大，需要谨慎的评估来确保解决方案与将来需求的一致性。
In almost all cases, the share-based approach to control the resources should satisfy the resource control requirements.
在几乎所有情况下，基于份额的资源控制方法应该可以满足资源控制需求。
The use case points method, which we 'l sketch below, is a promising estimation method that fits in nicely with the use case approach to describing requirements.
我们将会在下面介绍到的用例点方法，是一种十分有前途的估算成本方法，能够很好的配合用例方法以描述需求。
The use-case technique is an increasingly popular approach to capturing requirements and driving system development.
用例技术是一种越来越流行的捕获需求和驱动系统开发的方法。
This approach is valuable when verifying that the solution meets nonfunctional requirements, where you repeatedly apply patterns and transformations to identify the best match.
当通过重复地应用模式和转换以确定最佳匹配来验证解决方案满足非功能需求时，该方法是有价值的。
See our definition of scope in the section An approach to defining requirements.
请参阅定义需求的方法部分中对范围的定义。
Take this same approach if you want to support a higher level of the current markup on the device when the current version of the markup does not satisfy your requirements.
您可以在标记的当前版本没有满足要求时使用相同的方式来支持设备上当前标记的更高级别。
RUP adds structure to an agile approach by focusing on driving out requirements uncertainty early and tightening process control naturally as the project progresses toward completion.
RUP通过在早期逐出需求的不确定性将结构添加到一个敏捷方法中，并且随着项目的不断推进很自然地绷紧了处理过程的控制。
However, that runs counter to the thinking behind the waterfall approach: Many design teams would view modifying the design after Stage 1 as a failure of their initial design or requirements process.
然而，使用瀑布型开发方法的执行与想象是相反的：很多设计团队把在阶段1之后的修改设计视为他们的最初设计或者需求过程的失败。
Researchers previously introduced this "smart" approach in cognitive radio designs, which sought to improve throughput by capturing the best available spectrum to meet user communication requirements.
先前研究人员将该“灵敏”方法引入认知无线电设计中，该设计通过捕获最佳可用频谱提高吞吐量以满足用户通信需求。
One straightforward approach for maintaining this type of traceability is to add appropriate metadata to both the requirements artifacts and the BRMS artifacts.
维护这种可跟踪性的一种简便方法是，在需求工件和BRMS 工件中添加适当的元数据。
With a few teams I've observed that used an OI approach, the requirements people began to receive change requests or meeting invitations to help clarify problems with the first iteration requirements.
在一些我所观察的使用OI方法的团队中，需求人员开始接受变更请求或进行会面以澄清第一次迭代需求中的问题。
Therefore, a usage-centered approach, as provided through RUP's application of use cases, is preferable to a data-centered approach to gain a broad view of the actual requirements.
因此，对于获得实际需求的主要视角来说，以用途为中心的方法(通过RUP的用例应用来提供)，优于用以数据为中心的方法。
Being familiar with the requirements will help you not to get bogged down in the requirement details and allow you to focus on the model and the design approach.
熟悉需求将帮助您免于在需求细节上花费过多时间和精力，使您能够将重点放在模型和设计方法上。
If the team in the example had been using an agile approach, as shown in Figure 2, it would have roughly sketched out the requirements, but in a way that allowed the project owners to prioritize them.
如果此示例中的团队使用了敏捷方法，如图2所示，则应该已经大致拟定了需求，但是允许项目所有者对需求进行优先排序。
Requirement definitions need not be defined in the manner described above, but this approach readily leads to a simplified implementation that can be traced directly back to the specific requirements.
需求定义无需以上述形式定义，但这种方法能得到简化的实现，可直接回溯到指定需求。
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 软件的方法。
A common approach is to perform a scoping and sourcing exercise in which you outline the requirements and effort that will be necessary for each portlet.
一种常见的方法是确定范围和来源，您可以在其中列出对于每个Portlet都非常必要的需求和工作。
I strongly recommend this paper to anyone responsible for defining the traceability needs for a project that USES a use case based approach to requirements.
我强力推荐负责为使用基于用例的方法分析需求的项目定义追溯需求的人阅读此文。
Since the target is created specifically to support those service requests, this pattern is a preferred approach for requirements of highly frequent transaction execution.
因为目标专门创建用于支持这些服务请求，所以对于高事务执行频率的需求，该模式是一种首选的方法。
The good news about this approach is that users are asked to commit to requirements much later than in a conventional waterfall approach.
这种方法的好处就是相对于传统的瀑布式方法来说，用户会在更晚的时候才被要求提交需求。
One approach is to treat requirements as a project-wide work item that stretches across the entire project lifecycle.
一种方法是将需求分析看作是在整个项目中进行的工作，跨整个项目生命周期。
Your organizational structure is used to justify the architectural approach for a system without consideration of the true requirements for that system.
在不考虑系统的真实需求的情况下，您的组织结构用于为该系统调整架构方法。
Examples of useful knowledge include the stakeholders requirements and priorities, an effective design approach, the technologies to be applied, and the internal and external dependencies.
有用的知识的实例包括涉众需求及优先权、有效的设计方法、要应用的技术，和内部及外部依赖。
In the first article in this series, "Part 1. Service identification", we outlined an approach for identifying services that are connected to business requirements.
在本系列的第1篇文章“第1部分服务识别”中，我们描绘出了识别那些同业务需求相连接的服务的一种方法的大致轮廓。
RUP recognizes the fact that your requirements will change throughout the project, and therefore it promotes a flexible approach to requirements management.
RUP认识到，您的需求在整个项目中会发生变更，因此，它推行灵活的需求管理方法。
Using the waterfall development approach leads to lots of partially done work, because a lot of time is spent upfront in elaborating requirements and in design.
使用瀑布开发方法将会产生大量部分完成的工作，因为大量的时间会花在改善需求和设计之上。
In general, the "right" approach for querying XML data needs to be chosen on a case-by-case basis, taking the application's requirements and characteristics into account.
一般而言，查询XML的“正确”途径需要在“逐个处理”的基础上加以选择，需要考虑应用程序的具体需求和特征。
The technical team that elaborates your to-be-automated business use cases into technical requirements is often even more receptive to this approach.
关于这种方法，精心描述你的自动化业务用例，让技术需求的技术团队通常更容易被接受。
应用推荐