Three students in school uniforms work through open books at a classroom table, with textbooks and stationery nearby and study notes on the whiteboard behind them.

Making Sense of G2 Computing Syllabus | SEC 2027 Parent and Student Guide

Making Sense of G2 Computing Syllabus is a practical introduction to the new 2027 Singapore-Cambridge SEC G2 Computing subject, syllabus K237. Students learn six connected modules: computer fundamentals, networking, the impact of computing, spreadsheets, media software and programming. The examination has a 70-mark e-Examination paper lasting 1 hour 30 minutes and an 80-mark lab-based paper lasting 2 hours 15 minutes. Both are compulsory and weighted equally, at 50 per cent each.

Parents can support this subject without being software engineers. The right questions are: Can the student explain why a computer or network behaves as it does? Can they select sensible tools, build a spreadsheet or media product, debug a visual program and save the required files independently? Practical confidence should develop alongside knowledge, responsible online behaviour and realistic subject choices. Confirm school offerings and the precise examination software requirements; do not assume that any home setup automatically matches an examination centre.

Quick summary:

Chapter navigator

  1. A new G2 Computing examination in 2027
  2. Paper 1 versus Paper 2: read the fine print
  3. The three assessment objectives
  4. Module 1: what is inside a computer
  5. Input, processing and output
  6. LAN, WAN, client and server
  7. IP addresses and MAC addresses
  8. Cloud services versus local storage
  9. Impact of computing and artificial intelligence
  10. Cybersecurity, scams and privacy
  11. Spreadsheets: data types and formatting
  12. Relative and absolute cell references
  13. Choosing spreadsheet functions
  14. Sorting, filtering and data validation
  15. Charts that communicate rather than decorate
  16. Vector graphics versus raster images
  17. Presentations, video and storyboards
  18. Programming begins with events and sequences
  19. Variables, conditions and loops
  20. Lists, functions and custom blocks
  21. Game programming: sprites, states and messages
  22. Microcontrollers have a specific paper boundary
  23. Paper 2 requires real file-management fluency
  24. How to debug rather than guess
  25. Four weeks of practice with visible outcomes
  26. What parents should and should not buy
  27. Subject choice, future pathways and sensible expectations
  28. Frequently asked questions about K237

1. A new G2 Computing examination in 2027

G2 Computing, syllabus K237, is listed as a new subject in the 2027 Singapore-Cambridge Secondary Education Certificate framework. It is not just another name for a general computer-literacy lesson or an assumption that every pupil will study a conventional text-based programming language. Its six modules connect computing fundamentals, networks, social impact, spreadsheets, media software and programming. The subject asks students to understand systems, make digital products and troubleshoot them. Families should check which schools offer K237 and the precise course arrangements before assuming that a learner’s Posting Group guarantees a place.

Illustration and practice: Ask a young person to describe what they have made on a computer rather than simply how many hours they spend using one. Editing a video, constructing a chart and debugging a game are different kinds of evidence. Interest in gaming alone does not establish readiness to plan a program or work systematically with data.

2. Paper 1 versus Paper 2: read the fine print

The K237 examination has two compulsory papers, each weighted at 50 per cent despite different raw marks. Paper 1 is a 1-hour-30-minute e-Examination worth 70 marks: 20 multiple-choice questions worth 20 marks and short structured questions worth 50. It covers all six modules. Paper 2 is a 2-hour-15-minute lab-based examination worth 80 marks and covers spreadsheets, media software and programming. All questions in both papers are compulsory. Candidates submit digital work for the practical paper; time to save required files is included.

Illustration and practice: A strong Paper 1 score cannot compensate for having no practical skills without consequences, because Paper 2 counts half. Ask the student to attempt a conceptual explanation, then produce a real file under a small time constraint, and compare the two performances.

3. The three assessment objectives

The official objectives separate knowledge and understanding, applying that knowledge, and using software to produce computing solutions. Their approximate overall weights are 20 per cent, 30 per cent and 50 per cent respectively. Students who can recognise a software menu but cannot create an accurate output need practice in production. Students who can follow a demonstration may still be unable to explain what a function or network device does. A balanced revision plan must include facts, explanations, decisions and practical artefacts. Memorising screen locations is especially brittle when a task changes.

Illustration and practice: Use a fictional school-club dataset to test three jobs: explain what a spreadsheet formula does, select a suitable chart and create that chart with meaningful labels. Record which part fails independently. The correction is not necessarily more time spent looking at tutorial videos.

4. Module 1: what is inside a computer

Students study CPU, GPU, main memory and secondary storage, along with common input and output devices. The key is purpose. A CPU executes general instructions, a GPU is useful for graphics processing, memory holds data being used and secondary storage retains files beyond a particular working session. Specifications affect how a computer performs, but the best purchase or setup depends on the task. The syllabus also includes comparing data units and types of secondary storage. A student need not buy expensive equipment just to learn these concepts.

Illustration and practice: Present two hypothetical laptops: one with more storage and one with more memory. Ask which might help a pupil who opens many programs and which might help someone who saves large video files. Demand a reason and avoid the simplistic claim that a single large number makes a computer ‘best’.

5. Input, processing and output

A computer system transforms suitable input data through processing to generate output. Students should be able to identify each stage in everyday applications. A microphone provides audio input; software processes it; speakers or a saved file may provide output. For a scanner, keyboard or barcode reader, the data flow differs but the reasoning is similar. The useful learning objective is to understand what information is received, what computation occurs and what result becomes available. This also supports later discussion of errors: poor input can lead to poor output even when the program runs.

Illustration and practice: Ask the child to map how a school library records a borrowed book using a barcode. What is scanned, what record is changed and what message appears to the librarian? Then alter the scenario so the barcode is damaged and discuss how the system might respond.

6. LAN, WAN, client and server

Networks allow devices to share information and resources. A home local area network connects devices in a limited area; the internet connects networks over large geographical distances. Students meet clients and servers, modems, wireless routers and network interfaces. They should understand the jobs of these components without claiming that one device is always identical to another. The G2 syllabus also distinguishes wired and wireless communication and intranets from the wider internet. Make the relationships visible through a simple diagram rather than isolated abbreviations.

Illustration and practice: Draw a phone, printer, laptop, router, modem and online service. Ask the pupil to trace what happens when a page is printed locally and when a webpage is requested over the internet. The paths should not be described as identical just because both involve computers.

7. IP addresses and MAC addresses

K237 includes the distinction between Internet Protocol addresses and Media Access Control addresses. These serve different purposes in communication: one supports routing across networks, while the other is used to direct data on a local network. The learner should not memorise only that both are ‘addresses’. Ask what kind of delivery problem each helps solve and how a device’s network identity may change in different circumstances. This topic becomes clearer when introduced through an analogy, but the analogy must not replace the technical distinction.

Illustration and practice: Compare a street address used to route a parcel through a city with a local delivery label within a building. Explain where the analogy breaks down, especially since network configurations can change. This builds a more precise answer than saying one address is simply ‘longer’.

8. Cloud services versus local storage

Cloud storage and applications involve computing resources accessed through the internet. Local storage and locally installed applications can provide different advantages and limitations. Students should examine access, connectivity, collaboration and control, not assume that cloud services are magically safe or always available. A file saved in a cloud account still requires responsible access settings, and internet outages may affect use. The syllabus treats these comparisons as part of understanding networks and practical technology decisions.

Illustration and practice: Give the student two situations: a group project needing shared edits and a task that must work without internet access. Ask which storage or application setup is appropriate and why. The response should mention at least one limitation of the preferred option.

9. Impact of computing and artificial intelligence

The syllabus explores computing in communication, education, transportation and retail, as well as examples of artificial intelligence such as classification, speech recognition and content generation. A mature answer weighs useful outcomes against limitations and consequences. A student who says ‘AI is always correct’ has missed a central idea. Systems depend on their inputs, design and operating conditions; users still need to check factual claims and respect privacy. This is an opportunity to teach practical judgement rather than admiration for fashionable technology.

Illustration and practice: Ask pupils to compare a human-created summary and an automated summary of a school announcement. What would they verify before acting on it? Discuss how inaccurate dates or invented details could affect a family, while acknowledging that software can also save time.

10. Cybersecurity, scams and privacy

Responsible computer use includes protecting accounts, recognising scams, understanding malware types, maintaining backups and thinking about personal information online. Password strength, updates and security tools help reduce risk but do not make risk disappear. The objective is to cultivate habits: inspect unexpected requests, use official channels for verification, do not share one-time codes, and store work safely. Students should also understand copyrighted material and avoid assuming that everything found online can be republished as their own.

Illustration and practice: Give a fictional message claiming that a student must urgently log in through an unfamiliar link to retain examination access. Ask which features are suspicious and how to verify through an independent official channel. Do not use a real credential or click the link for the exercise.

11. Spreadsheets: data types and formatting

A spreadsheet’s display is not the same as its underlying data. K237 includes formats for numbers, currency, percentages and dates, plus selected forms of conditional formatting. Students should recognise when a displayed percentage reflects an underlying fraction and should avoid converting text-looking numbers incorrectly. Formatting can improve readability, but an attractive worksheet with wrong formulas is not accurate. Conditional formatting may highlight values meeting a condition, yet the student must understand what that condition means. Build a reasoned data workflow before decorating cells.

Illustration and practice: Use a small expense table: amount, category and date. Format currency and dates appropriately, then highlight entries above a stated threshold. Ask whether a red cell is automatically a mistake or simply meets a rule chosen by the author.

12. Relative and absolute cell references

Relative references adjust when a formula is copied, while absolute references remain anchored to a chosen cell. This difference allows efficient spreadsheets but is a frequent source of errors. In a column of prices, `=A2*$D$1` could apply a fixed tax or rate stored in D1 as the formula is filled downward. If the dollar signs are omitted, the copied formula may refer to the wrong rate. Understanding why references move is more useful than remembering where the toolbar button sits.

Illustration and practice: Build a three-row price calculator and copy one formula down. Let the pupil deliberately remove the absolute reference and observe the changed outputs. The comparison makes a hidden error visible and encourages a check before submitting the practical file.

13. Choosing spreadsheet functions

The syllabus lists logical, arithmetic, statistical, text, lookup and date functions. These include IF, SUMIF, AVERAGEIF, COUNTIF, VLOOKUP and several others, but students should consult the exact examinable list and any specified limits. Knowing the name is not the same as identifying the problem a function solves. A student should be able to explain the inputs, predict an output, and test an edge case. Building a large function collection without understanding arguments is not efficient preparation.

Illustration and practice: Ask how to count club members who attended more than a threshold number of sessions. Compare manual counting with a condition-based spreadsheet formula, then change one attendance entry and observe whether the result updates correctly. The test checks both function selection and formula validity.

14. Sorting, filtering and data validation

Sorting changes the order in which records appear; filtering changes which records are currently displayed. Both can help analyse a dataset, but neither should silently change the meaning of the records. Data validation places constraints on accepted input and can show helpful error messages. These techniques are particularly relevant to tasks where a spreadsheet must remain usable by someone else. A good student checks whether a chosen sort range keeps whole records together and whether a validation rule rejects genuinely invalid entries.

Illustration and practice: Create a table of students, classes and attendance. Sort by attendance, filter one class and then set a validation rule on a score column. Ask what happens if the user types an impossible score. This is more instructive than merely memorising menu names.

15. Charts that communicate rather than decorate

The K237 syllabus includes bar, column, line, pie and combination charts, including a limited combination of columns and lines. Charts need accurate labels, axes and legends. Students must select a form appropriate to the question, not use the most colourful chart available. A line chart is often suited to time trends; a bar chart may compare categories. Pie charts can show proportions when the data represent a sensible whole. Editing the source table should update the linked chart.

Illustration and practice: Give the learner monthly club attendance and a separate table of snack preferences. Ask for the most useful chart for each dataset and an explanation of the choice. Then require title and axis labels and see whether the graph changes when one value is corrected.

16. Vector graphics versus raster images

Vector graphics use shapes and paths that can be resized without the same pixelation concerns as raster pictures. Raster images consist of coloured pixels and can lose apparent quality when enlarged. The syllabus covers both types and editing operations such as shapes, layering, grouping, transparency, resizing, cropping and adjustment. A learner should select a suitable format for an intended output. Simply naming a PNG or JPEG does not demonstrate understanding of why a certain file type or process fits a specific job.

Illustration and practice: Ask the student to design a simple club logo with geometric shapes and export it. Then enlarge the exported image and compare it with the editable vector version. Discuss why original editable files are valuable even after a final graphic has been saved.

17. Presentations, video and storyboards

The media module also includes consistent slide layouts, storyboarding, video construction, transitions, text, audio and basic frame-rate awareness. A good video task begins with the intended message and the sequence of scenes, not with a random sequence of effects. Students should practise arranging material in a logical order and checking whether audio can be heard and text can be read. The practical assessment may require producing such assets, so the student must know how to save and locate the final file.

Illustration and practice: Have the child plan a 30-second explanation of a school-club activity in four frames. Then build it with appropriate text and images. Compare the planned sequence with the export, checking clarity, consistency, timing and copyright permission for any reused material.

18. Programming begins with events and sequences

K237 programming includes interpreting flowcharts, using variables, conditional instructions, loops and visual programming blocks. For many learners, the crucial step is understanding that code executes in an order affected by conditions and events. The visible sprite in a game is only the front of the system. Students should predict what a sequence of blocks will do before running it, then compare prediction with the result. A program that ‘looks right’ may still contain faulty logic. Explanation and testing are complementary.

Illustration and practice: Take a sprite that moves ten steps when a key is pressed. Ask the learner to draw an event-sequence diagram and predict where the sprite will end after repeated key presses. Then change the step count and observe whether the prediction still works.

19. Variables, conditions and loops

A variable stores a value that can be updated. A condition selects what happens when a statement is true or false. A loop repeats instructions in a defined way. The distinction matters: using a one-time conditional where ongoing checking is required can produce an unexpected result. The syllabus includes nested conditions up to a stated level, different loop types, logical operators and random numbers. Students must be able to state what will happen for ordinary, boundary and unexpected inputs.

Illustration and practice: Write a block-program idea for a game in which a score increases when an object is collected. Ask what resets the score, what makes it increase and what stops the game. Test a case in which the player collects two objects almost simultaneously.

20. Lists, functions and custom blocks

Lists store several related values; custom blocks or functions package repeated instructions into a named operation. They support organisation and reduce duplication in a program. Students should understand what happens when an item is inserted, removed or changed at a given position, and what an empty or out-of-range situation might mean in the software. A custom block should have a clear job rather than combine unrelated steps. The syllabus specifies particular list operations and visual-programming blocks for examination.

Illustration and practice: Make a small list of game levels or names, then add and delete entries and predict how positions change. Next turn a repeated sprite action into a custom block and check that the game behaves the same way. The purpose is clarity and reuse, not making the code longer.

21. Game programming: sprites, states and messages

The game component includes stage coordinates, sprites, costumes, backdrops, movement, events, sounds, broadcast messages and collision detection. A well-structured project distinguishes visual appearance from the logic that controls it. When two scripts run concurrently, the order of events can affect outcomes. Students should debug what changed, what should have happened and which block prevented it. They also need basic practical habits such as giving objects meaningful names and organising a project before an examination.

Illustration and practice: Set up a game where touching a target changes a score and a backdrop changes at a threshold. Ask the pupil to test a target hit, a miss and two rapid hits. A bug log that identifies the trigger and outcome is more useful than clicking random blocks until something moves.

22. Microcontrollers have a specific paper boundary

The syllabus includes sensors, built-in and external inputs, outputs and block programming for microcontrollers. Its official note specifies that this microcontroller component is assessed in Paper 1 only. This distinction matters: pupils should understand sensor and output logic, but should not prepare for a physical-hardware build task in Paper 2 on the assumption that every teaching activity must appear in the lab examination. Schools may use prototype projects for learning, while examination arrangements follow the actual syllabus.

Illustration and practice: Imagine a light sensor controlling an LED display. Ask what input is being measured, what condition is tested and which output changes. Draw the logic as a simple flowchart. The model can be discussed without buying electronics or connecting unapproved equipment.

23. Paper 2 requires real file-management fluency

The practical examination is administered on a computer, and candidates submit required softcopies for marking. The official time allocation includes saving work. A correct spreadsheet formula or graphics composition may be worth little if the specified file is not saved in the required place or format. Students should practise identifying the working file, naming it accurately, saving changes and checking that it opens. Schools control their examination computer environment and approved software; home setups should support learning without pretending to reproduce the entire examination infrastructure.

Illustration and practice: During a timed home exercise, ask the child to create a chart, export an image and save a small program under clearly distinct filenames. At the end, close and reopen each file. This last step catches practical errors that ordinary written revision cannot reveal.

24. How to debug rather than guess

Debugging is a repeatable inquiry: observe actual behaviour, form a hypothesis, isolate the smallest change, test again and record what worked. It applies to formulas, charts, media exports and programs. A student who makes five unrelated changes simultaneously cannot know which one solved the problem. Good debugging also includes recognising when the data were wrong rather than the software. In school, ask the child to preserve the initial incorrect result so the correction can be understood, rather than erasing evidence of the learning process.

Illustration and practice: Give a spreadsheet total that updates incorrectly after one row is inserted. Let the student inspect referenced cells and test a smaller version. Once corrected, introduce a second row and check whether the formula is robust. The child should be able to explain the cause.

25. Four weeks of practice with visible outcomes

Week one can sample the six modules and identify whether the pupil’s difficulties are conceptual, practical or organisational. Week two focuses on one spreadsheet task and one programming issue, with clear success criteria. Week three introduces media production plus mixed questions from Paper 1. Week four includes one timed e-exam-style short set and one practical task with saving and checking. Adjust the sequence around school instruction and avoid copying specimen material without permission. A practical routine is a method for learning, not an official SEC timetable.

Illustration and practice: Keep four artefacts: an early spreadsheet, a corrected formula workbook, a small game and a media output. Ask the student to explain what was changed and why. This creates meaningful evidence of growing independence instead of measuring hours spent watching screens.

26. What parents should and should not buy

Computing does not require a family to purchase the fastest laptop or every commercial design app. Start by asking the school which software is used in class and what is needed for homework. Some approved examination environments differ from what a family has at home. Resources should support spreadsheets, media work and visual programming at the necessary level. It is sensible to prioritise safe practice, a stable place to save work and adequate time over expensive devices. A school may also provide lab access.

Illustration and practice: Before buying software, ask the child to demonstrate what existing tools cannot do for a real course task. Verify compatibility and school requirements. Buying a subscription to solve a basic planning or file-management problem often misses the underlying learning need.

27. Subject choice, future pathways and sensible expectations

K237 can help students explore systems, design and computational thinking. It is not, by itself, a guarantee of a computing career or any particular post-secondary admission. An appropriate choice depends on interest, school availability, prerequisite readiness, other subject commitments and current post-secondary criteria. A student who enjoys structured problem solving may thrive, while another may discover that precise testing and troubleshooting require more patience than expected. The school is best placed to explain actual combinations and opportunities to study subjects at different levels.

Illustration and practice: Ask the student to bring one self-made artefact and explain its original goal, what failed, what was repaired and what they would improve next. This gives much better evidence of motivation and ability than a declaration that they love computers.

28. Frequently asked questions about K237

Is G2 Computing a wholly practical subject? No; Paper 1 assesses knowledge and application across all six modules, and Paper 2 assesses software production. Does Paper 2 have more weighting because it has 80 marks? No, both papers contribute 50 per cent. Must every candidate program a microcontroller in the lab? The microcontroller element is specified for Paper 1 only. Is the subject just Scratch? No; spreadsheets, media tools, networks and impacts are substantial components. Does the exam require candidates to save work? Yes, the practical paper requires submission of softcopies, within its time allocation.

Illustration and practice: Before assessment week, make a two-column checklist: explain and produce. Every learner should be able to explain a computing idea, apply it to a small decision, produce a working digital artefact, and submit the correct saved file. Those are related but separate skills.

Official syllabus documents

Read the 2027 K237 G2 Computing syllabus PDF, the G2 school-candidate syllabus directory and the SEC overview. Private-candidate offerings and software notes are listed separately. The directory provides specimen-paper resources for the new subject. Consult those official versions for assessment detail, but make learning examples original and age-appropriate. This guide does not replace examination instructions or school-specific requirements.

Explore the connected learning guides

Choose the question that brought you here. Open one useful guide, try a small task, and stop when you have what you need.

Take one question further

The same learning habit can travel across subjects, while each subject keeps its own methods. These routes help you notice a difficulty, understand one part of it, and return to something you can do.

A word is familiar, but using it is difficult.

Move from recognising a word to retrieving it in a new context. Understand vocabulary plateaus.

Try it without the guide: Choose one word you already know. Close the guide and use it in a new sentence. Explain why it fits; try another context tomorrow.

A piece of writing has ideas, but the reader loses the thread.

Make the order of events and the links between sentences clear. Explore composition writing.

Try it without the guide: Choose one short paragraph. Read the relevant explanation, close it, and revise the paragraph. Ask someone to tell you what happened and why.

The Mathematics seems familiar, but marks still disappear.

Find the first point where the working stops being reliable. Find Secondary 4 A-Math mark leakage.

Try it without the guide: For a Secondary 4 A-Math question you have attempted, locate the first uncertain line. Repair that step, then try a comparable question without the worked answer.

A Science fact is remembered, but the explanation is incomplete.

Connect the evidence to a scientific idea and the resulting change. Follow the Primary Science learning route.

Try it without the guide: Choose a familiar Primary Science example. Explain the evidence, the idea and the result without notes. Then change one condition and explain your prediction.

Two accounts of the world seem to disagree.

Check the question, source, date and evidence before combining claims. Explore the World Knowledge research library.

Try it without the guide: Take one claim. Find the source best placed to support it, note its date, and state what remains uncertain. Return to your original question.

There is plenty of help, but independence is hard to see.

Check what the learner can understand and do after support is removed. Understand how education works.

Try it without the guide: Choose one small task the child has practised. Agree on a calm, brief attempt without prompts. Use what happens to choose one next step, then stop.

For the structure behind these connections, read the eduKateSingapore runtime manifest and the eduKate ecosystem boot contract. The reader map describes public navigation; those manifests preserve the wider ownership and return rules.