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 →
When entire composite data structures (e.g., a complete record or object) are passed between modules, but the receiving module uses only a subset of fields, it is called:
AData Coupling
BControl Coupling
CStamp Coupling (Data-Structure Coupling)
DCommon Coupling
Transferring risk impact to a third party (e.g., purchasing insurance or outsourcing a risky component) is called:
ARisk Avoidance
BRisk Mitigation
CRisk Transfer
DRisk Retention
An architectural style where components communicate asynchronously across an enterprise by generating and consuming messages is called:
ALayered (N-Tier) Architecture
BRepository Architecture
CMicrokernel Architecture
DEvent-Driven Architecture
Completely eliminating a risk exposure by altering project scope or technical approach is:
ARisk Mitigation
BRisk Acceptance
CRisk Transfer
DRisk Avoidance
In Software Testing, the process of executing a program with the deliberate intent of finding errors is the classic definition by:
AGlenford Myers
BBarry Boehm
CFred Brooks
DEdsger Dijkstra
The Critical Path Method (CPM) in software project scheduling determines:
AThe sequence of dependent tasks that defines the minimum total time required to complete the project
BThe path with the highest financial cost
CThe tasks with maximum buffer slack time
DThe sequence of unassigned developer tasks
What is the difference between Software Verification and Software Validation?
AVerification involves dynamic code execution; Validation involves static code inspection
BVerification ensures building the product right; Validation ensures building the right product
CVerification is done by end-users; Validation is done by developers
DVerification checks non-functional performance; Validation checks functional specifications
In project management network diagrams, total float (or slack time) represents:
AThe time required to compile the software codebase
BThe amount of time a task can be delayed without delaying the project completion date
CThe total overtime worked by software engineers
DThe total buffer reserved for bug fixing
Static software verification techniques performed without executing program code include:
AUnit Testing and Integration Testing
BStress Testing and Load Testing
CCode Inspections, Walkthroughs, and Static Analysis
DAlpha and Beta Acceptance Testing
Tasks located on the Critical Path in a PERT/CPM software project network diagram always have a Total Float of:
AMaximum Float
BPositive Float equal to 10 days
CZero Float
DNegative Float