确定和使用正确的工具进行需求收集。
需求收集是一种有损压缩。
它揭示了需求收集过程产生的大量缺陷。
It uncovers a large number of the defects generated during the requirements gathering process.
确定用例是项目的需求收集阶段的重要一步。
Developing use cases is a significant step in the requirement gathering phase of a project.
请回想一下您曾经参与过的一些需求收集活动。
Think back to some of the requirements gathering exercises you've participated in.
实现需求收集过程的选择依赖于开发项目更大的环境。
The choice of requirements gathering process to implement depends on the greater context of the development project.
三月：Acme的业务需求收集和服务建模注意事项。
March: Business requirements gathering and services modeling considerations for acme.
识别与外部实体的交互在构建用例模型的需求收集阶段进行。
Interactions with external entities are identified during the requirements gathering phase of establishing a use case model.
好的用例完成业务需求收集、软件构造和验收测试之间的循环。
A good use case closes the loop between business requirement gathering, software construction, and acceptance testing.
为实现所选择的需求收集过程极大的影响着软件开发项目的成功。
The requirements gathering process you choose to implement can have an enormous impact on the success of your software development project.
在企业所依靠的方法中，过程模型是分析和需求收集的主要工件。
In the method that the organization has come to rely on, the process models are the primary artifact for analysis and requirements gathering.
当用一种需求收集活动代替另一种时，重要的是把需求环境考虑在内。
When substituting one requirements gathering activity for another, it is important to take the requirements context into account.
除此之外，我们还会看看是否能够组织起一个更动态更可变的需求收集过程。
Out of this, we'll see if we can assemble a more dynamic and mutable requirements gathering procedure.
或者，这个团队可以仅由那些专门进行需求收集和用例开发的分析人员组成。
Or it may be made up solely of analysts who specialize in requirements gathering and use case development.
在供应链管理样本应用程序的开发的需求收集阶段，小组找出以下使用案例。
During the requirements gathering phase of the development of the Supply Chain Management sample application, the group identified the following use cases.
对流程进行了建模之后，可以将模型的输出作为活动的需求收集阶段的输入使用。
Once the processes are modeled, the outputs of the models can be used as inputs to the requirement gathering phase of an initiative.
RUP的第一个迭代更多地关注于需求收集，而对软件开发的关注要略微少一些。
The first iterations of RUP were focused more on requirement gathering and less on software development.
这个环境可以在需求收集过程自身中找到，也可以在另一个受到好评的模型中找到。
This context may be found in the requirements gathering process itself or in another complimentary model.
任何项目的需求收集过程都应该结合操作方面，它们量化了解决方案的可接受性能标准。
The requirements gathering process of any project should incorporate operational aspects that quantify acceptable performance criteria of the solution.
作为一种需求收集过程，“功能驱动开发”非常灵活，它有助于在开发周期中更改管理。
As a requirements gathering process, Feature-Driven development is very flexible, lending itself to change management throughout the development cycle.
例如，可以在初始阶段进行所有的需求收集工作，而在精化阶段进行设计工作。
For example, you could do all requirement-gathering in the Inception phase and make the Elaboration phase the phase in which you do your design work.
在明确说明了交付内容后，SOUP方法将建议一个用于进行需求收集和管理的正式流程。
As the descriptions of the deliverables make clear, the SOUP methodology recommends a formal process for requirements gathering and management.
可以而且应该尽早考虑业务术语表，甚至在需求收集阶段和项目定义阶段就开始这项活动。
A business glossary can and should be considered as early as possible — even during the requirements-gathering and project-definition phases.
请考虑在测试环境中使用IT和业务用户以便使用户能够构建其自己的模型并协助需求收集。
Consider use by it and business users within test environments to enable users to build their own models and assist with requirements gathering.
一个项目用例的开发通常被看作是促进需求收集过程的一种方法，从而加速应用软件的开发。
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.
在业务分析、需求收集和用例设计期间，有意忽略模型的细节，只显示对业务最重要的信息概念。
During business analysis, requirements gathering, and use-case design, the model deliberately lacks detail, showing only the information concepts that are most important for the business.
规则架构师必须确保通过与业务用户进行大量访谈并使用一些技术（如需求收集）来捕获所有规则。
The rules architect has to make sure that all rules are captured using techniques—such as requirements gathering—through numerous interviews with business users.
在大多数情况下，问题归结为组织远在解决方案需求收集之前就分配其预算了，更不用提很好地了解了。
In most cases, the issue comes down to the fact that an organization allocated its budget long before the solution requirements were even collected, let alone well understood.
因为需求收集是开发周期的基础，一个无效或选择欠妥的需求分析过程极大的增加了项目失败的可能性。
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.
实际上，这正是传统的需求收集过程的缺点之一—无法收集足够的细节，所以无法消除不可避免的实现问题。
In fact, that is one of the weaknesses of traditional requirements gathering - it can never gather enough detail to eliminate implementation questions that inevitably arise.
应用推荐