To survive G2 Computing Paper 2 for the 2027 Singapore-Cambridge Secondary Education Certificate, learn to produce and verify actual computer files—not just recognise screenshots of commands. K237 Paper 2 is a lab-based examination lasting 2 hours 15 minutes, carrying 80 raw marks and counting 50% of the subject. It has three compulsory tasks drawn from Modules 4–6: Media Software (approximately 30 marks), Spreadsheets (approximately 25 marks) and Programming (approximately 25 marks). The 135 minutes includes time to save the required softcopies on the candidate’s examination computer. A beautiful on-screen project that has not been saved or does not meet the task’s requirements is not a complete submission.
The first practical habit is to read the actual deliverables: what kind of graphic, spreadsheet or Scratch program is required, where it should be saved and how success can be tested. Then make a basic functioning version before polishing. A spreadsheet formula can produce a plausible number while using the wrong tax rate; an animation can look lively but fail to stop on the specified condition; a poster can be attractive yet export with cropped text. Every task benefits from checking the output against the instructions and an independent changed test.
G2 Computing is an introduction to digital problem solving and creative tools that can be useful in applied technology, software, digital media, business systems, data and other fields. It does not make one course or career automatic. The first SEC cohort uses full 2027 results in post-secondary applications from 2028, with course-specific requirements. The positive aim is to make digital work understandable, testable and accurate enough for another person to use.
The official Paper 2 structure in plain English
SEAB specifies two compulsory K237 papers. Paper 1 is a 90-minute e-examination of all six modules, 70 marks and 50% weight. Paper 2 is the 135-minute practical lab examination of Modules 4, 5 and 6, 80 marks and 50% weight. The Paper 2 mark guidance is approximately 30 for media software, 25 for spreadsheets and 25 for programming. These are approximate module allocations, not guaranteed identical time allocations in every actual task.
Candidates submit softcopies of required work, and the examination time includes saving. All three tasks are compulsory. The official centre is responsible for providing approved software and hardware, and the syllabus says each candidate should have sole use of a laptop for the lab. The SEAB school-candidate subject index lists Microsoft Office (Excel and PowerPoint) and Scratch among relevant software; exact installed versions and the examination’s instructions should be confirmed with school resources.
A crucial scope boundary is that microcontroller and MakeCode content is assessed under the written/electronic Paper 1 only, even though it appears in the overall G2 Computing programming syllabus. Paper 2 requires practical programming in the prescribed environment, including Scratch blocks, not the building of a physical microcontroller prototype. Do not waste the final lab revision week on an entirely different software or hardware examination.
The first seven practical lab actions
- Check the exact subject code K237 and the current school’s approved lab software versions.
- Read the tasks for required output types, filenames, dimensions, charts, behaviour and save location.
- Create and save a basic working file before adding advanced visual or programming detail.
- Test sample inputs, boundary conditions, calculations, visibility and playback against the task.
- Keep a meaningful distinction among source/editable files and exported deliverables.
- Allow genuine time for checking that the saved softcopies exist, open and contain the final changes.
- Rehearse the full media–spreadsheet–Scratch sequence within 135 minutes, then review what caused delay.
These habits are part of being a reliable digital creator, not a workaround to a grade. A student should be able to show how the work answers each requirement and what changes when an input differs. Copying a polished final sample without understanding its layers, formulas or blocks may produce one successful rehearsal yet leave the learner unprepared for an unfamiliar national task.
Why Paper 2 demands different practice from Paper 1
Paper 1 may ask which formula counts records meeting a criterion. Paper 2 may require creating a workbook in which that formula works when the records change. Paper 1 might show how one Scratch loop operates; Paper 2 may require debugging a running sprite or game. Paper 1 may test the concept of vector paths and raster pixels; Paper 2 may ask the candidate to construct and export actual media in an appropriate format.
A learner can be strong in theory and slow using a computer, or confident with menus but unable to explain a wrong formula. Prepare the two types separately and connect them with tests. Ask both why a method works and whether the saved artefact demonstrates that it works.
Media Task: communicate meaning before choosing visual effects
The Media Software task may require a visual or audiovisual artefact using specified source materials, objects, fills, outlines, transparency, cropping, layers, storyboard sequence or presentation/video editing techniques. The official scope covers vector graphics, raster graphics and presentations/videos. The right design depends on the given purpose, audience and constraints—not on how many transitions or filters are added.
Start with a task plan that lists every required visual element and the relationship among them. If a poster needs a title, date, location and safety instruction, ensure all are visible and legible before decorating. If a short video must introduce an event, display key details and end with an instruction, sequence those stages clearly. The plan should be tested against the actual deliverable, not only its appearance in the editor.
An imported image may be cropped or resized incorrectly. A title may disappear behind an opaque shape, or a grouped object may not be editable as expected. The candidate should check layer order, size and exported appearance, not assume that everything visible on the slide canvas will appear equally in the final file.
Vector graphics: paths, nodes and scalable shapes
Vector graphics describe shapes using paths and nodes. That allows suitable vector objects to be resized without raster-style pixelation. K237 includes creating lines, curves, ellipses, polygons and text; changing position, rotation, fills, outlines and transparency; grouping and ungrouping; placing text on a curved path; and manipulating nodes or merging shapes using union, intersect, fragment, subtract and combine operations.
Original fictional design task: create a clean icon for a community reading event using a circle, a curved banner and two overlapping geometric forms. A good solution uses vector shapes whose relative positions remain consistent when enlarged. The text needs to remain legible at the intended output size. If the icon requires a transparent background, verify the exported format preserves the desired transparency.
A student who saves a very small raster screenshot of the icon may find it blurred when enlarged. A vector original is useful for editing, while the raster export may be required for a particular submission. The file’s function, not its mere presence, determines which version is appropriate.
Raster graphics: pixels, cropping and quality checks
Raster graphics are composed of coloured pixels. K237 includes recognising PNG, GIF, TIFF, BMP and JPEG format characteristics, including transparency support, and applying crop, resize, brightness, sharpness and contrast operations. A photograph may be useful as a raster image even though enlarging it far beyond its original resolution can reduce perceived quality.
Invented case: a picture measuring 600 by 400 pixels is placed into a slide and then enlarged to fill a very large output. Enlarging the container does not create genuine new detail in the original pixels. The image may become visibly soft. The appropriate repair could involve a higher-resolution authorised source, reducing the displayed size or designing the layout differently.
A crop changes which information is visible. Cutting out the event’s venue sign may make a photograph more dramatic but less useful if the task requires the location to be obvious. A media answer should balance visual purpose and factual requirements. If an official image is not supplied for reuse, copyright and source permissions still matter.
Layering, grouping and transparency: a visual logic problem
A shape can obscure another because of front-to-back arrangement. To make a label readable, bring the relevant text to the front or adjust the background layer or fill. Grouping related objects allows them to be moved consistently but may make individual editing require ungrouping. These actions should be selected because they solve a visible requirement, not because a toolbar option is available.
In the fictional poster, a translucent rectangle is placed over a photograph to make white text more readable. If opacity is too high, the photo may disappear; too low and the label may have poor contrast. The learner should compare the visible result at the required output scale. A screenshot of the editor might not reveal how the exported graphic actually looks.
Video and slides: storyboard, master and playback
The syllabus includes slide-master consistency, storyboards, assembling video from still images and clips with text, transitions and sound, and understanding frame rates. A storyboard organises the story before production. A slide master can help apply a consistent visual style across a presentation, while suitable transitions support the sequence rather than replace a message.
Fictional task: create a 40-second introduction to a school exhibition. The storyboard has four stages: welcome, exhibits, visit information and closing invitation. If the finished clip ends before the location appears, it does not meet the practical communication goal even when sound and animation function perfectly.
Higher frame rates may create smoother motion but also increase resource needs under comparable encoding conditions. The best value is not automatically the highest possible frame rate if the task has file-size or playback constraints. Review the actual examination requirements for output resolution, file type, duration and sound, and export accordingly.
Spreadsheets: formulas must follow the meaning of the data
Module 4 requires applying cell formats, charts, mathematical and logical formulas, data functions, lookups, sorting, filtering and validation. The Paper 2 task should be approached as a small information system. Inputs represent real quantities; formulas express relationships; charts present results; validation helps manage data entry; and the saved workbook should behave when the inputs change.
Original fictional sales task: B2 contains units sold 8 and C2 unit price $6.50. In D2, =B2*C2 gives sales revenue $52.00. If the pupil uses addition, =B2+C2 returns 14.5, a plausible number but the wrong quantity. A hand calculation confirms the correct operation and helps detect a row or column reference mistake.
The formula should continue to work when data changes. If B2 increases to 10, D2 should recalculate to $65.00. A student who types $52.00 directly into D2 instead of entering the formula may produce the initial visible value but fail the requirement for automatic calculation. Testing a changed input exposes the difference.
Relative and absolute references: copying a formula should not break its meaning
A relative cell reference adjusts when a formula is filled or copied. An absolute reference such as $G$1 holds the specified column and row fixed. A mixed reference such as $G1 locks only the column, while G$1 locks only the row. These are address rules, not currency notation when they appear inside formula references. The most common practical mistake is copying a calculation whose tax or discount cell should remain fixed.
Original fictional workbook: D2 contains the revenue =B2*C2. Cell G1 contains tax rate 0.09. In E2, =D2*$G$1 calculates a tax amount; copying down to E3 changes D2 to D3 but continues to use G1. If the formula instead contains =D2*G1, copying it to the next row may use G2, which could be blank or contain an unrelated value.
A sensible check calculates one row manually, then changes the units or tax rate and watches how the affected cells respond. The formula should preserve the intended relationships after copying. This is much better evidence of skill than noting that the first row displays a plausible amount.
IF and conditional functions: what exactly is the business rule?
A spreadsheet task may ask students to label eligible participants based on marks, attendance or registration. An IF condition makes a choice: =IF(B2>=4,”Eligible”,”Not eligible”) treats exactly four sessions as eligible. A pupil writing >4 excludes that boundary. Test values three, four and five to identify the error rather than only test an easy high value.
AND and OR represent different logical requirements. Suppose a club requires attendance of at least four sessions AND parent consent. Using OR would wrongly accept a learner who meets only one condition. The official K237 syllabus also includes NOT and up to one level of nested IF; follow that level rather than importing a complicated formula with several nested branches from a different qualification.
Conditional functions such as SUMIF, COUNTIF and AVERAGEIF work on records that meet a criterion. If a table records registrations by club, COUNTIF can count rows matching the selected club while SUMIF totals an associated quantity. The criterion is part of the required calculation, not just an optional decoration.
A worked COUNTIF and SUMIF example
Invented spreadsheet rows have two columns: group and number of participants. Row 2 Art, 5; row 3 Science, 8; row 4 Art, 7; row 5 Drama, 4; row 6 Art, 3. If A2:A6 contains the group and B2:B6 the numbers, =COUNTIF(A2:A6,”Art”) gives three Art records, while =SUMIF(A2:A6,”Art”,B2:B6) gives 5 + 7 + 3 = 15 participants.
A learner who reports 3 as the number of participants has confused counting records with summing quantities. An AVERAGEIF across Art values gives 15/3 = 5 participants per Art record. Each function answers a different question. Change one group’s name or count and verify that the result updates rather than trusting the original row arrangement.
The K237 syllabus also includes mathematical, ranking and statistical functions such as ROUND, QUOTIENT, MOD, POWER, SQRT, MEDIAN, MODE.SNGL, MAX, MIN, LARGE, SMALL, RANK.EQ, COUNT, COUNTA and COUNTBLANK. Practise selecting a function from the required meaning; the Paper 2 lab may demand real execution rather than a multiple-choice label.
Lookups: exact matching prevents the wrong price
For VLOOKUP and HLOOKUP, the G2 syllabus includes exact matching. The key should uniquely identify the requested item within the supplied relevant range, and the retrieved value must come from the correct row or column. INDEX and MATCH provide further ways to locate a value by position. A lookup can be syntactically valid but return the wrong information if the range or column index is wrong.
Fictional table: product codes P01, P02 and P03 occupy cells A2:A4; prices $10, $15 and $25 occupy B2:B4. If the code to search is P02, =VLOOKUP(“P02”,A2:B4,2,FALSE) returns 15 through exact matching. A formula using the wrong index might return a code rather than a price, while one pointing to an incomplete range may fail.
Change the requested code to P03 and verify a result of $25. If the formula is copied, consider which lookup-table references should remain fixed. The learner should check that the retrieved value corresponds to the intended product, not just that the formula displays no error message.
Data validation and formatting are not the same as correctness
K237 requires number, currency, percentage and date formats, conditional formatting and data validation. Number formatting changes how a value is displayed, not necessarily its stored quantity. A value entered as 0.2 may be displayed as 20% after percentage formatting; a value entered as 20 and then formatted as a percent may display 2000%, depending on the application.
Data validation can limit permitted values or provide an error message for inputs outside the specified rule. Conditional formatting draws attention to cells meeting criteria, including greater-than, less-than and equal-to conditions in the syllabus. Neither control proves the original figures were entered honestly; correct source information and sensible checking remain essential.
Fictional task: an attendance column should accept integers from an allowed range according to the question’s input rule. A candidate sets validation and tests a permitted value plus one invalid value. This is evidence that the constraint works. Merely typing a note saying ‘no invalid entries’ does not create validation in the actual spreadsheet.
Charts: a useful graphic answers a question
The practical syllabus includes bar, column, pie and line charts, plus a line-and-column combination chart. Choose based on what is compared: categories, an ordered trend or parts of a meaningful whole. A chart’s title, legend, data labels and axes should support interpretation. Leaving an unlabeled vertical axis makes even a mathematically correct plot ambiguous.
Invented table: monthly attendance is 12, 18, 14 and 20 across four months. A line chart can show change over time while a column chart compares monthly counts. If the task asks for the percentage share of the whole four-month attendance, a pie chart answers a different question. Data and chart type should match the intended message.
If a source cell changes, linked chart elements should update when correctly configured. A student should change one practice input and inspect whether the plotted value changes. A beautiful static screenshot of the original chart would not demonstrate that the workbook itself is functioning.
Scratch programming: build behaviour, not just a picture
K237’s programming module includes variables, if and if–else instructions, basic and conditional loops, logical operators, random values, list operations, custom blocks, sprite positions, costumes, broadcasts, keyboard or mouse triggers, sound and collision detection. For Paper 2, Scratch-related practical skills matter. The program should behave correctly under specified inputs, not merely contain a set of colourful blocks.
Plan the smallest functional version. For a basic collecting game, identify the player sprite, target sprite, score variable and what should happen when they touch. A loop checks the collision. If touching occurs, score increases and the target is moved or temporarily hidden so the same contact cannot repeatedly award unintended points. The precise structure depends on the task.
Do not build several advanced screens before verifying that the score can change once correctly. The fastest route to a reliable program often begins with a simple script that passes one test, then another script handling a boundary or error condition.
Original Scratch task: a score counter
Fictional rule: When a green flag is clicked, initialise score to zero. Each time the player touches a target and a new collection is registered, increase the score by two. After three valid collections, display a completion message. The intended score progression is 0, 2, 4, 6. If the result becomes 8 after three collections, investigate duplicate triggering rather than blindly change the final threshold.
The check should use a repeatable sequence: start the program afresh; collect a target once; confirm score two; separate sprites and collect again; confirm four; collect a third time; confirm six and the required completion response. Resetting is vital because a score retained from an earlier run can create a false apparent bug.
A student whose game works only because they manually click the score display instead of the programmed sprite behaviour has not completed the same specification. Testing should reproduce the user’s intended interaction, not a special trick known only to the creator.
Logic boundaries: greater than versus greater than or equal
Suppose the Scratch game should stop when score reaches ten or more. A condition testing score > 10 may fail to stop at exactly ten. To check, start the game with score values nine, ten and eleven using a safe isolated test setup. The bug is a boundary-condition error, not an aesthetic problem.
For a loop repeating until the target is reached, verify that the variable can actually change in the direction needed for termination. A script that waits forever because the stop condition is impossible will not become correct by adding more sound effects or costumes. Inspect state changes in each iteration.
The K237 syllabus allows up to one level of nested conditional blocks for the specified basic learning outcomes. A new student does not need to write complex advanced programming logic beyond scope to demonstrate correct event handling and testing.
Lists, messages and custom blocks: structure protects consistency
Lists hold sequences of items that can be read, inserted, deleted or checked by index in the prescribed block language. A student should know which element a given list operation changes and whether indexing behaviour matches the specific application. A list with three entries does not automatically have a fourth valid item for a read operation.
Broadcast messages can coordinate sprites or stage events without forcing every action into one script. A custom block can group a repeated sequence of instructions and make the program easier to maintain. The benefit is not the number of extra blocks used; it is whether behaviour remains clear, testable and consistent with the game’s requirements.
Fictional game: after the player collects all three book icons, the player sprite sends a ‘level complete’ message, the stage switches backdrop, and the completion text appears. If the stage never receives the broadcast because the label differs, the score may be correct but the visible transition fails. Diagnose event communication rather than rewriting the whole game.
A full fictional three-task mini-project
Imagine a training assignment for a school’s reading festival—not an actual national examination task. The candidate must design a clear information graphic, build a spreadsheet calculating registrations and produce a Scratch mini-game in which a character collects book icons. The three artefacts should communicate one event but each demonstrates different competencies. The practical skill is meeting all the requirements and saving the correct independent files.
For the media task, use a storyboard or simple layout plan and create a heading, date, venue, readable icons and required notice. Test the output at its intended size and verify exported file quality. For spreadsheets, record attendance, use formulas for totals and categories, and create a chart with meaningful labels. Change a registration number to check formula recalculation.
For Scratch, initialise a score, let the sprite collect icons and trigger a completion event after the required number of valid collections. Test collisions, score changes, start-state reset and completion behaviour. A file that appears correct in the editor but fails when the green flag is clicked is not ready. Save each artefact in the required authorised location according to the task instructions.
Save and reopen: the overlooked last part of the examination
Paper 2 explicitly includes saving time within its 135-minute duration. Make a habit of saving early and at suitable checkpoints, not only when the clock is nearly finished. The correct final deliverables may involve an editable source file, a separate export or several files according to the actual paper. Follow its required names, formats and locations precisely rather than use a guessed universal naming system.
In practice, reopen a saved workbook and check the formulas; open the media export and inspect quality; run the saved Scratch project and test an interaction. A project can look right while an unsaved change remains only in memory, a file was saved in the wrong directory, or an exported object disappears because the output format behaves differently.
Do not use cloud accounts, external drives, phones or online resources unless officially permitted. The assessment centre’s provided computer and installed software control the examination environment. A student who encounters a technical issue should notify the authorised invigilator promptly instead of attempting an unauthorised workaround.
A realistic 135-minute task plan
Paper 2 contains approximately 30 marks media, 25 marks spreadsheets and 25 marks programming. A simple mark-proportional starting rehearsal would allocate somewhat more time to media, but the tasks differ in complexity and the actual examination does not mandate one fixed time budget for each. A useful practice schedule might reserve roughly 45 minutes for media, 35 minutes for spreadsheets, 40 minutes for programming and 15 minutes for saving, checking and unavoidable transitions. These amounts total 135 minutes and are only an illustrative planning model.
A candidate who is already fast with media may adjust to allow more programming debugging. Another who struggles with spreadsheet lookups might need a simpler checklist and a more realistic practice allocation. The essential rule is to leave enough time to produce all compulsory artefacts, verify basic functionality and complete the required submission process.
If a task is taking too long, complete its clearly specified essentials before adding cosmetic refinements. A spreadsheet with accurate formulas and the required chart is often more relevant to the task than a beautifully coloured table whose result is wrong. A Scratch game with a functioning start, interaction and end is more robust than ten animated decorations around a broken scoring condition.
Four weeks of genuine K237 Paper 2 improvement
Week 1 — get the software and saving right
Check the authorised application versions, source-file types and output expectations. Create a tiny media artefact, spreadsheet and Scratch project, save them correctly and reopen them to prove the files exist.
Week 2 — media and spreadsheet control
Practise vector objects, raster crop and export, slide consistency and short video/storyboard work. Build a spreadsheet with relative/absolute references, conditional aggregates, lookups, chart labels and valid input.
Week 3 — Scratch behaviour under changed inputs
Practise sprite movement, event messages, score variables, loops, conditionals, lists and custom blocks. Use boundary tests and reset states. Diagnose one bug from behaviour rather than randomly moving blocks.
Week 4 — complete all three tasks within 135 minutes
Rehearse media, spreadsheets and Scratch tasks together with compulsory saving and verification. Inspect what was delivered after reopening the files. Adjust time planning and retest the biggest recurring gap.
What parents and tutors should look for
Ask a learner to show the final saved file and explain one requirement it satisfies. In a spreadsheet, change a data value and observe what recalculates. In Scratch, change the starting score and test whether the condition still works. In media, compare source and export to identify lost transparency or cropping. These tests make learning visible even without a parent knowing every menu command.
A tutor should diagnose practical gaps separately: misunderstanding of a requirement, unfamiliarity with application tools, formula logic, programming bugs, and file submission mistakes. A genuine small group may help individual coaching and independent work when managed well, but class size alone does not prove effectiveness. Students should become progressively more capable without constant prompts.
Good habits include taking authorised breaks, following school rules, respecting copyright and privacy, and avoiding the submission of other people’s work as one’s own. Practical Computing can be creative and challenging without requiring unlimited late-night screen use. Sleep and normal school commitments remain important.
Secondary 1–4 and the future of practical digital skills
Lower-secondary learning may introduce responsible device use, structured information and simple algorithms. Upper-secondary G2 K237 extends those ideas into actual media, spreadsheets and programming practice. In the 2027 SEC year, the student must produce the prescribed artefacts under realistic conditions, manage time and troubleshoot without relying on an outside helper.
Computing knowledge can later support technology support, digital operations, applied design, business analytics, media creation and software-related pathways. These are exploratory interests. The 2028 Post-Secondary Admissions Exercise considers a candidate’s full SEC profile and individual courses’ entry rules; one Computing mark cannot promise or bar a profession.
Frequently asked questions
What is the official G2 Computing Paper 2 duration?
Two hours fifteen minutes, or 135 minutes, including time to save the required files.
How many raw marks and what percentage?
80 raw marks, contributing 50% of the overall Computing K237 grade.
How many practical tasks must be completed?
Three compulsory tasks: media software, spreadsheets and programming.
Are all tasks worth the same marks?
No. The syllabus indicates approximately 30 media marks, 25 spreadsheet marks and 25 programming marks.
Which modules appear in Paper 2?
Modules 4–6: Spreadsheets, Media Software and Programming.
Are all six modules included in Paper 1?
Yes. Paper 1 assesses Modules 1–6 through 20 MCQs and short structured questions.
Are MakeCode microcontrollers assessed in the lab paper?
Microcontroller content is explicitly Paper 1-only. The practical Paper 2 programming includes the prescribed Scratch skills.
What if the on-screen result looks right but the file was not saved?
The softcopy deliverable is part of assessment. Practise saving and verifying the required final files before finishing.
Should I manually type spreadsheet totals to be faster?
Not when the task requires functioning formulas or automatic recalculation. Read and satisfy the specific deliverable.
Does a Scratch game working once prove it is correct?
No. Test different starting states, boundary conditions, triggers, score changes and stopping behaviour.
Can private tutoring guarantee a strong K237 result?
No. Targeted teaching and independent rehearsal can help, but results depend on the learner’s performance and the official tasks.
The G2 Computing Paper 2 readiness checklist
- I have confirmed my registered G2 subject code K237 and the approved application environment.
- I know Paper 2 is 135 minutes, 80 marks and 50% overall.
- I can create, edit and export media with the required content visible.
- I can choose vector or raster methods and verify output resolution and transparency.
- I can enter and copy valid spreadsheet formulas with the right relative or fixed references.
- I can apply conditional logic, lookups, data validation and charts where required.
- I can program and debug Scratch sprites, conditions, loops, broadcasts and scoring.
- I understand that MakeCode microcontroller content belongs to Paper 1 here.
- I can save, locate and reopen my final files using the prescribed instructions.
- I have rehearsed all three tasks together and retained enough time for final checking.
Connected eduKateSG Computing and G2 guides
G2 Computing Paper 1 e-exam and six modules
K237 G2 Computing complete syllabus survival guide
G2 Computing syllabus and careers explained
G2 Computing algorithms, variables and loops
Why a successful run does not prove a program works
G1/G2/G3 Computing exam and lab differences
G2 Computing K237 and related SEC resources
G2 Mathematics, Science and Computing subject hub
2027 SEC G2 complete subject survival directory
2028 Polytechnic, PFP and Higher Nitec pathways
Official 2027 K237 syllabus and resources
SEAB G2 Computing K237 2027 syllabus PDF
SEAB 2027 G2 syllabuses and Computing specimen links
MOE 2028 post-secondary admissions updates
Based on the published 2027 SEC G2 Computing K237 syllabus, checked in October 2026. Every festival, price, code behaviour and software-task scenario above is an original instructional example, not a genuine SEC lab paper. Always follow school and SEAB rules on software, equipment, privacy, permitted materials, file submission and deadlines.