Why Have Formal Documents?Finally, writi

最全题库2022-08-02  50

问题 Why Have Formal Documents?Finally, writing the decisions down is essential. Only when one writes do the gaps appear and the  ( )  protrude(突出). The act of writing turns out to require hundreds of mini-decisions, and it is the existence of these that distinguishes clear, exact policies from fuzzy ones.Second, the documents will communicate the decisions to others. The manager will be continually amazed that policies he took for common knowledge are totally unknown by some member of his team. Since his fundamental job is to keep everybody going in the  ( )  direction, his chief daily task will be communication, not decision-making, and his documents will immensely (请作答此空)  this load.Finally, a manager’s documents give him a data base and checklist. By reviewing them ( )  he sees where he is, and he sees what changes of emphasis or shifts in direction are needed.The task of the manager is to develop a plan and then to realize it. But only the written plan is precise and communicable. Such a plan consists of documents on what, when, how much, where, and who. This small set of critical documents  ( )  much of the manager’s work. If their comprehensive and critical nature is recognized in the beginning, the manager can approach them as friendly tools rather than annoying busywork. He will set his direction much more crisply and quickly by doing so..A.extendB.broadenC.lightenD.release

选项

答案 C

解析 翻译:在这个世界上,似乎我们有太多的事情要去做,有太多的事情要去思考,那么需要做的最后一件事就是必须学习新事物。而用例恰恰可以解决带有需求的问题:如果具有( )声明的需求,则很难描述事件的步骤和序列。简单地说,用例可以将事件序列的说明放在一起,引导系统完成有用的任务。正如听起来一样简单——这很重要。在面对很多需求的时候,通常( )理解需求的作者真正想要系统做什么。在前面的例子中,通过指定特定行为发生的时间和条件,用例减少了需求的不确定性。这样的话,行为的顺序就可以当作是一种需求。用例特别适用于捕捉这类需求。尽管听起来可能很简单,但事实情况是由于(请作答此空)需求捕捉方法所侧重的是声明需求和“应该怎么样”的陈述,因此完全无法捕捉系统行为的( )方面。用例是一种简单而有效的表达系统行为的方式,使用这种方式所有参与者都很容易理解。但是与任何事物一样,用例也存在自己的问题——在用例非常有用的同时,人们也可能( )它,结果就产生了比原来更为糟糕的问题。因此重点在于:如何有效地使用用例,而又不会产生出比原来更严重的问题。A.现代的        B.常规的        C.不同的        D.正式的
转载请注明原文地址:https://tihaiku.com/congyezige/2408638.html

最新回复(0)