S6 ICT: system development life cycle (error rework)
- 2026-11-20
S6 ICT: system development life cycle (error rework)
Error rework only: ten common confusions corrected item by item, including person-days mistaken for days and inverted density divisors.
Error rework: the ten commonest confusions This paper does one thing: correct the ideas that keep going wrong. The SDLC is a framework and waterfall only one of its models; testing shifts left into coding; users sign off UAT; agile still plans and documents, just leanly; throwaway prototypes never ship; among the four maintenance types, perfective and adaptive dominate; requirements are managed by change control, not frozen. Three calculations catch students most often: reading person-days as days (70 person-days over seven people is ten days), inverting the defect density divisor (240 over 40 is six, not 0.6), and letting the coverage numerator exceed the denominator (1,020 over 1,200 is 85 percent).
01 Paper details (check answers afterwards)
| Item | Detail |
|---|---|
| Questions | 10 |
| Suggested time | 25 |
| Difficulty mix | Foundation 3 · Intermediate 3 · Challenge 3 · Error redo 1 |
| Chapter | Chapter: S6 ICT: Object-Oriented Programming and Debugging |
| Level | Error rework (10 items) |
02 Questions (10 items)
- FoundationWhat is wrong with saying the SDLC is the waterfall model?
- FoundationWhat is wrong with saying testing only happens after the system is complete?
- FoundationWhat is wrong with saying the development team signs off UAT?
- IntermediateWhat is wrong with saying agile means no planning and no documentation?
- IntermediateWhat is wrong with assuming a prototype becomes the final system?
- IntermediateWhat is wrong with saying maintenance only means fixing bugs?
- ChallengeWhat is wrong with freezing requirements once analysis is signed off?
- ChallengeError drill: a 200 person-day project with implementation at 35 percent gives 70 person-days. How many working days for 7 people? (Common wrong answer: 70 days)
- ChallengeError drill: 240 defects over 40 KLOC. What is the defect density? (Common wrong answer: 0.6)
- Error redoError drill: 1,200 statements with 1,020 executed. What is the coverage? (Common wrong answer: 102 percent)
03 Answers and one-line notes
| # | Answer | One-line note |
|---|---|---|
| 1 | The SDLC is the overall framework; waterfall, iterative, agile and spiral are models that implement it. | Treating a framework as one model makes sequential flow look like the only option. |
| 2 | Unit tests run during coding, and in the V model every development level has a matching test level. | Shifting testing left catches defects when they are cheapest to fix. |
| 3 | Users or customer representatives run and sign off UAT; the team only handles unit, integration and system testing. | Developers signing their own acceptance is marking their own paper. |
| 4 | Agile keeps a product backlog, sprint backlog, sprint goal and acceptance criteria; documents are lean but present. | Planless work is fake agile, not agile. |
| 5 | A throwaway prototype only clarifies requirements and is then discarded; only an evolutionary prototype grows into the product. | Prototypes usually ignore performance and security, so shipping one directly is a classic trap. |
| 6 | Maintenance covers corrective, adaptive, perfective and preventive work, and it is usually the costliest part of the life cycle. | Software maintenance taking over sixty percent of total cost is normal, not exceptional. |
| 7 | Requirements do change; a change control process assesses impact and re-estimates cost and schedule. | Freezing requirements only pushes the change into a more expensive phase. |
| 8 | It needs 10 working days, that is 70 divided by 7, not 70 days. | Person-days divided by people gives days; copying person-days as days is the commonest slip. |
| 9 | It is 6.0 defects per KLOC, not 0.6. | Swapping divisor and dividend shifts the answer tenfold; write the unit before the number. |
| 10 | It is 85.0 percent; coverage cannot exceed 100 percent. | The numerator cannot exceed the denominator; a bigger figure means the division is inverted. |
04 What to do after marking
- After marking, redo only the wrong items and write down which step went wrong (formula, unit, or misread number).
- Repeat the same item two days later; move to the next paper only when both attempts are correct.
- Parents only need the answer and note columns; there is no need to explain every item.
Want the five SDLC phases, the waterfall versus agile trade-off, and person-days, payback and defect density all straightened out? Book a TutorZone tutor and settle every number in twenty-five minutes.Tutor Registration →
Questions and answers are written originally by the TutorZone team and are not taken from any school, publisher or examination authority paper. Every value is checked by computer.



