VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Master G3 Computing SEAB Syllabus | Timeline of the Latest SEC FSBB

Three learners review open books together at a classroom table, with stacks of textbooks, stationery and a whiteboard in the bright room.

Master G3 Computing for the 2027 Singapore-Cambridge SEC with SEAB syllabus K349. Paper 1 is a two-hour written examination worth 60% (80 marks), covering five modules: Computing Fundamentals, Algorithms and Programming, Spreadsheets, Networking and Impact of Computing. Paper 2 is a 2-hour-30-minute lab examination worth 40% (70 marks), with one spreadsheet question and four to five programming questions using Python and JupyterLab. Students must understand, design, test and save working solutions, not merely watch coding tutorials.

Parents should confirm that the child takes G3 Computing K349 rather than a G1 Computing or Digital Literacy programme. Then check an original program, its test cases, a spreadsheet file and one written problem. A student may write code that runs but calculates the wrong answer, use a spreadsheet formula that fails when copied down, or confuse privacy with security. Good revision identifies the exact error and follows the school-provided software and examination instructions instead of collecting more online videos.

  • 2027 SEC G3 Computing code K349 (older reference code 7155), subject to the school’s offered curriculum.
  • Paper 1 Written: 2 hours, 80 marks, 60%, all compulsory across all five modules.
  • Paper 2 Lab-based: 2 hours 30 minutes, 70 marks, 40%; one spreadsheet and four to five Python programming questions.
  • A Python quick reference is provided; candidates save and submit required softcopy files as instructed.
  • SEAB requires school/centre facilities for candidates to access spreadsheet software, Python and JupyterLab; do not assume a personal home laptop can be brought.
  • Assessment objectives overall: knowledge 30%, application 40%, design/development/testing/refinement 30%.
  • The written SEC examination window is October–November 2027; confirm the specific Paper 2 lab arrangements with school and SEAB.
  • Train debugging, validation, trace tables, spreadsheets and responsible data handling as much as syntax.

Full SBB and the subject choice that parents should confirm

The first Full Subject-Based Banding cohort began Secondary 1 in 2024. Posting Groups refer to entry into secondary school while G1/G2/G3 identify individual subject levels. The consolidated Singapore-Cambridge SEC is examined from 2027, and the certificate records subjects and levels sat. A child enrolled in the G3 Computing elective must follow K349, not copy another level’s syllabus simply because both include familiar computers or common software.

Computing is not identical to learning to use office software and it is not an apprenticeship in building commercial websites. The K349 specification includes architecture, data representation, Boolean logic, algorithms, Python, spreadsheets, networks, cyber-safety and societal implications. The national examination tests both theory and practical solutions. The school’s syllabus sequence and computer-lab provision should guide practice.

The immutable eduKate Clementi first-principles teaching approach is particularly appropriate for coding. A tutor should inspect where a learner’s reasoning first diverges from the problem: misunderstood inputs, an invalid loop condition, a mistaken formula or a test case that never checked a boundary. Correct that principle, then let the student implement a new solution independently. Copying an online answer until it runs gives less reliable evidence of understanding.

SEAB 2027 G3 Computing K349 official syllabus PDF

The exact examination and software requirements

Paper 1 — written examination, 60%

This two-hour 80-mark paper includes single- and multiple-answer multiple-choice items, short answers, matching, cloze and structured questions. It tests all five modules and may provide relevant formulae. Students must understand what code does, interpret truth tables, explain networks and apply computing concepts to unfamiliar situations. All questions are compulsory.

The question format makes reading precision important. In a multiple-answer item, selecting only one plausible option can fail if more than one is required. In code-reading questions, an off-by-one loop or unexpected value is often clearer through a trace table than through guessing output.

Paper 2 — lab-based assessment, 40%

This 2-hour-30-minute 70-mark paper tests Module 2 Algorithms and Programming and Module 3 Spreadsheets. There is one spreadsheet question and four to five programming questions. Candidates work on a computer with access to spreadsheet software, Python and JupyterLab, and submit the specified files electronically. The time includes saving the required work.

A child who knows the syntax of Python but cannot create a valid file, debug a program or save work correctly remains at risk. Practise the exact school-approved workflow for locating question data, naming files, testing code and checking the final outputs. Do not assume cloud tools or personal devices are available.

Centre computer provision and calculator rules

The examination centre is responsible for suitable infrastructure. The SEAB syllabus states that each Paper 2 candidate should have sole use of a personal computer in the exam, with access to required spreadsheet and programming software. An SEAB-approved calculator may be used in both papers.

Parents should ask the school what practice opportunities, versions and secure submission procedures are provided. Do not buy a specialised computer expecting the child to take it into the exam. The official school notice governs equipment, allowed files, available commands and saving instructions.

How the assessment objectives connect

The official weighting is AO1 knowledge and understanding 30%, AO2 application 40% and AO3 design/development/testing/refinement 30%. Paper 1 accounts for 60% and Paper 2 for 40%. A well-prepared learner therefore understands concepts, applies them and also develops working solutions systematically.

Practice should include a written explanation of a method, a working implementation, tests showing where it succeeds or fails, and a revised implementation. An untested program copied from a screen is not proof of practical competence.

Five modules in the official K349 syllabus

Module 1 — Computing Fundamentals

Computer architecture, processors, memory and storage, bits and bytes, binary and hexadecimal, two’s complement and logic gates build an understanding of what a machine represents and does. Students should distinguish decimal from binary place value and know that a bit is not a byte. Truth tables with up to three inputs test whether they can reason from Boolean conditions.

Module 2 — Algorithms and Programming

Start by defining valid inputs, outputs and constraints. Use selection, iteration, Python variables, strings, lists, dictionaries, functions, file input/output, algorithmic patterns, trace tables, debugging and input validation. The syllabus includes incremental and modular design; successful programming is about solving a problem, not the number of libraries installed.

Module 3 — Spreadsheets

Cell references, relative versus absolute addressing, formulas, functions, Goal Seek, conditional formatting, date functions, lookup and statistical operations are specified. Students must build models that remain correct when copied or updated. A beautiful spreadsheet may still contain a broken mixed reference or incorrectly linked data.

Module 4 — Networking

LANs, WANs, network architecture, protocols, transmission, addressing, routing and data protection are assessed. Learners should understand why a home network differs from the public internet, the purpose of an IP address versus a MAC address and how encryption, firewalls and human behaviour affect security and privacy.

Module 5 — Impact of Computing

Computing influences people, economies, workplaces and decisions. The syllabus expects students to think about social, legal and ethical effects, including responsible collection and processing of data. The correct educational response is to identify risks and safeguards rather than treat every technology as either entirely good or bad.

Twelve skills worth practising with actual work

1. Bits, bytes and number systems

Convert between denary, binary and hexadecimal and distinguish decimal prefixes from binary prefixes.

Parent check: Ask why eight bits make a byte and whether 1 KiB equals 1,000 or 1,024 bytes.

2. Computer components and interfaces

Know the separate roles of processor, main memory, storage and typical interfaces without confusing them.

Parent check: Ask why RAM and a solid-state storage device serve different purposes.

3. Boolean logic and truth tables

Interpret AND, OR, NOT, NAND, NOR and XOR and reason about circuits of up to three inputs.

Parent check: Ask when XOR is true for two Boolean inputs.

4. Inputs and constraints

Before coding, specify valid input values, the required outputs and what should happen with invalid data.

Parent check: Ask whether a program should accept an empty name or a negative quantity.

5. Sequence, selection and iteration

Follow how instructions and branches run, and when a loop begins or stops.

Parent check: Ask what makes a loop terminate and whether the boundary case is included.

6. Data types and collections

Use numbers, strings, lists and dictionaries for appropriate purposes with clear indexing and conversion.

Parent check: Ask whether ’07’ and 7 represent the same kind of data.

7. Functions and scope

Organise code into reusable functions with parameters and return values, understanding local and global variables.

Parent check: Ask what the function receives, what it returns and what data it changes.

8. Algorithm design without shortcuts

Understand minimum, maximum, sum, search, filter and splitting patterns beyond relying only on built-in functions.

Parent check: Ask the learner to explain a search algorithm on five items by hand.

9. Trace tables and test cases

Use normal, error and boundary cases to test that the implementation really meets requirements.

Parent check: Ask what should happen at the minimum and maximum permitted values.

10. Spreadsheet references and functions

Choose relative, absolute and mixed references, logical conditions, lookups, aggregation and Goal Seek appropriately.

Parent check: Ask why a copied formula changes the wrong cell when a dollar sign is missing.

11. Network security and privacy

Explain encryption, passwords, malware, phishing, firewalls and lawful personal-data handling as principles.

Parent check: Ask why collecting fewer personal details can reduce risk.

12. File saving and independent lab execution

Create, test, correct and save programs and spreadsheet files under the required school environment.

Parent check: Ask whether the final file is the one that was tested and whether its outputs meet the question.

Four original examples that show actual computational thinking

Example 1: A small program with a hidden boundary error

Imagine a classroom program asks a user for a test score from 0 to 100 inclusive. The correct validation should reject values below 0 and above 100. An inexperienced learner may write a condition that rejects 0 and 100 because they use strict inequalities. Normal cases such as 60 still work, so an ordinary demonstration can conceal the flaw.

Design test cases for -1, 0, 1, 99, 100, 101 and invalid non-numeric input when applicable. This is safe basic coding practice: it exposes why a program that runs is not necessarily correct. The student’s test report should state expected and actual results and how the logic was repaired.

Example 2: A spreadsheet formula that is right in one row but wrong after copying

Consider a fictitious class event spreadsheet with each item’s quantity in column B, price in column C and a fixed discount rate in cell F1. A formula for discounted total might multiply B2*C2 by (1-$F$1). Without the absolute reference to F1, copying the formula down changes the discount-cell address and can silently produce inconsistent totals.

The learning target is not the discount amount; it is understanding the role of relative and absolute references. Let the student predict the copied formula before using the computer, then compare. A clear spreadsheet should also label units and inputs so another reader can check its meaning.

Example 3: Binary is a representation, not a physical number of coins

Convert denary 13 into binary 1101: the bits represent 8 + 4 + 0 + 1. This is straightforward, but the important concept is positional place value. Next ask what happens when 1 is added and the last three bits carry. The child who understands this can explain rather than memorize conversions.

Extend to a small fixed-width signed representation only after positive binary is secure. Use the official two’s-complement syllabus convention and available bit width to avoid an unbounded answer. Discuss how a computer stores representations, not just what a screen displays.

Example 4: Privacy should be considered in an invented school app

Suppose students design a class reading tracker. The app needs a book title and completion status; it probably does not need a learner’s home address, identification number or private family details. A responsible design identifies the minimum necessary data, access permissions, storage duration and who can view a record.

This is a simple privacy-by-design example, not a request to bypass school systems. It links the syllabus’s security and privacy domain to practical judgement. Students should use invented test data and follow school policies and Singapore PDPA guidance when working with real information.

The 2024–2028 national and school preparation timeline

  • 2024 — first Full SBB cohort enters Secondary 1; build Mathematics, reading, digital safety and basic problem-solving habits.
  • 2025 — Secondary 2; discuss actual Computing elective availability and readiness with the school.
  • 2026 — Secondary 3; establish binary, algorithms, basic Python and spreadsheet habits, alongside other theory modules.
  • November–December 2026 — retain the student’s own code and marked work to diagnose a few recurring programming errors.
  • January–March 2027 — complete the school’s K349 sequence and regularly revisit earlier algorithms.
  • April–June 2027 — combine spreadsheets, Python and testing practice with written Computing theory.
  • July–September 2027 — rehearse official lab workflows and written-paper reasoning using unfamiliar tasks.
  • October–November 2027 — national non-language SEC written window; exact Paper 1 and lab arrangements follow SEAB and school notices.
  • January 2028 — first SEC results and appropriate 2028 post-secondary applications.

A national timeline is not a claim that a specific Python paper will take place on a particular date. SEAB and the school publish examination details and lab instructions. Teachers may introduce spreadsheet work before advanced programming or use a different teaching sequence. Parent support should follow what the child has actually studied and avoid pressuring them to learn topics outside the prescribed scope merely because a software tutorial is trending.

A useful 2027 Secondary 4 preparation plan

November–December 2026: diagnose rather than reinstall everything

Compare the student’s unassisted Python program, a spreadsheet workbook and one written test. Check whether errors arise from problem interpretation, loop control, data types, cell references, binary representation or missing tests. Repair the earliest prerequisite, then try a new task.

January–March 2027: build regular programming and theory recall

Follow the school module sequence. Each week include a short theory problem and a small programming or spreadsheet task completed independently. Ask for a clear input/output plan before implementing and require a minimal test for correctness.

April–June 2027: integrate and debug

Practise code that handles valid, boundary and invalid inputs. For spreadsheets, test formulas after copying and using new data. Include written questions on networks, logic and privacy so the practical component does not crowd out the 60%-weight written examination.

July–September 2027: simulate the school lab format

Use the school-provided environment to practise saving and locating files, running test cases and reviewing outputs. Introduce some timed tasks; do not confuse a web-based development environment with the official lab arrangements. Prepare a separate 2-hour Paper 1 revision cycle.

October–November 2027: revise for reliable performance

Obtain confirmed dates, check school lab instructions and practise specific areas where the student still loses marks. The best last-minute correction may be to fix an input-validation mistake or a spreadsheet reference, not to install a new coding framework.

An eight-week recovery programme for Computing

Week 1 — map the difficulties

Use one short unassisted program, one spreadsheet calculation and one theory task. Sort errors into concept, algorithm, syntax, runtime, logic, spreadsheet, presentation or time.

Week 2 — repair computational foundations

Work on number systems, data types and simple Boolean expressions until the student can explain them without notes.

Week 3 — rebuild selection and loops

Use small programs with one condition and one iteration; have the learner predict the output before running code.

Week 4 — learn trace tables and testing

Write expected values for normal, boundary and error cases; use print statements or traces to find the first incorrect state.

Week 5 — practise small reusable functions

Break a program into input validation, calculation and output functions with clear roles and test each independently.

Week 6 — strengthen spreadsheets

Use relative, absolute and mixed references and functions on an original dataset; then change the input and verify the results.

Week 7 — combine written and lab-style practice

Answer a short theory set and build an independent spreadsheet or Python solution under a modest time limit.

Week 8 — test a new challenge

Use unfamiliar but syllabus-aligned tasks, compare to the initial error pattern and ask the school teacher for focused intervention if needed.

What a safe and effective home week looks like

Computing students do not need to spend every evening on a screen. A useful schedule may include two 20-minute programming sessions, one spreadsheet exercise, one theory-retrieval block and a short debugging review. Encourage the child to explain the problem before opening software and to take regular breaks from the keyboard. Ask them to save work under ordinary school conventions and to reflect on why a test failed.

Parents should keep devices and accounts safe. Use dummy test data, do not share passwords, and avoid following tutorials that request administrator access or unfamiliar software downloads. Do not ask a child to experiment on real systems without permission. Ethical computing is part of the syllabus and can be reinforced by ordinary household digital hygiene.

If the child is keeping up with classes and can independently solve novel tasks, outside tuition may not be necessary. School consultation is the first reasonable move when the gap is specific. A small group may help through shared problem-solving and close debugging feedback; individual support can address significant foundational difficulties. A tutor should know Python, spreadsheets and the K349 paper scheme, and should test independent work rather than show a complete solution to copy.

Computing, AI and 2028 education pathways

Computing can be a useful foundation for later programmes in software, engineering, digital design or data analysis, but K349 alone does not guarantee admission to any course. The 2028 Post-Secondary Admissions Exercise and revised JC L1R4 calculations use the full published set of eligibility and subject requirements. Parents should verify the actual course or institution criteria rather than claiming a Computing grade substitutes for all Mathematics or Science prerequisites.

AI-assisted coding is a contemporary tool, but it can conceal poor reasoning if a student pastes generated code without understanding it. School examination conditions, originality rules and allowed software are the authority. In home learning, a tutor or parent can use generated examples for discussion only if the student can trace, test and modify the algorithm personally. Independent competency is what matters in the examination.

Common Computing mistakes

A program that runs is always correct

A program may have logic errors or fail boundary conditions. Test cases are essential.

All Computing assessment is coding

Paper 1 covers architecture, binary, networking, impact and theory across five modules and carries 60%.

The student may bring their own laptop to the exam

The school or examination centre provides the prescribed lab facilities and instructions; parents should not assume personal devices are allowed.

Copying a Python snippet proves algorithm mastery

A learner must understand the inputs, logic, outputs, validation and tests and be able to solve new problems.

A copied spreadsheet formula remains correct

Relative references may move. Use absolute or mixed references appropriately and test the result.

More advanced tools mean better SEC results

The syllabus specifies particular Python, spreadsheet and conceptual tasks; extra frameworks may not help the assessed skills.

Security and privacy are the same

Security protects systems and data against threats; privacy concerns appropriate handling, access and use of personal information.

Frequently asked questions

What is the G3 Computing code for 2027?

K349. Its older reference code was 7155.

What is the examination split?

Paper 1 written is 60%, Paper 2 lab-based is 40%.

How long is the Computing lab exam?

Two hours and 30 minutes, including time to save the required softcopy work.

What languages and applications matter?

Python, JupyterLab and spreadsheet software according to the school and SEAB syllabus.

How many lab questions?

One spreadsheet question and four to five programming questions.

Is a Python quick reference provided?

Yes, the official syllabus specifies a supplied quick-reference guide.

Does the exam test cybersecurity?

It includes networking, security, privacy and impacts as part of the written content.

Should I buy a powerful computer?

Not necessary for most curriculum work; ask the school about access and the provided examination environment.

Can AI write the child’s examination solution?

The child’s work must follow school and exam rules; independent understanding and originality are essential.

What is the best progress indicator?

A new problem solved, tested, debugged and saved independently without copied solutions.

The Paper 2 lab workflow that prevents avoidable lost work

Before writing a line of code, the student should read the task, identify the required file names or outputs and understand which supplied materials are authoritative. Write down the input assumptions, expected results and one small manual example. Implement the minimum working version first, then extend it. This reduces the chance that a long complicated program contains an error that the learner cannot locate.

After each change, run a small test. If a program is expected to process an empty list, a list containing one item and a list containing several items, each case should be checked. Save the file using the school-prescribed name and location, then reopen it if possible to confirm that the final submitted version matches the last tested solution. A candidate should not rely on unsaved notebook state or a screenshot in place of the required softcopy.

The actual laboratory examination provides specific software and file submission instructions. Practising with a home computer can strengthen general habits, but the final procedure must be learnt through the school. Parents should ask whether the student has experience with the school’s available versions of Python, JupyterLab and spreadsheets, not assume that any cloud programming tool will behave identically.

A practical test-case table for a new algorithm

Consider a fictional program that counts how many temperatures in a list exceed a given threshold. Begin with a tiny case that can be solved manually. Then test an empty list, one value equal to the threshold, all values above, all values below, repeated numbers and a negative temperature when that is a valid value. The expected result must be written before running the code. This catches mistakes such as using greater-than-or-equal when strictly greater-than is required.

Now distinguish syntax errors, runtime errors and logic errors. Syntax errors prevent the program from being parsed as intended. Runtime errors occur during execution, such as an inappropriate operation on a value. Logic errors can give a plausible but incorrect answer without crashing. A child who simply reruns code repeatedly without identifying the class of error may fail to learn from debugging.

Use a trace table to record variable values at each iteration. If the final count is wrong, find the first line or iteration where the actual value differs from the expected one. Change that step, test again and add a new boundary case. This mirrors the first-principles repair method and turns debugging into a skill the student can explain.

A spreadsheet audit before a lab submission

Spreadsheets can produce confidently presented wrong answers. Ask the child to identify which cells are user inputs, which are formulas and which are outputs. Check relative and absolute references, including dollar signs that lock a row or column, then change one input and verify that dependent results update as predicted. For lookups, ensure the referenced range and matching logic actually represent the required data.

Use a separate sense check for calculations. If a class event sells ten items at five dollars each, a spreadsheet total of five hundred dollars is implausible unless another factor is present. Labels, units, totals and formatting help a reader identify this. Conditional formatting can signal values, but visual colour does not make the underlying formula correct.

Before submitting, review whether each named worksheet or file exists and whether it contains the latest tested result. Saving an unfinished draft as the final version is an avoidable mistake, yet no amount of advanced Python syntax will repair that workflow gap. The official exam instructions always take precedence.

Security, privacy and ethical computing at home

The syllabus includes the difference between security and privacy, malware, phishing, encryption and personal-data protection. Parents can support this learning through ordinary practices: use unique strong credentials, avoid sharing recovery information, verify the sender of unusual requests and update devices through trusted channels. Do not ask a student to test a cybersecurity idea against a real network or another person’s accounts without permission.

When discussing a fictional classroom data application, consider whether the program actually needs the users’ names, addresses or birthdays. Collecting less unnecessary personal information can reduce risk. If data are collected, explain the stated purpose, who is allowed access, how long they are kept and when they should be removed. Students should use synthetic data for school exercises unless the teacher authorises something else.

AI-assisted tools may help students explore an error, but a pasted answer is not equivalent to independent programming. The child should be able to explain each relevant line, demonstrate appropriate tests and adapt the program to a new requirement. Follow the school’s academic-integrity and SEC examination rules about permitted assistance.

Official and eduKate resources

SEAB 2027 SEC G3 Computing K349 official syllabus

SEAB 2027 G3 subject directory

SEAB SEC examination and timetable overview

MOE 2028 Post-Secondary Admissions Exercise

eduKate immutable Clementi small-group teaching reference

eduKate G3 Mathematics as a Computing prerequisite

eduKate G1/G2/G3 official syllabus finder

Three correct moves for parents

  • Verify K349 with the school and understand the separate written and lab examination requirements.
  • Review one original program, one spreadsheet and one theory answer to identify two high-impact errors.
  • Plan eight weeks of independent coding, tracing, testing, saving and explanation, asking the teacher for help where progress stalls.

Computing mastery is not copying code that works once. It is understanding the problem, producing a dependable solution, testing unusual cases, protecting data and explaining decisions. This is independent parent guidance, not an official SEAB or MOE publication.