/en-tutor-prep-s6-ict-system-maintenance-documentation-practice-1/
/en-tutor-prep-s6-ict-system-maintenance-documentation-practice-1/
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 (basics)

S6 ICT: system maintenance and documentation (basics)

  • 2026-11-20

S6 ICT: system maintenance and documentation (basics)

First paper builds the base: four maintenance types, maintenance cost share, the 3-2-1 backup rule, version numbering and user documentation.

Basics: maintenance types and documentation Maintenance is not only repair on failure. The four types each have a purpose: corrective fixes faults, adaptive follows the environment, perfective adds value, preventive cuts future failures, and they total exactly 100 percent, with maintenance taking 300,000 of a 500,000 lifecycle cost. Documentation and backup are the two legs: the 3-2-1 rule protects data, 1.4.9 is followed by 1.4.10 and not 1.5.0, and fifteen percent of a 120-page manual is 18 pages.

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 Basics (10 items)

02 Questions (10 items)

  1. FoundationWhich four types of system maintenance are normally recognised?
  2. FoundationOver a whole system lifecycle, roughly what share of total cost is maintenance?
  3. FoundationHow does perfective maintenance differ from corrective maintenance?
  4. FoundationWhat does the 3-2-1 rule for backup mean?
  5. IntermediateAfter fixing one bug, what should version 2.4.1 become?
  6. IntermediateAt 99.5 percent availability, how many hours a year may a system be down out of 8,760?
  7. ChallengeWith MTBF of 2,000 hours and MTTR of 4 hours, what is the availability?
  8. ChallengeWhat are user documentation and system documentation for?
  9. Error redoHow should a change request be handled?
  10. Error redoA 120-page user manual needs fifteen percent of its pages updated. How many pages is that?

03 Answers and one-line notes

# Answer One-line note
1 Corrective (fixing faults), adaptive (environment or requirement change), perfective (new features or efficiency), and preventive (improving reliability ahead of failure). The four types are split by purpose, not by who does them; only clear classification allows a maintenance budget.
2 About sixty percent. On a lifecycle total of 500,000, maintenance takes 300,000 and development 200,000. Maintenance runs longest, so its total often exceeds development.
3 Corrective maintenance repairs existing faults; perfective maintenance adds features or makes a working system faster and easier to use. Perfective work is about fifteen percent of the load: improvement, not rescue.
4 At least three copies of the data, on two different media or systems, with one copy off site or offline. The rule attacks one risk: a single medium, site or account must never be the only copy.
5 2.4.2. A bug fix bumps only the last digit; a new feature bumps the middle to 2.5.0; a breaking change bumps the first to 3.0.0. Version numbers exist so a maintainer can see the size of a change at a glance.
6 43.8 hours, which is 8,760 multiplied by 0.5 percent. Converting to hours is what tells you whether 99.5 percent is loose or strict.
7 99.80 percent, from 2,000 divided by 2,004. Availability is MTBF over MTBF plus MTTR, never MTBF alone.
8 User documentation teaches operation: manuals and online help. System documentation serves maintenance: architecture diagrams, data dictionary, install and restore steps. Different readers; missing either one makes the system hard to maintain.
9 Log it with an identifier, assess impact and cost, prioritise, change only after approval, then update documents, version number and the record. A change with no identifier is untraceable technical debt.
10 18 pages, from 120 multiplied by fifteen percent. Documentation updates need budgeted hours, or the manual lags at every release.

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 →