Secondary 4 Computing develops the ability to understand computer systems, organise information and construct solutions that work. For the 2027 Singapore–Cambridge Secondary Education Certificate (SEC), identify the subject as G1 K127, G2 K237 or G3 K349. SEAB’s G1, G2 and G3 directories distinguish these entries. This eduKate Punggol curriculum guide helps parents connect the correct syllabus with what their child needs to understand, produce and explain.
Begin with the registered subject level, the school’s current topic and one piece of work the student completed independently. Then check whether the difficulty lies in understanding a concept, planning a solution, using the software or checking the result. Secondary 4 learning includes strengthening earlier upper-secondary knowledge. A useful plan therefore connects the course as a whole with the next manageable learning step.
- Confirm the course: match the year, level and code before choosing materials.
- Understand the tools: block programming and Python require different preparation.
- Look for reasoning: ask what goes in, what changes and what should come out.
- Check behaviour: alter a value or requirement and see whether the solution still works.
- Keep concepts and practical work together: a polished file needs a sound explanation.
- Choose support from the evidence: identify the precise difficulty before adding more lessons.
EDUKATE PUNGGOL · SECONDARY 4
Find your next learning step
Choose the route closest to your child’s current need, or open the chapter index below.
- Identify the course · Match the level, scope and signs of understanding. Chapters 1–3.
- Understand systems and algorithms · Connect systems, data and solution planning. Chapters 4–7.
- Follow the programming · Trace, explain and test level-appropriate programs. Chapters 8–11.
- Use data and media responsibly · Check formulas, outputs and responsible use. Chapters 12–14.
- Assess, plan and choose support · Understand the papers and choose the next learning step. Chapters 15–18.
Open the chapter index · Explore the eduKate Punggol learning library
Checked on 21 November 2026 for school candidates taking the 2027 examination. Schools determine their teaching sequence and communicate the approved examination arrangements. All scenarios, datasets, programs and learning activities below are original teaching examples, not official examination questions, real school records or predictions.
Chapter index
Chapters 1–3 · Identify the course
Chapters 4–7 · Understand systems and algorithms
Chapters 8–11 · Follow the programming
Chapters 12–14 · Use data and media responsibly
Chapters 15–18 · Assess, plan and choose support
CHAPTER 1 OF 18 · Identify the course
1. Understand the course name and the three levels
MOE is the Ministry of Education; SEAB is the Singapore Examinations and Assessment Board. SEAB’s SEC explanation confirms the first SEC examination in 2027 and says that certification records subjects at their respective levels. For a school candidate, the school is the starting point for confirming the registered subject.
The current directories call the subject Computing at all three levels and list the G1 and G2 entries as new. An older Computer Applications resource may contain a useful explanation, but its title alone cannot establish that it matches this course. Check the actual topic and task against the current specification before using it as a revision checklist.
These names are becoming more visible during a curriculum transition. An official school curriculum page describes Computing at G1, G2 and G3 from upper secondary in 2026. This provides a concrete reason for families to encounter new terminology; it does not establish that a particular level is suddenly more popular or suitable for every child.
Keep a small course record: examination year, subject code, school materials, software used in lessons and current assessment scope. Add the teacher’s latest feedback. This record makes a conversation with a teacher or tutor more productive because everyone can discuss the same course and the same demonstrated need.
Read this map alongside the official G1 K127, G2 K237 and G3 K349 syllabuses. Each document contains the detailed learning outcomes and assessment specification. The table identifies the main differences; it is not an instruction to study every level.
| Entry | Curriculum map | Programming distinction |
|---|---|---|
| G1 K127 | Computer fundamentals; networking; impact of computing; document processing; spreadsheets; media software; programming. | Scratch, including game programming. |
| G2 K237 | Computer fundamentals; networking; impact of computing; spreadsheets; media software; programming. | Scratch and MakeCode; lists/arrays, custom blocks and microcontrollers. Microcontrollers and listed MakeCode blocks are Paper 1 only. |
| G3 K349 | Computer fundamentals; algorithms and programming; spreadsheets; networking; impact of computing. | Python, including strings, lists, dictionaries, functions, files, validation and testing; JupyterLab for the practical paper. |
Notice the different shape of the courses. G1 includes a separate document-processing module. G2’s programming is visual and includes physical-computing reasoning. G3 develops text programming alongside a more formal treatment of systems and data. A generic coding course may be interesting while covering only part of the student’s assessed needs.
For a parent, the best use of this map is to organise school work into a few visible categories. Place a spreadsheet exercise with spreadsheets, a network explanation with systems, and a program with its plan and tests. An empty category then becomes a question to investigate rather than an assumption that the student has already mastered it.
A topic can also connect several categories. A booking system stores data, makes decisions, communicates information and has users. The subject becomes easier to understand when those connections are explicit. Nevertheless, the school’s level-specific checklist remains the guide to what the student must learn.
A useful Computing explanation follows a requirement through to an observable result. Suppose a fictional workshop needs to know whether a session has space. The student should identify the number of registrations and the number of available places, explain the comparison and state the message that should appear. Clicking the right menu is only one part of this chain.
Ask for a prediction before a demonstration
Before running a program or recalculating a sheet, ask the student to predict the result for a small input. If there are twenty places and eighteen registrations, two places remain. If registrations rise to twenty-four, the session is over capacity by four. The student should explain that change before seeing the software produce it.
Then change the question. Perhaps the organiser wants the total registrations across all sessions, or wants to identify individual sessions needing attention. These are different outputs. A correct total does not automatically answer a question about each session. Recognising the required output is an important part of planning.
Look for independence at a sensible scale
A student does not need to build a large application to show progress. They might explain one condition, correct one copied formula, choose a meaningful test or improve a short document to meet a brief. Record the specific action they can now perform without prompting.
When work was completed with help, ask the student to repeat a small related task after the example is closed. This is a practical way to check transfer. If they struggle, return to the missing step without treating the earlier assisted success as wasted effort. It has identified where support is still needed.
Parents can help by asking clear questions and listening to the reasoning. They need not become the programmer or complete the file. The useful evidence is the student’s own explanation, decision and correction.
CHAPTER 4 OF 18 · Understand systems and algorithms
4. Connect hardware and software with a purpose
Consider a fictional workshop kiosk that records attendance. A keyboard or scanner supplies input; a program processes the entry; a screen displays a response; a saved file retains the record. The purpose helps distinguish these roles. A device’s appearance is less useful than an explanation of what it does in the system.
Now imagine the application closes before the updated record is saved. The screen may previously have shown the new attendance, yet the reopened file may lack that change. This thought exercise helps separate work currently being processed from a retained record. Ask the student to describe the sequence rather than rely on a vague statement that the computer “remembers everything”.
Compare a specification against the job
Suppose one proposed arrangement provides a clear display but an awkward input method. Another makes entry easy but gives staff no useful confirmation. Neither should be judged only by its largest advertised number. Define the task, identify the relevant requirement and explain how the proposed arrangement meets it.
The same reasoning applies to software. A spreadsheet may suit a small table with repeated calculations; a program may suit a more specific sequence of decisions. A presentation can communicate a process, but it does not automatically implement that process. Ask what the output needs to do after it has been created.
An effective response links the choice to the scenario. “Use a scanner” becomes more useful when the student explains what is scanned, how the identifier is checked and what happens when it is absent from the records. These connections show understanding beyond recognising a device name.
CHAPTER 5 OF 18 · Understand systems and algorithms
5. For G3, make representations and logic meaningful
The G3 specification includes binary and hexadecimal representation, two’s complement, Boolean logic and gates. Parents can recognise useful practice by looking for an explanation of what a representation means, rather than a string of unexplained conversions.
Follow the value through different representations
In an original example, the positive integer 58 is written as 00111010 in eight-bit binary: 32 + 16 + 8 + 2 = 58. Grouping the bits into 0011 and 1010 gives hexadecimal 3A. The value remains the same while its notation changes.
Now interpret 11111010 as an eight-bit two’s-complement number. The place values give −128 + 64 + 32 + 16 + 8 + 2 = −6. As an unsigned eight-bit integer, the same pattern represents 250. The specified interpretation matters. A student who states the format before calculating is less likely to combine two incompatible rules.
Translate a requirement into a logical condition
Suppose an interface should display a selection indicator when exactly one of two options is chosen. Call the options A and B. The indicator is off when neither is selected, on when only A is selected, on when only B is selected, and off when both are selected. That is the behaviour of exclusive OR.
Ask the student to compare the last case with ordinary OR. Both options being selected satisfies OR but does not satisfy “exactly one”. The difference comes from the requirement’s wording. Drawing a correct symbol without checking that wording can still produce the wrong system.
Keep units equally explicit. A hypothetical uncompressed record containing 600 one-byte entries uses 600 bytes for those entries. If a task adds a header, index or other overhead, include the stated extra amount. Do not quietly invent overhead or disregard a specified unit convention. The calculation should remain traceable to the problem.
CHAPTER 6 OF 18 · Understand systems and algorithms
6. Explain connections, access and protection
Networking becomes clearer when the student follows a particular piece of information. Imagine a workshop organiser editing a booking list while a colleague checks it from another device. Ask where the file is stored, which device is requesting it and what connection is needed. The answers describe the system more usefully than a collection of isolated terms.
The G1 and G2 specifications include local and cloud storage concepts. The G3 specification extends networking to architectures, addressing, protocols and transmission-error checks. Select the explanation depth appropriate to the child’s course.
Separate a connection problem from a data problem
If the colleague sees an old copy, several explanations are possible. They might have opened a different file, an update might not have been saved, or the required connection might be unavailable. Identify what was observed before choosing a remedy. Repeatedly restarting a device does not explain which possibility caused the problem.
A small diagram on paper can help: label the devices, identify the stored record and draw the direction of the request and response. Then remove one connection in the imagined system. Which action would stop working, and which local work could continue? The explanation should follow the proposed arrangement.
Match a safeguard to the problem
Suppose the concern is accidental editing of a shared list. Ask which users need to view it and which need to change it. If the concern is losing the only copy, ask how an earlier usable copy could be recovered. These are different problems and require different reasoning.
For a written response, name the threatened information or operation, explain the relevant mechanism and state its practical limit. “Make it secure” is an intention. Explaining how a particular control addresses a particular problem shows a more complete understanding.
CHAPTER 7 OF 18 · Understand systems and algorithms
7. Turn a request into an algorithm
An algorithm is a precise sequence of steps for solving a defined problem. Begin in ordinary language. For the fictional workshop, a request might be: “For each session, show whether registrations exceed places.” The word “each” matters because the program must consider the sessions separately.
Define inputs, processing and outputs
Inputs are registrations and capacity for a session. Processing compares them. Output reports whether the session needs review. State assumptions too: in this example, both inputs are whole numbers, registrations cannot be negative and capacity must be positive. These choices belong to the invented problem, not to a universal rule about every program.
A workable plan is: read one session; compare registrations with capacity; produce the corresponding message; repeat for the remaining sessions. This separates sequence, selection and repetition. The student can trace the plan with two sessions before translating it into the language used in class.
For a session with twenty registrations and twenty places, the output should remain “Within capacity” because the rule says exceeds. Writing a greater-than-or-equal comparison would answer a different requirement. The small boundary case can reveal a misunderstanding before the student spends time building an interface.
Decompose without losing the whole task
Separate obtaining data, checking it, making a decision and presenting the result. Then reconnect those parts. A correct decision routine cannot compensate for reading the wrong column; attractive output cannot compensate for a missing session. Each part needs a clear role and a clear handover.
A flowchart or short written plan should help someone follow the logic. Ask where the process begins, how a branch is chosen, what repeats and when it finishes. Decorative complexity is unnecessary. If the explanation becomes difficult to follow, reduce the example to fewer records and rebuild the sequence.
When a requirement changes, revise the plan before editing scattered instructions. For example, asking for the number of over-capacity sessions requires a count as well as individual decisions. The new output should be visible in the design.
CHAPTER 8 OF 18 · Follow the programming
8. For G1, understand events, state and repetition
G1’s Scratch scope includes variables, conditions and loops; nested if instructions are excluded. The Scratch Foundation’s introductory resources offer a guide and tutorials for becoming familiar with the platform. The learning goal is to connect instructions to predictable behaviour.
Original activity: a gallery guide moves to a destination
Imagine a guide sprite that begins at x = −120 and y = 0. On the start event, place it there. Repeat the following movement six times: change x by 40, then wait briefly so the movement is visible. Afterwards, show “Arrived” if x is greater than 100; otherwise show “Continue”. These are plain-language instructions for an original block-programming exercise.
The successive x positions are −80, −40, 0, 40, 80 and 120. The final position satisfies the defined destination-zone condition. Before running the project, ask the student to predict the last position and the message. The arithmetic and condition should explain the animation.
Now change the movement amount to 20 while retaining six repetitions. The final x position becomes 0, so the message is “Continue”. The program has followed the revised instructions correctly; the revised instructions no longer take the guide into the destination zone. This separates a software failure from a design that does not meet the intended outcome.
Check the beginning as well as the ending
Restart the activity. If the starting position is not restored, the next run may begin from the previous endpoint. Ask which instruction establishes the initial state. The same habit applies to a displayed count, a costume, a backdrop or a visibility setting.
Keep one change visible at a time. Add a sound or another sprite only after the movement and message behave as intended. The student should be able to explain which event starts each script. That explanation makes it easier to investigate behaviour when several scripts are active.
Parents can use three questions: Where does it start? Which instruction changes it? What condition decides the outcome? Those questions remain useful even when the family has never built a Scratch project before.
CHAPTER 9 OF 18 · Follow the programming
9. For G2, connect block programs with physical systems
The G2 syllabus adds list/array operations and functions or custom blocks, and includes microcontroller prototypes. Its microcontroller outcomes and listed MakeCode blocks are assessed in Paper 1 only. Do not turn that curriculum component into an assumption that Paper 2 requires building a physical device.
Original model: a workshop help-request counter
Imagine a counter for a supervised workshop. One recorded button A event adds one waiting request. One recorded button B event removes one request, but only if the count is above zero. The display shows the current count. Start at zero. This is a conceptual prototype for explaining input, stored state, decisions and output.
For the event sequence A, A, B, B, B, the displayed counts should be 1, 2, 1, 0 and 0. The final event must not produce −1. The condition before subtraction represents the requirement that this model cannot have a negative number of waiting requests.
The official MakeCode button-event reference explains how button events can trigger a handler. In a real class activity, use the teacher’s specified blocks and arrangement. Our trace describes recorded events; it does not assume that every physical press is automatically a valid new request from a different person.
Improve the model by examining what it leaves out
If the same person presses A twice, the counter cannot identify the duplicate. It stores a quantity, not a set of named requests. Ask what additional information would be needed to distinguish people, and whether collecting that information is necessary for the proposed task. This is a design question before it becomes a programming question.
A list could represent separate requests in a different version of the problem. A custom block could group instructions that are repeated together. Neither feature should be added merely to make the project look advanced. Explain the need it serves and how its behaviour will be checked.
Finally, change the requirement: perhaps the display must show both waiting requests and completed requests. The model now needs two quantities with different meanings. Ask which event changes each quantity and what should happen on restart. This makes the connection between a practical need and a program’s internal state visible.
CHAPTER 10 OF 18 · Follow the programming
10. For G3, connect code with the result it must calculate
Python code should express a plan that the student can explain. The official Python control-flow tutorial explains selection, repetition and functions. Use those ideas within the school’s syllabus scope. A working answer becomes more convincing when the student can trace it and adapt it to a changed requirement.
Original program: the longest qualifying sequence
A fictional equipment desk records daily loan counts. We want the longest consecutive run of days with at least eight loans. The supplied counts are 7, 9, 10, 4, 8, 8, 9 and 3. This is a run-length problem: qualifying days separated by a lower count do not belong to the same run.
def longest_run(counts, threshold):
current = 0
best = 0
for count in counts:
if count >= threshold:
current = current + 1
if current > best:
best = current
else:
current = 0
return best
print(longest_run([7, 9, 10, 4, 8, 8, 9, 3], 8))
The output is 3. The first qualifying run contains 9 and 10, so its length is two. The count of 4 ends that run. Later, 8, 8 and 9 form a run of three. The final 3 ends the current run without erasing the best run already found.
current answers “How long is the run ending here?” while best answers “What is the longest run seen so far?” Those are different questions. If a student can explain why the two variables are needed, they understand more than the appearance of the code.
Trace the state and define the input contract
After each supplied count, current is 0, 1, 2, 0, 1, 2, 3 and 0. The corresponding best values are 0, 1, 2, 2, 2, 2, 3 and 3. A hand trace should agree with the program.
This function assumes a supplied list of non-negative whole-number counts and a non-negative whole-number threshold. It does not obtain or validate keyboard text. Under this definition, an empty list returns zero. If a task requires file input or validation, those parts need their own design and checks.
Do not replace the explanation with “Python calculated it”. Ask why the reset occurs in the else branch and why the final result is returned after the loop. Each placement follows from the meaning of the variables.
CHAPTER 11 OF 18 · Follow the programming
11. Use tests that can reveal a particular mistake
Testing is stronger when each example has a purpose. For the longest-run function, a list containing 8 and 8 should return two at threshold eight. It checks that the boundary is included. A list containing 7 and 7 should return zero. It checks that a run does not begin without a qualifying item.
The list 8, 8, 2, 8 should return two. If the student forgets to reset current after the 2, the program may incorrectly report three. This test targets a specific error that a list of entirely qualifying values would not reveal.
Explain the expected result first
Write the input and expected output before running the test. Otherwise, an unexpected result can be accepted simply because the computer produced it. For a longer sequence, use a short trace with the variable values after each item. The trace gives a precise place to compare the plan with the execution.
Distinguish a program that cannot run from one that runs and calculates the wrong answer. A missing colon calls for a different investigation from a misplaced reset. For the latter, inspect how the state changes. Making unrelated edits until the result changes makes the explanation harder to trust.
Correct one identified cause, rerun the failing test, and then rerun a small set of earlier checks. A repair should not quietly damage a case that previously worked. Keep the original failing input as a useful example of why the correction was needed.
Transfer the habit to visual programs and files
The same method applies to the G1 guide sprite and G2 request counter. Restarting checks initialisation; a smaller movement checks the condition; an extra removal event checks the zero boundary. Testing is a way of thinking about behaviour, not a feature limited to text programming.
For a document or spreadsheet, a changed input can be a test too. Add a longer heading, copy a formula down or increase one session’s registrations. Ask whether the intended relationship survives. A file that looks correct only for the original example needs further investigation.
CHAPTER 12 OF 18 · Use data and media responsibly
12. Build a spreadsheet that explains its data
All three syllabuses include spreadsheets. Use the exact function scope for the registered level. The original workshop example below separates recorded data from calculated results. It also shows why a total can conceal a problem affecting individual sessions.
| Row / session in A | B: registrations | C: places | D: spare places | E: expected message |
|---|---|---|---|---|
| 2 / Amber | 18 | 20 | 2 | Within capacity |
| 3 / Birch | 24 | 20 | −4 | Review |
| 4 / Cedar | 15 | 20 | 5 | Within capacity |
| 5 / Delta | 21 | 20 | −1 | Review |
Enter =C2-B2 in D2 and copy down. In E2, enter =IF(D2<0,"Review","Within capacity") and copy down. The negative values identify sessions whose registrations exceed their places. At exactly twenty registrations, the spare count is zero and the message remains “Within capacity”.
=SUM(B2:B5) gives 78 registrations and =SUM(C2:C5) gives 80 places. The overall spare capacity is two, yet Birch and Delta still need review. Places in one session cannot automatically accommodate people registered for another. The calculation is correct; its interpretation requires attention to the arrangement.
Keep the meaning of references clear
Suppose H1 holds a fictional preparation allowance of three minutes per registered participant. In cell G2, =B2*$H$1 gives 54 minutes. Copying down produces 72, 45 and 63 minutes; =SUM(G2:G5) gives 234. The changing row reference selects each session, while the fixed reference retains the common allowance.
Microsoft’s reference guide explains how relative, absolute and mixed references behave when copied. Ask the student to predict the formula in the next row before filling it. A correct numerical result obtained from a typed constant is different from a formula that remains connected to the data.
For an additional check, reduce Birch registrations from 24 to 19. Its spare count becomes one, its message changes to “Within capacity”, total registrations become 73 and total preparation time becomes 219 minutes. Delta still requires review. Restore the original data after completing the test.
Use displays and validation to communicate meaning
An occupancy calculation =B2/C2, formatted as a percentage, gives 90%, 120%, 75% and 105%. Formatting the cell as a percentage does not change the underlying relationship. A value above 100% is meaningful here: registrations exceed places.
A chart should identify whether it compares registrations, capacity or preparation time. A clear title and units help the reader answer the intended question. Sorting should keep each session’s data together. Moving only one column can associate a correct number with the wrong session.
Validation can reject entries outside the stated input rules, but an allowed number may still be inaccurate. Entering eighteen instead of nineteen can pass a whole-number range check. The student should distinguish checking a permitted form from confirming that the information matches its source.
CHAPTER 13 OF 18 · Use data and media responsibly
13. Make documents and media serve the reader
The G1 specification includes document processing. Both G1 and G2 include vector and raster graphics, presentations and video. The practical question for families is whether the output meets its brief and communicates clearly.
Original brief: a repair-workshop instruction sheet
Imagine a one-page sheet that tells participants what to bring, where to report and how to identify their assigned session. The student should establish the information hierarchy before adding decorative elements. A reader must be able to locate the action they need to take.
A useful document check asks whether headings are consistent, a table remains readable, an image supports the explanation and the page still works after a longer session name is inserted. Repeated spaces used as a layout device may fail when text changes. The student should understand the formatting feature they choose.
For a presentation, assign each slide a clear purpose. A process slide might show the order of arrival, registration and preparation. A comparison slide might show two equipment arrangements. Adding every available transition would not make either explanation more complete.
Test the intended output
A graphic should remain usable at its intended size. If text becomes unreadable when the design is reduced, the output needs adjustment even if it looked attractive while being edited. Ask the student to preview it in the form in which a reader will encounter it.
For a short instructional video, plan what each scene contributes. Check whether the viewer can follow the action, whether captions correspond to the scene and whether sound helps rather than competes with the explanation. The quality judgement should follow the brief.
Retain editable work when the task requires it and produce the requested output format. Being able to locate, reopen and revise the correct file is part of making a usable deliverable. Parents can review the brief and ask what evidence shows that each requirement has been met.
CHAPTER 14 OF 18 · Use data and media responsibly
14. Discuss technology through consequences and evidence
Computing decisions affect people. A useful explanation identifies who benefits, who may encounter difficulty and which conditions matter. For the workshop booking system, online registration might simplify organising information while creating a practical barrier for someone who needs another way to register. A design can respond to that need without denying the usefulness of the system.
When discussing information online, separate a claim from evidence supporting it. A widely repeated statement may still depend on one unverified source. Ask what the information actually establishes and what would be needed to check it. This keeps a discussion of technology connected with careful judgement.
For G3, understand a small classification decision
The G3 syllabus includes AI, machine learning and nearest-neighbour classification using two quantitative features. An original simplified example uses two measurements, both in centimetres, to assign a new sample to one of two labelled reference samples.
Reference A has measurements (4, 3); reference B has measurements (8, 9); the new sample is (5, 5). Using ordinary straight-line distance, the squared distance to A is (5 − 4)² + (5 − 3)² = 5. The squared distance to B is (5 − 8)² + (5 − 9)² = 25. The new sample is nearer A, so this one-nearest-neighbour rule assigns A.
That calculation establishes the rule’s output for the supplied examples. It does not prove that the assigned label is correct in every real situation. Different reference examples, missing information or poorly chosen features could change the usefulness of the result. Ask what the measurements represent and why they are relevant.
Explain responsible use as part of the design
A fictional project can use invented records and original graphics. If a student includes another person’s material, they should check the permitted use and acknowledge it as required by the task. Copying a polished asset does not demonstrate the ability to create or explain the underlying work.
Similarly, outside assistance can help a student learn a method, but the student still needs to explain and reproduce the required reasoning. Use school instructions for what assistance is permitted in assessed work. At home, ask for an independent adaptation rather than treating a completed-looking answer as proof of understanding.
CHAPTER 15 OF 18 · Assess, plan and choose support
15. Understand the papers and their weightings
The assessment balance differs by level. These figures come from the linked G1, G2 and G3 specifications. All questions in both papers are compulsory; approved calculators are permitted. Practical saving time is included in Paper 2.
| Entry | Paper 1 | Paper 2 |
|---|---|---|
| G1 K127 | E-examination: 75 minutes, 60 marks, 40%. All modules; 20 MCQ marks and 40 structured-response marks. | Lab: 120 minutes, 90 marks, 60%. Media about 30; documents/spreadsheets about 35; programming about 25 marks. |
| G2 K237 | E-examination: 90 minutes, 70 marks, 50%. All modules; 20 MCQ marks and 50 structured-response marks. | Lab: 135 minutes, 80 marks, 50%. Media about 30; spreadsheets about 25; programming about 25 marks. |
| G3 K349 | Written: 120 minutes, 80 marks, 60%. All modules; mixed question formats. | Lab: 150 minutes, 70 marks, 40%. One spreadsheet question and four or five programming questions; Python quick reference supplied. |
A raw mark total should not be treated as the final weighting. For an invented G2 example, 56/70 in Paper 1 contributes 40 percentage points, while 48/80 in Paper 2 contributes 30 percentage points. The weighted total is 70%. Simply combining the raw marks would answer a different calculation. This example is arithmetic practice, not a predicted grade.
Practise the actual kind of response
An explanation task needs a reason that addresses the question. A lab task needs a correctly completed and saved file. The two can expose different difficulties, so include evidence from both when planning revision. A child who is quick with familiar software may still need help explaining why a solution works.
The specifications make the examination centre responsible for the required facilities and approved software. Confirm the school’s practice environment and instructions rather than inferring a software version or personal-device requirement from an online guide.
During ordinary practice, include time to read the brief, check supplied files, complete the requested work and save it as instructed. Reopen the intended file when checking a home exercise. This turns file handling into a routine part of completion.
Use timed work to investigate a particular difficulty after the method is understood. If the student repeatedly runs out of time, examine where it is spent: interpreting instructions, locating features, correcting logic or finishing files. The remedy depends on the cause.
CHAPTER 16 OF 18 · Assess, plan and choose support
16. Find the next learning need from actual work
Choose a short, recent piece of work and ask the student to explain one decision. The aim is to locate a teachable gap. A broad label such as “weak at Computing” tells the family little about what to do next.
| What you observe | What to check | A useful next activity |
|---|---|---|
| Runs the example but cannot explain it | Meaning of inputs, variables and output | Trace a smaller example aloud, then predict a changed input. |
| Formula works in the first row only | References after copying | Compare the first two formulas and identify what should stay fixed. |
| Program passes familiar data only | Conditions and boundary cases | Choose a case at the exact threshold and one that interrupts the pattern. |
| Attractive file misses the brief | Reading and completion of requirements | Match each requested output to visible evidence in the file. |
| Knows a term but gives a vague explanation | Connection between mechanism and scenario | Explain one action, its effect and a practical limit. |
| Needs frequent prompts to proceed | Independence at each step | Repeat a short related task with the worked example closed. |
Keep a small correction record with the original difficulty, the reason it occurred and one new example completed successfully. “Forgot a formula” is less informative than “used a relative reference for a value that should remain fixed”. The second description suggests a precise repair.
A single error should not become a permanent judgement about the child. Look for patterns across tasks. If several errors share the same cause, a short explanation of that cause may be more useful than completing another long worksheet with the same misunderstanding.
Check whether support is changing the behaviour
After teaching, return to a fresh example. The student should be able to explain the relevant idea with less prompting. If the same obstacle remains, adjust the example, representation or pace. More minutes are not automatically more useful if they repeat an explanation the student has not understood.
Share the actual work with the subject teacher when clarification is needed. A screenshot of the formula, a short program and the expected output, or an annotated brief gives the teacher something concrete to examine. This makes the conversation easier than a general report that the subject feels difficult.
CHAPTER 17 OF 18 · Assess, plan and choose support
17. Build a four-week cycle across concepts and practical work
Use this as an adaptable learning cycle, not a compulsory timetable. Select tasks from the school’s current scope and the difficulty identified in Chapter 16. Keep conceptual explanation and practical production visible throughout the month.
| Week | Learning focus | Evidence to keep |
|---|---|---|
| 1 | Confirm the course record. Review one concept response and one practical task. Choose one recurring difficulty. | A clear starting example and a specific explanation of the gap. |
| 2 | Rebuild the method using small examples. Practise the level’s appropriate tool and explain each important step. | A corrected example plus a successful changed-input check. |
| 3 | Combine related skills in a fresh task. Include planning, checking and the required file output. | An independently completed task and a short test or review record. |
| 4 | Use a suitable timed section, review the result and revisit the weakest remaining step. | A comparison with Week 1 and one realistic next target. |
Make the level visible in the selected task
A G1 student might combine the gallery-guide activity with a short explanation of its events and state. A G2 student might trace the request counter and explain how a change in requirements affects the stored information. A G3 student might adapt the longest-run function and justify the tests. These are examples of choosing an appropriate activity, not replacements for the full course.
Across the same month, include a spreadsheet task and a conceptual explanation from the current school topic. Keep the session short enough that the student can complete a meaningful cycle of attempt, feedback and correction. If a task repeatedly grows too large, reduce its dataset or number of outputs.
Use review time to decide what changes next
At the end of each week, ask what the student can now do without help and what remains uncertain. A useful answer names a behaviour: predicting a copied formula, explaining a branch or saving the required file correctly. This is more actionable than describing the week as simply good or bad.
If a school assessment is approaching, align the next cycle with its stated scope. Retain a brief check of earlier learning where errors recur. The purpose is to build connected understanding over time while responding to the immediate work the student must complete.
CHAPTER 18 OF 18 · Assess, plan and choose support
18. Choose support and answer the practical questions
Does enjoying games mean Computing will be straightforward?
Interest is a useful starting point. Assess readiness through the subject’s actual work: following requirements, explaining decisions, building a solution and correcting it. A student can enjoy using a digital product while still needing support to understand how to create one.
Should every student learn Python for this examination?
Use the programming distinction in Chapter 2. G1 and G2 preparation should follow their specified block-programming work; G3 includes Python. Optional exploration can be enjoyable, but it should fit around the student’s assessed needs and available time.
What should we ask before paying for support?
Show a recent independent task and ask how the provider would address the specific difficulty. Confirm the subject level, relevant software, opportunity for the student to work independently, and the feedback they will receive. Ask how progress will be demonstrated on a different task.
For a Punggol family, compare travel time with the amount of useful learning a session offers. School consultation, guided home practice, online support and in-person lessons can serve different needs. Availability, group size, fees and coverage should be checked directly with the provider; this guide does not establish those details for any centre.
What if the child can explain an idea but cannot use the software?
Choose a small practical task that requires that idea, using the school’s environment where possible. Work through the operational steps, then repeat with a changed input. If access or compatibility is the obstacle, explain it to the school so the next step addresses the real problem.
How should we think about future study?
Computing can help a student discover an interest and develop useful ways of solving problems. A future course decision still requires checking that course’s current entry requirements and the student’s full subject profile. Avoid assuming that taking Computing at any one level guarantees a place or is compulsory for every technology-related route.
What should we do first?
Confirm the code, select one independently completed task and use the diagnostic table to choose the next step. The complementary Secondary 4 Computing preparation guide focuses on organising preparation. The eduKate Punggol learning library provides further reading across subjects.
Official sources and technical references
- Course specifications: SEAB G1 Computing K127, G2 Computing K237 and G3 Computing K349.
- Current entries: 2027 G1 directory, 2027 G2 directory and 2027 G3 directory.
- Qualification: SEAB’s SEC overview.
- Technical explanations: Python control flow, getting started with Scratch, MakeCode button events and spreadsheet references.
Return to the official syllabus for a particular learning outcome or examination rule, and to the school for the student’s teaching sequence and arrangements. Use the examples in this guide to make the ideas easier to discuss and the next learning action easier to choose.
Previous chapter · Contents · Explore the eduKate Punggol learning library

