你可能感兴趣的试题

关于软件测试，（）的叙述是正确的。
①测试开始越早，越有利于发现软件缺陷
②采用正确的测试用例设计方法，软件测试可以做到穷举测试
③测试覆盖度和测试用例数量成正比
④软件测试的时间越长越好

功能测试执行过后一般可以确认系统的功能缺陷，缺陷的类型包括（）。
①功能不满足隐性需求
②功能实现不正确
③功能不符合相关的法律法规
④功能易用性不好

正确的集成测试描述包括（）。
①集成测试也叫做组装测试，通常是在单元测试的基础上，将模块按照设计说明书要求进行组装和测试的过程。
②自顶向下的增殖方式是集成测试的一种组装方式，它能较早地验证主要的控制和判断点，对于输入输出模块、复杂算法模块中存在的错误能够较早地发现。
③集成测试的目的在于检查被测模块能否正确实现详细设计说明中的模块功能、性能、接口和设计约束等要求
④集成测试需要重点关注各个模块之间的相互影响，发现并排除全局数据结构问题

以下关于软件质量特性测试的叙述，正确的是（）。
①成熟性测试是检验软件系统故障，或违反指定接口的情况下维持规定的性能水平有关的测试工作
②功能性测试是检验适合性、准确性、互操作性、安全保密性、功能依从性的测试工作
③易学性测试是检查系统中用户为操作和运行控制所花努力有关的测试工作
④效率测试是指在规定条件下产品执行其功能时，对时间消耗及资源利用的测试工作

对软件可靠性的理解，正确的是（）。
①软件可靠性是指在指定条件下使用时，软件产品维持规定的性能级别的能力
②软件可靠性的种种局限是由于随着时间的推移，软件需求和使用方式发生了变化
③软件可靠性包括成熟性、有效性、容错性、易恢复性等质量子特性
④针对软件可靠性中的容错性子特性应测试软件失效防护能力

以下说法不正确的选项包括（）。
①软件测试不仅仅指测试的执行，还包括很多其他的活动
②软件测试是一个独立的流程，贯穿产品整个生命周期，与其他流程并发地进行
③应用H模型有利于资源调配，有助于跟踪测试投入的流向
④H模型指出，单元测试、集成测试、系统测试不存在严格的次序关系，各层次之间的测试存在反复触发、迭代和增量关系等

以下控制流图的圈复杂度V（g）为（）。

计算机的用途不同，对其部件的性能指标要求也有所不同。以科学计算为主的计算机，对（）要求较高，而且应该重点考虑（）。

计算机的用途不同，对其部件的性能指标要求也有所不同。以科学计算为主的计算机，对（）要求较高，而且应该重点考虑（）。

设系统中有 R 类资源 m 个，现有 n 个进程互斥使用。若每个进程对 R 资源的最大需求为w，那么当m、n、w取下表的值时，对于下表中的a～e五种情况， （） 两种情况可能会发生死锁。对于这两种情况，若将 （） ，则不会发生死锁。
 

零件关系P（零件名，条形码，供应商，产地，价格）中的 （） 属性可以作为该关系的主键。查询产于西安且名称为“P2”的零件，结果以零件名、供应商及零件价格分列表示，对应的SQL语句为： 　　SELECT零件名，供应商，价格 　　FROM P 　　WHERE零件名=’P2’ AND （） ;

在Windows XP操作系统中，用户利用“磁盘管理”程序可以对磁盘进行初始化、创建卷，（）。通常将“C：\Windows\myprogram.exe”文件设置成只读和隐藏属性，以便控制用户对该文件的访问，这一级安全管理称之为（）安全管理。

For nearly ten years, the Unified Modeling Language (UML) has been the industry standard for visualizing, specifying, constructing, and documenting the（）of a software-intensive system. As the（）standard modeling language, the UML facilitates communication and reduces confusion among project（）. The recent standardization of UML 2.0 has further extended the language’s scope and viability. Its inherent expressiveness allows users to（）everything from enterprise information systems and distributed Web-based applications to real-time embedded systems. 　　The UML is not limited to modeling software. In fact, it is expressive enough to model（）systems, such as workflow in the legal system, the structure and behavior of a patient healthcare system, software engineering in aircraft combat systems, and the design of hardware. To understand the UML, you need to form a conceptual model of the language, and this requires learning three major elements: the UML’s basic building blocks, the rules that dictate how those building blocks may be put together, and some common mechanisms that apply throughout the UML.

零件关系P（零件名，条形码，供应商，产地，价格）中的 （） 属性可以作为该关系的主键。查询产于西安且名称为“P2”的零件，结果以零件名、供应商及零件价格分列表示，对应的SQL语句为： 　　SELECT零件名，供应商，价格 　　FROM P 　　WHERE零件名=’P2’ AND （） ;
 

在Windows XP操作系统中，用户利用“磁盘管理”程序可以对磁盘进行初始化、创建卷，（）。通常将“C：\Windows\myprogram.exe”文件设置成只读和隐藏属性，以便控制用户对该文件的访问，这一级安全管理称之为（）安全管理。

设系统中有 R 类资源 m 个，现有 n 个进程互斥使用。若每个进程对 R 资源的最大需求为w，那么当m、n、w取下表的值时，对于下表中的a～e五种情况， （） 两种情况可能会发生死锁。对于这两种情况，若将 （） ，则不会发生死锁。
 

For nearly ten years, the Unified Modeling Language (UML) has been the industry standard for visualizing, specifying, constructing, and documenting the（）of a software-intensive system. As the（）standard modeling language, the UML facilitates communication and reduces confusion among project（）. The recent standardization of UML 2.0 has further extended the language’s scope and viability. Its inherent expressiveness allows users to（）everything from enterprise information systems and distributed Web-based applications to real-time embedded systems. 　　The UML is not limited to modeling software. In fact, it is expressive enough to model（）systems, such as workflow in the legal system, the structure and behavior of a patient healthcare system, software engineering in aircraft combat systems, and the design of hardware. To understand the UML, you need to form a conceptual model of the language, and this requires learning three major elements: the UML’s basic building blocks, the rules that dictate how those building blocks may be put together, and some common mechanisms that apply throughout the UML.

For nearly ten years, the Unified Modeling Language (UML) has been the industry standard for visualizing, specifying, constructing, and documenting the（）of a software-intensive system. As the（）standard modeling language, the UML facilitates communication and reduces confusion among project（）. The recent standardization of UML 2.0 has further extended the language’s scope and viability. Its inherent expressiveness allows users to（）everything from enterprise information systems and distributed Web-based applications to real-time embedded systems. 　　The UML is not limited to modeling software. In fact, it is expressive enough to model（）systems, such as workflow in the legal system, the structure and behavior of a patient healthcare system, software engineering in aircraft combat systems, and the design of hardware. To understand the UML, you need to form a conceptual model of the language, and this requires learning three major elements: the UML’s basic building blocks, the rules that dictate how those building blocks may be put together, and some common mechanisms that apply throughout the UML.

For nearly ten years, the Unified Modeling Language (UML) has been the industry standard for visualizing, specifying, constructing, and documenting the（）of a software-intensive system. As the（）standard modeling language, the UML facilitates communication and reduces confusion among project（）. The recent standardization of UML 2.0 has further extended the language’s scope and viability. Its inherent expressiveness allows users to（）everything from enterprise information systems and distributed Web-based applications to real-time embedded systems. 　　The UML is not limited to modeling software. In fact, it is expressive enough to model（）systems, such as workflow in the legal system, the structure and behavior of a patient healthcare system, software engineering in aircraft combat systems, and the design of hardware. To understand the UML, you need to form a conceptual model of the language, and this requires learning three major elements: the UML’s basic building blocks, the rules that dictate how those building blocks may be put together, and some common mechanisms that apply throughout the UML.

For nearly ten years, the Unified Modeling Language (UML) has been the industry standard for visualizing, specifying, constructing, and documenting the（）of a software-intensive system. As the（）standard modeling language, the UML facilitates communication and reduces confusion among project（）. The recent standardization of UML 2.0 has further extended the language’s scope and viability. Its inherent expressiveness allows users to（）everything from enterprise information systems and distributed Web-based applications to real-time embedded systems. 　　The UML is not limited to modeling software. In fact, it is expressive enough to model（）systems, such as workflow in the legal system, the structure and behavior of a patient healthcare system, software engineering in aircraft combat systems, and the design of hardware. To understand the UML, you need to form a conceptual model of the language, and this requires learning three major elements: the UML’s basic building blocks, the rules that dictate how those building blocks may be put together, and some common mechanisms that apply throughout the UML.