So it is today.Schedule disaster,functio

题库2022-08-02  52

问题 So it is today.Schedule disaster,functional misfits,and system bugs all arise because the left hand doesn't know what the right hand is doing.As work(  ),the several teams slowly change the functions,size,and speeds of their own programs,and the explicitly or implicitly(  )their assumptions about the inputs available and the uses to be made of outputs.For example,the implementer of a program-overlaying function may run into problems and reduce speed-relying on statistics that show how(  )this function will arise in application programs.Meanwhile,back at the ranch,his neighbor may be designing a major part of the supervisor so that it critically depends upon the speed of this function.This change in speed itself becomes a major specification change,and it needs to be proclaimed abroad and weighed from a system point of view.How,then,shall teams(  )with one another In as many ways as possible.Informally.Good telephone service and a clear definition of intergroup dependencies will encourage the hundreds of calls upon which common interpretation of written documents depends.Meetings.Regular project meetings,with one team after another giving technical briefings,are(  ).Hundreds of minor misunderstangings get smoked out this way.Workbook.A formal project workbook must be started at the beginning.问题1选项A.startsB.proceedsC.stopsD.speeds问题2选项A.changeB.proceedsC.smoothD.hide问题3选项A.frequentlyB.usuallyC.commonlyD.rarely问题4选项A.workB.programC.communicateD.talk问题5选项A.worthlessB.valuelessC.uselessD.invaluable

选项

答案 BADCD

解析 如今也是一样。进度灾难、功能的不适应加上系统缺陷,这些都是由于左手不知道右手在做什么。当工作进行的时候,一些团队慢慢改变他们自己程序的功能、规模和速度,并且直接或间接地改变关于输入效用的假设和由输出组成的使用。
例如,一个覆盖程序函数的实现者可能遇上问题,并且减少依赖于展现这个函数在应用程序中多么罕见的统计的速度。与此同时回到农场,他的邻居可能是设计的一个主要部分的监督人,这样它极度取决于函数的速度。这种变化在速度本身成为一个主要规划变化,它需要对外宣布,从概念系统来做衡量。
那么,团队应当用尽可能多的方式彼此交流。
非正式的。良好的电话服务和明确定义的组间依赖关系将鼓励成百上千的书面文件共同翻译上所依赖的调用。
会议。定期项目会议,一个接一个给技术简报的团队是无价的。许多小的误解在这种方式下得到化解。
工作薄。一个正式的项目工作薄必须一开始就准备。
转载请注明原文地址:https://tihaiku.com/congyezige/2410279.html

最新回复(0)