S6 ICT: system development life cycle (intermediate)
- 2026-11-20
S6 ICT: system development life cycle (intermediate)
Next step: agile and Scrum, sprint points converted to hours, return on investment, defect density and conversion strategies.
Intermediate: agile, sprints and conversion Waterfall freezes requirements before building, while agile slices delivery into short sprints that each ship working software. The three Scrum roles divide the work: the product owner orders the backlog, the Scrum Master removes obstacles, and the team delivers. Points are relative estimates, so converting them to hours needs the team own rate; this paper turns 270 points into 1,620 hours at six hours each, then shows a five-person team at 800 hours a month finishing in about 2.02 months. Parallel, direct, pilot and phased conversion are weighed with the extra running cost worked out.
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 | Intermediate (10 items) |
02 Questions (10 items)
- FoundationWhat are the three fundamental differences between agile development and waterfall?
- FoundationWhich three roles does Scrum define?
- Foundation6 sprints of 2 weeks each: how many weeks and days, and how many story points at 45 points per sprint?
- IntermediateA backlog of 300 points at 45 points per sprint needs how many sprints, how many extra weeks over the planned 6, and how many points in the last sprint?
- Intermediate270 points at 6 hours per point is how many hours, and how many months for 5 people at 8 hours a day and 20 days a month?
- IntermediateA system returns $900,000 against a $600,000 development cost. What is the return on investment?
- ChallengeTesting finds 240 defects and 60 more appear in production on a 40 KLOC system. What is the defect density?
- ChallengeA parallel conversion runs both systems for 2 months at $40,000 a month each. What is the extra cost?
- ChallengeWhat is the order of the four testing levels from smallest to largest?
- Error redoA burn-down of 240 points over 6 sprints gives 40 points per sprint ideally; after 4 sprints 120 points are done, leaving 120. How far behind is the team?
03 Answers and one-line notes
| # | Answer | One-line note |
|---|---|---|
| 1 | Iterative delivery of working software, treating requirement change as normal, and measuring progress by working software rather than documents. | Agile does not lack process; it shortens the feedback cycle from months to weeks. |
| 2 | Product owner, Scrum Master, and the development team. | The product owner decides what, the Scrum Master keeps the process flowing, and the team delivers. |
| 3 | 12 weeks, that is 84 days, delivering 270 points. | Story points are relative estimates, not hours. |
| 4 | 7 sprints, that is 14 weeks, 2 weeks more; the last sprint carries 30 points. | Round up when there is a remainder; 6.7 sprints is not an answer. |
| 5 | 1620 hours; with 800 hours a month that is about 2.02 months. | Converting points to hours needs the team own rate, otherwise the estimate means nothing. |
| 6 | ROI is (900,000 minus 600,000) divided by 600,000, that is 50.0 percent. | ROI is divided by cost, not by benefit; using the wrong denominator doubles the figure. |
| 7 | Density is 240 divided by 40, that is 6.0 defects per KLOC. | Defect density divides by code size so projects can be compared. |
| 8 | An extra $80,000, the two months of duplicated running cost. | Parallel running is safest and costliest; direct cut-over is cheapest and riskiest. |
| 9 | Unit testing, integration testing, system testing, then acceptance testing. | Each level must pass before moving up; skip integration and system testing turns into a debugging session. |
| 10 | Ideal remainder is 80 points against an actual 120, so the team is 40 points behind. | Read the trend rather than one point; two or three sprints behind means scope must be adjusted. |
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.



