S6 ICT: system development life cycle (basics)
- 2026-11-20
S6 ICT: system development life cycle (basics)
Basics first: the five phases, waterfall, feasibility study and the requirements specification, so the process and its documents line up.
Basics: five phases, waterfall and feasibility System development starts with a problem and ends when the system retires. The five phases are analysis, design, implementation, testing and maintenance; waterfall demands sign-off at each phase, which gives the clearest milestones and the latest feedback. Feasibility asks four questions: can it be built, does it pay, is it lawful, and will operations cope. The requirements specification is produced in analysis, states functional and non-functional needs, and then serves both as the start of design and the yardstick at acceptance. Ten items follow, four of them requiring person-days, payback and total cost of ownership to be computed.
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 | Basics (10 items) |
02 Questions (10 items)
- FoundationWhich five phases make up the systems development life cycle (SDLC)?
- FoundationWhat is the most typical feature of the waterfall model?
- FoundationWhich four areas does a feasibility study normally assess?
- IntermediateIn which phase is the software requirements specification produced, and which two kinds of requirement does it state?
- IntermediateA project totals 200 person-days, with implementation at 35 percent and testing at 15 percent. How many person-days does each take?
- IntermediateOf a 120 working-day schedule, testing takes 15 percent; cutting it to 10 percent saves how many days?
- ChallengeDevelopment costs $480,000 and saves $160,000 a year. What is the payback period and the five-year net benefit?
- ChallengeThree-year total cost of ownership: hardware $60,000, licence $24,000 a year, staff $180,000, and maintenance at 12 percent of the $240,000 development cost each year. What is the total?
- Challenge6 people work 25 working days. How many person-days is that, and how many days would 5 people need?
- Error redoWho runs and signs off user acceptance testing, and which tests belong to the development team?
03 Answers and one-line notes
| # | Answer | One-line note |
|---|---|---|
| 1 | Analysis, design, implementation (coding), testing, and maintenance (including evaluation). | The five phases are the skeleton; every model orders work along them, only the cycling differs. |
| 2 | Phases proceed in sequence, each signed off before the next begins; late changes force earlier phases to be redone at the highest cost. | Waterfall gives clear milestones but delivers feedback too late. |
| 3 | Technical, economic, legal and compliance, and operational feasibility including schedule. | Economic feasibility weighs benefits against costs, not just the quoted price. |
| 4 | It is produced in the analysis phase and states functional requirements plus non-functional requirements such as performance, security and usability. | The SRS is both the starting point of design and the yardstick at acceptance; a missing item becomes a dispute later. |
| 5 | Implementation takes 70 person-days and testing 30 person-days. | Multiply by the percentages first; together they account for half the effort. |
| 6 | From 18 days down to 12 days, saving 6 days. | Compressed testing means less verification coverage; the days saved must be paid back from a risk budget. |
| 7 | Payback is 3.0 years; the five-year net benefit is $320,000. | Payback is cost divided by annual saving, and the net figure must deduct the investment. |
| 8 | The total is $398,400. | Total cost of ownership covers the whole holding period, not just the purchase price. |
| 9 | 150 person-days, so 5 people need 30 working days. | Person-days stay fixed, so people and days move in opposite directions. |
| 10 | Users or customer representatives run and sign off UAT; the development team owns unit, integration and system testing. | UAT asks whether the system suits the business, not whether the code has bugs. |
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.



