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
131. Application prgram interface is
- It supports system modeling during the analysis and design stages of the software process
- Organization responsible for approving U.S. standards
- Stimuli that occurs irregularly
- Formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services.
132. Method of defining a collection of hardware and software components and their interfaces to establish the framework for the development of a computer system
- As low as reasonably practical (ALARP) risk
- Architectural design
- Attack
- None of these
133. Probabiity of an accident arising because of hazard is minimum subject of other costs
- As low as reasonably practical (ALARP) risk
- Architectural design
- Attack
- None of these
134. Fault tolerance system are
- These system runs on a single processor or an integrated group of processors
- A system where each sub-system can respond to generated events where the events might be generated from other sub-systems of from environment of the system
- A system continues in operation after some system faults have manifested themselves.
- A system whose operation is incorrect, if results are not produced according to the timing specifications.
135. The misuse of system vulnerablity is
- As low as reasonably practical (ALARP) risk
- Architectural desig
- Attack
- None of these
136. Attribute-based identification is
- Here each component has a unique name and an associated set of attribute, which differs for each version of componnt
- Extent to which a software system records information concerning transactions performed against the system
- Extent to which a system or component is operational and accessible when required for use
- They are used to describe the over all behavior of the system
137. Audiable is
- Here each component has a unique name and an associated set of attribute, which differs for each version of component
- Extent to which a software system records information concerning transactions performed against the system
- Extent to which a system or component is operational and accessible when required for use
- They are used to describe the over all behavior of the system
138. Availability is
- Here each component has a unique name and an associated set of attribute, which differs for each version of component
- Extent to which a software system records information concerning transactions performed against the system.
- Extent to which a sytem or component is operational and accessible when required for use
- They are used to describe the over all behavior of the system
139. Behavioral models is
- Here each component has a unique name and an associated set of attribute, which differs for each version of componnt
- Extent to which a software system records information concerning tranactions perfrmed against the system.
- Extent to which a system or component is operational and accessibe when required for use
- Use to describe the over alll behavior of the system
140. In Bottom-up integration
- The low-level components of a system are integrated and tested before the higher-level components have been developed
- The testing process starts with modules at lower levels in the hierachy and works up the hierachy of modules until the final module is tested.
- An event driven control system, where an event is broad casted to each sub-system and any sub-system that can handle that event responds to it.
- Control starts of the top of a sub routine hierachy and through sub routine calls passes to lower levels.