Software Engineering MCQ Chapter 11

Posted by

Software Engineering MCQ, with 100% FREE PDF Download.

201. Manufacturing phase is
(A) Period in the software life cycle in which a software product is created from design documentation and debugged.
(B) Period in the software life cycle in which a software product is integrated in its operational environment, and tested in this environment to ensure it performs as required.
(C) Period in the software life cycle during which the basic version of a software product is adapted to a specified set of operational environments and is distributed to a customer base.
(D) None of these

202. Human engineering is
(A) It is concerned with the design, evaluation, and implementation of interactive computing systems for human use and with the study of major phenomena surrounding them.
(B) Extent to which a software product fulfills its purpose without wasting user’s time/ energy/degrading their morale.
(C) Human behavior that results in the introduction of faults into a system.
(D) None of these

203. Hazard severity
(A) Hazard cannot arise due system design.
(B) The probability of the event occurring which create a hazard.
(C) An assessment of the worst possible damage, which could result from a particular hazard.
(D) A condition with the potential for causing or contributing to an accident.

204. Latency is
(A) Ability of two or more systems, to exchange information and to use the information that has been exchanged.
(B) Time taken to respond to an event.
(C) Either the hazard not arises, if arise; it will not result in an accident.
(D) None of these

205. Fault tree analysis is
(A) It is the process of modifying the state space of the system so that the effects of the fault are minimized and system can continue in operation in some degraded state.
(B) Capacity of a system or component to continue normal operation despite the presence of hardware or software faults.
(C) It is the widely used hazard technique
(D) Incorrect step, process, or data definition in a computer program

206. Lehman’s Fourth Law (Lehman and Belady 1985) is
(A) Organizational stability: Over a program’s lifetime, its rate of development is approximately constant and independent of the resources devoted to system development.
(B) Increase complexity: As an evolving program change, its strictures tend to become more complex. Extra resources must be devoted to preserving and simplifying the structure.
(C) Large program evolution: Program evolution is a self-regulating process.
(D) None of these

207. Human error is
(A) It is concerned with the design, evaluation, and implementation of interactive computing systems for human use and with the study of major phenomena surrounding them.
(B) Extent to which a software product fulfills its purpose without wasting user’s time/ energy/degrading their morale.
(C) Human behavior that results in the introduction of faults into a system.
(D) None of these

208. Fault-tolerant architectures is
(A) The software and hardware system architectures that provide explicit support for tolerance, which includes software redundancy and faulttolerance controller that detects problems and supports fault recovery*
(B) It is an initial step for requirements engineering process, includes the outline description of system, its use in an organization and recommending the system feasibility.
(C) Trustworthiness with which a system or component can be modified for use in applications or environments other than those for which it was specifically designed.
(D) None of these

209. Match the following: A- Formal mathematical transformation: B- Formal process model: C-Formal Specifications: D-Formal System development:
1- Here the formal mathematical representation of the system takes place.
2- It is a starting point for process analysis. It is abstract and only defines the principal process activities and deliverables.
3-Specifications expressed in a language whose vocabulary, syntax and semantics are formally defined.
4-It is more common to waterfall model, but here the development process is based on formal mathematical transformation of a system specification to an exactable program.
(A) A-1,B-2,C-3,D-4
(B) A-4,B-2,C-3,D-1
(C) A-2,B-1,C-3,D-4
(D) A-1,B-3,C-2,D-4

210. Lehman’s First Law (Lehman and Belady 1985) is
(A) Continuing change: A program used in real-world environment must change necessarily or become progressively less useful in that environment.
(B) Increase complexity: As an evolving program change, its strictures tend to become more complex. Extra resources must be devoted to preserving and simplifying the structure.
(C) Large program evolution: Program evolution is a self-regulating process.
(D) None of these

211. Graphics
(A) Extent to which a system or component performs a broad range of functions.
(B) The objective of an organization to achieve.
(C) Methods and techniques for converting data to or from graphic display via computers.
(D) None of these

212. Intolerable risk is
(A) Ability of two or more systems, to exchange information and to use the information that has been exchanged.
(B) Time taken to respond to an event.
(C) Either the hazard not arises, if arise; it will not result in an accident.
(D) None of these

213. Hazard
(A) Hazard cannot arise due system design.
(B) The probability of the event occurring which create a hazard.
(C) An assessment of the worst possible damage, which could result from a particular hazard.
(D) A condition with the potential for causing or contributing to an accident.

214. Human Computer Interaction is
(A) It is concerned with the design, evaluation, and implementation of interactive computing systems for human use and with the study of major phenomena surrounding them.
(B) Extent to which a software product fulfills its purpose without wasting user’s time/ energy/degrading their morale.
(C) Human behavior that results in the introduction of faults into a system.
(D) None of these

215. Match the following : A- Maintenance control: B- Maintenance prediction: C- Maintenance process:
1-Cost of planning and scheduling hardware preventive maintenance, and software maintenance and upgrades, managing the hardware and software baselines, and providing response for hardware corrective maintenance.
2- Predicting the number of change requires a system understanding and the relationship between the system and external environment. 3- It is triggered by a set of change requests from system users, management or customers.
(A) A-1, B-3,C-2
(B) A-1,B-2,C-3
(C) A-2,B-3,C-1
(D) A-3,B-2,C-1

216. Installation and checkout phase
(A) Period in the software life cycle in which a software product is created from design documentation and debugged.
(B) Period in the software life cycle in which a software product is integrated in its operational environment, and tested in this environment to ensure it performs as required.
(C) Period in the software life cycle during which the basic version of a software product is adapted to a specified set of operational environments and is distributed to a customer base.
(D) None of these

217. A- Interface requirement: B-Interface testing: C-Interfaces design:
1- Requirements derived from the interfaces of existing system and developing system.
2- It detects faults that have been arise in the system because of interface errors or invalid assumptions about interface.
3-Activity concerned with the interfaces of the software system contained in the software requirements and software interface requirements documentation.
(A) A-1,B-2,C-3
(B) A-2,B-1,C-3
(C) A-2,B-3,C-1
(D) A-3,B-2,C-1

218. Software implementation is
(A) It is concern with modification of existing system to meet changing requirements.
(B) It is a process of converting system specifications into an executable system.
(C) It analyzes and checks system representation such as the requirements document, design diagrams and program source code.
(D) None of these

219. An object-oriented model of system architecture structures the system into a set of loosely coupled objects with well-defined interfaces.
(A) Object design models
(B) Object interface design
(C) Object oriented models
(D) None of these

220. Interoperability is
(A) Ability of two or more systems, to exchange information and to use the information that has been exchanged.
(B) Time taken to respond to an event.
(C) Either the hazard not arises, if arise; it will not result in an accident.
(D) None of these


201. (C) 202. (B) 203. (C) 204. (B) 205. (C)
206. (A) 207. (C) 208. (A) 209. (A) 210. (A)
211. (C) 212. (C) 213. (D) 214. (A) 215. (B)
216. (B) 217. () 218. (B) 219. (C) 220. (A)