Dear Readers, Welcome to Software Engineering Objective Questions and Answers have been designed specially to get you acquainted with the nature of questions you may encounter during your Job interview for the subject of Software Engineering Multiple choice Questions. These Objective type Software Engineering are very important for campus placement test and job interviews. As per my experience good interviewers hardly plan to ask any particular question during your Job interview and these model questions are asked in the online technical test and interview of many IT & Non IT Industry.
(A) requirement analysis.
(B) risk management.
(C) quality management.
(D) configuration management.
Ans: B
(A) Data coupling.
(B) control coupling.
(C) stamp coupling.
(D) content coupling.
Ans: D
(A) Software requirement specification.
(B) Software design.
(C) Testing.
(D) Both (A) and (B)
Ans: A
(A) unit testing. (B) beta testing.
(C) Stress testing. (D) mutation testing.
Ans: D
(A) Preventative maintenance.
(B) Adaptive maintenance.
(C) Corrective maintenance.
(D) Perfective maintenance.
Ans: D
(A) Bottom up testing
(B) Top-down testing
(C) Sandwich testing
(D) Big-Bang testing
Ans: D
(A) correct.
(B) unambiguous.
(C) consistent.
(D) verifiable.
Ans: B
(A) Mutation testing
(B) Stress testing
(C) Black box testing
(D) White box testing
Ans: A
(A) Sequential
(B) Communicational
(C) Procedural
(D) Logical
Ans: B
(A) Object Oriented Analysis.
(B) Object Oriented Design
(C) Object Oriented Analysis & Design
(D) None of the above
Ans: A
(A) White box testing
(B) Stress testing
(C) Integrated testing
(D) Black box testing
Ans: D
(A) Evolutionary Development Model
(B) Waterfall Model
(C) Prototyping
(D) Iterative Enhancement Model
Ans: A
(A) Software requirements definition
(B) Structured requirements definition
(C) Software requirements diagram
(D) Structured requirements diagram
Ans: B
(A) Common Cost Estimation Model.
(B) Constructive Cost Estimation Model.
(C) Complete Cost Estimation Model.
(D) Comprehensive Cost Estimation Model.
Ans: B
(A) Abstract data types are the same as classes
(B) Abstract data types do not allow inheritance
(C) Classes cannot inherit from the same base class
(D) Object have state and behavior
Ans: B
(A) No coupling
(B) Control coupling
(C) Common coupling
(D) Data coupling
Ans: D
(A) In the first loop
(B) in the first and second loop
(C) In every loop
(D) before using spiral model
Ans: C
(A) The waterfall model
(B) prototyping model
(C) the evolutionary model
(D) the spiral model
Ans: A
(A) cause-effect graph
(B) dependence matrix
(C) Structure chart
(D) SRS
Ans: B
(A) mandatory 1 cardinality
(B) mandatory many cardinality
(C) optional 0 or 1 cardinality
(D) optional zero-many cardinality
Ans: D
(A) increases.
(B) decreases.
(C) remains constant.
(D) cannot say anything.
Ans: A
(A) static testing of single module
(B) dynamic testing of single module
(C) static testing of single and multiple module
(D) dynamic testing of single and multiple module
Ans: D
(A) object.
(B) class.
(C) inheritance.
(D) aggregation.
Ans: C
(A) reliability
(B) efficiency
(C) portability
(D) all of the above
Ans: B
(A) verifiable
(B) traceable
(C) modifiable
(D) complete
Ans: A
(A) adaptive maintenance
(B) corrective maintenance
(C) perfective maintenance
(D) preventive maintenance
Ans: A
(A) 0
(B) 1
(C) 2
(D) None of above
Ans: A
(A) Acceptance testing
(B) Integration testing
(C) System Testing
(D) Unit testing
Ans: A
(A) Data
(B) Behaviour
(C) State
(D) Both Data and behaviour
Ans: D
(A) 10
(B) 14
(C) 20
(D) 12
Ans: B
(A) is_a relationship
(B) part_of relationship
(C) composed_of relationship
(D) none of above
Ans: C
(A) RE = P/L
(B) RE = P + L
(C) RE = P*L
(D) RE = 2* P *L
Ans: C
(A) 15
(B) 20
(C) 25
(D) 28
Ans: B
(A) Static view.
(B) Functional view.
(C) Dynamic view.
(D) All the above.
Ans: A
(A) CASE Tools
(B) CAME tools
(C) CAQE tools
(D) CARE tools
Ans: A
(A) Preventive Maintenance
(B) Adaptive Maintenance
(C) Corrective Maintenance
(D) Perfective Maintenance
Ans: A
(A) The waterfall model
(B) prototyping model
(C) the evolutionary model
(D) the spiral model
Ans: B
(A) Basic COCOMO model
(B) Intermediate COCOMO model
(C) Detailed COCOMO model
(D) All the three COCOMO models
Ans: A
(A) requirements gathering
(B) requirements analysis
(C) design
(D) coding
Ans: C
(A) bug
(B) error
(C) risk
(D) failure
Ans: C
(A) design errors
(B) analysis errors
(C) procedure errors
(D) interface errors
Ans: D
(A) flowcharts
(B) structure charts
(C) decision tables
(D) cause-effect graphs
Ans: A
(A) an error.
(B) a failure.
(C) a fault.
(D) a defect.
Ans: D
(A) black box testing
(B) white box testing
(C) data variable testing
(D) data flow testing
Ans: A
(A) Computer Aided Software Engineering
(B) Component Aided Software Engineering
(C) Constructive Aided Software Engineering
(D) Computer Analysis Software Engineering
Ans: A
(A) Set of instructions + operating procedures
(B) Programs + documentation + operating procedures
(C) Programs + hardware manuals
(D) Set of programs
Ans: B
(A) Quality management
(B) Risk management
(C) Performance management
(D) Efficiency management
Ans: B
(A) Coding
(B) Testing
(C) Maintenance
(D) Abstraction
Ans: D
(A) Requirements elicitation
(B) Requirements analysis
(C) Requirements design
(D) Requirements documentation
Ans: C
(A) Functional Application Specification Technique
(B) Fast Application Specification Technique
(C) Facilitated Application Specification Technique
(D) None of the above
Ans: C