你可能感兴趣的试题

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

某软件项目的活动图如下图所示，其中顶点表示项目里程碑，连接顶点的边表示包含的活动，边上的数字表示活动的持续时间（天），则完成该项目的最少时间为（）天。

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

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

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

进程P1、P2、P3、P4和P5的前趋图如下所示：

若用PV操作控制进程P1、P2、P3、P4和P5并发执行的过程，需要设置5个信号量S1、S2、S3、S4和S5，且信号量S1~S5的初值都等于零。如下的进程执行图中a和b处应分别填写（）。

进程P1、P2、P3、P4和P5的前趋图如下所示：

若用PV操作控制进程P1、P2、P3、P4和P5并发执行的过程，需要设置5个信号量S1、S2、S3、S4和S5，且信号量S1~S5的初值都等于零。如下的进程执行图中c和d处应分别填写（）。

进程P1、P2、P3、P4和P5的前趋图如下所示：

若用PV操作控制进程P1、P2、P3、P4和P5并发执行的过程，需要设置5个信号量S1、S2、S3、S4和S5，且信号量S1~S5的初值都等于零。如下的进程执行图中e和f处应分别填写（）。

对下图所示的程序流程图进行语句覆盖测试和路劲覆盖测试，至少需要（）个测试用例。

对下图所示的程序流程图进行语句覆盖测试和路劲覆盖测试，采用McCabe度量法计算其环路复杂度为（）。

以下UML图是（）。

以下UML图中，表示（）。

以下UML图中，表示（）。

下图所示为观察者（Obserrver）模式的抽象示意图，其中（）知道其观察者，可以有任何多个观察者观察同一个目标；提供住处和删除观察者对象的接口。

下图所示为观察者（Obserrver）模式的抽象示意图，此模式体现的最主要的特征是（）。

装饰器（Decorator）模式用于（）。
①将一个对象加以包装以给客户提供其希望的另外一个接口
②将一个对象加以包装以提供一些额外的行为
③将一个对象加以包装以控制对这个对象的访问
④将一系列对象加以包装以简化其接口

外观（Facade）模式用于（）。
①将一个对象加以包装以给客户提供其希望的另外一个接口
②将一个对象加以包装以提供一些额外的行为
③将一个对象加以包装以控制对这个对象的访问
④将一系列对象加以包装以简化其接口

某确定的有限自动机（DFA）的状态转换图如下图所示（A是初态，D、E是终态），则该DFA能识别（）。

函数main、f的定义如下所示，调用函数们f（）时，第一个参数采用传值（callbyvalue）方式，第二个参数采用传引用（callbyreference）方式，main函数中“print（x）”执行后输出的值为（）。

下图为一个表达式的语法树，该表达式的后缀形式为（）。

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

其中，每个供应商可以为多个项目供应多种零件，每个项目可由多个供应商供应多种零件。SPP需要生成一个独立的关系模式，其联系类型为（54）给定关系模式SPP（供应商号，项目号，零件号，数量）查询至少供应了3个项目（包含3项）的供应商，输出其供应商号和供应零件数量的总和，并按供应商号降序排列。

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

其中，每个供应商可以为多个项目供应多种零件，每个项目可由多个供应商供应多种零件。SPP需要生成一个独立的关系模式，其联系类型为（54）给定关系模式SPP（供应商号，项目号，零件号，数量）查询至少供应了3个项目（包含3项）的供应商，输出其供应商号和供应零件数量的总和，并按供应商号降序排列。

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

其中，每个供应商可以为多个项目供应多种零件，每个项目可由多个供应商供应多种零件。SPP需要生成一个独立的关系模式，其联系类型为（54）给定关系模式SPP（供应商号，项目号，零件号，数量）查询至少供应了3个项目（包含3项）的供应商，输出其供应商号和供应零件数量的总和，并按供应商号降序排列。

某汽车加工工厂有两条装配线L1和L₂，每条装配线的工位数均为n（S_ij，i=1或2，j=1，2，...，n），两条装配线对应的工位完成同样的加工工作，但是所需要的时间可能不同（a_ij，i=1或2，j=1，2，...，n）。汽车底盘开始到进入两条装配线的时间（e₁，e₂）以及装配后到结束的时间（X₁X₂）也可能不相同。从一个工位加工后流到下一个工位需要迁移时间（t_ij，i=1或2，j=2，...n）。现在要以最快的时间完成一辆汽车的装配，求最优的装配路线。分析该问题，发现问题具有最优子结构。以L₁为例，除了第一个工位之外，经过第j个工位的最短时间包含了经过L₁的第j-1个工位的最短时间或者经过L₂的第j-1个工位的最短时间，如式（1）。装配后到结束的最短时间包含离开L₁的最短时间或者离开L₂的最短时间如式（2）。

由于在求解经过L₁和L₂的第j个工位的最短时间均包含了经过L₁的第j-1个工位的最短时间或者经过L₂的第j-1个工位的最短时间，该问题具有重复子问题的性质，故采用迭代方法求解。

某汽车加工工厂有两条装配线L1和L₂，每条装配线的工位数均为n（S_ij，i=1或2，j=1，2，...，n），两条装配线对应的工位完成同样的加工工作，但是所需要的时间可能不同（a_ij，i=1或2，j=1，2，...，n）。汽车底盘开始到进入两条装配线的时间（e₁，e₂）以及装配后到结束的时间（X₁X₂）也可能不相同。从一个工位加工后流到下一个工位需要迁移时间（t_ij，i=1或2，j=2，...n）。现在要以最快的时间完成一辆汽车的装配，求最优的装配路线。分析该问题，发现问题具有最优子结构。以L₁为例，除了第一个工位之外，经过第j个工位的最短时间包含了经过L₁的第j-1个工位的最短时间或者经过L₂的第j-1个工位的最短时间，如式（1）。装配后到结束的最短时间包含离开L₁的最短时间或者离开L₂的最短时间如式（2）。

由于在求解经过L₁和L₂的第j个工位的最短时间均包含了经过L₁的第j-1个工位的最短时间或者经过L₂的第j-1个工位的最短时间，该问题具有重复子问题的性质，故采用迭代方法求解。

某汽车加工工厂有两条装配线L1和L₂，每条装配线的工位数均为n（S_ij，i=1或2，j=1，2，...，n），两条装配线对应的工位完成同样的加工工作，但是所需要的时间可能不同（a_ij，i=1或2，j=1，2，...，n）。汽车底盘开始到进入两条装配线的时间（e₁，e₂）以及装配后到结束的时间（X₁X₂）也可能不相同。从一个工位加工后流到下一个工位需要迁移时间（t_ij，i=1或2，j=2，...n）。现在要以最快的时间完成一辆汽车的装配，求最优的装配路线。分析该问题，发现问题具有最优子结构。以L₁为例，除了第一个工位之外，经过第j个工位的最短时间包含了经过L₁的第j-1个工位的最短时间或者经过L₂的第j-1个工位的最短时间，如式（1）。装配后到结束的最短时间包含离开L₁的最短时间或者离开L₂的最短时间如式（2）。

由于在求解经过L₁和L₂的第j个工位的最短时间均包含了经过L₁的第j-1个工位的最短时间或者经过L₂的第j-1个工位的最短时间，该问题具有重复子问题的性质，故采用迭代方法求解。

某汽车加工工厂有两条装配线L1和L₂，每条装配线的工位数均为n（S_ij，i=1或2，j=1，2，...，n），两条装配线对应的工位完成同样的加工工作，但是所需要的时间可能不同（a_ij，i=1或2，j=1，2，...，n）。汽车底盘开始到进入两条装配线的时间（e₁，e₂）以及装配后到结束的时间（X₁X₂）也可能不相同。从一个工位加工后流到下一个工位需要迁移时间（t_ij，i=1或2，j=2，...n）。现在要以最快的时间完成一辆汽车的装配，求最优的装配路线。分析该问题，发现问题具有最优子结构。以L₁为例，除了第一个工位之外，经过第j个工位的最短时间包含了经过L₁的第j-1个工位的最短时间或者经过L₂的第j-1个工位的最短时间，如式（1）。装配后到结束的最短时间包含离开L₁的最短时间或者离开L₂的最短时间如式（2）。

由于在求解经过L₁和L₂的第j个工位的最短时间均包含了经过L₁的第j-1个工位的最短时间或者经过L₂的第j-1个工位的最短时间，该问题具有重复子问题的性质，故采用迭代方法求解。

完形填空：下面短文有5处空白，请根据短文内容为每处空白确定1个最佳选项。
The beauty of software is in its function， in its internal structure， and in the way in which 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 software designer， an internal structure that is partitioned in a simple and intuitive manner， and that minimizes internal coupling is beautiful.To developers and managers ， a motivated team of developers making significant progress every week， and producing defect-free code， is beautiful.There is beauty on all these levels.
our world needs software--lots of software. Fifty years ago software was something that ran in a few big and expensive machines. Thirty years ago it was something that ran in most companies and industrial settings. Now there is software running in our cell phones， watches， appliances， automobiles，toys， and tools. And need for new and better software never（72）.As our civilization grows and expands， as developing nations build their infrastructures， as developed nations strive to achieve ever greater efficiencies， the need for more and more Software（73）to increase. It would be a great shame if， in all that software， there was no beauty. 
We know that software can be ugly. We know that it can be hard to use， unreliable ， and carelessly structured. We know that there are software systems whose tangled and careless internal structures make them expensive and difficult to change. We know that there are software 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， software developers tend to create more ugly systems than beautifulones. 
There is a secret that the best software developers know. Beauty is cheaper than ugliness. Beauty is faster than ugliness. A beautiful software system can be built and maintained in less
time， and for less money ，than an ugly one. Novice software developers don’t. understand this. 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 e 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 build and maintain， and are delivered soonest.

完形填空：下面短文有5处空白，请根据短文内容为每处空白确定1个最佳选项。
The beauty of software is in its function， in its internal structure， and in the way in which 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 software designer， an internal structure that is partitioned in a simple and intuitive manner， and that minimizes internal coupling is beautiful.To developers and managers ， a motivated team of developers making significant progress every week， and producing defect-free code， is beautiful.There is beauty on all these levels.
our world needs software--lots of software. Fifty years ago software was something that ran in a few big and expensive machines. Thirty years ago it was something that ran in most companies and industrial settings. Now there is software running in our cell phones， watches， appliances， automobiles，toys， and tools. And need for new and better software never（72）.As our civilization grows and expands， as developing nations build their infrastructures， as developed nations strive to achieve ever greater efficiencies， the need for more and more Software（73）to increase. It would be a great shame if， in all that software， there was no beauty.
We know that software can be ugly. We know that it can be hard to use， unreliable ， and carelessly structured. We know that there are software systems whose tangled and careless internal structures make them expensive and difficult to change. We know that there are software 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， software developers tend to create more ugly systems than beautifulones.
There is a secret that the best software developers know. Beauty is cheaper than ugliness. Beauty is faster than ugliness. A beautiful software system can be built and maintained in less
time， and for less money ，than an ugly one. Novice software developers don’t. understand this. 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 e 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 build and maintain， and are delivered soonest.

完形填空：下面短文有5处空白，请根据短文内容为每处空白确定1个最佳选项。
The beauty of software is in its function， in its internal structure， and in the way in which 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 software designer， an internal structure that is partitioned in a simple and intuitive manner， and that minimizes internal coupling is beautiful.To developers and managers ， a motivated team of developers making significant progress every week， and producing defect-free code， is beautiful.There is beauty on all these levels.
our world needs software--lots of software. Fifty years ago software was something that ran in a few big and expensive machines. Thirty years ago it was something that ran in most companies and industrial settings. Now there is software running in our cell phones， watches， appliances， automobiles，toys， and tools. And need for new and better software never（72）.As our civilization grows and expands， as developing nations build their infrastructures， as developed nations strive to achieve ever greater efficiencies， the need for more and more Software（73）to increase. It would be a great shame if， in all that software， there was no beauty.
We know that software can be ugly. We know that it can be hard to use， unreliable ， and carelessly structured. We know that there are software systems whose tangled and careless internal structures make them expensive and difficult to change. We know that there are software 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， software developers tend to create more ugly systems than beautifulones.
There is a secret that the best software developers know. Beauty is cheaper than ugliness. Beauty is faster than ugliness. A beautiful software system can be built and maintained in less
time， and for less money ，than an ugly one. Novice software developers don’t. understand this. 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 e 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 build and maintain， and are delivered soonest.

完形填空：下面短文有5处空白，请根据短文内容为每处空白确定1个最佳选项。
The beauty of software is in its function， in its internal structure， and in the way in which 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 software designer， an internal structure that is partitioned in a simple and intuitive manner， and that minimizes internal coupling is beautiful.To developers and managers ， a motivated team of developers making significant progress every week， and producing defect-free code， is beautiful.There is beauty on all these levels.
our world needs software--lots of software. Fifty years ago software was something that ran in a few big and expensive machines. Thirty years ago it was something that ran in most companies and industrial settings. Now there is software running in our cell phones， watches， appliances， automobiles，toys， and tools. And need for new and better software never（72）.As our civilization grows and expands， as developing nations build their infrastructures， as developed nations strive to achieve ever greater efficiencies， the need for more and more Software（73）to increase. It would be a great shame if， in all that software， there was no beauty.
We know that software can be ugly. We know that it can be hard to use， unreliable ， and carelessly structured. We know that there are software systems whose tangled and careless internal structures make them expensive and difficult to change. We know that there are software 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， software developers tend to create more ugly systems than beautifulones.
There is a secret that the best software developers know. Beauty is cheaper than ugliness. Beauty is faster than ugliness. A beautiful software system can be built and maintained in less
time， and for less money ，than an ugly one. Novice software developers don’t. understand this. 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 e 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 build and maintain， and are delivered soonest.

完形填空：下面短文有5处空白，请根据短文内容为每处空白确定1个最佳选项。
The beauty of software is in its function， in its internal structure， and in the way in which 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 software designer， an internal structure that is partitioned in a simple and intuitive manner， and that minimizes internal coupling is beautiful.To developers and managers ， a motivated team of developers making significant progress every week， and producing defect-free code， is beautiful.There is beauty on all these levels.
our world needs software--lots of software. Fifty years ago software was something that ran in a few big and expensive machines. Thirty years ago it was something that ran in most companies and industrial settings. Now there is software running in our cell phones， watches， appliances， automobiles，toys， and tools. And need for new and better software never（72）.As our civilization grows and expands， as developing nations build their infrastructures， as developed nations strive to achieve ever greater efficiencies， the need for more and more Software（73）to increase. It would be a great shame if， in all that software， there was no beauty.
We know that software can be ugly. We know that it can be hard to use， unreliable ， and carelessly structured. We know that there are software systems whose tangled and careless internal structures make them expensive and difficult to change. We know that there are software 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， software developers tend to create more ugly systems than beautifulones.
There is a secret that the best software developers know. Beauty is cheaper than ugliness. Beauty is faster than ugliness. A beautiful software system can be built and maintained in less
time， and for less money ，than an ugly one. Novice software developers don’t. understand this. 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 e 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 build and maintain， and are delivered soonest.