What is SEC Examinations | G2 Computing (SEAB K237)

Original worked examples and skill checks

These examples are original teaching exercises, not official specimen-paper questions or licensed software demonstrations. They isolate small decisions for learning; the examination may combine several concepts and demand complete practical files. Practise each example independently and then change the test condition.

Example 1: Binary and bytes

Situation and result: Eight bits make one byte. An illustrative image file measured at 5,000,000 bytes is roughly five million decimal bytes, but a different unit convention using powers of two can produce a different displayed megabyte value.

Why it works: The key is to state whether the prefix is decimal or binary when precision matters, not simply convert every quantity by a guessed factor.

Try a fresh condition: Compare 1,000,000 bytes and 1,048,576 bytes and explain why they are different quantities.

After reading the explanation, hide it and ask the student to predict the output or decision before running software. Record whether the output matches the prediction. If it fails, find the first incorrect assumption, repair it and retest. This turns an error into a small experiment rather than a reason to memorise the answer.

Example 2: Two devices, one local network

Situation and result: A laptop connects through a Wi-Fi router to a printer, but the internet service is down. Printing locally may still work because the LAN can remain active.

Why it works: A local network can continue functioning when external connectivity fails. The printer’s location and network configuration determine the actual possibility.

Try a fresh condition: Name one possible reason the printer cannot be reached despite working Wi-Fi.

Example 3: Cloud storage reliability

Situation and result: A learner edits a document in a cloud application but has no internet connection during the next session.

Why it works: Cloud applications may require network access or offline support; local storage may remain available without internet. Avoid assuming every cloud service behaves identically.

Try a fresh condition: Suggest a responsible backup routine that protects work while respecting school data policies.

Example 4: Spreadsheet SUM

Situation and result: Cells B2 through B6 contain the numbers 12, 14, 8, 16 and 10. `=SUM(B2:B6)` yields 60.

Why it works: The range covers five numeric cells. Counting the column header or leaving out the last row would change the result.

Try a fresh condition: Modify B6 to 20 and predict the new total before opening the spreadsheet.

Example 5: Copying a fixed rate

Situation and result: A discount rate of 10% sits in cell E1 and each item’s price appears in column B. A suitable copied formula in C2 is `=B2*(1-$E$1)` if E1 contains 0.10.

Why it works: The dollar signs keep the reference to the common rate fixed when the formula is filled down, while B2 changes to B3, B4 and so on.

Try a fresh condition: Copy to row 3 and explain which references move and which remain fixed.

Example 6: Validation of a score

Situation and result: A spreadsheet accepts scores from 0 to 100 inclusive. Input validation should reject −1 and 101 while accepting 0, 50 and 100.

Why it works: Boundary testing checks limits that routine mid-range practice may miss. A custom error message should tell the user what values are allowed.

Try a fresh condition: Propose a validation rule for a whole-number student count that cannot be negative.

Example 7: Line graph or pie chart

Situation and result: A table records weekly sign-ups over six weeks. A line chart is generally a useful choice for time trends, while a pie chart is less suitable for showing change across six periods.

Why it works: The chart type should match the question, not merely the software’s most colourful option.

Try a fresh condition: Choose a chart for a breakdown of all sign-ups across three event categories at one date.

Example 8: Vector versus raster

Situation and result: An original school logo is made of vector paths. Enlarging it normally retains smooth shape boundaries, while stretching a low-resolution raster may expose visible pixels.

Why it works: The difference arises from geometric paths versus a fixed grid of pixel information.

Try a fresh condition: Describe which format is preferable for a large printed banner and one caveat about export.

Example 9: Video storyboard

Situation and result: A 20-second video has four five-second clips: opening location, activity, participant reaction and closing information.

Why it works: The sequence gives a beginning and end; editing must also preserve readable titles and the desired output.

Try a fresh condition: Reorder clips two and three and discuss whether the viewer’s understanding improves or worsens.

Example 10: Scratch variable trace

Situation and result: A Scratch-style game sets score to 0, then raises score by 2 whenever a player collects a token. After three successful collections, the expected score is 6.

Why it works: The update should occur only when the collection event is true, not every time a loop checks whether the sprite exists.

Try a fresh condition: Add one unsuccessful collision and predict whether the score should change.

Example 11: Scratch conditional boundary

Situation and result: A game displays a win screen when score is 10 or more. A conditional using ‘score > 10’ fails at exactly 10.

Why it works: The correct logical condition includes 10, and a boundary test exposes the difference.

Try a fresh condition: Prepare expected results for scores 9, 10 and 11.

Example 12: Loops and changing state

Situation and result: A loop repeats an action five times, changing a counter from 0 by +1 each time. The final value is 5, assuming the loop executes five iterations.

Why it works: Students should trace the counter before and after each iteration rather than infer the result from the word repeat alone.

Try a fresh condition: Start counter at 3 and predict the final value.

Example 13: MakeCode sensor conceptual question

Situation and result: An imagined microcontroller program turns an LED on when a measured light level is lower than a specified threshold. The condition must be evaluated against the sensor reading.

Why it works: A low light reading satisfying the condition produces the intended output; this is an input-processing-output chain. For K237 MakeCode is a Paper 1 concept, not the main Paper 2 coding platform.

Try a fresh condition: Add an exact-equality reading and decide whether the condition should use less-than or less-than-or-equal.

Example 14: Troubleshooting an exported file

Situation and result: A student finishes a video task but the exported file is missing the final title. The timeline was edited after the most recent export.

Why it works: The deliverable is the exported output, not the appearance of the editing interface. Saving the project and exporting after edits are separate steps.

Try a fresh condition: Create a mock check that reopens the final file and verifies three required features.

Example 15: Cybersecurity message

Situation and result: A fictional message says a school account will be closed unless the user submits a password through an unfamiliar form within ten minutes.

Why it works: Urgency and requests for credentials are warning signs; verification should occur through the school’s established channel, without using the suspicious link.

Try a fresh condition: Write a short checklist that avoids sharing personal secrets while confirming a legitimate notice.

How to plan, test and debug a computing solution

Start with a plain-language problem statement. Write down the required inputs and outputs, their data types and any permitted ranges. A teacher may specify a spreadsheet that rejects invalid stock counts or a program that returns the first matching item. Those requirements guide implementation more effectively than picking software features at random.

Next decompose the solution: data acquisition, validation, processing, presentation and saving. Describe the relevant relationships before writing code or formulas. This makes it easier to detect a missing step and avoids spending time on decorative formatting while the core result is still wrong.

Test normal cases and boundary cases deliberately. An ordinary mid-range score may pass every condition, while an exact threshold reveals a missing equality sign. Check empty input, repeated values, very small quantities and invalid formats where those cases are relevant to the specification. Record expected results before observing actual ones.

Distinguish syntax errors, runtime problems and logic errors where applicable. A syntax error prevents code from being interpreted correctly; a runtime failure arises during execution; a logic error may generate a plausible but wrong answer. Fixing each requires a different investigation. For spreadsheets, identify whether the issue lies in the selected range, copied reference, data type or chart source.

Finally inspect the deliverable, not only the workspace. The digital lab includes time to save files, and the submitted softcopy must reflect the final work. A correct answer that was never saved may be unavailable to the marking process. Reopen the actual exported or saved file during practice and verify its content against the task.

What an effective mock lab looks like

A good K237 simulation includes a timed spreadsheet, a small Scratch game/program and a media artefact, using the school-approved tools. The approximate marks of 25, 25 and 30 help allocate attention, but the paper’s total 135 minutes includes saving time.

Set a checklist before beginning: which files are required, where outputs must appear, how calculations will be checked, and how much time remains for verification. This prevents a last-minute scramble to locate a file or export a project that was only saved within the editing application.

Do not claim that any individual home software version is automatically approved for national examinations. The syllabus describes required software categories and the candidate instructions specify the examination environment. Practise in a version and configuration confirmed by the school where possible, while learning concepts that transfer across interfaces.

Ten common mistakes and why they matter

Assuming G2 Computing is only Scratch

The syllabus also examines fundamentals, networks, impact, spreadsheets and media software.

The correction is to locate the first failed decision and test it on new data. A learner should be able to explain what went wrong and why the revised solution is valid. Simply pressing Run again or copying a formula without checking references may hide the original misunderstanding.

Using G3 Python instructions for G2

G2 Paper 2 uses the prescribed software and Scratch, media and spreadsheets, not the G3 Python/JupyterLab format.

Treating both papers as 50 raw marks

They have different raw totals, 70 and 80, but each is weighted 50%.

Ignoring Paper 1 because it is digital

The e-exam covers all six modules and has 20 MCQs plus 50 marks of structured tasks.

Practising MakeCode for the lab instead of Scratch

MakeCode blocks are assessed in Paper 1 only under the published K237 tables.

Not allocating time to media creation

The practical includes about 30 marks on media software, a meaningful task beside spreadsheets and programming.

Wrong spreadsheet references

Use relative or absolute references deliberately and test copied formulas on more than one row.

Unreliable exported or unsaved files

Check the actual digital deliverables, names and formats against the exam instructions.

Overlooking scams and AI limitations

Cyber safety and impact of computing are part of the official content and not optional background.

Relying on one familiar programming example

Practice tracing code with changed initial values and boundary cases to reveal hidden assumptions.

A six-week study sequence

Week 1 — confirm the correct code and environment

Read the K237 table and school guidance. Diagnose concepts, practical fluency, file management and tests separately.

A useful weekly measure is whether a student can explain the problem, predict the expected output and verify a fresh result unaided. A full folder of copied projects does not show that these independent decisions have been learnt.

Week 2 — rebuild core data and network understanding

Practise vocabulary with drawings, comparison cases and short source questions. Explain the difference between storage and memory, or LAN and internet.

Week 3 — develop spreadsheet reliability

Create formulas, use correct references, select charts and test validation rules. Change the data to check whether the workbook behaves correctly.

Week 4 — strengthen programming and debugging

Use Scratch variables, conditions, loops, events and lists, with MakeCode theory where relevant. Trace before running.

Week 5 — perform a simulated paper and lab

Match the syllabus time and mode. For G2 include digital media; for G3 include the required Python and spreadsheet tasks. Practise saving and checking output.

Week 6 — correct the highest-impact problems

Use an error log to identify recurring mistakes. Retest with fresh inputs, confirm the permitted software and equipment, and protect rest before examinations.

Questions parents can ask without writing code themselves

What exactly is the task’s input and expected output?
Which part of the program or spreadsheet makes the important decision?
What happens when the input is zero, missing or exactly at the limit?
Can you explain the difference between a wrong answer and an invalid file?
How did you check whether the formula still works when copied?
Which software and response mode does the 2027 K237 paper actually require?
Where is your saved final output, and can you reopen it?
Can you show me one change you made after testing?
What would make the system unsafe or unfair to users?
What new question will prove you understand this skill next week?

Parents should aim to make the learner’s thinking visible, not to provide a prewritten script. A small-group tutor can help by identifying whether a child misunderstood the specification, chose the wrong data structure, wrote incorrect syntax, lost track of a file or simply ran out of time. Each problem needs a different intervention.

In eduKate’s three-student tutorial approach, close observation should lead to targeted feedback and increasing independence. A smaller class by itself is not proof of results. The valuable outcome is that the student can make and explain the next correct decision without prompts, then repeat it on an unfamiliar task.

Frequently asked questions about G2 Computing K237

What is G2 Computing K237?

A new 2027 SEC G2 subject assessing fundamentals, networking, digital impact, spreadsheets, media software and programming.

Did G2 Computing have an old N(A) code?

SEAB lists its previous reference as not applicable because K237 is a new 2027 syllabus.

What is the Paper 1 format?

A 90-minute computer-delivered e-exam: 20 MCQs and 50 structured marks, total 70.

What is the practical format?

Paper 2 is a 135-minute lab examination worth 80 marks, with three tasks across media, spreadsheets and programming.

How are the papers weighted?

50% each, even though raw totals are different.

Is MakeCode examined in Paper 2?

The syllabus tables specify MakeCode blocks for Paper 1 only; Scratch is listed for Paper 1 and Paper 2.

Does Paper 2 require media work?

Yes, with an approximate 30-mark task along with spreadsheet and programming tasks.

Do all questions have to be answered?

Yes. Both papers are compulsory and the syllabus states all questions in both are compulsory.

Is an approved calculator allowed?

Yes, subject to SEAB regulations, though software skill remains essential.

Does the lab include time to save files?

Yes. The 2-hour-15-minute duration includes time for saving the required work.

Is G2 Computing the same as G3 Computing?

No. G3 K349 has a different subject level, five modules and a Python/JupyterLab lab.

Can I practise using my own software at home?

Use school-approved platforms and confirm the examination’s installed software requirements rather than assuming any app will be provided.

SEC grades and future course choices

G2 subject grades run from 1 to 6, and grade 5 or better meets the SEC subject certificate-award threshold. Those thresholds are not the entry requirements for individual JC, polytechnic, ITE or computing programmes. Current admissions rules and the candidate’s full subject combination determine eligibility.

Computing skills also have value outside the examination: managing data carefully, checking algorithms, identifying misleading digital content, communicating findings and protecting information. Students can build those abilities even if they eventually study a different post-secondary subject.

Official SEAB documents and further reading

The structure and content described here were checked against the official 2027 K237 syllabus PDF, 2027 G2 school-candidate syllabus list and SEC overview as available on 11 November 2026. The sample tasks and calculations are independent educational illustrations. Use the latest SEAB candidate instructions for actual software, formats, file submission and examinations.

For the next useful lesson, choose a small unfamiliar problem, state its requirements, predict an output, build the solution and test it against an edge case. Save the final artefact and reopen it. That routine develops the computing judgment the SEC is designed to assess, rather than dependence on a memorised set of clicks.

The subject modules explained through familiar situations

Module 1: computer fundamentals

A computer receives data as input, processes it and produces output using a processor, memory, storage and interface devices. CPU and GPU have different roles, while integrated and dedicated graphics can use memory differently. Storage technology influences capacity, speed, durability and portability.

The learning challenge is to distinguish a temporary working memory such as RAM from long-term storage. If the computer is turned off, a document not saved to durable storage can be lost even though it was visible on the screen. A powerful GPU does not automatically imply faster performance on every task.

Compare two fictional laptops for a school project: one has faster storage, the other more RAM. Decide which specification is relevant to running many applications and explain what additional information you would ask for.

A good diagnostic asks the learner to identify the input, the processing or decision step, the expected output and one plausible failure. If the result changes when a condition or data item changes, the explanation should change with it. That is evidence of computational thinking rather than recognition of a copied interface.

Module 2: networks and the internet

Networks permit resource sharing and communication among devices. The syllabus includes wired and wireless connections, modems, routers, LAN and WAN, intranets, the internet, MAC and IP addresses, and cloud versus local computing.

A home Wi-Fi network is not identical to the internet. A device may successfully connect to a local router while external internet service is unavailable. MAC and IP addresses serve different roles in local versus wider network communication and should not be treated as interchangeable strings.

Draw a home network including three devices, a router and modem. Label what the router connects, what a cloud application requires and where a breakdown could occur.

Module 3: technology, safety, AI and digital ethics

Computing influences communication, learning, transport, retail and other fields. The syllabus introduces examples of artificial intelligence, cybersecurity threats such as phishing and malware, and responsible use of computers and information.

An AI classifier may produce useful results but can misclassify a case. A convincing-looking message is not proof the sender is legitimate. Responsible users verify origin, protect personal information and understand how a system can be misused.

Give two fictional messages, one from a verified school account and one asking for a password through a suspicious link. Discuss how to check authenticity without clicking or exposing personal data.

Module 4: spreadsheet data and formulae

Spreadsheet cells store numbers, text and formulas. Relative and absolute references behave differently when a formula is copied. Sorting, filtering, functions, charts and validation help turn raw records into decisions.

A common error is to copy a tax formula while allowing the cell containing the tax rate to move, causing inconsistent results. The correct reference type depends on which values should change across rows. A formatted chart can look convincing while plotting the wrong range.

Practise a small budget workbook: use SUM for totals, percentage formulas for comparisons and an absolute reference where one rate applies to several rows. Check the result by hand on one row.

Module 4: chart quality and validation

The syllabus includes using appropriate charts, interpreting data and controlling input through validation criteria and custom error messages. A chart title and axis labels should accurately represent what the worksheet measures.

A pie chart of student counts may be meaningful when categories make up a whole, but less useful for trends across several months. A spreadsheet does not make values reliable simply because they are organised in neat cells.

Give students a fictional weekly attendance table and ask which chart best shows change over time. Then create a rule to reject negative attendance counts.

Module 5: vector graphics and editing

Vector images use paths and nodes and can be resized without losing clarity in ordinary vector rendering. Students can use shapes, text, layering, transformations and suitable layout methods to communicate visually.

A logo made of paths can be enlarged without the pixelated appearance of a small raster image. But vector artwork must still use sensible composition and legible text; unlimited resizing does not guarantee good design.

Create an original three-shape symbol for a reading club. Test alignment, contrast and readability at both large and small display sizes.

Module 5: video and multimedia

Media software involves planning and arranging visual elements, editing timeline sequences and presenting suitable digital outputs. The practical task should demonstrate specified transformations, graphics or video-editing techniques rather than simply opening an application.

A clip transition that looks impressive can weaken communication when it obscures the message. Basic sequencing, readable captions and appropriate timing often matter more. Creative tasks also require careful file management and the right export format.

Plan a 20-second original school-event video with three clips and a title. Explain what each sequence communicates and how the exported file would be checked.

Module 6: Scratch programming fundamentals

Scratch represents a program through blocks. Variables store values, while selection chooses between paths and repetition repeats instructions. Boolean and relational operators support decisions. Lists and custom blocks can simplify larger processes.

A program that adds one to a score on every frame instead of every successful action may produce an unexpected score. The error is logical: the code executes at the wrong moment, not that the variable is labelled incorrectly.

Trace an original Scratch-style score counter from an event, through a condition and into a variable update. Write the expected new value after each action.

Module 6: Scratch game behaviour

Games use sprites, coordinates, orientation, costumes, backdrops, timing, event messages and interactions between objects. The program must respond consistently to user inputs and state changes.

A character can appear to jump while a collision condition remains wrong. Test the condition and the expected event rather than simply adjusting the sprite graphic until it looks correct.

Design a game with one moving character, one target and a score. Plan what happens on collision and when the game ends, then test edge conditions.

Module 6: MakeCode only where listed

The 2027 K237 syllabus includes MakeCode blocks for microcontroller understanding, with the syllabus tables identifying MakeCode as examined in Paper 1 only. Scratch blocks apply to both Paper 1 and Paper 2 for the indicated learning outcomes.

Do not use a MakeCode-only project as a substitute for the Scratch programming practical. Understanding a block-based concept can transfer between environments, but the assessment specifies which platform belongs to which paper.

Prepare one conceptual MakeCode trace for a sensor and LED output, then use Scratch for a practical game task with variables and conditionals.

Computational thinking: decomposition and abstraction

Decomposition separates a difficult job into manageable parts, while abstraction retains relevant features and removes distracting detail. These approaches help both programming and spreadsheet work.

A library-loan tracker can be divided into input, validation, processing and output. Students should not start with decorative screens before deciding what values are needed and what the system must calculate.

Design a simple borrowing counter with a flowchart and list the data a program truly needs. Separate appearance choices from rules.

Debugging with normal and boundary cases

A program that works for familiar inputs may fail at zero, negative numbers, an empty list or a maximum value. Debugging means locating the wrong assumption, fixing it and retesting rather than repeatedly pressing Run.

Suppose a program displays ‘Success’ when score is greater than 50, but the rule says 50 and above. The boundary input 50 exposes the error; the correct comparison should include equality.

Prepare test cases for 49, 50 and 51. State the expected and observed result of each before changing the conditional.

File saving and lab workflow

The K237 practical includes time for saving digital files. Candidates should know how to identify the expected output, create it in the approved software, verify its contents and use the instructions for submission.

A correct spreadsheet formula that is never saved to the required deliverable is not a completed submission. A video exported with the wrong dimensions or a game saved without its latest changes can also create avoidable problems.

Practise a mock lab with named deliverables and a final checklist: file present, correct format, opens successfully and corresponds to the task. Follow actual SEAB naming requirements when published.

Understanding K237 versus G3 Computing K349

K237 covers six modules and explicitly includes media creation and Scratch programming. K349 has five modules and assesses programming in Python and spreadsheets in its lab. The two are not simply the same syllabus with easier or harder marks.

A G2 learner should not spend most practical preparation writing advanced Python if the assessed lab requires Scratch, media software and spreadsheets. Likewise, a G3 learner cannot replace Python lab practice with a video editor.

Use a two-column checklist showing modules, software, paper mode, raw marks and weights for the subject the student is actually taking.

Original worked examples and skill checks

Example 1: Binary and bytes

Why it works: The key is to state whether the prefix is decimal or binary when precision matters, not simply convert every quantity by a guessed factor.

Try a fresh condition: Compare 1,000,000 bytes and 1,048,576 bytes and explain why they are different quantities.

Example 2: Two devices, one local network

Situation and result: A laptop connects through a Wi-Fi router to a printer, but the internet service is down. Printing locally may still work because the LAN can remain active.

Why it works: A local network can continue functioning when external connectivity fails. The printer’s location and network configuration determine the actual possibility.

Try a fresh condition: Name one possible reason the printer cannot be reached despite working Wi-Fi.

Example 3: Cloud storage reliability

Situation and result: A learner edits a document in a cloud application but has no internet connection during the next session.

Why it works: Cloud applications may require network access or offline support; local storage may remain available without internet. Avoid assuming every cloud service behaves identically.

Try a fresh condition: Suggest a responsible backup routine that protects work while respecting school data policies.

Example 4: Spreadsheet SUM

Situation and result: Cells B2 through B6 contain the numbers 12, 14, 8, 16 and 10. `=SUM(B2:B6)` yields 60.

Why it works: The range covers five numeric cells. Counting the column header or leaving out the last row would change the result.

Try a fresh condition: Modify B6 to 20 and predict the new total before opening the spreadsheet.

Example 5: Copying a fixed rate

Situation and result: A discount rate of 10% sits in cell E1 and each item’s price appears in column B. A suitable copied formula in C2 is `=B2*(1-$E$1)` if E1 contains 0.10.

Why it works: The dollar signs keep the reference to the common rate fixed when the formula is filled down, while B2 changes to B3, B4 and so on.

Try a fresh condition: Copy to row 3 and explain which references move and which remain fixed.

Example 6: Validation of a score

Situation and result: A spreadsheet accepts scores from 0 to 100 inclusive. Input validation should reject −1 and 101 while accepting 0, 50 and 100.

Why it works: Boundary testing checks limits that routine mid-range practice may miss. A custom error message should tell the user what values are allowed.

Try a fresh condition: Propose a validation rule for a whole-number student count that cannot be negative.

Example 7: Line graph or pie chart

Why it works: The chart type should match the question, not merely the software’s most colourful option.

Try a fresh condition: Choose a chart for a breakdown of all sign-ups across three event categories at one date.

Example 8: Vector versus raster

Situation and result: An original school logo is made of vector paths. Enlarging it normally retains smooth shape boundaries, while stretching a low-resolution raster may expose visible pixels.

Why it works: The difference arises from geometric paths versus a fixed grid of pixel information.

Try a fresh condition: Describe which format is preferable for a large printed banner and one caveat about export.

Example 9: Video storyboard

Situation and result: A 20-second video has four five-second clips: opening location, activity, participant reaction and closing information.

Why it works: The sequence gives a beginning and end; editing must also preserve readable titles and the desired output.

Try a fresh condition: Reorder clips two and three and discuss whether the viewer’s understanding improves or worsens.

Example 10: Scratch variable trace

Situation and result: A Scratch-style game sets score to 0, then raises score by 2 whenever a player collects a token. After three successful collections, the expected score is 6.

Why it works: The update should occur only when the collection event is true, not every time a loop checks whether the sprite exists.

Try a fresh condition: Add one unsuccessful collision and predict whether the score should change.

Example 11: Scratch conditional boundary

Situation and result: A game displays a win screen when score is 10 or more. A conditional using ‘score > 10’ fails at exactly 10.

Why it works: The correct logical condition includes 10, and a boundary test exposes the difference.

Try a fresh condition: Prepare expected results for scores 9, 10 and 11.

Example 12: Loops and changing state

Situation and result: A loop repeats an action five times, changing a counter from 0 by +1 each time. The final value is 5, assuming the loop executes five iterations.

Why it works: Students should trace the counter before and after each iteration rather than infer the result from the word repeat alone.

Try a fresh condition: Start counter at 3 and predict the final value.

Example 13: MakeCode sensor conceptual question

Try a fresh condition: Add an exact-equality reading and decide whether the condition should use less-than or less-than-or-equal.

Example 14: Troubleshooting an exported file

Situation and result: A student finishes a video task but the exported file is missing the final title. The timeline was edited after the most recent export.

Why it works: The deliverable is the exported output, not the appearance of the editing interface. Saving the project and exporting after edits are separate steps.

Try a fresh condition: Create a mock check that reopens the final file and verifies three required features.

Example 15: Cybersecurity message

Situation and result: A fictional message says a school account will be closed unless the user submits a password through an unfamiliar form within ten minutes.

Why it works: Urgency and requests for credentials are warning signs; verification should occur through the school’s established channel, without using the suspicious link.

Try a fresh condition: Write a short checklist that avoids sharing personal secrets while confirming a legitimate notice.

How to plan, test and debug a computing solution

What an effective mock lab looks like

Ten common mistakes and why they matter

Assuming G2 Computing is only Scratch

The syllabus also examines fundamentals, networks, impact, spreadsheets and media software.

Using G3 Python instructions for G2

G2 Paper 2 uses the prescribed software and Scratch, media and spreadsheets, not the G3 Python/JupyterLab format.

Treating both papers as 50 raw marks

They have different raw totals, 70 and 80, but each is weighted 50%.

Ignoring Paper 1 because it is digital

The e-exam covers all six modules and has 20 MCQs plus 50 marks of structured tasks.

Practising MakeCode for the lab instead of Scratch

MakeCode blocks are assessed in Paper 1 only under the published K237 tables.

Not allocating time to media creation

The practical includes about 30 marks on media software, a meaningful task beside spreadsheets and programming.

Wrong spreadsheet references

Use relative or absolute references deliberately and test copied formulas on more than one row.

Unreliable exported or unsaved files

Check the actual digital deliverables, names and formats against the exam instructions.

Overlooking scams and AI limitations

Cyber safety and impact of computing are part of the official content and not optional background.

Relying on one familiar programming example

Practice tracing code with changed initial values and boundary cases to reveal hidden assumptions.

A six-week study sequence

Week 1 — confirm the correct code and environment

Read the K237 table and school guidance. Diagnose concepts, practical fluency, file management and tests separately.

Week 2 — rebuild core data and network understanding

Practise vocabulary with drawings, comparison cases and short source questions. Explain the difference between storage and memory, or LAN and internet.

Week 3 — develop spreadsheet reliability

Create formulas, use correct references, select charts and test validation rules. Change the data to check whether the workbook behaves correctly.

Week 4 — strengthen programming and debugging

Use Scratch variables, conditions, loops, events and lists, with MakeCode theory where relevant. Trace before running.

Week 5 — perform a simulated paper and lab

Match the syllabus time and mode. For G2 include digital media; for G3 include the required Python and spreadsheet tasks. Practise saving and checking output.

Week 6 — correct the highest-impact problems

Use an error log to identify recurring mistakes. Retest with fresh inputs, confirm the permitted software and equipment, and protect rest before examinations.

Questions parents can ask without writing code themselves

What exactly is the task’s input and expected output?
Which part of the program or spreadsheet makes the important decision?
What happens when the input is zero, missing or exactly at the limit?
Can you explain the difference between a wrong answer and an invalid file?
How did you check whether the formula still works when copied?
Which software and response mode does the 2027 K237 paper actually require?
Where is your saved final output, and can you reopen it?
Can you show me one change you made after testing?
What would make the system unsafe or unfair to users?
What new question will prove you understand this skill next week?

Frequently asked questions about G2 Computing K237

What is G2 Computing K237?

A new 2027 SEC G2 subject assessing fundamentals, networking, digital impact, spreadsheets, media software and programming.

Did G2 Computing have an old N(A) code?

SEAB lists its previous reference as not applicable because K237 is a new 2027 syllabus.

What is the Paper 1 format?

A 90-minute computer-delivered e-exam: 20 MCQs and 50 structured marks, total 70.

What is the practical format?

Paper 2 is a 135-minute lab examination worth 80 marks, with three tasks across media, spreadsheets and programming.

How are the papers weighted?

50% each, even though raw totals are different.

Is MakeCode examined in Paper 2?

The syllabus tables specify MakeCode blocks for Paper 1 only; Scratch is listed for Paper 1 and Paper 2.

Does Paper 2 require media work?

Yes, with an approximate 30-mark task along with spreadsheet and programming tasks.

Do all questions have to be answered?

Yes. Both papers are compulsory and the syllabus states all questions in both are compulsory.

Is an approved calculator allowed?

Yes, subject to SEAB regulations, though software skill remains essential.

Does the lab include time to save files?

Yes. The 2-hour-15-minute duration includes time for saving the required work.

Is G2 Computing the same as G3 Computing?

No. G3 K349 has a different subject level, five modules and a Python/JupyterLab lab.

Can I practise using my own software at home?

Use school-approved platforms and confirm the examination’s installed software requirements rather than assuming any app will be provided.

SEC grades and future course choices

Official SEAB documents and further reading

Why does the 2027 SEC Computing syllabus matter?

The Singapore–Cambridge Secondary Education Certificate brings together the former N(T), N(A) and O-Level examinations from the 2027 graduating cohort. Students continue to be examined in individual subjects at approved G-levels. A specific code is therefore essential. Someone searching only for ‘Computing past papers’ might accidentally select G2 K349 materials, which cover a different mix of software, programming language and paper format.

K237 is a new G2 subject whose official earlier-code field is not applicable. The title alone does not confirm that an old workbook matches the 2027 syllabus. Before relying on a source, match its concepts and practical tasks to the published scheme.

Computing is valuable because it teaches learners to describe problems precisely, design processes and test whether a system actually does what it should. Writing a program is one way to demonstrate that skill; setting up a secure network, selecting a suitable data chart or creating a reliable digital artefact also require careful decisions.

The paper structures explained, one at a time

Paper 1: e-Examination

Duration: 1 hour 30 minutes. Raw marks: 70. Weight: 50%. All six modules. Section A is 20 compulsory multiple-choice questions with four options, 20 marks. Section B consists of a variable number of compulsory short structured questions, 50 marks. The paper assesses knowledge and application rather than lab file submission.

Effective preparation should match the paper rather than simply copying exercises from a general coding tutorial. For a theoretical question, learn to explain concepts and trace small examples on paper. For lab tasks, practise the real application environment, save the expected output and check the produced file. A working result is more informative than a screenshot of someone else’s successful answer.

Paper 2: Computer-based practical

Duration: 2 hours 15 minutes. Raw marks: 80. Weight: 50%. Three compulsory tasks: media software about 30 marks, spreadsheets about 25 marks and programming about 25 marks. The candidate uses approved installed software, saves work and submits the required softcopy files; saving time is included in the examination duration.

Understanding assessment objectives, not merely marks

K237 uses AO1 for knowledge (about 20% overall), AO2 for application (about 30%) and AO3 for practical skill (50%). Paper 1 covers knowledge and application, while Paper 2 directly tests practical performance.

The assessment percentages describe skills, not the probability that one favourite question will appear. An algorithm may be assessed by tracing its output, proposing a change or producing running code. A spreadsheet idea may appear as a theory question about references and as a live task that must be saved. Students need to understand both versions.

A reliable study session therefore has three parts: explain the idea without opening an application, attempt a new problem under suitable conditions, and check the output against the actual requirements. If an error occurs, identify whether it comes from misunderstanding the problem, the representation, the implementation or the final saved deliverable.

The subject modules explained through familiar situations

Module 1: computer fundamentals

Module 2: networks and the internet

Draw a home network including three devices, a router and modem. Label what the router connects, what a cloud application requires and where a breakdown could occur.

Module 3: technology, safety, AI and digital ethics

Give two fictional messages, one from a verified school account and one asking for a password through a suspicious link. Discuss how to check authenticity without clicking or exposing personal data.

Module 4: spreadsheet data and formulae

Practise a small budget workbook: use SUM for totals, percentage formulas for comparisons and an absolute reference where one rate applies to several rows. Check the result by hand on one row.

Module 4: chart quality and validation

Give students a fictional weekly attendance table and ask which chart best shows change over time. Then create a rule to reject negative attendance counts.

Module 5: vector graphics and editing

Create an original three-shape symbol for a reading club. Test alignment, contrast and readability at both large and small display sizes.

Module 5: video and multimedia

Plan a 20-second original school-event video with three clips and a title. Explain what each sequence communicates and how the exported file would be checked.

Module 6: Scratch programming fundamentals

Trace an original Scratch-style score counter from an event, through a condition and into a variable update. Write the expected new value after each action.

Module 6: Scratch game behaviour

Games use sprites, coordinates, orientation, costumes, backdrops, timing, event messages and interactions between objects. The program must respond consistently to user inputs and state changes.

A character can appear to jump while a collision condition remains wrong. Test the condition and the expected event rather than simply adjusting the sprite graphic until it looks correct.

Design a game with one moving character, one target and a score. Plan what happens on collision and when the game ends, then test edge conditions.

Module 6: MakeCode only where listed

Prepare one conceptual MakeCode trace for a sensor and LED output, then use Scratch for a practical game task with variables and conditionals.

Computational thinking: decomposition and abstraction

Decomposition separates a difficult job into manageable parts, while abstraction retains relevant features and removes distracting detail. These approaches help both programming and spreadsheet work.

Design a simple borrowing counter with a flowchart and list the data a program truly needs. Separate appearance choices from rules.

Debugging with normal and boundary cases

Suppose a program displays ‘Success’ when score is greater than 50, but the rule says 50 and above. The boundary input 50 exposes the error; the correct comparison should include equality.

Prepare test cases for 49, 50 and 51. State the expected and observed result of each before changing the conditional.

File saving and lab workflow

Practise a mock lab with named deliverables and a final checklist: file present, correct format, opens successfully and corresponds to the task. Follow actual SEAB naming requirements when published.

Understanding K237 versus G3 Computing K349

Use a two-column checklist showing modules, software, paper mode, raw marks and weights for the subject the student is actually taking.

Original worked examples and skill checks

Example 1: Binary and bytes

Why it works: The key is to state whether the prefix is decimal or binary when precision matters, not simply convert every quantity by a guessed factor.

Try a fresh condition: Compare 1,000,000 bytes and 1,048,576 bytes and explain why they are different quantities.

Example 2: Two devices, one local network

Situation and result: A laptop connects through a Wi-Fi router to a printer, but the internet service is down. Printing locally may still work because the LAN can remain active.

Why it works: A local network can continue functioning when external connectivity fails. The printer’s location and network configuration determine the actual possibility.

Try a fresh condition: Name one possible reason the printer cannot be reached despite working Wi-Fi.

Example 3: Cloud storage reliability

Situation and result: A learner edits a document in a cloud application but has no internet connection during the next session.

Why it works: Cloud applications may require network access or offline support; local storage may remain available without internet. Avoid assuming every cloud service behaves identically.

Try a fresh condition: Suggest a responsible backup routine that protects work while respecting school data policies.

Example 4: Spreadsheet SUM

Situation and result: Cells B2 through B6 contain the numbers 12, 14, 8, 16 and 10. `=SUM(B2:B6)` yields 60.

Why it works: The range covers five numeric cells. Counting the column header or leaving out the last row would change the result.

Try a fresh condition: Modify B6 to 20 and predict the new total before opening the spreadsheet.

Example 5: Copying a fixed rate

Situation and result: A discount rate of 10% sits in cell E1 and each item’s price appears in column B. A suitable copied formula in C2 is `=B2*(1-$E$1)` if E1 contains 0.10.

Why it works: The dollar signs keep the reference to the common rate fixed when the formula is filled down, while B2 changes to B3, B4 and so on.

Try a fresh condition: Copy to row 3 and explain which references move and which remain fixed.

Example 6: Validation of a score

Situation and result: A spreadsheet accepts scores from 0 to 100 inclusive. Input validation should reject −1 and 101 while accepting 0, 50 and 100.

Why it works: Boundary testing checks limits that routine mid-range practice may miss. A custom error message should tell the user what values are allowed.

Try a fresh condition: Propose a validation rule for a whole-number student count that cannot be negative.

Example 7: Line graph or pie chart

Why it works: The chart type should match the question, not merely the software’s most colourful option.

Try a fresh condition: Choose a chart for a breakdown of all sign-ups across three event categories at one date.

Example 8: Vector versus raster

Situation and result: An original school logo is made of vector paths. Enlarging it normally retains smooth shape boundaries, while stretching a low-resolution raster may expose visible pixels.

Why it works: The difference arises from geometric paths versus a fixed grid of pixel information.

Try a fresh condition: Describe which format is preferable for a large printed banner and one caveat about export.

Example 9: Video storyboard

Situation and result: A 20-second video has four five-second clips: opening location, activity, participant reaction and closing information.

Why it works: The sequence gives a beginning and end; editing must also preserve readable titles and the desired output.

Try a fresh condition: Reorder clips two and three and discuss whether the viewer’s understanding improves or worsens.

Example 10: Scratch variable trace

Situation and result: A Scratch-style game sets score to 0, then raises score by 2 whenever a player collects a token. After three successful collections, the expected score is 6.

Why it works: The update should occur only when the collection event is true, not every time a loop checks whether the sprite exists.

Try a fresh condition: Add one unsuccessful collision and predict whether the score should change.

Example 11: Scratch conditional boundary

Situation and result: A game displays a win screen when score is 10 or more. A conditional using ‘score > 10’ fails at exactly 10.

Why it works: The correct logical condition includes 10, and a boundary test exposes the difference.

Try a fresh condition: Prepare expected results for scores 9, 10 and 11.

Example 12: Loops and changing state

Situation and result: A loop repeats an action five times, changing a counter from 0 by +1 each time. The final value is 5, assuming the loop executes five iterations.

Why it works: Students should trace the counter before and after each iteration rather than infer the result from the word repeat alone.

Try a fresh condition: Start counter at 3 and predict the final value.

Example 13: MakeCode sensor conceptual question

Try a fresh condition: Add an exact-equality reading and decide whether the condition should use less-than or less-than-or-equal.

Example 14: Troubleshooting an exported file

Situation and result: A student finishes a video task but the exported file is missing the final title. The timeline was edited after the most recent export.

Why it works: The deliverable is the exported output, not the appearance of the editing interface. Saving the project and exporting after edits are separate steps.

Try a fresh condition: Create a mock check that reopens the final file and verifies three required features.

Example 15: Cybersecurity message

Situation and result: A fictional message says a school account will be closed unless the user submits a password through an unfamiliar form within ten minutes.

Why it works: Urgency and requests for credentials are warning signs; verification should occur through the school’s established channel, without using the suspicious link.

Try a fresh condition: Write a short checklist that avoids sharing personal secrets while confirming a legitimate notice.

How to plan, test and debug a computing solution

What an effective mock lab looks like

Ten common mistakes and why they matter

Assuming G2 Computing is only Scratch

The syllabus also examines fundamentals, networks, impact, spreadsheets and media software.

Using G3 Python instructions for G2

G2 Paper 2 uses the prescribed software and Scratch, media and spreadsheets, not the G3 Python/JupyterLab format.

Treating both papers as 50 raw marks

They have different raw totals, 70 and 80, but each is weighted 50%.

Ignoring Paper 1 because it is digital

The e-exam covers all six modules and has 20 MCQs plus 50 marks of structured tasks.

Practising MakeCode for the lab instead of Scratch

MakeCode blocks are assessed in Paper 1 only under the published K237 tables.

Not allocating time to media creation

The practical includes about 30 marks on media software, a meaningful task beside spreadsheets and programming.

Wrong spreadsheet references

Use relative or absolute references deliberately and test copied formulas on more than one row.

Unreliable exported or unsaved files

Check the actual digital deliverables, names and formats against the exam instructions.

Overlooking scams and AI limitations

Cyber safety and impact of computing are part of the official content and not optional background.

Relying on one familiar programming example

Practice tracing code with changed initial values and boundary cases to reveal hidden assumptions.

A six-week study sequence

Week 1 — confirm the correct code and environment

Read the K237 table and school guidance. Diagnose concepts, practical fluency, file management and tests separately.

Week 2 — rebuild core data and network understanding

Practise vocabulary with drawings, comparison cases and short source questions. Explain the difference between storage and memory, or LAN and internet.

Week 3 — develop spreadsheet reliability

Create formulas, use correct references, select charts and test validation rules. Change the data to check whether the workbook behaves correctly.

Week 4 — strengthen programming and debugging

Use Scratch variables, conditions, loops, events and lists, with MakeCode theory where relevant. Trace before running.

Week 5 — perform a simulated paper and lab

Match the syllabus time and mode. For G2 include digital media; for G3 include the required Python and spreadsheet tasks. Practise saving and checking output.

Week 6 — correct the highest-impact problems

Use an error log to identify recurring mistakes. Retest with fresh inputs, confirm the permitted software and equipment, and protect rest before examinations.

Questions parents can ask without writing code themselves

What exactly is the task’s input and expected output?
Which part of the program or spreadsheet makes the important decision?
What happens when the input is zero, missing or exactly at the limit?
Can you explain the difference between a wrong answer and an invalid file?
How did you check whether the formula still works when copied?
Which software and response mode does the 2027 K237 paper actually require?
Where is your saved final output, and can you reopen it?
Can you show me one change you made after testing?
What would make the system unsafe or unfair to users?
What new question will prove you understand this skill next week?

Frequently asked questions about G2 Computing K237

What is G2 Computing K237?

A new 2027 SEC G2 subject assessing fundamentals, networking, digital impact, spreadsheets, media software and programming.

Did G2 Computing have an old N(A) code?

SEAB lists its previous reference as not applicable because K237 is a new 2027 syllabus.

What is the Paper 1 format?

A 90-minute computer-delivered e-exam: 20 MCQs and 50 structured marks, total 70.

What is the practical format?

Paper 2 is a 135-minute lab examination worth 80 marks, with three tasks across media, spreadsheets and programming.

How are the papers weighted?

50% each, even though raw totals are different.

Is MakeCode examined in Paper 2?

The syllabus tables specify MakeCode blocks for Paper 1 only; Scratch is listed for Paper 1 and Paper 2.

Does Paper 2 require media work?

Yes, with an approximate 30-mark task along with spreadsheet and programming tasks.

Do all questions have to be answered?

Yes. Both papers are compulsory and the syllabus states all questions in both are compulsory.

Is an approved calculator allowed?

Yes, subject to SEAB regulations, though software skill remains essential.

Does the lab include time to save files?

Yes. The 2-hour-15-minute duration includes time for saving the required work.

Is G2 Computing the same as G3 Computing?

No. G3 K349 has a different subject level, five modules and a Python/JupyterLab lab.

Can I practise using my own software at home?

Use school-approved platforms and confirm the examination’s installed software requirements rather than assuming any app will be provided.

SEC grades and future course choices

Official SEAB documents and further reading

What is SEC Examinations | G2 Computing (SEAB K237)? G2 Computing K237 is a new Singapore–Cambridge Secondary Education Certificate subject with its first examination in 2027. It is not only coding. Students learn six connected modules: computer fundamentals, networking, the impact of computing, spreadsheets, media software and programming. The assessment includes a computer-delivered e-examination and a practical lab examination where candidates create and submit digital files.

What parents and students need to know first: The two compulsory papers are weighted equally despite different raw marks. Paper 1 is a 90-minute computer-delivered e-exam worth 70 raw marks and 50% of the grade; it contains 20 MCQs for 20 marks and short structured tasks for 50 marks. Paper 2 is a 2-hour-15-minute lab exam worth 80 marks and 50% of the grade, with media-software work (about 30 marks), spreadsheets (about 25) and programming (about 25). The practical uses Scratch for game programming and spreadsheets and media software as applicable; MakeCode microcontroller blocks are assessed in Paper 1 only.

2027 SEC level: G2.
Official code: K237; new subject without an earlier equivalent code.
Paper 1: e-Examination: 70 marks, 50%, 1 hour 30 minutes.
Paper 2: Computer-based practical: 80 marks, 50%, 2 hours 15 minutes.
All questions: compulsory in both papers.
Official syllabus: SEAB K237 2027 PDF.
School subject list: SEAB 2027 G2 examination subjects.
First action: confirm the student’s correct code, exam software and component requirements.

Why does the 2027 SEC Computing syllabus matter?

The paper structures explained, one at a time

Paper 1: e-Examination

Paper 2: Computer-based practical

Understanding assessment objectives, not merely marks

The subject modules explained through familiar situations

Module 1: computer fundamentals

Module 2: networks and the internet

Draw a home network including three devices, a router and modem. Label what the router connects, what a cloud application requires and where a breakdown could occur.

Module 3: technology, safety, AI and digital ethics

Give two fictional messages, one from a verified school account and one asking for a password through a suspicious link. Discuss how to check authenticity without clicking or exposing personal data.

Module 4: spreadsheet data and formulae

Practise a small budget workbook: use SUM for totals, percentage formulas for comparisons and an absolute reference where one rate applies to several rows. Check the result by hand on one row.

Module 4: chart quality and validation

Give students a fictional weekly attendance table and ask which chart best shows change over time. Then create a rule to reject negative attendance counts.

Module 5: vector graphics and editing

Create an original three-shape symbol for a reading club. Test alignment, contrast and readability at both large and small display sizes.

Module 5: video and multimedia

Plan a 20-second original school-event video with three clips and a title. Explain what each sequence communicates and how the exported file would be checked.

Module 6: Scratch programming fundamentals

Trace an original Scratch-style score counter from an event, through a condition and into a variable update. Write the expected new value after each action.

Module 6: Scratch game behaviour

Games use sprites, coordinates, orientation, costumes, backdrops, timing, event messages and interactions between objects. The program must respond consistently to user inputs and state changes.

A character can appear to jump while a collision condition remains wrong. Test the condition and the expected event rather than simply adjusting the sprite graphic until it looks correct.

Design a game with one moving character, one target and a score. Plan what happens on collision and when the game ends, then test edge conditions.

Module 6: MakeCode only where listed

Prepare one conceptual MakeCode trace for a sensor and LED output, then use Scratch for a practical game task with variables and conditionals.

Computational thinking: decomposition and abstraction

Decomposition separates a difficult job into manageable parts, while abstraction retains relevant features and removes distracting detail. These approaches help both programming and spreadsheet work.

Design a simple borrowing counter with a flowchart and list the data a program truly needs. Separate appearance choices from rules.

Debugging with normal and boundary cases

Suppose a program displays ‘Success’ when score is greater than 50, but the rule says 50 and above. The boundary input 50 exposes the error; the correct comparison should include equality.

Prepare test cases for 49, 50 and 51. State the expected and observed result of each before changing the conditional.

File saving and lab workflow

Practise a mock lab with named deliverables and a final checklist: file present, correct format, opens successfully and corresponds to the task. Follow actual SEAB naming requirements when published.

Understanding K237 versus G3 Computing K349

Use a two-column checklist showing modules, software, paper mode, raw marks and weights for the subject the student is actually taking.

Original worked examples and skill checks

Example 1: Binary and bytes

Why it works: The key is to state whether the prefix is decimal or binary when precision matters, not simply convert every quantity by a guessed factor.

Try a fresh condition: Compare 1,000,000 bytes and 1,048,576 bytes and explain why they are different quantities.

Example 2: Two devices, one local network

Situation and result: A laptop connects through a Wi-Fi router to a printer, but the internet service is down. Printing locally may still work because the LAN can remain active.

Why it works: A local network can continue functioning when external connectivity fails. The printer’s location and network configuration determine the actual possibility.

Try a fresh condition: Name one possible reason the printer cannot be reached despite working Wi-Fi.

Example 3: Cloud storage reliability

Situation and result: A learner edits a document in a cloud application but has no internet connection during the next session.

Why it works: Cloud applications may require network access or offline support; local storage may remain available without internet. Avoid assuming every cloud service behaves identically.

Try a fresh condition: Suggest a responsible backup routine that protects work while respecting school data policies.

Example 4: Spreadsheet SUM

Situation and result: Cells B2 through B6 contain the numbers 12, 14, 8, 16 and 10. `=SUM(B2:B6)` yields 60.

Why it works: The range covers five numeric cells. Counting the column header or leaving out the last row would change the result.

Try a fresh condition: Modify B6 to 20 and predict the new total before opening the spreadsheet.

Example 5: Copying a fixed rate

Situation and result: A discount rate of 10% sits in cell E1 and each item’s price appears in column B. A suitable copied formula in C2 is `=B2*(1-$E$1)` if E1 contains 0.10.

Why it works: The dollar signs keep the reference to the common rate fixed when the formula is filled down, while B2 changes to B3, B4 and so on.

Try a fresh condition: Copy to row 3 and explain which references move and which remain fixed.

Example 6: Validation of a score

Situation and result: A spreadsheet accepts scores from 0 to 100 inclusive. Input validation should reject −1 and 101 while accepting 0, 50 and 100.

Why it works: Boundary testing checks limits that routine mid-range practice may miss. A custom error message should tell the user what values are allowed.

Try a fresh condition: Propose a validation rule for a whole-number student count that cannot be negative.

Example 7: Line graph or pie chart

Why it works: The chart type should match the question, not merely the software’s most colourful option.

Try a fresh condition: Choose a chart for a breakdown of all sign-ups across three event categories at one date.

Example 8: Vector versus raster

Situation and result: An original school logo is made of vector paths. Enlarging it normally retains smooth shape boundaries, while stretching a low-resolution raster may expose visible pixels.

Why it works: The difference arises from geometric paths versus a fixed grid of pixel information.

Try a fresh condition: Describe which format is preferable for a large printed banner and one caveat about export.

Example 9: Video storyboard

Situation and result: A 20-second video has four five-second clips: opening location, activity, participant reaction and closing information.

Why it works: The sequence gives a beginning and end; editing must also preserve readable titles and the desired output.

Try a fresh condition: Reorder clips two and three and discuss whether the viewer’s understanding improves or worsens.

Example 10: Scratch variable trace

Situation and result: A Scratch-style game sets score to 0, then raises score by 2 whenever a player collects a token. After three successful collections, the expected score is 6.

Why it works: The update should occur only when the collection event is true, not every time a loop checks whether the sprite exists.

Try a fresh condition: Add one unsuccessful collision and predict whether the score should change.

Example 11: Scratch conditional boundary

Situation and result: A game displays a win screen when score is 10 or more. A conditional using ‘score > 10’ fails at exactly 10.

Why it works: The correct logical condition includes 10, and a boundary test exposes the difference.

Try a fresh condition: Prepare expected results for scores 9, 10 and 11.

Example 12: Loops and changing state

Situation and result: A loop repeats an action five times, changing a counter from 0 by +1 each time. The final value is 5, assuming the loop executes five iterations.

Why it works: Students should trace the counter before and after each iteration rather than infer the result from the word repeat alone.

Try a fresh condition: Start counter at 3 and predict the final value.

Example 13: MakeCode sensor conceptual question

Try a fresh condition: Add an exact-equality reading and decide whether the condition should use less-than or less-than-or-equal.

Example 14: Troubleshooting an exported file

Situation and result: A student finishes a video task but the exported file is missing the final title. The timeline was edited after the most recent export.

Why it works: The deliverable is the exported output, not the appearance of the editing interface. Saving the project and exporting after edits are separate steps.

Try a fresh condition: Create a mock check that reopens the final file and verifies three required features.

Example 15: Cybersecurity message

Situation and result: A fictional message says a school account will be closed unless the user submits a password through an unfamiliar form within ten minutes.

Why it works: Urgency and requests for credentials are warning signs; verification should occur through the school’s established channel, without using the suspicious link.

Try a fresh condition: Write a short checklist that avoids sharing personal secrets while confirming a legitimate notice.

How to plan, test and debug a computing solution

What an effective mock lab looks like

Ten common mistakes and why they matter

Assuming G2 Computing is only Scratch

The syllabus also examines fundamentals, networks, impact, spreadsheets and media software.

Using G3 Python instructions for G2

G2 Paper 2 uses the prescribed software and Scratch, media and spreadsheets, not the G3 Python/JupyterLab format.

Treating both papers as 50 raw marks

They have different raw totals, 70 and 80, but each is weighted 50%.

Ignoring Paper 1 because it is digital

The e-exam covers all six modules and has 20 MCQs plus 50 marks of structured tasks.

Practising MakeCode for the lab instead of Scratch

MakeCode blocks are assessed in Paper 1 only under the published K237 tables.

Not allocating time to media creation

The practical includes about 30 marks on media software, a meaningful task beside spreadsheets and programming.

Wrong spreadsheet references

Use relative or absolute references deliberately and test copied formulas on more than one row.

Unreliable exported or unsaved files

Check the actual digital deliverables, names and formats against the exam instructions.

Overlooking scams and AI limitations

Cyber safety and impact of computing are part of the official content and not optional background.

Relying on one familiar programming example

Practice tracing code with changed initial values and boundary cases to reveal hidden assumptions.

A six-week study sequence

Week 1 — confirm the correct code and environment

Read the K237 table and school guidance. Diagnose concepts, practical fluency, file management and tests separately.

Week 2 — rebuild core data and network understanding

Practise vocabulary with drawings, comparison cases and short source questions. Explain the difference between storage and memory, or LAN and internet.

Week 3 — develop spreadsheet reliability

Create formulas, use correct references, select charts and test validation rules. Change the data to check whether the workbook behaves correctly.

Week 4 — strengthen programming and debugging

Use Scratch variables, conditions, loops, events and lists, with MakeCode theory where relevant. Trace before running.

Week 5 — perform a simulated paper and lab

Match the syllabus time and mode. For G2 include digital media; for G3 include the required Python and spreadsheet tasks. Practise saving and checking output.

Week 6 — correct the highest-impact problems

Use an error log to identify recurring mistakes. Retest with fresh inputs, confirm the permitted software and equipment, and protect rest before examinations.

Questions parents can ask without writing code themselves

What exactly is the task’s input and expected output?
Which part of the program or spreadsheet makes the important decision?
What happens when the input is zero, missing or exactly at the limit?
Can you explain the difference between a wrong answer and an invalid file?
How did you check whether the formula still works when copied?
Which software and response mode does the 2027 K237 paper actually require?
Where is your saved final output, and can you reopen it?
Can you show me one change you made after testing?
What would make the system unsafe or unfair to users?
What new question will prove you understand this skill next week?

Frequently asked questions about G2 Computing K237

What is G2 Computing K237?

A new 2027 SEC G2 subject assessing fundamentals, networking, digital impact, spreadsheets, media software and programming.

Did G2 Computing have an old N(A) code?

SEAB lists its previous reference as not applicable because K237 is a new 2027 syllabus.

What is the Paper 1 format?

A 90-minute computer-delivered e-exam: 20 MCQs and 50 structured marks, total 70.

What is the practical format?

Paper 2 is a 135-minute lab examination worth 80 marks, with three tasks across media, spreadsheets and programming.

How are the papers weighted?

50% each, even though raw totals are different.

Is MakeCode examined in Paper 2?

The syllabus tables specify MakeCode blocks for Paper 1 only; Scratch is listed for Paper 1 and Paper 2.

Does Paper 2 require media work?

Yes, with an approximate 30-mark task along with spreadsheet and programming tasks.

Do all questions have to be answered?

Yes. Both papers are compulsory and the syllabus states all questions in both are compulsory.

Is an approved calculator allowed?

Yes, subject to SEAB regulations, though software skill remains essential.

Does the lab include time to save files?

Yes. The 2-hour-15-minute duration includes time for saving the required work.

Is G2 Computing the same as G3 Computing?

No. G3 K349 has a different subject level, five modules and a Python/JupyterLab lab.

Can I practise using my own software at home?

Use school-approved platforms and confirm the examination’s installed software requirements rather than assuming any app will be provided.