/en-tutor-prep-s6-ict-system-maintenance-documentation-practice-3/
/en-tutor-prep-s6-ict-system-maintenance-documentation-practice-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

S6 ICT: system maintenance and documentation (challenge)

S6 ICT: system maintenance and documentation (challenge)

  • 2026-11-20

S6 ICT: system maintenance and documentation (challenge)

Third paper: the price of each extra nine, log capacity, rewrite payback, technical debt and documentation coverage.

Challenge: availability, capacity and maintenance economics Every nine of availability costs money. 99.9 percent allows 525.6 minutes down a year, 99.99 percent only 52.6, and 99.999 percent 5.26. Capacity follows the same logic: at 200 events a second of 300 bytes each, a day of logs is 5.18 GB, thirty days is 155.4 GB, and 4:1 compression brings it to 38.85 GB. Maintenance decisions are economic: a 600,000 rewrite saving 180,000 a year pays back in 3.33 years; forty debt defects at six hours and 500 an hour cost 120,000 in interest; and 340 documented modules out of 400 is 85 percent coverage with sixty missing.

01 Paper details (check answers afterwards)

Item Detail
Questions 10
Suggested time 25
Difficulty mix Foundation 4 · Intermediate 2 · Challenge 2 · Error redo 2
Chapter Chapter: S6 ICT: System maintenance and documentation
Level Challenge (10 items)

02 Questions (10 items)

  1. FoundationConvert 99.9, 99.99 and 99.999 percent availability into yearly downtime.
  2. FoundationAt 200 events a second and 300 bytes each, how large is one day of logs, and thirty days?
  3. FoundationCompressed at 4:1, how large do those thirty days of logs become?
  4. FoundationA rewrite costs 600,000 and saves 180,000 a year in maintenance. What is the payback period?
  5. IntermediateForty technical debt defects at six hours each and 500 per hour: what is the total cost?
  6. IntermediateWith 340 of 400 modules documented, what is the coverage, and how many are missing?
  7. ChallengeChanging five percent of 50,000 lines at forty lines per person-day: how many person-days?
  8. ChallengeDowntime costs 1,200 an hour; at 99.9 percent availability, what is the yearly loss?
  9. Error redoWhy do teams fear upgrading a legacy system, and how does technical debt interest show?
  10. Error redoHow do maintenance testing and acceptance testing divide the work, and why is regression testing critical?

03 Answers and one-line notes

# Answer One-line note
1 525.6 minutes (8.76 hours), 52.6 minutes, and 5.26 minutes. Each extra nine cuts downtime by an order of magnitude and raises cost a tier.
2 One day is 5,184,000,000 bytes, or 5.18 GB; thirty days is 155.4 GB. Log capacity comes from event rate times bytes times 86,400 seconds, never from guesswork.
3 38.85 GB, from 155.4 divided by four. A compression ratio is an assumption to record in capacity planning and verify regularly.
4 3.33 years, from 600,000 divided by 180,000. Compare payback with remaining life; only a payback shorter than that justifies a rewrite.
5 120,000, from forty times six times five hundred. Turning interest into money is what lets management prioritise.
6 85.0 percent, with 60 modules still undocumented (15 percent). Coverage counts modules, not pages.
7 2,500 lines changed, needing 63 person-days after rounding 62.5 up. Maintenance effort must be in person-days to compare with team capacity.
8 10,512, from 8.76 hours times 1,200. Pricing downtime is what gives availability investment a benchmark.
9 Nobody knows every dependency, so one change triggers cascading faults; the interest shows as rising hours, test scope and defect rate per change. Fear of upgrading is a symptom; the cause is years of thin documentation and testing.
10 Acceptance testing confirms user requirements and is signed off by users; maintenance testing runs unit and integration checks on the change, and regression testing proves old features still work. The biggest risk in a maintenance change is not the new feature but old features breaking.

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 four maintenance types, availability and MTTR conversions, plus RTO, RPO, backup maths and documentation coverage all settled? Book a TutorZone tutor and work through every figure 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.

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