/en-tutor-prep-s6-ict-system-development-lifecycle-practice-3/
/en-tutor-prep-s6-ict-system-development-lifecycle-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 development life cycle (challenge)

S6 ICT: system development life cycle (challenge)

  • 2026-11-20

S6 ICT: system development life cycle (challenge)

Challenge: COCOMO, function points, defect removal efficiency, availability, risk exposure and earned value.

Challenge: estimation, metrics and earned value Managing a project takes numbers, not feelings. COCOMO estimates effort from size, and an exponent above one means doubling size more than doubles effort; function points weight five component types and adjust them with fourteen factors. Quality is measured by defect removal efficiency, availability and coverage; risk ranks by probability times impact, so a total exposure of 130,000 is the buffer to hold. Earned value puts schedule and cost on one sheet: SPI 0.80 with CPI 0.89 means late and over budget at once, so 562,500 is the honest forecast of the final cost.

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

02 Questions (10 items)

  1. FoundationIn basic organic COCOMO with E = 2.4 times KLOC to the power 1.05, what effort in person-months does a 10 KLOC project need?
  2. FoundationFor the same project, D = 2.5 times E to the power 0.38. What duration does that give?
  3. FoundationFunction points: 6 external inputs at 4 each, 4 external outputs at 5, 3 queries at 4, 3 internal logical files at 10 and 2 external interface files at 7. What is the UFP, and the AFP at TDI 42?
  4. IntermediateTesting finds 200 defects and 40 escape to production. What is the defect removal efficiency?
  5. IntermediateWith MTBF of 4,000 hours and MTTR of 2 hours, what is availability?
  6. IntermediateThree risks: probability 0.3 with a $200,000 impact, 0.1 with $500,000, and 0.5 with $40,000. What is total risk exposure?
  7. ChallengeWith PV $200,000, EV $160,000, AC $180,000 and BAC $500,000, what are SPI, CPI and EAC?
  8. ChallengeA flow graph has 12 edges, 10 nodes and 1 connected component. What is the cyclomatic complexity?
  9. ChallengeA system has 1,200 statements and tests execute 1,020 of them. What is statement coverage?
  10. Error redoA team writes 24,000 lines in 120 person-days. What is the productivity per person-day, and the effort for 30,000 lines?

03 Answers and one-line notes

# Answer One-line note
1 E is 2.4 times 10 to the power 1.05, about 26.9 person-months. An exponent above one means effort grows faster than size; double the size is more than double the work.
2 D is about 8.7 months. Duration is not proportional to effort; adding people shortens schedules only up to a point.
3 UFP is 100 and AFP is 107.0. The adjustment factor stays between 0.65 and 1.35 and cannot be stretched at will.
4 DRE is 200 divided by 240, about 83.3 percent. The denominator is total defects including escapes, not just those found.
5 Availability is 4,000 divided by 4,002, about 99.95 percent. Availability is a time ratio, not a claim that failures are rare.
6 The total is $130,000. Risk exposure multiplies probability by impact to rank risks, not to forecast the actual loss.
7 SPI is 0.80, CPI is 0.89 and EAC is $562,500. Both indices below one mean late and over budget; EAC projects the final cost through CPI.
8 CC is 12 minus 10 plus 2, that is 4. Cyclomatic complexity equals the number of independent paths, hence the minimum tests for branch coverage.
9 1,020 divided by 1,200 gives 85.0 percent. Coverage can never exceed 100 percent; above that means the denominator is wrong.
10 200 lines per person-day, so 30,000 lines need 150 person-days. Compare productivity within one team and language; lines of code across languages mean nothing.

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.

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