Software Development Life Cycle Models MCQs 2026

42 questions with detailed answers · 22 from past papers · 5 quiz batches available

📚 Software Engineering📄 22 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 1Questions 1–10 of 42
  1. Q1Past Paper · PPSC/FPSC/NTSeasy

    incremental delivery is best defined as

    1. Asuccessive releases each adding subsets of total functionality
    2. Bone release after thirty years only
    3. Chardware-only increments
    4. Dno integration testing
    💡 Explanation:

    Increments grow the system over time.

  2. Q2Past Paper · PPSC/FPSC/NTSeasy

    iterative development is best defined as

    1. Astrictly linear single pass
    2. Brepeated cycles of design, build and evaluate
    3. Cno user feedback loops
    4. Donly maintenance activities
    💡 Explanation:

    Iteration refines understanding and product.

  3. Q3Past Paper · PPSC/FPSC/NTSmedium

    RAD approach is best defined as

    1. Aheavy user involvement, prototyping and CASE tools
    2. Bfrozen specs for a decade
    3. Cno user contact
    4. Dmanual machine code only
    💡 Explanation:

    RAD compresses schedule via participation.

  4. Q4Past Paper · PPSC/FPSC/NTSeasy

    prototyping for requirements is best defined as

    1. Areplacing all formal testing
    2. Beliminating design documents always
    3. Cavoiding users entirely
    4. Dclarifying ambiguous needs via executable or mock-up models
    💡 Explanation:

    Prototypes reduce requirements uncertainty.

  5. Q5Past Paper · PPSC/FPSC/NTSeasy

    feasibility study is best defined as

    1. Achoosing UI colours only
    2. Bassessing technical, economic, schedule and operational viability
    3. Ccafeteria planning only
    4. Dselecting IDE themes only
    💡 Explanation:

    Feasibility decides if project should proceed.

  6. Q6Past Paper · PPSC/FPSC/NTSeasy

    requirements phase is best defined as

    1. Adeployment to production only
    2. Beliciting, analyzing and documenting stakeholder needs
    3. Cdeleting legacy data only
    4. Dprinting manuals before analysis
    💡 Explanation:

    Requirements define what to build.

  7. Q7Past Paper · PPSC/FPSC/NTSeasy

    design phase is best defined as

    1. Aonly debugging production
    2. Bonly payroll processing
    3. Conly ad copy writing
    4. Dcreating architecture and detailed specifications
    💡 Explanation:

    Design maps requirements to structure.

  8. Q8Past Paper · PPSC/FPSC/NTSmedium

    software crisis is best defined as

    1. Aabundance of perfect software
    2. Blarge projects missing cost, schedule and quality targets
    3. Cshortage of electricity only
    4. Dexcess of finished systems
    💡 Explanation:

    1960s-70s failures motivated software engineering.

  9. Q9hard

    CMMI maturity is best defined as

    1. Aonly Agile to Waterfall mapping
    2. Bmedal ranks in sports only
    3. CGPU clock speeds
    4. Dprocess improvement levels from Initial to Optimizing
    💡 Explanation:

    CMMI institutionalizes process capability.

  10. Q10hard

    ISO 12207 is best defined as

    1. AWi-Fi protocol spec
    2. Bfood hygiene code
    3. Cmotor oil viscosity grades
    4. Dinternational standard for software life cycle processes
    💡 Explanation:

    12207 defines life cycle process framework.

  11. Q11medium

    configuration baseline is best defined as

    1. Arandom draft note
    2. Bunlabeled backup
    3. Capproved configuration item version used as reference
    4. Dinformal chat log
    💡 Explanation:

    Baselines anchor change control.

  12. Q12medium

    change control board is best defined as

    1. Ateam that writes all code alone
    2. Bgroup that evaluates and dispositions change requests
    3. Ccafeteria committee
    4. Dhardware paint crew
    💡 Explanation:

    CCB governs approved changes.

  13. Q13medium

    work breakdown structure is best defined as

    1. Atokenizing source text
    2. Borganizing lunch menus
    3. Csorting keyboard brands
    4. Dhierarchical decomposition of project deliverables
    💡 Explanation:

    WBS defines scope packages.

  14. Q14easy

    verification is best defined as

    1. Afitness for user needs only
    2. Boffice decor compliance
    3. Cchecking conformance to specifications — building the product right
    4. Dwarehouse temperature
    💡 Explanation:

    Verification matches specs.

  15. Q15easy

    validation is best defined as

    1. Aconfirming the right product is built for user needs
    2. Bsyntax correctness only
    3. Cindentation style only
    4. Dlogo colour only
    💡 Explanation:

    Validation matches real needs.

  16. Q16easy

    validation is best defined as

    1. Aconfirming the right product is built for user needs
    2. Bsyntax correctness only
    3. Cindentation style only
    4. Dlogo colour only
    💡 Explanation:

    Validation matches real needs.

  17. Q17easy

    verification is best defined as

    1. Afitness for user needs only
    2. Boffice decor compliance
    3. Cchecking conformance to specifications — building the product right
    4. Dwarehouse temperature
    💡 Explanation:

    Verification matches specs.

  18. Q18medium

    work breakdown structure is best defined as

    1. Atokenizing source text
    2. Borganizing lunch menus
    3. Csorting keyboard brands
    4. Dhierarchical decomposition of project deliverables
    💡 Explanation:

    WBS defines scope packages.

  19. Q19medium

    change control board is best defined as

    1. Ateam that writes all code alone
    2. Bgroup that evaluates and dispositions change requests
    3. Ccafeteria committee
    4. Dhardware paint crew
    💡 Explanation:

    CCB governs approved changes.

  20. Q20medium

    configuration baseline is best defined as

    1. Arandom draft note
    2. Bunlabeled backup
    3. Capproved configuration item version used as reference
    4. Dinformal chat log
    💡 Explanation:

    Baselines anchor change control.

  21. Q21hard

    ISO 12207 is best defined as

    1. AWi-Fi protocol spec
    2. Bfood hygiene code
    3. Cmotor oil viscosity grades
    4. Dinternational standard for software life cycle processes
    💡 Explanation:

    12207 defines life cycle process framework.

  22. Q22hard

    CMMI maturity is best defined as

    1. Aonly Agile to Waterfall mapping
    2. Bmedal ranks in sports only
    3. CGPU clock speeds
    4. Dprocess improvement levels from Initial to Optimizing
    💡 Explanation:

    CMMI institutionalizes process capability.

  23. Q23Past Paper · PPSC/FPSC/NTSmedium

    software crisis is best defined as

    1. Aabundance of perfect software
    2. Blarge projects missing cost, schedule and quality targets
    3. Cshortage of electricity only
    4. Dexcess of finished systems
    💡 Explanation:

    1960s-70s failures motivated software engineering.

  24. Q24Past Paper · PPSC/FPSC/NTSmedium

    Brooks Law is best defined as

    1. Aadding people to a late project often makes it later
    2. Balways accelerates delivery linearly
    3. Chas zero communication cost
    4. Deliminates all defects
    💡 Explanation:

    Coordination overhead can dominate.

  25. Q25hard

    preventive maintenance is best defined as

    1. Aactions to reduce future failure likelihood
    2. Bignoring technical debt
    3. Cdeleting specs
    4. Dfreezing code forever
    💡 Explanation:

    Preventive lowers future risk.

  26. Q26medium

    perfective maintenance is best defined as

    1. Aimproving performance or capabilities per user request
    2. Breplacing power supplies
    3. Ccable colour standards
    4. Dparking policies
    💡 Explanation:

    Perfective enhances beyond bug fixes.

  27. Q27medium

    adaptive maintenance is best defined as

    1. Afixing sort algorithm bugs only
    2. Bcomment spelling only
    3. CIDE theme updates
    4. Dmodifying software for environmental changes
    💡 Explanation:

    Adaptive responds to external change.

  28. Q28easy

    corrective maintenance is best defined as

    1. Aadapting to new tax law only
    2. Badding unrequested features
    3. Crewriting for new language fashion
    4. Dfixing discovered faults in delivered software
    💡 Explanation:

    Corrective fixes defects.

  29. Q29Past Paper · PPSC/FPSC/NTSmedium

    acceptance testing is best defined as

    1. Acompiler settings only
    2. Bconfirming the system satisfies user acceptance criteria
    3. Cdeveloper satisfaction only
    4. Ddatabase vendor preference
    💡 Explanation:

    Users validate fitness for purpose.

  30. Q30Past Paper · PPSC/FPSC/NTSmedium

    integration testing is best defined as

    1. Asyntax check of one line only
    2. Bverifying interfaces between combined modules
    3. Coffice seating charts
    4. Demployee leave forms
    💡 Explanation:

    Integration exposes interface defects.

  31. Q31easy

    implementation phase is best defined as

    1. Aacceptance testing only
    2. Bconstructing software modules per approved design
    3. Ccontract signing only
    4. Dhardware disposal only
    💡 Explanation:

    Coding realizes the design.

  32. Q32Past Paper · PPSC/FPSC/NTSmedium

    V-Model is best defined as

    1. Aonly coding without verification
    2. Bmarketing phases only
    3. Chardware assembly only
    4. Deach development phase paired with a corresponding test phase
    💡 Explanation:

    V-Model links design to validation.

  33. Q33Past Paper · PPSC/FPSC/NTSeasy

    Waterfall SDLC model is best defined as

    1. Aoverlapping iterations without documentation
    2. Bno testing phase ever
    3. Conly prototyping without requirements
    4. Dsequential phases where each phase completes before the next begins
    💡 Explanation:

    Waterfall is linear and document-driven.

  34. Q34Past Paper · PPSC/FPSC/NTSeasy

    prototyping for requirements is best defined as

    1. Areplacing all formal testing
    2. Beliminating design documents always
    3. Cavoiding users entirely
    4. Dclarifying ambiguous needs via executable or mock-up models
    💡 Explanation:

    Prototypes reduce requirements uncertainty.

  35. Q35Past Paper · PPSC/FPSC/NTSmedium

    Spiral model is best defined as

    1. Asingle pass delivery only
    2. Bno stakeholder review
    3. Citerative cycles with explicit risk analysis at each revolution
    4. Dno prototyping allowed
    💡 Explanation:

    Boehm Spiral is risk-driven.

  36. Q36Past Paper · PPSC/FPSC/NTSeasy

    incremental delivery is best defined as

    1. Asuccessive releases each adding subsets of total functionality
    2. Bone release after thirty years only
    3. Chardware-only increments
    4. Dno integration testing
    💡 Explanation:

    Increments grow the system over time.

  37. Q37Past Paper · PPSC/FPSC/NTSeasy

    iterative development is best defined as

    1. Astrictly linear single pass
    2. Brepeated cycles of design, build and evaluate
    3. Cno user feedback loops
    4. Donly maintenance activities
    💡 Explanation:

    Iteration refines understanding and product.

  38. Q38Past Paper · PPSC/FPSC/NTSmedium

    RAD approach is best defined as

    1. Aheavy user involvement, prototyping and CASE tools
    2. Bfrozen specs for a decade
    3. Cno user contact
    4. Dmanual machine code only
    💡 Explanation:

    RAD compresses schedule via participation.

  39. Q39medium

    traceability matrix is best defined as

    1. Amapping requirements through design to tests
    2. Bemployee salary table
    3. Ccoffee inventory
    4. Dfont catalog only
    💡 Explanation:

    Traceability supports coverage analysis.

  40. Q40Past Paper · PPSC/FPSC/NTSeasy

    design phase is best defined as

    1. Aonly debugging production
    2. Bonly payroll processing
    3. Conly ad copy writing
    4. Dcreating architecture and detailed specifications
    💡 Explanation:

    Design maps requirements to structure.

  41. Q41Past Paper · PPSC/FPSC/NTSeasy

    requirements phase is best defined as

    1. Adeployment to production only
    2. Beliciting, analyzing and documenting stakeholder needs
    3. Cdeleting legacy data only
    4. Dprinting manuals before analysis
    💡 Explanation:

    Requirements define what to build.

  42. Q42Past Paper · PPSC/FPSC/NTSeasy

    feasibility study is best defined as

    1. Achoosing UI colours only
    2. Bassessing technical, economic, schedule and operational viability
    3. Ccafeteria planning only
    4. Dselecting IDE themes only
    💡 Explanation:

    Feasibility decides if project should proceed.