On This Page

This set of Software Engineering Multiple Choice Questions & Answers (MCQs) focuses on Software Engineering Set 18

Q1 | Hazard avoidance
  • Hazard cannot arise due system design.
  • The probability of the event occurring which create a hazard.
  • An assessment of the worst possible damage, which could result from a particular hazard.
  • A condition with the potential for causing or contributing to an accident.
Q2 | Evolutionary prototyping is
  • It describes the basic entities in the design and relation between them.
  • Observational techniques used to understand social and organizational requirements.
  • It is based on the idea of developing an initial implementation, exposing it uses on requirement and refining it through many versions until an adequate system has been developed.
  • Based on an idea of developing an initial implementation, exposing this to uses comment and retiring it until and adequate system has been developed.
Q3 | Match the following :A- Managed device :B-Managed object:C- Managed processes:1- Type of node residing on a network, such as a computer, printer or routers that contain a management agent.2- Characteristic of a managed device that can be monitored, modified or controlled.3- It is a defined process model. Procedures used are defined and scheduling and relationship between them is defined.
  • A-1, B-3,C-2
  • A-1,B-2,C-3
  • A-2,B-3,C-1
  • A-3,B-2,C-1
Q4 | Goal is
  • Extent to which a system or component performs a broad range of functions.
  • The objective of an organization to achieve.
  • Methods and techniques for converting data to or from graphic display via computers.
  • None of these
Q5 | Implementation phase is
  • Period in the software life cycle in which a software product is created from design documentation and debugged.*
  • 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.
  • 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.
  • None of these
Q6 | Evolvability is
  • Trustworthiness with which a system or component can be modified to take advantage of new software or hardware technologies.
  • An error of some kind or an unexpected event occurs during the execution of a program
  • Here the objective of the process is to work with uses to explore their requirement and deliver a final system.
  • Possible loss or harm in computing system.
Q7 | Match the following A- Functionalrequirements: B- Functional scope : C- Function-point count: D- Function-related measures: 1- It describe the functionality or services that system is expected to provide. 2- Range to which a system component is capable of being applied. 3- These are language independent productive measure.. 4- It is related to the overall functionality of the delivered software.
  • A-4,B-2,C-3,D-1
  • A-2,B-1,C-3,D-4
  • A-1,B-3,C-2,D-4
  • A-1,B-2,C-3,D-4
Q8 | Lehman’s Second Law (Lehman and Belady 1985) is
  • Continuing change: A program used in real-world environment must change necessarily or become progressively less useful in that environment.
  • 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.
  • Large program evolution: Program evolution is a self-regulating process.
  • None of these
Q9 | Hazard probability
  • Hazard cannot arise due system design.
  • The probability of the event occurring which create a hazard.
  • An assessment of the worst possible damage, which could result from a particular hazard.
  • A condition with the potential for causing or contributing to an accident.
Q10 | Flexibility
  • The software and hardware system architectures that provide explicit support for tolerance, which includes software redundancy and fault- tolerance controller that detects problems and supports fault recovery
  • 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.
  • 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.
  • None of these
Q11 | Extendibility is
  • Trustworthiness with which a system or component can be modified to increase its storage or functional capacity
  • Pertaining to a system/component that automatically places itself in a safe operating mode in the event of a failure.
  • Pertaining to a system or component that continues to provide partial operational capability in the event of certain failures.
  • None of these
Q12 | Generality is
  • It is a measure of number of function that calls some other function.
  • It is measure of number of functions, which are called by a function.
  • In it server is only responsible for data management.
  • None of these
Q13 | Manufacturing phase is
  • Period in the software life cycle in which a software product is created from design documentation and debugged.
  • 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.
  • 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.
  • None of these Human engineering is
Q14 | Lehman’s Fourth Law (Lehman and Belady 1985) is
  • Organizational stability: Over a program’s lifetime, its rate of development is approximately constant and independent of the resources devoted to system development.
  • 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.
  • Large program evolution: Program evolution is a self-regulating process.
  • None of these
Q15 | Human error is
  • 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.
  • Extent to which a software product fulfills its purpose without wasting user’s time/ energy/degrading their morale.
  • Human behavior that results in the introduction of faults into a system.
  • None of these
Q16 | Fault-tolerant architectures is
  • The software and hardware system architectures that provide explicit support for tolerance, which includes software redundancy and fault- tolerance controller that detects problems and supports fault recovery*
  • 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.
  • 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.
  • None of these
Q17 | Match the following:A- Formal mathematical transformation:B- Formal process model:C-Formal Specifications:D-Formal System development:1- Here the formal mathema- tical 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-1,B-2,C-3,D-4
  • A-4,B-2,C-3,D-1
  • A-2,B-1,C-3,D-4
  • A-1,B-3,C-2,D-4
Q18 | Lehman’s First Law (Lehman and Belady 1985) is
  • Continuing change: A program used in real-world environment must change necessarily or become progressively less useful in that environment.
  • 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.
  • Large program evolution: Program evolution is a self-regulating process.
  • None of these
Q19 | Graphics
  • Extent to which a system or component performs a broad range of functions.
  • The objective of an organization to achieve.
  • Methods and techniques for converting data to or from graphic display via computers.
  • None of these
Q20 | Intolerable risk is
  • Ability of two or more systems, to exchange information and to use the information that has been exchanged.
  • Time taken to respond to an event.
  • Either the hazard not arises, if arise; it will not result in an accident.
  • None of these
Q21 | Hazard
  • Hazard cannot arise due system design.
  • The probability of the event occurring which create a hazard.
  • An assessment of the worst possible damage, which could result from a particular hazard.
  • A condition with the potential for causing or contributing to an accident.
Q22 | Human Computer Interaction is
  • 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.
  • Extent to which a software product fulfills its purpose without wasting user’s time/ energy/degrading their morale.
  • Human behavior that results in the introduction of faults into a system.
  • None of these
Q23 | 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-1, B-3,C-2
  • A-1,B-2,C-3
  • A-2,B-3,C-1
  • A-3,B-2,C-1
Q24 | Installation and checkout phase
  • Period in the software life cycle in which a software product is created from design documentation and debugged.
  • 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.
  • 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.
  • None of these
Q25 | Software implementation is
  • It is concern with modification of existing system to meet changing requirements.
  • It is a process of converting system specifications into an executable system.
  • It analyzes and checks system representation such as the requirements document, design diagrams and program source code.
  • None of these