你可以在图8中看到你的用例图。
原则2:挑战你的用例目标
让你的用例描述清晰、一致。
你怎样组织你的用例？
请确定你在坚持不懈地为你的用例捕获这些属性。
Make sure you capture these attributes for your use cases diligently.
如果你的架构基于框架，那么它就无法基于你的用例。
If your architecture is based on frameworks, then it cannot be based on your use cases.
记住故事板就是要补充你的用例，而不是它们的替代者！
Remember that storyboards are meant to complement your use cases, and are not a replacement for them!
很快地，你就可以像睡莲覆盖池塘一样，覆盖你的用例图。
Soon, you will cover your use case diagram with use cases like water lilies cover a pond.
如果你的用例模型正在爆炸式增长，你应该挑战你的用例粒度。
If your use case model is exploding, challenge the granularity of your use cases.
这有助于你组织用例信息，回答本文开头的第一个问题：你怎样组织你的用例？
This helps you organize the use case information answering the first question at the beginning of this article: How do you organize your use cases?
它通过为你的用例描述提供具有精确含义的通用词汇术语，来连接你的各个用例。
It interconnects your use cases by providing a common vocabulary of terms with precise meanings for your use case descriptions.
一件重要的事情是不要把功能分解到你的用例模型中；即，不要把你的用例打破成较小的部分。
An important thing not to do is to functionally decompose your use case model; that is, do not break your use cases into smaller parts.
当你在进行分析的时候，你的用例描述只记录了从系统外面的用户角度来看，系统的行为是什么样子的。
While you are in an analysis mindset, your use case description will generally address only the behavior of the system that is externally visible to an actor using the system.
适当结构化你的用例模型(原则2：向你的用例目标和原则挑战；原则3：使用需求属性决定最好的用例模型)。
Structure your use case model appropriately (Principle 2: Challenge your use case goals and Principle 3: use requirement attributes to determine the best use case model).
特别地，你将时常会有关于如何构建用例模型11的多种选择；当你这样做时，用上述的属性定位你的用例模型。
In particular, you will often have multiple choices about how to structure your use case model 11; when you do, align your use case model with the above attributes.
如果你不能提供足够的细节，那反而真有失败的可能：开发组即使阅读了你的用例描述，还是不得不重新探明需求。
If you do not provide enough detail, then there is a real possibility of failure: the development team will have to re-discover the requirements even after they read your use-case description.
连接你的业务用例，避免冗余，并确认你的需求(原则6：提出域模型和原则7：使用实体的生命周期)。
Connect your business use cases, avoid redundancies, and validate your requirements (Principle 6: Produce a domain model and Principle 7: use entity lifecycles).
适当描述你的业务用例(原则5：用例描述：阐明“是什么”，而不是“如何做”)？
Describe your business use cases appropriately (Principle 5: use case descriptions: State what and not how)?
一旦你确定了你的范围，你可以开始确定用例和参与者。
Once you have confirmed your scope, you can start identifying use cases and actors.
你将在你的项目中碰到不同的用例种类，因此尽早地从每个种类中选出一个代表性的用例，用它进行工作。
You will encounter different categories of use cases in your project, so select a representative use case from each category early on and work on it.
那么，对你的列表中的用例类型要求哪些工件呢？
So which artifacts are required for the use-case types in your list?
以上你了解了用例这个系统行为，它很接近地建模了你系统的执行内容。
You can see from the above use case that the behaviour of your system mirrors its implementation closely.
通过追踪从用例到业务用例、特性需求、测试，或者甚至其它用例，你可以更容易地衡量相关需求的变化所带来的影响，并验证覆盖率。
By tracing use cases to business requirements, feature-level requirements, tests, or even other use cases you can more easily measure the impact of change on related requirements and verify coverage.
它的主页上提供了一些样例的链接，你会发现，用这种方式构建书目能够提供许多不同的方式来发掘元数据。
From some of the example links on the home page, you can see that building in this way enables very different ways of exploring metadata.
关于这种方法，精心描述你的自动化业务用例，让技术需求的技术团队通常更容易被接受。
The technical team that elaborates your to-be-automated business use cases into technical requirements is often even more receptive to this approach.
记住：你如何重构用例模型将会影响其它的工作。
Remember: How you restructure the use case model will affect the efforts of others.
确认你的需求的业务用户，会对基于用例的方法感到非常舒服。
Business users who validate your requirements can feel quite comfortable with a use case-based approach.
那样的话，你应该先集中于高级别客户的用例的健壮性回归。
Then, you should focus the sanity regression suite on high-profile customer use cases.
起先，你会想要集中在每个用例对于要进行的开发是否足够详细。
At first, you'll want to focus on whether each use case is sufficiently detailed for development to proceed.
这些修订有助于你控制用例的变化。
应用推荐