/en-tutor-prep-s5-ict-system-development-life-cycle-practice-4/
/en-tutor-prep-s5-ict-system-development-life-cycle-practice-4/
英文版
3
General Inquiry: info@TutorZone.com.hk
Office Hours: Monday to Saturday - 9:00 AM to 6:00 PM
WhatsApp Monday to Sunday - 24 hours
Hotline: +852 6828 1809
Instant Support: +852 9061 3106

S5 ICT | System Development Life Cycle Practice Paper 4 (Error Rework)

S5 ICT | System Development Life Cycle Practice Paper 4 (Error Rework)

  • 2026-11-03

S5 ICT | System Development Life Cycle Practice Paper 4 (Error Rework)

Paper 4 reworks the traps from the first three papers: stage ownership, Waterfall rework cost, the four kinds of maintenance, acceptance meaning, the two feasibilities, and four calculations on schedule, load, expected value and total cost.

Attempt first, mark afterwards Allow about thirty minutes; state the stage or the formula before the answer, and label each slip as concept, sequence or arithmetic.

01 Paper details (check answers afterwards)

Item Detail
Questions 10 items
Suggested time About 30 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)

  1. FoundationCoding and unit testing belong to which stage of the system development life cycle?
  2. FoundationWhy is a requirements error found in the third stage of a Waterfall project so costly?
  3. FoundationWhich four kinds of work does system maintenance cover?
  4. FoundationWhat has been established once user acceptance testing passes?
  5. IntermediateWhich question does technical feasibility answer, and which does economic feasibility answer?
  6. IntermediateA project runs 20 weeks, with the last 6 weeks for testing and deployment; at 5 working days per week, how many working days remain for development?
  7. IntermediateA system handles 15,000 transactions a day and a four-hour peak carries 60 percent of the load; what is the average per hour at peak?
  8. ChallengeDirect cutover fails with probability 15 percent and would cost 300,000 dollars; extra parallel running costs 30,000 dollars. Which should be chosen on expected value?
  9. ChallengeOn-premise servers cost 24,000 dollars a year plus 80,000 dollars upfront; cloud costs 2,400 dollars a month. What is the four-year difference?
  10. Error redoA student says agile development needs no documentation; what is the correct view?

03 Answers and one-line notes

# Answer One-line note
1 The implementation stage, covering coding and testing Analysis says what must be done and design says how; implementation is where code is written and tested.
2 The earlier analysis and design work must be redone, and every later stage returns to the start Each stage output is frozen, so the later the discovery, the wider the rework.
3 Corrective, adaptive, perfective and preventive maintenance All four happen after go-live: fixing faults, matching environment changes, improving, and servicing ahead of failure.
4 Users have confirmed the system works in real business scenarios and can go live as planned Users run acceptance testing, and passing it hands responsibility from the build team to operations.
5 Technical feasibility asks whether current technology and staff can deliver it; economic feasibility asks whether benefits exceed costs Both must pass: feasible but unaffordable, or affordable but impossible, are both reasons not to start.
6 70 working days 20 minus 6 leaves 14 weeks, and 14 times 5 gives 70 working days.
7 2,250 transactions 15,000 times 0.6 gives 9,000, and dividing by four hours gives 2,250 per hour.
8 Parallel running, since the expected loss of 45,000 dollars exceeds the extra 30,000 dollars The expected loss is 300,000 times 0.15, which is 45,000 dollars and above the parallel cost.
9 On-premise 176,000 dollars against cloud 115,200 dollars, so on-premise is 60,800 dollars higher On-premise is 24,000 times four plus 80,000, cloud is 2,400 times twelve times four, and the two are subtracted.
10 Agile still documents, but keeps it as lean as needed and favours working software and continuous communication The agile manifesto values working software over exhaustive documentation, which does not mean no documentation at all.

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.

Join as a tutor or coach — academic, music, sports, arts, STEM. Free to register. See how it works →