CPU执行算术运算或者逻辑运算时，常将源操作数和结果暂存在( )中。

要判断字长为16位的整数a的低四位是否全为0，则( )。

计算机系统中常用的输入/输出控制方式有无条件传送、中断、程序查询和DMA方式等。当采用( )方式时，不需要CPU执行程序指令来传送数据。

某系统由下图所示的冗余部件构成。若每个部件的千小时可靠度都为R，则该系统的千小时可靠度为( )。

已知数据信息为16位，最少应附加( )位校验位，才能实现海明码纠错。

以下关于Cache(高速缓冲存储器)的叙述中，不正确的是( )。

HTTPS使用( )协议对报文进行封装。

以下加密算法中适合对大量的明文消息进行加密传输的是( )。

假定用户A、B 分别从I₁、I₂两个CA取得了各自的证书，下面( )是A 、B 互信的必要条件。

甲软件公司受乙企业委托安排公司软件设计师开发了信息系统管理软件，由于在委托开发合同中未对软件著作权归属作出明确的约定，所以该信息系统管理软件的著作权由( )享有。

根据我国商标法，下列商品中必须使用注册商标的是( )。

甲、乙两人在同一天就同样的发明创造提交了专利申请专利局将分别向各申请人通报有关情况，并提出多种可能采用的解决办法。下列说法中，不可能采用( )。

数字语音的采样频率定义为8kHz，这是因为( )。

使用图像扫描仪以300DPI的分辨率扫描一幅3x4英寸的图片，可以得到( )像素的数字图像。

某软件项目的活动图如下图所示，其中顶点表示项目里程碑，连接顶点的边表示包含的活动，边上的数字表示活动的持续时间(天)，则完成该项目的最少时间为(15)天。活动BD和HK最早可以从第(16)天开始。(活动AB 、AE和AC最早从第1天开始)

某软件项目的活动图如下图所示，其中顶点表示项目里程碑，连接顶点的边表示包含的活动，边上的数字表示活动的持续时间(天)，则完成该项目的最少时间为(15)天。活动BD和HK最早可以从第(16)天开始。(活动AB 、AE和AC最早从第1天开始)

在采用结构化开发方法进行软件开发时，设计阶段接口设计主要依据需求分析阶段的(17)。接口设计的任务主要是(18)。

在采用结构化开发方法进行软件开发时，设计阶段接口设计主要依据需求分析阶段的(17)。接口设计的任务主要是(18)。

在进行软件开发时，采用无主程序员的开发小组，成员之间相互平等;而主程序员负责制的开发小组，由一个主程序员和若干成员组成，成员之间没有沟通。在一个由8名开发人员构成的小组中，无主程序员组和主程序员组的沟通路径分别是( )。

在高级语言源程序员，常需要用户定义的标识符程序员的对象命名，常见的命名对象有( )。
①关键字（或保留字） ②变量 ③函数 ④ 数据类型 ⑤注释

在仅由字符a、b构成的所有字符串中，其中以b结尾的字符串集合可用正规式表示为( )。

在以阶段划分的编译中，判断程序语句的形式是否正确属于( ) 阶段的工作。

某计算机系统页面大小为4K，进程的页面变换表如下所示。若进程的逻辑地址为2D16H 。该地址经过变换后，其物理地址应为 ( )。

某系统中有3个并发进程竞争资源R ，每个进程都需要5个R ，那么至少有( ) 个R，才能保证系统不会发生死锁。

以下关于C/S( 客户机/服务器)体系结构的优点的叙述中，不正确的是 ( ) 。

在设计软件的模块结构时，( )不能改进设计质量。

在面向对象方法中，多态指的是( )。

在数据库系统运行维护阶段，通过重建视图能够实现( )。

数据库概念结构设计阶段是在( )的基础上，依照用户需求对信息进行分类、聚集和概括，建立概念模型。

数据模型通常由( )三要素构成。

给定关系模式R<U ，F> ，其中U为关系R的属性集，F是U上的一组函数依赖，X、Y、Z、W是U上的属性组。下列结论正确的是( )。

在关系R(A1，A2 ，A3) 和 S(A2 ，A3 ，A4) 上进行关系运算，与该关系表达式等价的是( )。

将该查询转换为等价的SQL语句如下:

给定关系模式R<U ，F> ，U={A，B，C，D，E}，F= {B→A ，D →A ，A→E ，AC →B }，则R的候选关键字为(34)，分解ρ= (R1（ABCE)，R2（CD)} (35)。

给定关系模式R<U ，F> ，U={A，B，C，D，E}，F= {B→A ，D →A ，A→E ，AC →B }，则R的候选关键字为(34)，分解ρ= (R1（ABCE)，R2（CD)} (35)。

并发执行的三个事务T1、T2 和T3，事务T1对数据D1加了共享锁，事务T2、T3分别对数据D2 、D3加了排它锁，之后事务T1对数据(36)；事务T2对数据(37) 。

并发执行的三个事务T1、T2 和T3，事务T1对数据D1加了共享锁，事务T2、T3分别对数据D2 、D3加了排它锁，之后事务T1对数据(36)；事务T2对数据(37) 。

数据库概念结构设计阶段的工作步骤依次为 ( )。

在数据传输过程中，为了防止被窃取可以通过( )来实现的。

在某企业的工程项目管理数据库中供应商关系Supp、项目关系Proj和零件关系Part 的E-R模型和关系模式如下：

Supp (供应商号，供应商名，地址，电话) //供应商号唯一标识Supp中的每一个元组
Proj (项目号，项目名，负责人，电话) //项目号唯一标识Proj中的每一个元组
Part (零件号，零件名) //零件号唯一标识Part中的每一个元组
其中，每个供应商可以为多个项目供应多种零件，每个项目可以由多个供应商供应多种零件，每种零件可以由多个供应商供应给多个项目。SP_P 的联系类型为(40),(41)。

在某企业的工程项目管理数据库中供应商关系Supp、项目关系Proj和零件关系Part 的E-R模型和关系模式如下：

Supp (供应商号，供应商名，地址，电话) //供应商号唯一标识Supp中的每一个元组
Proj (项目号，项目名，负责人，电话) //项目号唯一标识Proj中的每一个元组
Part (零件号，零件名) //零件号唯一标识Part中的每一个元组
其中，每个供应商可以为多个项目供应多种零件，每个项目可以由多个供应商供应多种零件，每种零件可以由多个供应商供应给多个项目。SP_P 的联系类型为(40),(41)。

给定关系模式SP_P (供应商号，项目号，零件号，数量)，查询至少给3 个(包含3个)不同项目供应了零件的供应商，要求输出供应商号和供应零件数量的总和，并按供应商号降序排列。
SELECT 供应商号， SUM (数量) FROMSP _P
(42)
(43)
(44)；

给定关系模式SP_P (供应商号，项目号，零件号，数量)，查询至少给3 个(包含3个)不同项目供应了零件的供应商，要求输出供应商号和供应零件数量的总和，并按供应商号降序排列。
SELECT 供应商号， SUM (数量) FROMSP _P
(42)
(43)
(44)；

给定关系模式SP_P (供应商号，项目号，零件号，数量)，查询至少给3 个(包含3个)不同项目供应了零件的供应商，要求输出供应商号和供应零件数量的总和，并按供应商号降序排列。
SELECT 供应商号， SUM (数量) FROMSP _P
(42)
(43)
(44)；

某企业的信息系统管理数据库中的员工关系模式为Emp (员工号，姓名，部门号，岗位，联系地址，薪资)，函数依赖集 F={员工号→(姓名，部门号，岗位，联系地址)，岗位→薪资}。Emp关系的主键为(45)，函数依赖集F(46)。

某企业的信息系统管理数据库中的员工关系模式为Emp (员工号，姓名，部门号，岗位，联系地址，薪资)，函数依赖集 F={员工号→(姓名，部门号，岗位，联系地址)，岗位→薪资}。Emp关系的主键为(45)，函数依赖集F(46)。

满足BCNF范式的关系( )。

数据的物理存储结构，对于程序员来讲，( )。

在SQL中，用户( )获取权限。

保证并发调度的可串行化，是为了确保事务的( )。

满足两阶段封锁协议的调度一定是( )。

下图中两个事务的调度属于( )。

以下对数据库故障的描述中，不正确的是( )。

有两个关系模式R(A，B，C，D)和S(A，C，E，G)，则X=RxS的关系模式是( )。

给定关系模式R<U ，F> ，其中属性集U={A，B，C，D，E，G ，H} 函数依赖集F= {A→B，AE→H，BG→DC，E→C，H→E } ，下列函数依赖不成立的是( )。

在日志中加入检查点，可( )。

某销售公司需开发数据库应用系统管理客户的商品购买信息。该系统需记录客户的姓名、出生日期、年龄和身份证号信息，记录客户每次购买的商品名称和购买时间等信息。如果在设计时将出生日期和年龄都设定为客户实体的属性，则年龄属于(57)，数据库中购买记录表中每条购买记录对应的客户必须在客户表中存在，这个约束属于(58)。

某销售公司需开发数据库应用系统管理客户的商品购买信息。该系统需记录客户的姓名、出生日期、年龄和身份证号信息，记录客户每次购买的商品名称和购买时间等信息。如果在设计时将出生日期和年龄都设定为客户实体的属性，则年龄属于(57)，数据库中购买记录表中每条购买记录对应的客户必须在客户表中存在，这个约束属于(58)。

NULL值在数据库中表示(59)，逻辑运算UNKNOWN OR TRUE 的结果是(60)。

NULL值在数据库中表示(59)，逻辑运算UNKNOWN OR TRUE 的结果是(60)。

CAP理论是NoSQL理论的基础，下列性质不属于CAP的是( )。

以下是平行数据库的四种体系结构，在( )体系结构中所有处理器共享一个公共的主存储器和磁盘。

数据仓库中的数据组织是基于( )模型的。

数据挖掘中分类的典型应用不包括(64)。(65)可以用于数据挖掘的分类任务。

数据挖掘中分类的典型应用不包括(64)。(65)可以用于数据挖掘的分类任务。

在浏览器地址栏输入一个正确的网址后，本地主机将首先在( )中查询该网址对应的IP地址。

下面关于Linux 目录的描述中，正确的是( )。

以下IP地址中，属于网络10.110.12.29/255.255.255.224的主机IP是( ) 。

在异步通信中，每个字符包含1位起始位、7位数据位和2位终止位，若每秒钟传送500个字符，则每秒有效数据速率为( ) 。

以下路由策略中，依据网络信息经常更新路由的是( ) 。

The beauty of software is in its funciion ,in its internal srurcture,and in zhe way inwhich it is created by a team. To a user，a program with just the right features presented through an intuitive and (71) interface is beautiful.To a soware designer，an intemal sucre that is partitioned in a simple and intuitive manner，and that minirnÍzes intemal coupling is beautiful.To developers and managers ，a motivated tenof developers makingignificant progress eve week，and producing defect-free code，is beautifu l. There is beauty on all these levels.
Our world needs software -- 10ts of syears ago soware was something
that ran in a few big and expensive machines. years ago it was something that ran in most companies and industrial settings. Now there is sware running in our cell phones ， watches ，appliances，automobi1es ，toys，and tools. And need for new and betler soware never (72) As our civilization grows and expands，as developirig nations build their masuctures，as deve10ped nations striveωachieve ever greater efficiencies，the need for more and more software (73)to increase. It would be a great shame if，in all that soware，there was no beauty.
We know that soware can be uglWe know that it can be hard to use，unreliable ，and carelessly structured. We know that there are software systems whose tangled and careless intemal structures make them expensive and difficult to change. We know that there are soware systems that present their features through an awkward and cumbersome interface.We know that there are software systems that crash and misbehave. These are (74) systems. Unfortunately ，as a profession ，soware developers tend to create more ugly systems than beautiful ones.
There is a secret at the best sofuλrare developers know. Beauty is cheaper than ugliness. Beauty is faster than ugliness. A beautiful soware system can be built and maintained in less time，and for less money，than an ugly one. Novice soware developers don't understand is. They think that they have to do everything fast and quick.They think that beauty is (75). No! By doing things fast and quick，they make messes that make the software stiff and hard to understand. Beautiful systems are flexible and easy to understand. Building them and maintaining them is a joy. It is ugliness that is impractical.Ugliness will slow you down and make your software expensive and brittle. Beautiful systems cost the least to build and maintain ，and are delivered soonest.

The beauty of software is in its funciion ,in its internal srurcture,and in zhe way inwhich it is created by a team. To a user，a program with just the right features presented through an intuitive and (71) interface is beautiful.To a soware designer，an intemal sucre that is partitioned in a simple and intuitive manner，and that minirnÍzes intemal coupling is beautiful.To developers and managers ，a motivated tenof developers makingignificant progress eve week，and producing defect-free code，is beautifu l. There is beauty on all these levels.
Our world needs software -- 10ts of syears ago soware was something
that ran in a few big and expensive machines. years ago it was something that ran in most companies and industrial settings. Now there is sware running in our cell phones ， watches ，appliances，automobi1es ，toys，and tools. And need for new and betler soware never (72) As our civilization grows and expands，as developirig nations build their masuctures，as deve10ped nations striveωachieve ever greater efficiencies，the need for more and more software (73)to increase. It would be a great shame if，in all that soware，there was no beauty.
We know that soware can be uglWe know that it can be hard to use，unreliable ，and carelessly structured. We know that there are software systems whose tangled and careless intemal structures make them expensive and difficult to change. We know that there are soware systems that present their features through an awkward and cumbersome interface.We know that there are software systems that crash and misbehave. These are (74) systems. Unfortunately ，as a profession ，soware developers tend to create more ugly systems than beautiful ones.
There is a secret at the best sofuλrare developers know. Beauty is cheaper than ugliness. Beauty is faster than ugliness. A beautiful soware system can be built and maintained in less time，and for less money，than an ugly one. Novice soware developers don't understand is. They think that they have to do everything fast and quick.They think that beauty is (75). No! By doing things fast and quick，they make messes that make the software stiff and hard to understand. Beautiful systems are flexible and easy to understand. Building them and maintaining them is a joy. It is ugliness that is impractical.Ugliness will slow you down and make your software expensive and brittle. Beautiful systems cost the least to build and maintain ，and are delivered soonest.

The beauty of software is in its funciion ,in its internal srurcture,and in zhe way inwhich it is created by a team. To a user，a program with just the right features presented through an intuitive and (71) interface is beautiful.To a soware designer，an intemal sucre that is partitioned in a simple and intuitive manner，and that minirnÍzes intemal coupling is beautiful.To developers and managers ，a motivated tenof developers makingignificant progress eve week，and producing defect-free code，is beautifu l. There is beauty on all these levels.
Our world needs software -- 10ts of syears ago soware was something
that ran in a few big and expensive machines. years ago it was something that ran in most companies and industrial settings. Now there is sware running in our cell phones ， watches ，appliances，automobi1es ，toys，and tools. And need for new and betler soware never (72) As our civilization grows and expands，as developirig nations build their masuctures，as deve10ped nations striveωachieve ever greater efficiencies，the need for more and more software (73)to increase. It would be a great shame if，in all that soware，there was no beauty.
We know that soware can be uglWe know that it can be hard to use，unreliable ，and carelessly structured. We know that there are software systems whose tangled and careless intemal structures make them expensive and difficult to change. We know that there are soware systems that present their features through an awkward and cumbersome interface.We know that there are software systems that crash and misbehave. These are (74) systems. Unfortunately ，as a profession ，soware developers tend to create more ugly systems than beautiful ones.
There is a secret at the best sofuλrare developers know. Beauty is cheaper than ugliness. Beauty is faster than ugliness. A beautiful soware system can be built and maintained in less time，and for less money，than an ugly one. Novice soware developers don't understand is. They think that they have to do everything fast and quick.They think that beauty is (75). No! By doing things fast and quick，they make messes that make the software stiff and hard to understand. Beautiful systems are flexible and easy to understand. Building them and maintaining them is a joy. It is ugliness that is impractical.Ugliness will slow you down and make your software expensive and brittle. Beautiful systems cost the least to build and maintain ，and are delivered soonest.

The beauty of software is in its funciion ,in its internal srurcture,and in zhe way inwhich it is created by a team. To a user，a program with just the right features presented through an intuitive and (71) interface is beautiful.To a soware designer，an intemal sucre that is partitioned in a simple and intuitive manner，and that minirnÍzes intemal coupling is beautiful.To developers and managers ，a motivated tenof developers makingignificant progress eve week，and producing defect-free code，is beautifu l. There is beauty on all these levels.
Our world needs software -- 10ts of syears ago soware was something
that ran in a few big and expensive machines. years ago it was something that ran in most companies and industrial settings. Now there is sware running in our cell phones ， watches ，appliances，automobi1es ，toys，and tools. And need for new and betler soware never (72) As our civilization grows and expands，as developirig nations build their masuctures，as deve10ped nations striveωachieve ever greater efficiencies，the need for more and more software (73)to increase. It would be a great shame if，in all that soware，there was no beauty.
We know that soware can be uglWe know that it can be hard to use，unreliable ，and carelessly structured. We know that there are software systems whose tangled and careless intemal structures make them expensive and difficult to change. We know that there are soware systems that present their features through an awkward and cumbersome interface.We know that there are software systems that crash and misbehave. These are (74) systems. Unfortunately ，as a profession ，soware developers tend to create more ugly systems than beautiful ones.
There is a secret at the best sofuλrare developers know. Beauty is cheaper than ugliness. Beauty is faster than ugliness. A beautiful soware system can be built and maintained in less time，and for less money，than an ugly one. Novice soware developers don't understand is. They think that they have to do everything fast and quick.They think that beauty is (75). No! By doing things fast and quick，they make messes that make the software stiff and hard to understand. Beautiful systems are flexible and easy to understand. Building them and maintaining them is a joy. It is ugliness that is impractical.Ugliness will slow you down and make your software expensive and brittle. Beautiful systems cost the least to build and maintain ，and are delivered soonest.

The beauty of software is in its funciion ,in its internal srurcture,and in zhe way inwhich it is created by a team. To a user，a program with just the right features presented through an intuitive and (71) interface is beautiful.To a soware designer，an intemal sucre that is partitioned in a simple and intuitive manner，and that minirnÍzes intemal coupling is beautiful.To developers and managers ，a motivated tenof developers makingignificant progress eve week，and producing defect-free code，is beautifu l. There is beauty on all these levels.
Our world needs software -- 10ts of syears ago soware was something
that ran in a few big and expensive machines. years ago it was something that ran in most companies and industrial settings. Now there is sware running in our cell phones ， watches ，appliances，automobi1es ，toys，and tools. And need for new and betler soware never (72) As our civilization grows and expands，as developirig nations build their masuctures，as deve10ped nations striveωachieve ever greater efficiencies，the need for more and more software (73)to increase. It would be a great shame if，in all that soware，there was no beauty.
We know that soware can be uglWe know that it can be hard to use，unreliable ，and carelessly structured. We know that there are software systems whose tangled and careless intemal structures make them expensive and difficult to change. We know that there are soware systems that present their features through an awkward and cumbersome interface.We know that there are software systems that crash and misbehave. These are (74) systems. Unfortunately ，as a profession ，soware developers tend to create more ugly systems than beautiful ones.
There is a secret at the best sofuλrare developers know. Beauty is cheaper than ugliness. Beauty is faster than ugliness. A beautiful soware system can be built and maintained in less time，and for less money，than an ugly one. Novice soware developers don't understand is. They think that they have to do everything fast and quick.They think that beauty is (75). No! By doing things fast and quick，they make messes that make the software stiff and hard to understand. Beautiful systems are flexible and easy to understand. Building them and maintaining them is a joy. It is ugliness that is impractical.Ugliness will slow you down and make your software expensive and brittle. Beautiful systems cost the least to build and maintain ，and are delivered soonest.