Software Engineering MCQ Questions and Answers
The Software Engineering MCQ questions with answers section is designed for students preparing for technical interviews and placement tests. It covers the principles of software development life cycles (SDLC), agile models, testing, and project management. Practicing programming questions and answers in this domain helps you understand design methodologies, quality assurance, and software maintenance concepts. Top companies like TCS, Infosys, Wipro, and Cognizant frequently include such MCQs to assess your technical foundation. This guide includes solved questions with explanations to ensure conceptual clarity and practical understanding—ideal for both beginners and experienced candidates looking to refresh their technical knowledge.
Software Engineering MCQ
Showing 10 of
288 questions
211. Manugacturing phase is
- Period in the software life cyce in which a software product is created rom design documentation and debugged.
- Period in the software life cycle in which a software produt is integrated in its oprational environment, and tested in this environment to ensure it performs as required.
- Period in the softwarelife cycle during which the basis version of a software product is adapted to a specified set of operational environments and is distributed to a customer base.
- None of these
212. Human engineering 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 produt 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
213. Hazard severity
- 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 protential for causing or contributing to an accident.
214. Hazard severity
- 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 protential for causing or contributing to an accident.
215. Latency is
- Ability of two or more systems, to exchange information and to use the information that has been exxchanged
- Time taken to respond to an event.
- Either the hazard not arises, if arise; it will not result in an accident.
- None of these
216. Fault tree analysis is
- 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.
- Capacity of a system or component to continue normal operation despite the presence of hardware or software faults
- It is the widely used hazard technique
- Incorrect in a computer program defintion in a computer program
217. 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
218. 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
219. 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 initial step for requirements engineering process, includes the outline description of system, its use in anorganization and recommending the system feasibility.
- Trustorthiness 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
220. 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 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 format 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