On This Page

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

Q1 | An object-oriented model of system architecture structures the system into a set of loosely coupled objects with well-defined interfaces.
  • Object design models
  • Object interface design
  • Object oriented models
  • None of these
Q2 | Interoperability 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
Q3 | Parkinson’s Law is
  • The cost is determined by available resources rather than by objective assessment.
  • A program used in real-world environment must change necessarily or become progressively less useful in that environment.
  • As an evolving program change, its strictures tend to become more complex.
  • Program evolution is a self-regulating process.
Q4 | Retirement phase is
  • Reason for a computer program to resume execution after a failure, using status and results recorded at a checkpoint.
  • Period of time in the software life cycle during which support for a software product is terminated.
  • The fault detection mechanism is initiated after the system state has been changed to check if a fault has occurred.
  • None of these
Q5 | Retrospective Fault detection is
  • Reason for a computer program to resume execution after a failure, using status and results recorded at a checkpoint.
  • Period of time in the software life cycle during which support for a software product is terminated.
  • The fault detection mechanism is initiated after the system state has been changed to check if a fault has occurred*
  • None of these
Q6 | Risk planning process
  • Extent to which a software module can be used in more than one computing program
  • It involves regular monitoring of the risks identified and of new risks that develops.
  • It considers each of the key risks that are identified and identifies strategies to manage the risk.
  • None of these
Q7 | Software engineering method is
  • Associated with production of software as per specification
  • Structured approach to software development, whose aim is to facilitate the production of high-quality software in a cost-effective way.
  • An engineering discipline, concern with software development.
  • None of these
Q8 | Restart is
  • Reason for a computer program to resume execution after a failure, using status and results recorded at a checkpoint.
  • Period of time in the software life cycle during which support for a software product is terminated.
  • The fault detection mechanism is initiated after the system state has been changed to check if a fault has occurred.
  • None of these
Q9 | Risk Management is
  • Here each identified risk is analyzed and prioritized
  • It begins after all hazards are identified. For each hazard, the outcome of the risk assessment process is a statement of acceptability.
  • The anticipate risks which night affect the project schedule or the quality of the software being developed and to take action to avoid these risks.
  • None of these
Q10 | ROCOF (Rate of failure occurrence) is
  • The probability that the system will cause an accident
  • Extent to which a system or component can function correctly in the presence of invalid inputs or stressful environment conditions.
  • The frequency of occurrence with which unexpected behavior is likely to occur
  • None of these
Q11 | Software system is
  • Associated with functionality of software and constraints of operations defined.
  • It consists of computer programs, configuration files that are used to set up these programs system documentation for describing to structure of the system and used documentation that describes use of the system.
  • It involves executing an implementation of the software with test data and examines the outputs of the software and its operational behavior to check that it is performing as required
  • None of these
Q12 | Scalability is
  • Avoiding catastrophic moment
  • Ease with which a system or component are modified to fit the problem area.
  • It is a bounded area of responsibility.
  • None of these
Q13 | Risk analysis process is
  • Here each identified risk is analyzed and prioritized
  • It begins after all hazards are identified. For each hazard, the outcome of the risk assessment process is a statement of acceptability.
  • The anticipate risks which night affect the project schedule or the quality of the software being developed and to take action to avoid these risks.
  • None of these
Q14 | Reusability is
  • Extent to which a software module can be used in more than one computing program.
  • It involves regular monitoring of the risks identified and of new risks that develops.
  • It considers each of the key risks that are identified and also identifies strategies to manage the risk.
  • None of these
Q15 | Safety argument is
  • Associated with the role of people involved in software process and the activities for which they are responsible.
  • The most effective technique for demonstrating the safety of a system is proof by contradiction.
  • It is concerned with establishing a confidence level in the system that might vary from low to high
  • None of these
Q16 | Risk assessment is
  • Here each identified risk is analyzed and prioritized
  • It begins after all hazards are identified. For each hazard, the outcome of the risk assessment process is a statement of acceptability.
  • The anticipate risks which night affect the project schedule or the quality of the software being developed and to take action to avoid these risks.
  • None of these
Q17 | Risk is
  • The probability that the system will cause an accident
  • Extent to which a system or component can function correctly in the presence of invalid inputs or stressful environment conditions.
  • The frequency of occurrence with which unexpected behavior is likely to occur.
  • None of these
Q18 | Safety is
  • Avoiding catastrophic moment
  • Ease with which a system or component are modified to fit the problem area.
  • It is a bounded area of responsibility.
  • None of these
Q19 | Role is
  • Avoiding catastrophic moment
  • Ease with which a system or component are modified to fit the problem area.
  • It is a bounded area of responsibility
  • None of these
Q20 | Robustness is
  • The probability that the system will cause an accident
  • Extent to which a system or component can function correctly in the presence of invalid inputs or stressful environment conditions
  • The frequency of occurrence with which unexpected behavior is likely to occur.
  • None of these
Q21 | Risk monitoring process
  • Extent to which a software module can be used in more than one computing program
  • It involves regular monitoring of the risks identified and of new risks that develops.
  • It considers each of the key risks that are identified and identifies strategies to manage the risk.
  • None of these
Q22 | These objects can be realized as parallel process with method corresponding to defined object operations.
  • Self-descriptiveness
  • Servers
  • Simplicity
  • None of these
Q23 | Safety validation is
  • Associated with the role of people involved in software process and the activities for which they are responsible.
  • The most effective technique for demonstrating the safety of a system is proof by contradiction.
  • It is concerned with establishing a confidence level in the system that might vary from low to high
  • None of these
Q24 | Software process model
  • Time-period that begins when a software product is conceived and ends when the software is no longer available for use.
  • Adaptive maintenance, performed to make a computer program usable in a changed environment.
  • A simplified description of a software process that is presented from a particular perspective.
  • None of these
Q25 | Extent to which a system or component contains enough information to explain its objectives and properties is referred as
  • Self-descriptiveness
  • Servers
  • Simplicity
  • None of these