Software Development Life Cycle Models MCQs 2026

39 questions with detailed answers · 18 from past papers · 4 quiz batches available

📚 Software Engineering 📄 18 Past-Paper Qs ✓ Free · No Login Needed
🎯 Mock Test

Read each question, think about the answer, then click Show Answer to reveal the correct option and explanation. Load 10 at a time so it stays manageable — perfect for one-topic study sessions on the bus or during a break.

Page 1 of 1 Questions 110 of 39
  1. Q1 medium

    change control board is best defined as

    1. A team that writes all code alone
    2. B group that evaluates and dispositions change requests
    3. C cafeteria committee
    4. D hardware paint crew
    💡 Explanation:

    CCB governs approved changes.

  2. Q2 medium

    configuration baseline is best defined as

    1. A random draft note
    2. B unlabeled backup
    3. C approved configuration item version used as reference
    4. D informal chat log
    💡 Explanation:

    Baselines anchor change control.

  3. Q3 hard

    ISO 12207 is best defined as

    1. A Wi-Fi protocol spec
    2. B food hygiene code
    3. C motor oil viscosity grades
    4. D international standard for software life cycle processes
    💡 Explanation:

    12207 defines life cycle process framework.

  4. Q4 hard

    CMMI maturity is best defined as

    1. A only Agile to Waterfall mapping
    2. B medal ranks in sports only
    3. C GPU clock speeds
    4. D process improvement levels from Initial to Optimizing
    💡 Explanation:

    CMMI institutionalizes process capability.

  5. Q5 Past Paper · PPSC/FPSC/NTS medium

    Brooks Law is best defined as

    1. A adding people to a late project often makes it later
    2. B always accelerates delivery linearly
    3. C has zero communication cost
    4. D eliminates all defects
    💡 Explanation:

    Coordination overhead can dominate.

  6. Q6 hard

    preventive maintenance is best defined as

    1. A actions to reduce future failure likelihood
    2. B ignoring technical debt
    3. C deleting specs
    4. D freezing code forever
    💡 Explanation:

    Preventive lowers future risk.

  7. Q7 medium

    perfective maintenance is best defined as

    1. A improving performance or capabilities per user request
    2. B replacing power supplies
    3. C cable colour standards
    4. D parking policies
    💡 Explanation:

    Perfective enhances beyond bug fixes.

  8. Q8 medium

    adaptive maintenance is best defined as

    1. A fixing sort algorithm bugs only
    2. B comment spelling only
    3. C IDE theme updates
    4. D modifying software for environmental changes
    💡 Explanation:

    Adaptive responds to external change.

  9. Q9 easy

    corrective maintenance is best defined as

    1. A adapting to new tax law only
    2. B adding unrequested features
    3. C rewriting for new language fashion
    4. D fixing discovered faults in delivered software
    💡 Explanation:

    Corrective fixes defects.

  10. Q10 Past Paper · PPSC/FPSC/NTS medium

    acceptance testing is best defined as

    1. A compiler settings only
    2. B confirming the system satisfies user acceptance criteria
    3. C developer satisfaction only
    4. D database vendor preference
    💡 Explanation:

    Users validate fitness for purpose.

  11. Q11 Past Paper · PPSC/FPSC/NTS medium

    integration testing is best defined as

    1. A syntax check of one line only
    2. B verifying interfaces between combined modules
    3. C office seating charts
    4. D employee leave forms
    💡 Explanation:

    Integration exposes interface defects.

  12. Q12 easy

    implementation phase is best defined as

    1. A acceptance testing only
    2. B constructing software modules per approved design
    3. C contract signing only
    4. D hardware disposal only
    💡 Explanation:

    Coding realizes the design.

  13. Q13 Past Paper · PPSC/FPSC/NTS medium

    V-Model is best defined as

    1. A only coding without verification
    2. B marketing phases only
    3. C hardware assembly only
    4. D each development phase paired with a corresponding test phase
    💡 Explanation:

    V-Model links design to validation.

  14. Q14 Past Paper · PPSC/FPSC/NTS easy

    Waterfall SDLC model is best defined as

    1. A overlapping iterations without documentation
    2. B no testing phase ever
    3. C only prototyping without requirements
    4. D sequential phases where each phase completes before the next begins
    💡 Explanation:

    Waterfall is linear and document-driven.

  15. Q15 Past Paper · PPSC/FPSC/NTS medium

    software crisis is best defined as

    1. A abundance of perfect software
    2. B large projects missing cost, schedule and quality targets
    3. C shortage of electricity only
    4. D excess of finished systems
    💡 Explanation:

    1960s-70s failures motivated software engineering.

  16. Q16 medium

    traceability matrix is best defined as

    1. A mapping requirements through design to tests
    2. B employee salary table
    3. C coffee inventory
    4. D font catalog only
    💡 Explanation:

    Traceability supports coverage analysis.

  17. Q17 easy

    validation is best defined as

    1. A confirming the right product is built for user needs
    2. B syntax correctness only
    3. C indentation style only
    4. D logo colour only
    💡 Explanation:

    Validation matches real needs.

  18. Q18 easy

    verification is best defined as

    1. A fitness for user needs only
    2. B office decor compliance
    3. C checking conformance to specifications — building the product right
    4. D warehouse temperature
    💡 Explanation:

    Verification matches specs.

  19. Q19 medium

    work breakdown structure is best defined as

    1. A tokenizing source text
    2. B organizing lunch menus
    3. C sorting keyboard brands
    4. D hierarchical decomposition of project deliverables
    💡 Explanation:

    WBS defines scope packages.

  20. Q20 medium

    change control board is best defined as

    1. A team that writes all code alone
    2. B group that evaluates and dispositions change requests
    3. C cafeteria committee
    4. D hardware paint crew
    💡 Explanation:

    CCB governs approved changes.

  21. Q21 medium

    configuration baseline is best defined as

    1. A random draft note
    2. B unlabeled backup
    3. C approved configuration item version used as reference
    4. D informal chat log
    💡 Explanation:

    Baselines anchor change control.

  22. Q22 hard

    ISO 12207 is best defined as

    1. A Wi-Fi protocol spec
    2. B food hygiene code
    3. C motor oil viscosity grades
    4. D international standard for software life cycle processes
    💡 Explanation:

    12207 defines life cycle process framework.

  23. Q23 Past Paper · PPSC/FPSC/NTS medium

    software crisis is best defined as

    1. A abundance of perfect software
    2. B large projects missing cost, schedule and quality targets
    3. C shortage of electricity only
    4. D excess of finished systems
    💡 Explanation:

    1960s-70s failures motivated software engineering.

  24. Q24 hard

    preventive maintenance is best defined as

    1. A actions to reduce future failure likelihood
    2. B ignoring technical debt
    3. C deleting specs
    4. D freezing code forever
    💡 Explanation:

    Preventive lowers future risk.

  25. Q25 medium

    adaptive maintenance is best defined as

    1. A fixing sort algorithm bugs only
    2. B comment spelling only
    3. C IDE theme updates
    4. D modifying software for environmental changes
    💡 Explanation:

    Adaptive responds to external change.

  26. Q26 easy

    corrective maintenance is best defined as

    1. A adapting to new tax law only
    2. B adding unrequested features
    3. C rewriting for new language fashion
    4. D fixing discovered faults in delivered software
    💡 Explanation:

    Corrective fixes defects.

  27. Q27 Past Paper · PPSC/FPSC/NTS medium

    acceptance testing is best defined as

    1. A compiler settings only
    2. B confirming the system satisfies user acceptance criteria
    3. C developer satisfaction only
    4. D database vendor preference
    💡 Explanation:

    Users validate fitness for purpose.

  28. Q28 Past Paper · PPSC/FPSC/NTS medium

    integration testing is best defined as

    1. A syntax check of one line only
    2. B verifying interfaces between combined modules
    3. C office seating charts
    4. D employee leave forms
    💡 Explanation:

    Integration exposes interface defects.

  29. Q29 easy

    implementation phase is best defined as

    1. A acceptance testing only
    2. B constructing software modules per approved design
    3. C contract signing only
    4. D hardware disposal only
    💡 Explanation:

    Coding realizes the design.

  30. Q30 Past Paper · PPSC/FPSC/NTS easy

    design phase is best defined as

    1. A only debugging production
    2. B only payroll processing
    3. C only ad copy writing
    4. D creating architecture and detailed specifications
    💡 Explanation:

    Design maps requirements to structure.

  31. Q31 Past Paper · PPSC/FPSC/NTS easy

    requirements phase is best defined as

    1. A deployment to production only
    2. B eliciting, analyzing and documenting stakeholder needs
    3. C deleting legacy data only
    4. D printing manuals before analysis
    💡 Explanation:

    Requirements define what to build.

  32. Q32 Past Paper · PPSC/FPSC/NTS easy

    feasibility study is best defined as

    1. A choosing UI colours only
    2. B assessing technical, economic, schedule and operational viability
    3. C cafeteria planning only
    4. D selecting IDE themes only
    💡 Explanation:

    Feasibility decides if project should proceed.

  33. Q33 Past Paper · PPSC/FPSC/NTS easy

    prototyping for requirements is best defined as

    1. A replacing all formal testing
    2. B eliminating design documents always
    3. C avoiding users entirely
    4. D clarifying ambiguous needs via executable or mock-up models
    💡 Explanation:

    Prototypes reduce requirements uncertainty.

  34. Q34 Past Paper · PPSC/FPSC/NTS medium

    RAD approach is best defined as

    1. A heavy user involvement, prototyping and CASE tools
    2. B frozen specs for a decade
    3. C no user contact
    4. D manual machine code only
    💡 Explanation:

    RAD compresses schedule via participation.

  35. Q35 Past Paper · PPSC/FPSC/NTS easy

    iterative development is best defined as

    1. A strictly linear single pass
    2. B repeated cycles of design, build and evaluate
    3. C no user feedback loops
    4. D only maintenance activities
    💡 Explanation:

    Iteration refines understanding and product.

  36. Q36 Past Paper · PPSC/FPSC/NTS easy

    incremental delivery is best defined as

    1. A successive releases each adding subsets of total functionality
    2. B one release after thirty years only
    3. C hardware-only increments
    4. D no integration testing
    💡 Explanation:

    Increments grow the system over time.

  37. Q37 Past Paper · PPSC/FPSC/NTS medium

    Spiral model is best defined as

    1. A single pass delivery only
    2. B no stakeholder review
    3. C iterative cycles with explicit risk analysis at each revolution
    4. D no prototyping allowed
    💡 Explanation:

    Boehm Spiral is risk-driven.

  38. Q38 Past Paper · PPSC/FPSC/NTS medium

    Brooks Law is best defined as

    1. A adding people to a late project often makes it later
    2. B always accelerates delivery linearly
    3. C has zero communication cost
    4. D eliminates all defects
    💡 Explanation:

    Coordination overhead can dominate.

  39. Q39 medium

    perfective maintenance is best defined as

    1. A improving performance or capabilities per user request
    2. B replacing power supplies
    3. C cable colour standards
    4. D parking policies
    💡 Explanation:

    Perfective enhances beyond bug fixes.