CSS Prepare

optional · CSS study notes

🗄️ OLD — Project Management and Process Improvement (consolidated)

CSS Computer Science (Optional) — Paper-I, Section-B, Topic V. Covers two distinct syllabus items: Project Management and Process Improvement. Between them, this pairing has appeared in 4 of the last 7 available papers (2021, 2024, 2025, and 2025's dedicated SPI question) — one of the more dependable clusters on the syllabus.

Project Management Phases

  1. Conception & Initiation — define the project's purpose and confirm it's worth doing (feasibility).
  2. Planning — scope, schedule, resource allocation, and budget; this is where scheduling tools (below) get built.
  3. Execution — the team does the actual development work according to the plan.
  4. Monitoring / Performance Tracking — compare actual progress against the plan; adjust as needed.
  5. Closure — formally end the project, hand over deliverables, capture lessons learned.

Scheduling & Estimation Tools

  • Gantt chart: a horizontal bar chart showing each task's start/end dates and overlap with other tasks — good for visualizing the overall timeline.
  • PERT chart (Program Evaluation and Review Technique): a network diagram showing task dependencies and the critical path — the longest dependency chain, which determines the minimum possible project duration. Where a Gantt chart shows when, a PERT chart shows what depends on what.
  • COCOMO (Constructive Cost Model): estimates development effort (person-months) from estimated size (lines of code) and a set of project-type/complexity multipliers — the standard named cost-estimation model for this syllabus.

Risk Management

A repeating cycle, not a one-time step: identify risks → analyse their probability and impact → plan a response (avoid, mitigate, transfer, or accept the risk) → monitor continuously as the project proceeds, since new risks emerge and old ones change likelihood as the project moves forward.

Team Organization

Brief awareness is enough: common models include a hierarchical/chief-programmer team (one senior lead directs the work) versus a democratic/egoless team (shared decision-making, peer review) — trade-off is central control and accountability versus better morale and idea-sharing.

🔥

Repeated in past papers: 2021 Q7(a) asked for detailed notes on the PERT chart (and UML). 2024 Q7(a) asked to discuss the phases of project management (conception, planning, execution, monitoring, closure) directly. 2025 Q7(a) asked for the different types of planning phases conducted during software development, with tasks performed at each stage. See 🔥 Most Repeated — Software Engineering.

Process Improvement

Improving the process itself, across projects — not just steering one project to completion.

The Software Process Improvement (SPI) Framework

A repeating cycle: measure current process performance → analyse the gap against a target maturity model → plan specific changes → implement them → measure again to confirm the change actually helped. FPSC gave this a full 8-mark sub-question on its own in 2025 — a strong signal it's moving from "mentioned in passing" to "asked directly," so don't treat it as a footnote to CMMI.

CMMI as the Benchmark

CMMI (see the Software Quality Assurance page for its five maturity levels: Initial → Managed → Defined → Quantitatively Managed → Optimizing) is the most common maturity model used to benchmark an organization's process before and after an SPI initiative — the two topics are meant to be studied together, not as unrelated facts.

Determining Which Projects Need SPI

Not every project needs a formal SPI initiative — the exam has specifically asked "how do you determine the projects for which the SPI framework should be used?" A reasonable answer weighs: recurring, avoidable defects across multiple projects (a process problem, not a one-off mistake), consistent schedule/budget overruns, and low current CMMI maturity level relative to the organization's goals.

🔥

Repeated in past papers — new emphasis in 2025: Q7(c), 8 marks: "What is the Software Process Improvement (SPI) framework? Highlight the different steps... and how to determine the projects for which SPI framework should be used." See 🔥 Most Repeated — Software Engineering for the full model answer.

MCQ Trap

  • A PERT chart shows dependencies and the critical path; a Gantt chart shows the calendar timeline. A question describing "the longest sequence of dependent tasks that determines minimum project duration" is asking about PERT's critical path, not Gantt.