Software Engineering — Practice MCQs (25)

Q1. SDLC stands for: A) Software Design Logic Code
B) Software Development Life Cycle
C) System Data Link Control
D) Structured Debug Line Check

Q2. Waterfall model is best characterized as: A) Highly iterative with daily changing scope always
B) Sequential phase-by-phase
C) No documentation
D) Only for AI

Q3. Agile emphasizes: A) Heavy upfront contracts only
B) Iterative delivery and responding to change
C) Avoiding customer contact
D) No testing

Q4. Scrum uses: A) Sprints
B) Only waterfall gates
C) Only punch cards
D) No standup meetings ever

Q5. SRS document primarily contains: A) Machine code
B) Software requirements specification
C) Only UI screenshots without needs
D) Compiler errors

Q6. High cohesion means: A) Module elements closely related to one purpose
B) Modules depend tightly on many others
C) Spaghetti code
D) No functions

Q7. Low coupling means: A) Modules highly interdependent
B) Modules relatively independent
C) One giant module only
D) No interfaces

Q8. Unit testing tests: A) Whole system with users
B) Individual components/functions
C) Only network cables
D) Only documentation

Q9. Black-box testing focuses on: A) Internal code structure
B) Inputs/outputs without seeing code
C) Only compiler design
D) Gate-level circuits

Q10. White-box testing uses: A) Only GUI clicks without logic knowledge
B) Internal structure/paths of code
C) Only marketing surveys
D) Only UML logos

Q11. Integration testing verifies: A) Modules work together
B) Only a single line of code
C) Only hardware voltage
D) Only fonts

Q12. Acceptance testing is typically done: A) Only by compiler
B) With respect to user/customer requirements
C) Before coding starts always
D) Only on dead code

Q13. UML Use Case diagram shows: A) Actors and use cases
B) Only database indexes
C) Only CPU registers
D) Only IP packets

Q14. Class diagram shows: A) Runtime packet capture
B) Classes, attributes, relationships
C) Only Gantt charts
D) Only ER optional

Q15. Sequence diagram emphasizes: A) Time-ordered message interactions
B) Only file permissions
C) Only color models
D) Only sorting

Q16. Corrective maintenance fixes: A) New features only
B) Defects/bugs after delivery
C) Only hardware fans
D) Only documentation fonts

Q17. Adaptive maintenance is for: A) Environment/platform changes
B) Only adding games
C) Only deleting tests
D) Only encryption keys

Q18. CASE tools help in: A) Cooking
B) Computer-aided software engineering tasks
C) Only painting
D) Only networking cables

Q19. LOC metric counts: A) Lines of code
B) Layers of cake
C) Lost optical cables
D) Logical output channels only always

Q20. CMMI is related to: A) Cooking maturity
B) Process maturity/capability models for organizations
C) Only CSS
D) Only Bluetooth

Q21. Prototype model is useful when: A) Requirements are unclear and early feedback needed
B) Requirements never change and users unavailable forever
C) No UI exists as concept
D) Only batch payroll in 1960s

Q22. Spiral model explicitly includes: A) Risk analysis iterations
B) Only one pass forever
C) No documentation ever
D) Only HTML

Q23. Verification asks: A) Are we building the product right?
B) Are we building the right product?
C) Only about salary
D) Only about routers

Q24. Validation asks: A) Are we building the product right?
B) Are we building the right product?
C) Only about syntax
D) Only about RAM

Q25. Regression testing is done: A) After changes to ensure old features still work
B) Only once before any coding
C) Only on hardware
D) Never after bug fixes

---

Answer Key

1. B — Software Development Life Cycle.
2. B — Linear sequential.
3. B — Iterative + change.
4. A — Time-boxed sprints.
5. B — Requirements spec.
6. A — Single-minded module.
7. B — Independence.
8. B — Smallest testable units.
9. B — Spec/behaviour focus.
10. B — Code paths.
11. A — Combined modules.
12. B — User acceptance.
13. A — Actors + use cases.
14. B — Static structure.
15. A — Messages over time.
16. B — Bug fixing.
17. A — Adapt to environment.
18. B — CASE.
19. A — Lines of Code.
20. B — Capability Maturity Model Integration.
21. A — Clarify via prototype.
22. A — Risk-driven cycles.
23. A — Verification.
24. B — Validation.
25. A — Retest after change.