中文（繁體）
中文（简体）
English
S5 ICT | System Development Life Cycle Practice Paper 1
S5 ICT | System Development Life Cycle Practice Paper 1
Paper 1 starts with the five stages, covering Waterfall traits, requirements, acceptance testing and conversion trade-offs.
Attempt first, mark afterwards Allow about twenty-five minutes; name the stages before ordering them rather than memorising initials.
01 Paper details (check answers afterwards)
| Item | Detail |
|---|---|
| Questions | 10 items |
| Suggested time | About 25 minutes |
| Difficulty mix | Foundation 4 · Intermediate 3 · Challenge 2 · Error redo 1 |
| Chapter | Chapter: S5 ICT | System Development Life Cycle Tutor Prep Guide |
| Level | S5 (Secondary 5) ICT |
02 Questions (10 items)
- FoundationWhat are the five main stages of the system development life cycle?
- FoundationWhat is the clearest characteristic of the Waterfall model?
- FoundationWhat is the main deliverable of the system analysis stage?
- FoundationWhich test has real users check the system against genuine business scenarios?
- IntermediateExamining whether development and running costs are lower than expected benefits is which type of feasibility?
- IntermediateWhen is prototyping most suitable?
- IntermediateWhich stage of the system life cycle usually takes the largest share of total cost?
- ChallengeWhat is the main trade-off between parallel conversion and direct cutover?
- ChallengeA project runs 12 weeks with the last 4 weeks for testing and deployment; at 5 working days per week, how many working days are left for development?
- Error redoA student claims unit testing is done by users; what is the correct division of testing work?
03 Answers and one-line notes
| # | Answer | One-line note |
|---|---|---|
| 1 | Feasibility study, system analysis, system design, implementation, maintenance and review | Names vary by methodology, but the order always runs from understanding to long-term upkeep. |
| 2 | Each stage must finish before the next starts, so late changes cost far more | The output of each stage is frozen, which pushes problems into later stages. |
| 3 | A requirements specification covering functional and non-functional requirements | The specification is the shared basis for design and acceptance testing. |
| 4 | User acceptance testing (UAT) | Users run UAT, while developers carry out unit and integration testing. |
| 5 | Economic feasibility | Economic feasibility weighs costs against benefits, while technical feasibility asks whether the technology and staff can deliver. |
| 6 | When users cannot state requirements clearly, an operational prototype confirms them step by step | A prototype lets users react to something concrete, cutting late rework. |
| 7 | The maintenance stage | Maintenance often exceeds half of total cost, so maintainability matters at design time. |
| 8 | Parallel conversion is low risk but costly, while direct cutover is cheaper but riskier | Parallel running means two systems live at once, raising staffing and licence costs. |
| 9 | 40 working days | 12 minus 4 leaves 8 weeks, and 8 times 5 gives 40 working days. |
| 10 | Developers run unit and integration tests; users run acceptance testing | Each test level has its own owner, and mixing them up loses the acceptance check. |
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.
Need a tutor for this chapter? Register hereTutor 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.