摘要：对于【软件评测师】软考考试而言，试题无疑是最重要的学习资料之一。在软考备考过程中，吃透试题、掌握试题所考知识点、熟悉试题的出题思路，对我们提升分数的效果是最明显的，通过对试题的反复练习，还可以查漏补缺。今天，给大家带来【2020年11月软件评测师模拟试题上午（二）】部分试题的详解，一起来看看吧~



1、以下选项中，不属于安全防护策略的是（  ）
A、 入侵检测
B、 安全日志
C、 容量测试
D、 漏洞扫描

答案:C
答题解析:

本题考查安全防护策略的基础知识。

安全防护策略包括：入侵检测、隔离防护、安全日志和漏洞扫描。容量测试是性能测试的一种，不属于安全防护策略。故正确答案为C。

2、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（ 71 ）choices.Now I do not think software（ 72 ）have less inherent courage and firmness than chefs，nor than other engineering managers. But false（ 73 ）to match the patron’s desired date is much more common in our discipline than elsewhere in engineering. It is very（ 74 ）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（ 75 ）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

答案:B
答题解析:表示：“同样的，相同的”意思。

附（参考翻译）：

观察一下编程人员，你可能会发现，同厨师一样，某项任务的计划进度，可能受限于顾客要求的紧迫程度，但紧迫程度无法控制实际的完成情况。就像约好在两分钟内完成一个煎蛋，看上去可能进行得非常好。但当它无法在两分钟内完成时，顾客只能选择等待或者生吃煎蛋。软件顾客的情况类似。

我现在并不认为软件经理内在的勇气和坚持不如厨师，或者不如其他工程经理。但为了满足顾客期望的日期而造成的不合理进度安排，在软件领域中却比其他的任何工程领域要普遍得多。而且，非量化方法的采用，少得可怜的数据支特，加上完全借助软件经理的直觉，这样的方式很难生产出健壮可靠和规避风险的估计。

显然我们需要两种解决方案。开发并推行生产率图表、缺陷率、估算规则等，整个组织最终会从这些数据的共享上获益。或者在基于可靠基础的估算出现之前，项目经理需要挺直腰杆并坚持他们的估计，确信自己的经验和直觉总比从期望得出的估计要强得多。

3、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（ 71 ）choices.Now I do not think software（ 72 ）have less inherent courage and firmness than chefs，nor than other engineering managers. But false（ 73 ）to match the patron’s desired date is much more common in our discipline than elsewhere in engineering. It is very（ 74 ）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（ 75 ）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、testers
B、constructors
C、managers
D、architects

答案:C
答题解析:表示“经理”的意思。

附（参考翻译）：

观察一下编程人员，你可能会发现，同厨师一样，某项任务的计划进度，可能受限于顾客要求的紧迫程度，但紧迫程度无法控制实际的完成情况。就像约好在两分钟内完成一个煎蛋，看上去可能进行得非常好。但当它无法在两分钟内完成时，顾客只能选择等待或者生吃煎蛋。软件顾客的情况类似。

我现在并不认为软件经理内在的勇气和坚持不如厨师，或者不如其他工程经理。但为了满足顾客期望的日期而造成的不合理进度安排，在软件领域中却比其他的任何工程领域要普遍得多。而且，非量化方法的采用，少得可怜的数据支特，加上完全借助软件经理的直觉，这样的方式很难生产出健壮可靠和规避风险的估计。

显然我们需要两种解决方案。开发并推行生产率图表、缺陷率、估算规则等，整个组织最终会从这些数据的共享上获益。或者在基于可靠基础的估算出现之前，项目经理需要挺直腰杆并坚持他们的估计，确信自己的经验和直觉总比从期望得出的估计要强得多。

查看完整试题>>>