19-Soft-A7 Software Development Process · Undated paper
Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)
National Exams — 04-Soft-A7, Software Process (closed book, two aid sheets, 3 hours). Notes on the paper: eight questions constitute the exam paper; answer FIVE of the eight, and the first FIVE as they appear in the answer book are marked. Each question is of equal value, and each sub-question within a question is of equal value (shown here as 20 marks per question on a 100-mark basis) — this solution answers all eight as a full study resource. Question 3 asks for a Gantt/timeline schedule for a personal address-book application; Question 4 introduces a hospital patient-registration system that Question 5's Function-Point estimate builds on.
Reference texts. Sommerville, Software Engineering, 10th ed., Ch. 2 (Software Processes), Ch. 3 (Agile Software Development), Ch. 5 (System Modeling), Ch. 8–9 (Testing), Ch. 22–23 (Project Management, Configuration Management), Ch. 9 (Software Evolution/Maintenance); Pressman, Software Engineering: A Practitioner's Approach, 9th ed., Ch. 2–3 (Process Models, Agile), Ch. 23–24 (Project Management, Risk Management), Ch. 29 (Function-Point sizing), Ch. 22 (SQA), Ch. 24 (Software Configuration Management); IEEE/ISO 12207 (Software Life Cycle Processes); SWEBOK v4 (Software Engineering Process, Software Configuration Management, Software Maintenance KAs).
Question text not reproduced: the examination questions are © Engineers and Geoscientists BC. Open the official past paper (linked at the top of this page) to read the question, then follow the worked solution below.
Given. A personal address-book application (add, delete, edit, save, load contacts), estimated project duration 4 weeks (20 working days). The schedule must show managerial, development, and QA activities.
Find. Two Gantt/timeline charts, one per process model, with approximate day durations for every stage.
Approach. For Part (a), lay the five generic phases (Question 1a) out strictly sequentially over the 20 days. For Part (b), split the same 20 days into four 1-week sprints, each delivering one working slice of the CRUD feature set (add/delete → edit/save → load → polish), each followed by its own short QA pass, with continuous program management running throughout both.
Part a) — Waterfall process model.
Part b) — Agile development methodology, 1-week sprints.
| Model | Stage breakdown (days) | Total |
|---|---|---|
| Waterfall (a) | Req 2 → Design 3 → Impl 9 → QA 4 → Deploy 2 | 20 days |
| Agile (b) | 4 sprints × (4d dev + 1d QA) | 20 days |
