CSS Prepare

optional · CSS study notes

Software Process Improvement (SPI)

CSS CS Optional — Paper-I, Section-B, Topic V. Improves the process itself, across projects — not just one project.

🔑 SPI Framework — Repeating Cycle

  1. Measure current process performance
  2. Analyse gap against target maturity model
  3. Plan specific changes
  4. Implement changes
  5. Measure again — confirm it helped
  • FPSC gave this a full 8-mark sub-question in 2025 — treat as standalone, not a CMMI footnote.

📌 CMMI as Benchmark

  • CMMI (see SQA page: Initial → Managed → Defined → Quantitatively Managed → Optimizing) benchmarks maturity before/after SPI.
  • Study CMMI + SPI as one pair.

📌 Determining Which Projects Need SPI

  • Recurring, avoidable defects across projects (process problem, not one-off)
  • Consistent schedule/budget overruns
  • Low current CMMI level vs org's target

🔥 Past Papers

  • 2025 Q7(c), 8 marks — SPI framework, steps, how to determine which projects need it.

⚠️ MCQ Trap

  • Don't drift into describing Gantt/PERT — SPI = measure→analyse→plan→implement→measure cycle.

📜 Past-Paper Questions & MCQs (CSS 2016–2026)

2025 · Paper-I · Q7(c) · 8 marks

Q. What is the Software Process Improvement (SPI) framework? Highlight the steps and key elements. Describe the models within SPI and how to determine the projects for which SPI should be used.

Ans.

  • SPI is the systematic effort to assess and improve an organisation's software development process so that quality, cost and delivery time get better.
  • Steps:
    • Assess the current process (find strengths and weaknesses).
    • Plan improvements and set goals.
    • Implement the changes (training, new methods, tools).
    • Evaluate results with measurements, then repeat (continuous improvement).
  • Key elements: management commitment, process measurement (metrics), a process model or standard, training, and feedback and learning.
  • Models:
    • CMMI (five levels: Initial, Managed, Defined, Quantitatively Managed, Optimizing)
    • IDEAL (Initiating, Diagnosing, Establishing, Acting, Learning)
    • ISO/IEC 15504 (SPICE), ISO 9001, Six Sigma, and Lean
  • Which projects should use SPI: large and long-running projects, critical or regulated systems, organisations with frequent delays, defects or rework, and repeated projects where better process pays back. Small one-off projects gain little.

MCQs

2025 P-I · Q2. What is the main goal of Capability Maturity Model Integration (CMMI)?

  • (A) To enhance the maturity of the software process ✅
  • (B) To increase the quality of software
  • (C) To provide a user-friendly experience
  • (D) None of these
  • Answer: (A).
  • Why: CMMI is a process-improvement model that rates an organisation's process maturity on five levels (Initial, Managed, Defined, Quantitatively Managed, Optimizing). Better quality is a result of a mature process, not the direct goal, and user experience is not its concern.