Observe that for the programmer，as for the chef，the urgency of the patron（顾客）may govern the scheduled completion of the task，but it cannot govern the actual completion. An omelette（煎蛋），promised in two minutes，may appear to be progressing nicely. But when it has not set in two minutes，the customer has two choices—waits or eats it raw. Software customers have had（ 请作答此空 ）choices.Now I do not think software（ ）have less inherent courage and firmness than chefs，nor than other engineering managers. But false（ ）to match the patron’s desired date is much more common in our discipline than elsewhere in engineering. It is very（ ）to make a vigorous，plausible，and job risking defense of an estimate that is derived by no quantitative method，supported by little data，and certified chiefly by the hunches of the managers.Clearly two solutions are needed. We need to develop and publicize productivity figures，bug-incidence figures，estimating rules，and so on. The whole profession can only profit from（ ）such data. Until estimating is on a sounder basis，individual managers will need to stiffen their backbones and defend their estimates with the assurance that their poor hunches are better than wish derived estimates.
- A.no
- B.the same
- C.other
- D.lots of
正确答案及解析
正确答案
解析
表示：“同样，相同”意思。附（参考翻译）：观察一下编程人员，你可能会发现，同厨师一样，某项任务计划进度，可能受限于顾客要求紧迫程度，但紧迫程度无法控制实际完成情况。就像约好在两分钟内完成一个煎蛋，看上去可能进行得非常好。但当它无法在两分钟内完成时，顾客只能选择等待或者生吃煎蛋。软件顾客情况类似。我现在并不认为软件经理内在勇气和坚持不如厨师，或者不如其他工程经理。但为了满足顾客期望日期而造成不合理进度安排，在软件领域中却比其他任何工程领域要普遍得多。而且，非量化方法采用，少得可怜数据支特，加上完全借助软件经理直觉，这样方式很难生产出健壮可靠和规避风险估计。显然我们需要两种解决方案。开发并推行生产率图表、缺陷率、估算规则等，整个组织最终会从这些数据共享上获益。或者在基于可靠基础估算出现之前，项目经理需要挺直腰杆并坚持他们估计，确信自己经验和直觉总比从期望得出估计要强得多。
