In a world whereit seems we already have too much to do, and too many things to think about, itseems

In a world whereit seems we already have too much to do, and too many things to think about, itseems the last thing we need is something new that we have to learn.But use cases dosolve a problem with requirements:with （71） declarative requirements it's hard to describe steps and sequences ofevents.Use cases, statedsimply, allow description of sequences of events that, taken together, lead toa system doing something useful.As simple as this sounds,this is important.When confronted only with a pile of requiements, it's often（72）to make sense of what the authors of therequirements really wanted the system to do.In the preceding example, use casesreduce the ambiguity of the requirements by specifying exactly when and underwhat conditions certain behavior occurs;as such, the sequence of the behaviors canbe regarded as a requirement. Use cases are particularly well suited to captureapproaches. Although this may sound simple, the fact is that （73） requirement capture approaches, with theiremphasis on declarative requirements and "shall"statements,completely fail to capture fail to capture the （74） of the system's behavior. Use cases are asimple yet powerful way to express the behavior of the system in way that allstakeholders can easily understand.But,likeanything, use cases come with their own problems, and as useful as theyare,they can be （75）. The result is something that is as bad, if not worse, that the originalproblem.Therein it's important to utilize use cases effectively withoutcreating a greater problem than the one you started with.
A：impossible
B：possible
C：sensible
D：practical


(中级)软件设计师     中级     too     设计师     whereit     already