2015下半年软件设计师考试（英语部分）

In a world where it seems we already have too much to do, and too many things to think about, it seems the last thing we need is something new that we have to learn.

But use cases do solve a problem with requirements: with strict declarative requirements it's hard to describle steps and sequences of events.

Use cases, stated simply, allow description of sequences of events that, taken together, lead to a system doing something useful. As simple as this sounds, this is important. When confronted only with a pile of requiements, it's often impossible to make sense of what the authors of the requirements really wanted the system to do.In the preceding example, use cases reduce the ambiguity of the requirements by specifying exactly when and under what conditions certain behavior occurs; as such, the sequence of the behaviors can be regarded as a requirement. Use cases are particularly well suited to capture approaches. Although this may sound simple, the fact is that conventional requirement capture approaches, with their emphasis on declarative requirements and "shall" statements, completely fail to capture fail to capture the dynamics of the system's behavior. Use cases are a simple yet powerful way to express the behavior of the system in way that all stakeholders can easily understand.

But, like anything, use cases come with their own problems, and as useful as they are, they can be misapplied. The result is something that is as bad, if not worse, that the original problem. Therein it's important to utilize use cases effectively without creating a greater problem than the one you started with.

在一个我们似乎已经有太多事情要做，太多事情要思考的世界里，我们最不需要的似乎是我们必须学习的新东西。

但是用例确实解决了需求的一个问题：对于严格的声明性需求，很难描述事件的步骤和序列。

简单地说，用例允许描述事件序列，这些事件组合在一起，导致系统做一些有用的事情。听起来很简单，但这很重要。当只面对一堆需求时，通常不可能理解需求的作者真正希望系统做什么。在前面的例子中，用例通过精确地指定特定行为发生的时间和条件来减少需求的模糊性；因此，行为的顺序可以被视为一项要求。用例特别适合捕获方法。虽然这听起来可能很简单，但事实是，传统的需求捕获方法强调声明性需求和“应”语句，完全无法捕获系统行为的动态。用例是一种简单而强大的方式，以所有涉众都能轻松理解的方式来表达系统的行为。

但是，和其他任何事情一样，用例也有自己的问题，尽管它们很有用，但也可能被误用。其结果与最初的问题一样糟糕，甚至更糟。因此，有效地利用用例而不产生比你开始时更大的问题是很重要的。

加油吧骚年！