您现在的位置:希赛网 > 云阅读 > 软件设计师考试考点分析与真题详解(第4版) > 综述
第 13 章:计算机专业英语 作者:希赛教育软考学院 来源:希赛网 2014年01月27日
综述
上一节 本书简介 下一节
第 13 章:计算机专业英语 作者:希赛教育软考学院 来源:希赛网 2014年01月27日
试卷分析
第13章 计算机专业英语
本章主要讲解计算机专业英语。
13.1 综述
英语能力是软件设计师的必备能力,因此,计算机英语是软件设计师考试的重要内容。考试大
纲要求"具有工程师所要求的英语阅读水平,理解本领域的英语术语".在软件设计师上午试题中,共
75分,其中英语占5分(2007年以前英语占10分)。
1.软件设计师英语考试与其他英语考试的比较
近几年的软件设计师英语考试主要有如下几方面的特点。
难度略高于大学英语四级,相当于研究生入学考试。
题材限于计算机文化读物,不如其他英语考试广泛。
题型只限于短文填空(完型填空),题型单一。
2.复习与应试要点
根据考试试题的特点,软件设计师英语复习要点如下。
找一本研究生入学考试(或四级)英语复习资料,复习相关的固定搭配、短语、语法知识,重
点复习其中的完型填空,掌握完型填空的考点及要求。
注意多读计算机报刊、杂志的时文,在了解这个领域最新信息的同时积累语言知识,训练阅读
能力。在复习时看一些计算机英语材料,对这一领域的表达方式和词汇进行热身。本章我们精选了
一些英语材料,供大家复习参考。
用近几年的软件设计师英语考试试题进行模拟测试,本章收集了近几年的试题。
由于软件设计师英语考试题型只限于短文填空(完型填空),因此,自己可以在考前作一些专
项练习,结合复习总结出一些解题的技巧。一般可采用三步法,其要点如下。
粗略地看一遍全文,了解全文的信息。
以了解的信息作为基础,对全文进行精读,并进行完型填空。
从全局的角度,对答卷进行检查。
版权方授权希赛网发布,侵权必究
13.2 试卷分析
上一节 本书简介 下一节
从1991年起,软件设计师计算机专业英语部分的考查方式为完型填空,延续至今。
从广度上看,考查的题材比较新颖,内容广泛,涵盖了计算机的几个主要领域。
涉及到网络的:2006年11月考网络访问控制,2006年5月考Cookies,2005年5月考DOM,2003
年考网络协议,2003年考浏览器,2001年考数据包裹,2000年考VOIP(IP话音业务)解决方案;
涉及面向对象知识的:2008年12月考UML,2008年5月考面向对象分析,2007年11月考RUP;
涉及到程序语言及其基础理论的:2002年考强制型语言,1998年考字处理拼写检查,1996年考
Java;
涉及到信息安全的:2005年11月考数字认证,2005年5月考邮件病毒,2002年考计算机系统攻
击,2000年考防火墙;
涉及到计算机系统结构的:2001年考多指令多数据流系统,1992年考精简指令集对复杂指令集
的争议;
涉及到数据库的:1997年考关系型数据库模型,1994年考面向对象的数据库管理系统;
涉及到操作系统的:1995年考微内核技术,1994年考Windows NT操作系统;
涉及到新的应用技术和领域的:2006年11月考虚拟化,1995年考可视化的开发工具,1993年考
移动式计算机,1992年考人工智能硬件;
涉及到计算机文化和产业的:1999年考信息产业,1991年考计算机文化教育产业。
但从深度上看,对计算机知识考得都比较浅显,多是一些IT方面的时文摘要。考查的力度仅仅体
现在"了解,知道"这个层次上,没有对考生做更深入的要求。
从考查的内容来看,不仅仅考查计算机知识。还考一些英语基础,如:查上下文和主题、词形
的辨析、词义的辨析、词性的辨析、考时态、考语态和分词、介词及其固定搭配等。
因此在准备这部分考试内容的时候,不应该仅仅局限于计算机领域词汇的记忆。考试大纲要
求"具有工程师所要求的英语阅读水平,理解本领域的英语术语".这要求考生在语言的基本功上应该
有所积累,如大学英语四六级,研究生英语考试考纲要求的词汇,相关的固定搭配、短语,相关的
语法知识,这些都是"正确阅读和理解文章"的本钱。除此之外,还应该注意多读计算机报刊、杂志的
时文,在了解这个领域最新信息的同时积累语言知识,训练阅读能力。最好还能辅以一些英语短文
完型填空的练习,自己总结出一些解题的技巧。从这几年来的试卷和考试大纲来看,主要考查两个
方面。
考查的计算机专业词汇及相关知识,这方面,试卷既体现了"日新月异"的特点,又选择了相对稳
定和主流的内容,没有刻意地求"新"和求"偏".笔者根据命题的趋势,从近年来较新的计算机文献中
挑选了一些专业词汇和缩略语作为附录。既注意了"新",又兼顾了"全",剔除了过分陈旧和过分偏颇的
词汇。在今后几年可能会考查到,或者作为文章的题材涉及到。亦可供平时查阅之用,免去考生自
己收集整理之繁琐。希望对大家有所帮助。
考查"正确阅读和理解计算机领域的英文文献",本章中编者精选了一些最新英语素材,供考生复
习时参考。
版权方授权希赛网发布,侵权必究
第 13 章:计算机专业英语 作者:希赛教育软考学院 来源:希赛网 2014年01月27日
例题分析
上一节 本书简介 下一节
第 13 章:计算机专业英语 作者:希赛教育软考学院 来源:希赛网 2014年01月27日
阅读素材
13.3 例题分析
例题1(2011年5月试题71~75)
Ravi, like many project (71) ,had studied the waterfall model of software
development as the primary software life-cycle (72) .He was all set to use it for an
upcoming project, his first assignment.However, Ravi found that the waterfall model could
not be used because the customer wanted the software delivered in stages, something that
implied that the system had to be delivered and built in (73) and not as (74) .
The situation in many other projects is not very different. The real world rarely presents
a problem in which a standard process, or the process used in a previous project, is the best
choice.To be the most suitable, an existing process must be (75) to the new problem.A
development process, even after tailoring, generally cannot handle change requests.To
accommodate change requests without losing control of the project, you must supplement
the development process with a requirement change management process.
(71)A.customers B.managers C.users D.administrators
(72)A.activity B.procedure C.process D.progress
(73)A.parts B.modules C.software D.a whole
(74)A.parts B.modules C.software D.a whole
(75)A.modified B.used C.suited D.tailored
例题分析:
文章大意如下:
Ravi就像很多研究过以瀑布模型为软件生命周期过程的软件开发项目经理一样,他被安排使用
瀑布模型去开发一个即将启动的项目,而且这是他的第一个任务。然而,Ravi发现不能在项目中使
用瀑布模型,因为客户想要该软件分阶段交付,而不是作为一个整体交付。
在很多其他的项目中也有类似的情况,现实生活中,本来就很少有能完全按标准来进行处理的
问题,可能某标准处理前一个问题非常合适,但处理现在这个问题就不定适合了。最合适的方法就
是对一个新的问题必须采用切合它自身的方法。为了适应变化的变更请求而不失去对项目的控制,
你必须要支持项目的发展过程与一个需求变更管理过程。
例题答案:(71)B (72) C (73) A (74) D (75)D
版权方授权希赛网发布,侵权必究
13.4 阅读素材
这里结合考试内容的特点,精选了一些计算机英语的阅读素材,供考试复习参考。为培养考生
的阅读习惯与能力,提高阅读水平,这里就不再提供译文,必要时读者可以借助词典。
(1)Unix was originally developed at Bell Laboratories as a reaction to the large,
complex, non-portable operating systems of the early 1970s. AT&T did not see a significant
opportunity in licensing or supporting an operating system; Instead, it provided Unix source
code for a nominal license fee and small per-unit royalties. A number of academic efforts
sprang up to take advantage of this opportunity and extend the original sources with new
and interesting features. In the mid-1980s, every computer manufacturer either provided or
planned to provide a Unix-based operating system for its computers. Each company had
chosen a particular version of Unix to start with, and then added various proprietary
features. Although all of these operating systems claimed to be Unix, software written on
one version was often not portable to the other versions.
(2)Many believed this effort by AT&T was bad news for the software community.
Among them was Richard Stallman, a programmer at MIT, who in 1984 founded the GNU
Project ("GNU is Not Unix") as an effort to rewrite Unix as "free" software-that is,
software not controlled by any one person and available for anybody to use and modify as
desired. This led to the creation in 1985 of the Free Software Foundation (FSF), the
main funding and advocacy organization for the GNU Project.The Free Software
Foundation established the GNU General Public License (GPL), the most important
open source license in use today. While the GNU Project was getting started, other efforts
began to at least standardize the definition of Unix to enhance software portability. One
such effort was the formation of the IEEE 1003 standards committee, which would go on to
produce the set of standards known as the Portable Operating System Interface
(POSIX)。Another effort of note was the creation of the X/Open organization, a
commercial venture oriented toward application portability, testing, and branding of Unix-
compatible operating systems.
(3)The concept of a storage device has changed dramatically from the first magnetic
disk drive introduced by the IBM RAMAC in 1956 to today's server rooms with detached
and fully networked storage servers. Storage has expanded in both large and small
directions-up to multi-terabyte server appliances and down to multi-gigabyte MP3 players
that fit in a pocket. All use the same underlying technology-the rotating magnetic disk
drive-but they quickly diverge from there.
(4)SAN relies on each server connecting to it to provide security and management of
the portion of the storage pool assigned to it. Only recently are techniques being
introduced that allow storage pools to be shared among servers, but this is usually only
when the host servers are tightly clustered. The key is that the traditional SAN system is
trying to present a view of direct-attached, dedicated disks to each server while pulling out
the reliability, backup, and disk management issues from single-server control. SAN is
geared for raw performance and generally achieves better performance than direct-
attached disks as a result of larger caches and buffering. In fact, early SANs had SCSI
connections to the hosts, as well as to the back-end disks.
(5)The overwhelming majority of information in an enterprise is unstructured-that is,
it is not resident in relational databases that tabulate the data and transactions occurring
throughout the enterprise. This unstructured information exists in the form of HTML pages,
documents in proprietary formats, and forms (e.g., paper and media objects)。 Together
with information in relational and proprietary databases, these documents constitute the
enterprise information ecosystem.
(6)It is well known that some of the most valuable knowledge in an enterprise
resides in the minds of its employees. Enterprises must combine digital information with the
knowledge and experience of employees. An important distinction between the enterprise
and the Internet is that while Internet users are anonymous for the most part, enterprise
users are answerable and guided by specific controllable processes. Privacy issues are also
very different in an enterprise, since people are usually engaged in enterprise-specific
behavior and are being compensated for their engagement.
(7)In past decades, "Moore's law" has governed the revolution in microelectronics.
Through continuous advancements in device and fabrication technology, the industry has
maintained exponential progress rates in transistor miniaturization and integration density.
As a result, microchips have become cheaper, faster, more complex, and more power
efficient.
(8)Much of the performance gain in digital hardware can be traced to corresponding
advances in integrated circuit technology. For example, over the past 30 years we have
witnessed a steady decrease in transistor channel length by two orders of magnitude from
10?m in 1970 to less than 0.1?m today. While this reduction of feature size benefits analog
and digital circuits alike, overall analog circuit performance is compromised by other trends
such as reduced supply voltages.
(9)This is the new world order: software development on a global scale. As is almost
always the case, this doesn't mean the entire technical arm of a corporation breaking off
and floating across an ocean in one clean clump, but rather numerous small teams here
and there "sharing the pain" across time zones. Nowadays it's not atypical to have multiple
teams on multiple continents working on the same project. It's not just financial pressures
that come to bear and break developers into teams. The sheer size-raw lines of code-of
many of today's projects means they're just too big for one group to handle on its own.
And whether teams are spread across a campus or across multiple continents, distributed
development affects the way that we write code.
(10)Individuals from different cultures are also likely to be motivated differently. In