In a world where it seems we already hav

题库2022-08-02 35

问题 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 （　　） 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 （　　） 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 （　　） requirement capture approaches, with their emphasis on declarative requirements and "shall" statements, completely fail to capture fail to capture the （　　） 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 （　　）. 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.问题1选项A.plentyB.looseC.extraD.strict问题2选项A.impossibleB.possibleC.sensibleD.practical问题3选项A.modernB.conventionalC.differentD.formal问题4选项A.staticsB.natureC.dynamicsD.originals问题5选项A.misappliedB.appliedC.usedD.powerful

选项

答案 DABCA

解析英文含义：
在一个似乎已经有做不完的事情的世界里，我们有大量事情要思考，似乎我们不太需要学习新的东西。
但是用例解决问题是有条件的：严密的说明性需求使得描述事件的步骤和次序变得举步维艰。
简单地讲，用例描述一组事件序列，系统性地执行产生相应有用的结果。听上去简单明了，这是很重要的。当面对一大堆的需求时，通常不太可能理解这些需求的发起者到底想要系统做什么。在前面的案例中，用例通过详细准确描述什么时间、什么情况下确定的行为会发生，以减少需求的不确定。像这样的一些动作序列被看作是一个需求。用例特别适合于捕捉方法。虽然这听起来很简单，但事实上不同的需求会根据他们各自在说明性需求和“应有”的声明的侧重面上捕捉方法，导致完全无法捕捉到系统行为的初衷。用例是一个所有的利益相关者都可以很容易地理解的、简单却十分有效的表达系统的行为的方式。
但是，和其他任何事情一样，用例也存在自身的问题，可能会被误用而弄巧成拙。造成的后果也很糟糕，或许只是没有比原本想要解决的问题更麻烦罢了。因此有效使用用例而避免制造更大的麻烦是非常重要的。

转载请注明原文地址:https://tihaiku.com/congyezige/2417914.html

本试题收录于：中级软件评测师题库软件水平考试初中高级分类

中级软件评测师

软件水平考试初中高级

相关试题推荐

随机试题

最新回复(0)

In a world where it seems we already hav

中级软件评测师

软件水平考试初中高级