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

2016年上半年上午卷

In the fields of physical security and information security, access control is the selective restriction of access to a place or other resource. The act of accessing may mean consuming, entering, or using. Permission to access a resource is valled authorization. An access control mechanism (71) $connects$ between a user (or a process executing on behalf of a user) and system resources, such as applications, operating systems, firewalls, routers, files, and databases. The system must first authenticate a user seeking access. Typically the suthentication function determines whether the user is (72) $permitted$ to access the system at all. Then the access control function determines if the specific requested access by this user is permitted. A security administrator maintains an authorization database that specifies what type of access to which resources is allowed for this user. The access control function consults this database to determine whether to (73) $grant$ access. An auditing function monitors and keeps a record of user accesses to system resources. In ppractice, a number of (74) $users$ may cooperatively share the access control function. All operating systems have at least a rudimentary, and in many cases a quite robust, acess control component. Add-on security packages can add to the (75) $automated$ access control capabilities of the OS. Particular applications or utilities, such as a database management system, also incorporate access control functions. External devices, such as firewalls, can also provide access control services.

在物理安全和信息安全领域，访问控制是对访问场所或其他资源的选择性限制。访问行为可能意味着消费，进入或使用。访问资源的权限是valled授权。访问控制机制（71）连接用户（或代表用户执行的进程）和系统资源，例如应用程序，操作系统，防火墙，路由器，文件和数据库。系统必须首先验证寻求访问的用户。通常，身份验证功能确定是否允许用户（72）完全访问系统。然后，访问控制功能确定是否允许该用户的特定请求访问。安全管理员维护一个授权数据库，该数据库指定对该用户允许哪些资源的访问类型。访问控制功能参考该数据库以确定是否（73）授予访问权限。审计功能监视并记录用户对系统资源的访问。在ppractice中，许多（74）用户可以协作共享访问控制功能。所有操作系统至少都具有基本功能，并且在许多情况下是一个相当强大的接入控制组件。附加安全包可以添加到OS的（75）自动访问控制功能。特定应用程序或实用程序（例如数据库管理系统）还包含访问控制功能。外部设备（如防火墙）也可以提供访问控制服务。

(71)
A. cooperates 协作
B. coordinates 坐标
C. $connects$ 所连接
D. mediates 中介
(72)
A. denied 否认
B. $permitted$ 允许
C. prohibited 被禁止
D. rejected 被拒绝
(73)
A. open 打开
B. monitor 监控
C. $grant$ 发放
D. seek 寻求
(74)
A. components 组件
B. $users$ 用户
C. mechanisms 机制
D. algorithms 算法
(75)
A. remote 远程
B. native 本地人
C. controlled 受控
D. $automated$ 自动化

---

2016年下半年上午卷

Software entities are more complex for their size than perhaps any other human construct, bacause no two parts are alike (at least above the statement level). If they are, we make the two similar parts into one, a 71($subroutine$), open or closed, In this respect software systems differ profoundly from computers, buldings, or automobiles, where repeated elements abound.
Digital computers are themselves more complex than most things people build; they have very large numbers of states. This makes conceiving, describing, and testing them hard, Software systems have orders of magnitude more 72($states$) than computers do.
Likewise, a scaling-up of a software entity is not merely a repetition of the same elements in larger size; it is neccessarily an increase in the number of different elements. In most cases, the elements interact with each other in some 73($nonlinear$) fashion, and the complexity of the whole increases much more than linearly.
The complexity of software is an 74($essential$) property, not an accidental one. Hence descriptions of a software entity that abstract away its complexity often abstract away its essence. Mathematics and the physical sciences made great strides for three centuries by constructing simplified models of complex phenomena, deriving properties from the models, and verifying those properties experimentally. This worked because the complexities 75($ignored$) in the models were not the essential properties of the phenomena. It does not work when the complexities are the essence.
Many of the classical problems of developing software products derive from this essential complexity and its nonlinear increases with size. Not only technical problems but management problems as well come from the complexity.

软件实体的大小比任何其他人类构造更复杂，因为没有两个部分是相似的（至少高于语句级别）。如果它们是，我们将两个相似的部分组合成一个，71（子程序），打开或关闭。在这方面，软件系统与计算机，建筑物或汽车有很大不同，其中重复的元素比比皆是。
数字计算机本身比人们构建的大多数东西更复杂;他们有很多州。这使得构思，描述和测试它们变得困难，软件系统比计算机具有更多的数量级（状态）。
同样，软件实体的扩大不仅仅是更大尺寸的相同元素的重复;不可避免地增加了不同元素的数量。在大多数情况下，元素以某种73（非线性）方式相互作用，并且整体的复杂性增加远远超过线性。
软件的复杂性是74（必要）属性，而不是偶然的属性。因此，描述抽象其复杂性的软件实体往往抽象出其本质。通过构建复杂现象的简化模型，从模型中推导出属性，并通过实验验证这些属性，数学和物理科学在三个世纪中取得了长足的进步。这是有效的，因为模型中的复杂性75（忽略）不是这种现象的基本属性。当复杂性是本质时，它不起作用。
开发软件产品的许多经典问题源于这种基本的复杂性，并且其非线性随着尺寸的增加而增加。不仅技术问题，而且管理问题也来自复杂性。

(71)
A. task 任务
B. job 工作
C. $subroutine$ 子程序
D. program 程序
(72)
A. $states$ 状态
B. parts 部分
C. conditions 条件
D. expressions 表达式
(73)
A. linear 线性
B. $nonlinear$ 非线性
C. parallel 平行
D. additive 添加剂
(74)
A. surface 表面
B. outside 外边
C. exterior 外观
D. $essential$ 必要
(75)
A. fixed 固定
B. included 包括
C. $ignored$ 忽视
D. stabilized 稳定