Software Engineering
Software Engineering MCQs with Answers
Software engineering MCQs with answers and detailed explanations for NTS, GAT, university tests and IT job interviews. SDLC, testing and design covered. Take a scored quiz instead →
A strong whole-part ownership relationship where child objects CANNOT exist independently of their parent container (e.g., Building and Rooms) is:
AAggregation
BAssociation
CRealization
DComposition
In Requirements Engineering, the process of resolving conflicting requirements between different stakeholders is known as:
ARequirement Negotiation
BRequirement Elicitation
CRequirement Specification
DRequirement Validation
Which document serves as the formal contractual agreement between software developers and customers detailing system functionality?
ASoftware Architecture Document (SAD)
BSoftware Requirement Specification (SRS)
CTest Summary Report
DProject Charter
According to IEEE standards, an ideal Software Requirement Specification (SRS) document must be:
ABrief, Informal, Abstract, and Flexible
BCode-Centric, Technical, Complex, and Rigid
CUnambiguous, Complete, Verifiable, and Consistent
DRedundant, Variable, Dynamic, and Subjective
The phenomenon where software requirements continuously expand during development beyond original scope limits is termed:
AFeature Bloat
BRequirement Drift
CArchitecture Erosion
DScope Creep
In Software Maintenance, Lehman’s Laws of Software Evolution state that continuous change causes software structure to deteriorate unless work is done to maintain it. This is the law of:
AIncreasing Complexity
BContinuing Change
CSelf Regulation
DConservation of Familiarity
Technique used to assess the specific software components that will be affected by a proposed requirement change is:
ARoot Cause Analysis
BImpact Analysis
CCost-Benefit Analysis
DDefect Density Analysis
The software quality metric calculated as the total number of confirmed defects divided by the size of the software module (e.g., defects per KLOC) is:
ADefect Removal Efficiency
BFailure Rate
CDefect Density
DMean Time To Failure (MTTF)
In Integration Testing, combining all software modules simultaneously to test the entire system at once without incremental integration is called:
ATop-Down Integration
BBottom-Up Integration
CSandwich Integration
DBig-Bang Integration
In Function Point Analysis (FPA), software functionality is evaluated across five primary components: External Inputs, External Outputs, External Inquiries, Internal Logical Files, and:
ADatabase Table Constraints
BSystem Call Routines
CHardware Memory Allocation
DExternal Interface Files