你可能感兴趣的试题

信息工程方法把整个信息系统的开发过程划分为4个实施阶段，其自上而下的顺序是（）。

软件的分层式体系结构把软件系统划分为4层，这4层结构自顶向下分别是（）。

1台服务器、3台客户机和2台打印机构成了一个局域网（如下图所示）。在该系统中，服务器根据某台客户机的请求，将数据在一台打印机上输出。设服务器、各客户机及各打印机的可用性分别为a、b、c，则该系统的可用性为（）。

某工程计划如下图所示，图中标注了完成任务A~H所需的天数，其中虚线表示虚任务。经评审后发现，任务D还可以缩短3天（即只需7天就能完成），则总工程可以缩短（）天。

某IP网络连接如下图所示，在这种配置下IP全局广播分组不能够通过的路径是（）。

已知3个类O、P和Q，类O中定义了一个私有方法F1、一个公有方法F2和一个受保护的方法F3；类P和类Q为类O的派生类，其继承方式如下所示：classP：protectedO{…}；classQ：publicO{…}；在关于方法F1的描述中正确的是（）；在关于方法F2的描述中正确的是（）；在关于方法F3的描述中正确的是（）。

设指令由取指、分析、执行3个子部件完成，并且每个子部件的时间均为△t。若采用常规标量单流水线处理机（即该处理机的度为1），连续执行12条指令，共需（）△t。若采用度为4的超标量流水线处理机，连续执行上述12条指令，只需（）△t。

在一个客户信息系统中存在两种类型的客户：个人客户和集团客户。对于个人客户，系统中保存了其客户标识和基本信息（包括姓名、住宅电话和email）；对于集团客户，系统中保存了其客户标识，以及与该集团客户相关的若干个联系人的信息（联系人的信息包括姓名、住宅电话、email、办公电话和职位）。根据上述描述，得到了如下所示的UML类图，其中类“客户”的属性有（）；类“人”的属性有（）。

某计算机主存按字节编址，主存与高速缓存Cache的地址变换采用组相联映像方式（即组内全相联，组间直接映像）。高速缓存分为2组，每组包含4块，块的大小为512B，主存容量为1MB。构成高速缓存的地址变换表相联存储器容量为（）bit。每次参与比较的存储单元为（）个。

已知3个类O、P和Q，类O中定义了一个私有方法F1、一个公有方法F2和一个受保护的方法F3；类P和类Q为类O的派生类，其继承方式如下所示：classP：protectedO{…}；classQ：publicO{…}；在关于方法F1的描述中正确的是（）；在关于方法F2的描述中正确的是（）；在关于方法F3的描述中正确的是（）。

设指令由取指、分析、执行3个子部件完成，并且每个子部件的时间均为△t。若采用常规标量单流水线处理机（即该处理机的度为1），连续执行12条指令，共需（）△t。若采用度为4的超标量流水线处理机，连续执行上述12条指令，只需（）△t。

某计算机主存按字节编址，主存与高速缓存Cache的地址变换采用组相联映像方式（即组内全相联，组间直接映像）。高速缓存分为2组，每组包含4块，块的大小为512B，主存容量为1MB。构成高速缓存的地址变换表相联存储器容量为（）bit。每次参与比较的存储单元为（）个。

在一个客户信息系统中存在两种类型的客户：个人客户和集团客户。对于个人客户，系统中保存了其客户标识和基本信息（包括姓名、住宅电话和email）；对于集团客户，系统中保存了其客户标识，以及与该集团客户相关的若干个联系人的信息（联系人的信息包括姓名、住宅电话、email、办公电话和职位）。根据上述描述，得到了如下所示的UML类图，其中类“客户”的属性有（）；类“人”的属性有（）。

已知3个类O、P和Q，类O中定义了一个私有方法F1、一个公有方法F2和一个受保护的方法F3；类P和类Q为类O的派生类，其继承方式如下所示：classP：protectedO{…}；classQ：publicO{…}；在关于方法F1的描述中正确的是（）；在关于方法F2的描述中正确的是（）；在关于方法F3的描述中正确的是（）。

COCOMO模型能够依据待开发软件的规模来估计软件开发的工期。若COCOMO模型公式为：其中，KDSI为预计应交付的源程序千行数，MM为开发该软件所需的人月数。设软件开发的生产率为每个人月能编写的最终能交付的源程序千行数（KDSI/MM），则根据上述COCOMO模型可以看出，软件开发的生产率随软件开发规模而变化的趋势如图（）所示。

企业信息系统往往是一个具有业务复杂性和技术复杂性的大系统，针对其建设，系统分析首先要进行的工作是（）。系统开发的目的是（）。

编号为0、1、2、3、…、15的16个处理器，用单级互联网络互联。当互连函数为Cube3（4维立方体单级互联函数）时，6号处理器与（）号处理器相连接。若采用互连函Shuffle（全混洗单级互联函数）时，6号处理器与（）号处理器相连接。

设有员工实体Employee（employeeID，name，sex，age，tel，departID），其中employeeID为员工号，name为员工姓名，sex为员工性别，age为员工年龄，tel为员工电话，记录该员工的手机号码、办公室电话等，departID为员工所在部门号，参照另一部门实体Department的主码departID。Employee实体中存在派生属性（）；Employee实体中还存在多值属性（）；对属性departID的约束是（）。

某高可靠性计算机系统由下图所示的冗余部件构成。若每个部件的千小时可靠度R 均为0.9，则该计算机系统的千小时可靠度为（）；该计算机系统的失效率 可使用（）来计算。 注： t 表示时间。

影响文件系统可靠性因素之一是文件系统的一致性问题，如果读取（）的某磁盘块，修改后在写回磁盘前系统崩溃，则对系统的影响相对较大。通常的解决方案是采用文件系统的一致性检查，一致性检查包括块的一致性检查和文件的一致性检查。在块的一致性检查时，检测程序构造一张表，表中为每个块设立两个计数器，一个跟踪该块在文件中出现的次数，一个跟踪该块在空闲表中出现的次数。若系统有16个块，检测程序通过检测发现表（）状态下的文件系统是一致的。

某书店有一个收银员，该书店最多允许n 个购书者进入。将收银员和购书者看作不同的进程，其工作流程如下图所示。利用PV 操作实现该过程，设置信号量S1、S2 和Sn，初值分别为0，0，n。则图中a1，a2 应填入（），图中b1 和b2 应填入（）。

SOX is an alternative（）for XML. It is useful for reading and creating XML content in a（）editor. It is then easily transformed into proper XML. SOX was created because developers can spend a great deal of time with raw XML. For many of us, the popular XML（）have not reached a point where their tree views, tables and forms can completely substitute for the underlying（）language. This is not surprising when one considers that developers still use a text view, albeit enhanced, for editing other languages such as Java. SOX uses（）to represent the structure of an XML document,which eliminates the need for closing tags and a number of quoting devices. The result is surprisingly clear.

企业信息系统往往是一个具有业务复杂性和技术复杂性的大系统，针对其建设，系统分析首先要进行的工作是（）。系统开发的目的是（）。

编号为0、1、2、3、…、15的16个处理器，用单级互联网络互联。当互连函数为Cube3（4维立方体单级互联函数）时，6号处理器与（）号处理器相连接。若采用互连函Shuffle（全混洗单级互联函数）时，6号处理器与（）号处理器相连接。

影响文件系统可靠性因素之一是文件系统的一致性问题，如果读取（）的某磁盘块，修改后在写回磁盘前系统崩溃，则对系统的影响相对较大。通常的解决方案是采用文件系统的一致性检查，一致性检查包括块的一致性检查和文件的一致性检查。在块的一致性检查时，检测程序构造一张表，表中为每个块设立两个计数器，一个跟踪该块在文件中出现的次数，一个跟踪该块在空闲表中出现的次数。若系统有16个块，检测程序通过检测发现表（）状态下的文件系统是一致的。

若系统有16个块，检测程序通过检测发现表（）状态下的文件系统是一致的。

某高可靠性计算机系统由下图所示的冗余部件构成。若每个部件的千小时可靠度R 均为0.9，则该计算机系统的千小时可靠度为（）；该计算机系统的失效率 可使用（）来计算。 注： t 表示时间。

设有员工实体Employee（employeeID，name，sex，age，tel，departID），其中employeeID为员工号，name为员工姓名，sex为员工性别，age为员工年龄，tel为员工电话，记录该员工的手机号码、办公室电话等，departID为员工所在部门号，参照另一部门实体Department的主码departID。Employee实体中存在派生属性（）；Employee实体中还存在多值属性（）；对属性departID的约束是（）。

某书店有一个收银员，该书店最多允许n 个购书者进入。将收银员和购书者看作不同的进程，其工作流程如下图所示。利用PV 操作实现该过程，设置信号量S1、S2 和Sn，初值分别为0，0，n。则图中a1，a2 应填入（），图中b1 和b2 应填入（）。

SOX is an alternative（）for XML. It is useful for reading and creating XML content in a（）editor. It is then easily transformed into proper XML. SOX was created because developers can spend a great deal of time with raw XML. For many of us, the popular XML（）have not reached a point where their tree views, tables and forms can completely substitute for the underlying（）language. This is not surprising when one considers that developers still use a text view, albeit enhanced, for editing other languages such as Java. SOX uses（）to represent the structure of an XML document,which eliminates the need for closing tags and a number of quoting devices. The result is surprisingly clear.

设有员工实体Employee（employeeID，name，sex，age，tel，departID），其中employeeID为员工号，name为员工姓名，sex为员工性别，age为员工年龄，tel为员工电话，记录该员工的手机号码、办公室电话等，departID为员工所在部门号，参照另一部门实体Department的主码departID。Employee实体中存在派生属性（）；Employee实体中还存在多值属性（）；对属性departID的约束是（）。

SOX is an alternative（）for XML. It is useful for reading and creating XML content in a（）editor. It is then easily transformed into proper XML. SOX was created because developers can spend a great deal of time with raw XML. For many of us, the popular XML（）have not reached a point where their tree views, tables and forms can completely substitute for the underlying（）language. This is not surprising when one considers that developers still use a text view, albeit enhanced, for editing other languages such as Java. SOX uses（）to represent the structure of an XML document,which eliminates the need for closing tags and a number of quoting devices. The result is surprisingly clear.

SOX is an alternative（）for XML. It is useful for reading and creating XML content in a（）editor. It is then easily transformed into proper XML. SOX was created because developers can spend a great deal of time with raw XML. For many of us, the popular XML（）have not reached a point where their tree views, tables and forms can completely substitute for the underlying（）language. This is not surprising when one considers that developers still use a text view, albeit enhanced, for editing other languages such as Java. SOX uses（）to represent the structure of an XML document,which eliminates the need for closing tags and a number of quoting devices. The result is surprisingly clear.

With hundreds of millions of electronic（）taking place daily, businesses and organizations have a strong incentive to protect the（）of the data exchanged in this manner, and to positively ensure the（）of those involved in the transactions. This has led to an industry-wide quest for better, more secure methods for controlling IT operations, and for deploying strong security mechanisms deeply and broadly throughout networked infrastructures and client devices. One of the more successful concepts to engage the imaginations of the security community has been the development of standards-based security（）that can be incorporated in the hardware design of client computers. The principle of encapsulating core security capabilities in（）and integrating security provisions at the deepest levels of the machine operation has significant benefits for both users and those responsible for securing IT operations.

SOX is an alternative（）for XML. It is useful for reading and creating XML content in a（）editor. It is then easily transformed into proper XML. SOX was created because developers can spend a great deal of time with raw XML. For many of us, the popular XML（）have not reached a point where their tree views, tables and forms can completely substitute for the underlying（）language. This is not surprising when one considers that developers still use a text view, albeit enhanced, for editing other languages such as Java. SOX uses（）to represent the structure of an XML document,which eliminates the need for closing tags and a number of quoting devices. The result is surprisingly clear.

With hundreds of millions of electronic（）taking place daily, businesses and organizations have a strong incentive to protect the（）of the data exchanged in this manner, and to positively ensure the（）of those involved in the transactions. This has led to an industry-wide quest for better, more secure methods for controlling IT operations, and for deploying strong security mechanisms deeply and broadly throughout networked infrastructures and client devices. One of the more successful concepts to engage the imaginations of the security community has been the development of standards-based security（）that can be incorporated in the hardware design of client computers. The principle of encapsulating core security capabilities in（）and integrating security provisions at the deepest levels of the machine operation has significant benefits for both users and those responsible for securing IT operations.

With hundreds of millions of electronic（）taking place daily, businesses and organizations have a strong incentive to protect the（）of the data exchanged in this manner, and to positively ensure the（）of those involved in the transactions. This has led to an industry-wide quest for better, more secure methods for controlling IT operations, and for deploying strong security mechanisms deeply and broadly throughout networked infrastructures and client devices. One of the more successful concepts to engage the imaginations of the security community has been the development of standards-based security（）that can be incorporated in the hardware design of client computers. The principle of encapsulating core security capabilities in（）and integrating security provisions at the deepest levels of the machine operation has significant benefits for both users and those responsible for securing IT operations.

With hundreds of millions of electronic（）taking place daily, businesses and organizations have a strong incentive to protect the（）of the data exchanged in this manner, and to positively ensure the（）of those involved in the transactions. This has led to an industry-wide quest for better, more secure methods for controlling IT operations, and for deploying strong security mechanisms deeply and broadly throughout networked infrastructures and client devices. One of the more successful concepts to engage the imaginations of the security community has been the development of standards-based security（）that can be incorporated in the hardware design of client computers. The principle of encapsulating core security capabilities in（）and integrating security provisions at the deepest levels of the machine operation has significant benefits for both users and those responsible for securing IT operations.

With hundreds of millions of electronic（）taking place daily, businesses and organizations have a strong incentive to protect the（）of the data exchanged in this manner, and to positively ensure the（）of those involved in the transactions. This has led to an industry-wide quest for better, more secure methods for controlling IT operations, and for deploying strong security mechanisms deeply and broadly throughout networked infrastructures and client devices. One of the more successful concepts to engage the imaginations of the security community has been the development of standards-based security（）that can be incorporated in the hardware design of client computers. The principle of encapsulating core security capabilities in（）and integrating security provisions at the deepest levels of the machine operation has significant benefits for both users and those responsible for securing IT operations.