2013软件设计师考试（英语部分）

2013年上半年上午卷

So it is today. Schedule disaster, functional misfits, and system bugs all arise because the left hand doesn’t know what eht right hand is doing. As work (71) $proceeds$ the several teams slowly change the functions, size, and speeds of their own programs, and the explicitly or implicitly (72) $change$ 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 (73) this function will arise in application programs. Meanwhile, back at statistics that show how (73) $rarely$ 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 (74) $communicate$ with one another? In as many ways as possible. Informally. Good telephone service and a clear definition of interfroup dependencies will encourage the hundreds of calls upon which common interpretation of written documents depends. Meetings, Regular porject meetings, with one team after another giving technical briefings, are (75) $invaluable$. Hundreds of minor misunderstangings get smoked out this way. Workbook. Aformal project workbook must be started at the beginning.

今天就是这样。安排灾难&＃xff0c;功能不适和系统错误都会出现&＃xff0c;因为左手不知道右手正在做什么。随着工作&＃xff08;71&＃xff09;的进行&＃xff0c;几个团队慢慢地改变他们自己的程序的功能&＃xff0c;大小和速度&＃xff0c;并明确地或隐含地&＃xff08;72&＃xff09;改变他们对可用输入和输出使用的假设。例如&＃xff0c;程序覆盖功能的实现者可能遇到问题并且降低速度 - 依赖于统计数据&＃xff0c;该统计数据显示在应用程序中将如何&＃xff08;73&＃xff09;出现该功能。同时&＃xff0c;回到统计数据显示应用程序中很少会出现这种功能。同时&＃xff0c;回到牧场&＃xff0c;他的邻居可能正在设计主管的一个主要部分&＃xff0c;因此它关键取决于这个功能的速度。速度的这种变化本身就成为一个重大的规范变化&＃xff0c;它需要在国外宣布并从系统的角度加以权衡。那么&＃xff0c;团队&＃xff08;74&＃xff09;如何相互沟通&＃xff1f;尽可能多的方式。非正式的。良好的电话服务和明确的组织间依赖性定义将鼓励数百次书面文件的共同解释所依赖的电话。会议&＃xff0c;定期会议&＃xff0c;一个接一个的团队进行技术简报&＃xff0c;是非常宝贵的。以这种方式吸取了数以百计的小错误。工作簿。必须在开始时启动Aformal项目工作簿。

(71)
A. starts 启动
B. $proceeds$ 收益
C. stops 停止
D. speeds 速度
(72)
A. $change$ 更改
B. proceeds 收益
C. smooth 平滑
D. hide 隐藏
(73)
A. frequently 经常
B. usually 平时
C. commonly 常用
D. $rarely$ 很少
(74)
A. work 工作
B. program 程序
C. $communicate$ 通信
D. talk 谈论
(75)
A. worthless 无用
B. valueless 无价值
C. useless 无用
D. $invaluable$ 无价

2013年下半年下午卷

There is nothing in this world constant but inconstance. SWIFT Project after project designs a set of algorithms and then plunges into consruction of customer-deliverable software on schedule that demands delivery of the first thing built. In most projects, the first system built is (71) $barely$ usable, Itmay be too slow, too big, awkward to use, or all three. There is no (72) $alternative$ but to start again, smarting but smarter, and build a redesigned version in which these problems are solved. The discard and (73) $redesign$ may be done in one lump, or it may be done piece-by-piece. But all large-system experience shows that it will be done. Where a new system concept or new technology is used, one has to build a system to throw away, for wven the best planning is not so omniscient as to get it right the first time. The management question, therefore, is not whether to build a pilot system and throw it away. You will do that. The only questiion is whether to plan in advance to build a (74) $throwaway$, or to promise to deliver the throwaway to customers. Seen this way, the answer is much clearer.
Delivering that throwaway to customers buys time, but it does so only at the (75) $cost$ of agony for the user, distraction for the builders while they do the redesign, and a bad reputation for the product that best redesign will find fard to live down. Hence plan to throw one away, you will ,anyhow.

在这个世界上没有什么是不变的&＃xff0c;但却是不稳定的。 SWIFT项目在项目设计了一套算法之后&＃xff0c;然后按计划投入客户可交付的软件&＃xff0c;这需要交付第一件事。在大多数项目中&＃xff0c;第一个构建的系统&＃xff08;71&＃xff09;几乎不可用&＃xff0c;它可能太慢&＃xff0c;太大&＃xff0c;难以使用&＃xff0c;或者全部三个。没有&＃xff08;72&＃xff09;替代方案&＃xff0c;但重新开始&＃xff0c;聪明但更聪明&＃xff0c;并构建一个重新设计的版本&＃xff0c;解决这些问题。丢弃和&＃xff08;73&＃xff09;重新设计可以一次完成&＃xff0c;也可以一块一块地完成。但是所有大型系统的经验表明它将会完成。在使用新系统概念或新技术的情况下&＃xff0c;必须建立一个可以扔掉的系统&＃xff0c;因为最好的规划并不是那么无所不知&＃xff0c;以至于第一次就做好了。因此&＃xff0c;管理问题不在于是否建立一个试点系统并将其扔掉。你会那样做的。唯一的问题是&＃xff0c;是否提前计划建造&＃xff08;74&＃xff09;一次性&＃xff0c;或承诺向客户提供一次性服务。从这个角度看&＃xff0c;答案更加清晰。
向客户提供一次性投资可以节省时间&＃xff0c;但这只会导致用户痛苦的成本&＃xff0c;建筑商在进行重新设计时分散注意力&＃xff0c;以及对最佳重新设计的产品的不良声誉将导致生活费用下降下。无论如何&＃xff0c;你会计划抛弃一个人

(71)
A. almost 几乎
B. often 经常
C. usually 平时
D. $barely$ 仅仅
(72)
A. $alternative$ 替代
B. need 需要
C. possibility 可能性
D. solution 解
(73)
A. design 设计
B. $redesign$ 重新设计
C. plan 计划
D. build 建立
(74)
A. $throwaway$ 丢弃
B. system 系统
C. software 软件
D. product 产品
(75)
A. worth 价值
B. value 值
C. $cost$ 成本
D. invaluable 无价