JSS 3 First Term

Lesson objectives

By the end of the week, learners should be able to:

1. Recall the full curriculum across all three terms without notes.
2. Classify problems into computational and non-computational.
3. Apply computational problem-solving steps to a new scenario.
4. State why senior secondary work builds on junior secondary foundations.
5. Judge whether a given task is suitable for algorithmic solution.

Key vocabulary

• Senior review: consolidating knowledge across all terms before advanced work.
• Computational problem: a task amenable to an algorithmic solution.
• Non-computational problem: a task requiring manual or unstructured handling.
• Algorithm: a finite sequence of precise instructions solving one problem.
• Algorithmic solution: a procedure following an algorithm rather than intuition.
• Foundations: the underlying skills supporting advanced work.
• Suitability: whether a task fits algorithmic methods.

Common misconceptions

• "All problems need an algorithm." Many problems cannot be solved algorithmically; intuition applies instead.
• "Review means rereading." Review means testing and reapplying, not passively reading.
• "Advanced work ignores prior learning." Advanced work builds directly on prior skills.

Teacher activities

1. Starter: show the three-term title list and ask pairs to recall one definition each without notes.
2. Share the recalled definitions and check the ones missed for reteaching.
3. Introduce computational versus non-computational problems with worked examples.
4. Show how an algorithm solves a computational problem step by step.
5. Explain why senior secondary work builds on junior secondary foundations.
6. Close with the suitability task and exit question.

Student activities

1. Recall one definition per term without notes and note any misses.
2. Classify ten statements as computational or non-computational with a reason.
3. Apply computational problem-solving steps to a new scenario on paper.
4. Explain why senior secondary builds on junior secondary in one paragraph.
5. Judge whether a given task is suitable for algorithmic solution.
6. Answer the exit question in one sentence about algorithmic suitability.

Practical / learning evidence

A five-statement classification worksheet, a worked algorithm for one scenario, and a one-paragraph senior-review justification. Hand in both for marking.

Resources and preparation

Blank classification templates, sample scenarios and senior review prompts. Offline route: paper versions, no device needed. Display examples carefully and avoid exposing sensitive learner information.

Assessment for learning

Inspect the classification for correct categories and reasons. Check the algorithm for a sensible step sequence. Mark the justification for a clear foundation rationale. Flag any learner who claims every problem needs an algorithm.

Inclusion and homework

Provide the blank classification prefilled for learners who need scaffolding and allow oral completion. Extend confident learners with six more statements and a non-computational problem homework. Homework: name three areas where prior knowledge matters most for senior secondary work.

Lesson objectives

By the end of the week, learners should be able to:

1. Write a program using variables, arithmetic and printing.
2. State why high-level languages suit school teaching.
3. Distinguish interpreters from compilers in behaviour.
4. Trace a simple program predicting the expected output.
5. Compare high-level languages on ease and readability.

Key vocabulary

• Programming language: a structured notation telling the computer what to do.
• Variable: a named container holding a value.
• High-level language: closer to human speech than machine code.
• Interpreter: converts and executes line by line.
• Compiler: converts the whole program into executable code at once.
• Trace: predicting results by stepping through code.
• Readability: how easily a human can read source code.
• Ease: how simple writing the program feels.

Common misconceptions

• "Programming is only for geniuses." Programming is a craft improved through practice like any other.
• "Interpreters and compilers never differ." They behave fundamentally differently in error reporting.
• "Every language runs identically under the hood." Low-level and high-level languages map differently to machine code.

Teacher activities

1. Starter: run a PRINT statement and display the result without revealing the code.
2. Name programming concepts and demonstrate writing a simple program.
3. Explain why high-level languages suit school teaching on readability.
4. Describe interpreter versus compiler behaviour on a live system.
5. Trace a simple program line by line and predict the output.
6. Close with the readability comparison and exit question.

Student activities

1. Guess the PRINT command from the starter RUN.
2. Write a simple program using variables, arithmetic and PRINT.
3. Explain why high-level languages suit school teaching in one paragraph.
4. Describe interpreter versus compiler behaviour briefly.
5. Trace a simple program and write the predicted output.
6. Compare high-level and assembly languages on readability.
7. Answer the exit question in one sentence about why high-level suits schools.

Practical / learning evidence

A recorded program plus documented expected output, a traced prediction and a high-level versus assembly comparison. Submit all three for marking.

Resources and preparation

A computer with a BASIC interpreter installed, blank windows and sample tracing cards. Keep the interpreter in a read-only folder for learners lacking install capability. Disable Caps Lock before typing. Verify the computer starts reliably.

Assessment for learning

Inspect the typed program for correct variable assignment and PRINT syntax. Compare the traced output with the actual interpreter output. Ask a learner to explain why high-level languages suit schools better than assembly. Flag any learner who confuses interpreter and compiler roles.

Inclusion and access

Prebuild the interpreter folder with Welcome and sample programs. Provide a tracing template with output lines preprinted. Extend confident learners with two tracing tasks and a second readability comparison. Homework: write a second program differing only in operators and compare the outputs.

Lesson objectives

By the end of the week, learners should be able to:

1. Define a function and state its input and output parameters.
2. Call a function by passing values correctly.
3. Declare a one-dimensional array and index elements properly.
4. Use an array to store multiple values in sequence.
5. Trace a function call returning a value correctly.

Key vocabulary

• Function: a reusable block performing one computation.
• Parameter: an input variable receiving a passed value.
• Return: giving a value back to the caller after computation.
• Array: a sequence stored in consecutive memory slots.
• Index: the position number of an element in the array.
• One-dimensional array: an array storing values along one axis.
• Reusable block: a section of code called multiple times with different inputs.
• Trace: predicting results by stepping through code.

Common misconceptions

• "Functions replace loops." Functions handle single operations; loops handle repetition.
• "An array stores text." Arrays store homogeneous values; text often sits in a string type separately.
• "Index starts at zero always." Zero-based indexing is common but some languages start elsewhere.

Teacher activities

1. Starter: ask why repeated tasks should use functions rather than duplication.
2. Define a function and give input and output parameters explicitly.
3. Demonstrate calling a function by passing values.
4. Declare a one-dimensional array and index elements step by step.
5. Demonstrate calling a function returning a computed value.
6. Close with the function-trace task and exit question.

Student activities

1. Answer the starter and state the benefit of reusing functions.
2. Define a function in their own words and name input and output parameters.
3. Call a function by passing the correct values.
4. Declare a one-dimensional array and index elements properly.
5. Trace a function call and write the returned value.
6. Answer the exit question comparing functions with loops in one sentence.

Practical / learning evidence

A declared array with indexing exercises, a function call with a returned value, and a function-trace worksheet. Submit all three for marking.

Resources and preparation

Computers with the interpreter, blank arrays and sample tracing cards. Prebuild the interpreter in a read-only folder. Disable Caps Lock before typing. Verify the computer starts reliably.

Assessment for learning

Inspect the array declaration for correct indexing. Check the function return value matches the traced result. Mark the function trace for correct parameter passing. Flag any learner who thinks functions replace loops entirely.

Inclusion and homework

Provide the array template prefilled for learners who need scaffolding and allow oral function calls. Extend confident learners with two arrays and a function that returns an array element. Homework: write a second function that takes an array and returns the sum of its elements.

Lesson objectives

By the end of the week, learners should be able to:

1. Define object, class and instance in their own words.
2. Name at least three object attributes and methods.
3. Create a simple class with one attribute and one method.
4. Instantiate an object and call its method.
5. Explain why OOP helps larger software teams.

Key vocabulary

• Object: an instance tied to data and behaviour.
• Class: a blueprint defining object attributes and methods.
• Instance: one concrete object created from a class.
• Attribute: data held inside an object.
• Method: behaviour belonging to the object.
• Instantiate: creating a concrete object from a class.
• Blueprint: the structural template a class provides.
• Data and behaviour: attributes and methods together.
• Team: a group of developers building software together.

Common misconceptions

• "Objects are the same as variables." Objects bundle data and behaviour; variables hold single values.
• "Classes store actual data." Classes describe structure; instances hold data.
• "OOP replaces procedural programming." OOP complements procedural styles when scaling to large teams.

Teacher activities

1. Starter: display a class diagram on the board and ask what it represents.
2. Define object, class and instance one by one with worked examples.
3. Name object attributes and methods as a class brainstorm.
4. Create a simple class with one attribute and one method.
5. Instantiate an object and call its method step by step.
6. Close with the team-scale explanation and exit question.

Student activities

1. Answer the starter and describe what the class represents.
2. Define object, class and instance in their own words.
3. Name at least three object attributes and methods from their own experience.
4. Create a simple class with one attribute and one method.
5. Instantiate an object and call its method with the correct arguments.
6. Explain why OOP helps larger teams in one paragraph.
7. Answer the exit question comparing OOP with procedural style in one sentence.

Practical / learning evidence

A one-class definition sheet, a class skeleton with attribute and method declarations and an instantiated object demonstration. Submit all three for marking.

Resources and preparation

Computers with an OOP interpreter or modern Python available, blank templates and sample class names. Provide a prebuilt interpreter in a read-only folder if one exists. Disable Caps Lock before typing.

Assessment for learning

Inspect the class definition for correct attribute and method naming. Check the instantiated object call for matching arguments. Ask a learner to explain why OOP helps large teams. Flag any learner who treats classes as data holders.

Inclusion and homework

Provide the class template prefilled for attribute and method names and allow oral instantiation. Extend confident learners with two objects and a second class-method demonstration. Homework: describe one real application built with object-oriented principles in one paragraph.

Lesson objectives

By the end of the week, learners should be able to:

1. Define a database system and describe its role in organisations.
2. Name the main components of a relational schema.
3. Write basic SQL CREATE TABLE statements for fields and constraints.
4. Describe a primary key and a foreign key and their roles.
5. Judge whether a schema satisfies business rules.

Key vocabulary

• Database system: software storing, managing and retrieving records.
• Schema: the design defining tables, fields and relationships.
• Relational schema: a tabular schema holding linked tables.
• CREATE TABLE: SQL syntax declaring a new table.
• Field: a column holding a characteristic of each record.
• Constraint: a rule limiting allowed data values.
• Primary key: a unique identifier for each record within a table.
• Foreign key: a field linking a row in one table to another.
• Business rule: an operational requirement a schema must satisfy.

Common misconceptions

• "A database is just a spreadsheet." Databases enforce constraints and relationships that spreadsheets ignore.
• "SQL creates empty tables only." SQL can insert data and define relationships too.
• "Primary keys can share values." Primary keys must uniquely identify each record.

Teacher activities

1. Starter: ask where a school keeps student records if not on a teacher's desktop.
2. Define a database system and describe its organisational role.
3. Name the main relational schema components one by one.
4. Demonstrate writing a CREATE TABLE statement with constraints.
5. Define primary and foreign keys with a worked example.
6. Close with the schema-satisfies-rule task and exit question.

Student activities

1. Answer the starter and identify the right storage location.
2. Define a database system in their own words and state its role.
3. Name the main relational schema components in one sentence each.
4. Write a CREATE TABLE statement with fields and constraints.
5. Define a primary key and a foreign key with one example each.
6. Judge whether a given schema satisfies the stated business rules.
7. Answer the exit question in one sentence about databases versus spreadsheets.

Practical / learning evidence

A CREATE TABLE worksheet, a primary-key-versus-foreign-key example and a schema-satisfies-rule worksheet. Submit all three for marking.

Resources and preparation

Printed SQL templates, blank schema diagrams and sample business rules. Offline route: paper versions, no device needed. Display any DBMS installation carefully and avoid touching live databases.

Assessment for learning

Inspect the CREATE TABLE for correct syntax and constraint names. Check the PK versus FK example for correct links. Mark the schema-satisfies-rule for defensible judgement. Flag any learner who calls the database a big spreadsheet.

Inclusion and homework

Provide the CREATE TABLE prefilled for field and constraint names and allow oral SQL. Extend confident learners with two CREATE TABLE statements and a third homework to verify foreign-key integrity. Homework: name one advantage and one disadvantage of relational databases over spreadsheets.

Lesson objectives

By the end of the week, learners should be able to:

1. Recap network topologies and routing concepts from earlier terms.
2. Name internet technologies such as DNS, HTTP and TCP.
3. Describe why the World Wide Web runs as a service on the internet.
4. Trace packet journeys across routers and switches.
5. Explain latency as the sum of transmission and processing delays.

Key vocabulary

• Internet technology: named services running on the internet such as DNS and HTTP.
• DNS: the domain name system translating names to addresses.
• HTTP: the protocol transferring web pages.
• TCP: a protocol ensuring reliable delivery of packets.
• Router: a device forwarding packets between networks.
• Switch: a device forwarding frames within one network.
• Latency: the delay before a packet reaches its destination.
• Transmission delay: time spent on the physical medium.
• Processing delay: time spent handling the packet at each node.

Common misconceptions

• "DNS and HTTP are the same thing." DNS resolves names; HTTP transfers pages.
• "The web requires cables only." Wireless networks also run on radio signals.
• "Latency disappears once you reach your target." Latency returns during reassembly time.

Teacher activities

1. Starter: ask how a browser turns www.example.com into a numeric address.
2. Recap network topologies and routing briefly.
3. Name DNS, HTTP and TCP one by one with a brief purpose.
4. Model tracing a packet journey from browser to server.
5. Define latency as the sum of transmission and processing delays.
6. Close with the technology-versus-protocol distinction and exit question.

Student activities

1. Answer the starter and explain the role of DNS.
2. Name the four internet technologies and state each purpose.
3. Describe why the World Wide Web runs as a service on the internet.
4. Trace a packet journey from browser to server through routers.
5. Define latency as the sum of transmission and processing delays.
6. Answer the exit question in one sentence about DNS versus HTTP.

Practical / learning evidence

A four-technology comparison sheet, a packet-journey trace and a latency breakdown. Submit both for marking.

Resources and preparation

Printed comparison sheet, blank trace template and sample latency scenarios. Offline route: paper versions, no device needed. Display any router or switch carefully and avoid dismantling during demonstration.

Assessment for learning

Inspect the comparison sheet for four distinct technologies with purposes. Mark the packet journey for correct router and switch paths. Check the latency breakdown for sensible sums. Flag any learner who conflates DNS with HTTP.

Inclusion and homework

Provide the comparison prefilled for learners who need scaffolding and allow oral trace. Extend confident learners with five technologies and a second packet journey. Homework: name two internet technologies outside the main list and state each purpose.

Lesson objectives

By the end of the week, learners should be able to:

1. Define HTML and explain its role as the structure of web pages.
2. Name at least five HTML tags and describe each role.
3. Build a simple webpage using headings, paragraphs and lists.
4. Add a hyperlink to link sections within one page.
5. Save the HTML file and open it in a browser.

Key vocabulary

• HTML: markup language defining page structure.
• Tag: a labelled instruction such as <h1>.
• Heading: a title tag used for hierarchy.
• Paragraph: a container for flowing text.
• List: bulleted or numbered items made of list tags.
• Hyperlink: a link connecting one page to another.
• Structure: the skeletal layout of content.
• Markup language: a language describing content via tags.
• Browser: software rendering HTML into visible pages.

Common misconceptions

• "HTML is the same as the web." HTML is one markup language among many; the web includes CSS and JavaScript too.
• "Every tag carries its own behaviour." Tags mostly carry structure; behaviour comes from scripting and styling.
• "An HTML page needs no closing tag." Every opening tag needs a matching closing tag in well-formed HTML.

Teacher activities

1. Starter: show a heading and a paragraph and ask which carries structure.
2. Define HTML and name five tags one by one with a brief description.
3. Demonstrate building a simple webpage with headings, paragraphs and lists.
4. Add a hyperlink linking one page to another.
5. Save the HTML file and open it in a browser to confirm.
6. Close with the build-your-own-page task and exit question.

Student activities

1. Choose the structure carrier from the starter and explain the reason.
2. Define HTML in their own words and name five tags with descriptions.
3. Build a simple webpage with headings, paragraphs and lists.
4. Add a hyperlink linking one page to another.
5. Save the HTML file under a clear filename and reopen it to confirm.
6. Answer the exit question in one sentence about HTML versus the web.

Practical / learning evidence

A saved HTML file with headings, paragraphs, lists and one hyperlink, plus an inspection checklist confirming the browser renders it. Submit the file and checklist for marking.

Resources and preparation

Computers with a text editor and a browser, blank templates and sample HTML. Check the editor opens cleanly and that browsers render HTML instantly. Disable Caps Lock before typing. Verify the computer starts reliably.

Assessment for learning

Inspect the saved HTML for correct opening and closing tags. Check the inspection checklist for browser rendering confirmation. Ask a learner to describe the difference between HTML and CSS behaviour. Flag any learner who thinks HTML runs on its own.

Inclusion and homework

Provide the template with sample HTML prebuilt so learners focus on structure. Allow extra time for saving and reopening. Extend confident learners with three tags and a second homework listing real websites built with HTML alone. Homework: add one heading, one paragraph and one list to an existing HTML page.

Lesson objectives

By the end of the week, learners should be able to:

1. Define the software development life cycle and its phases.
2. Name the eight phases in order.
3. Compare waterfall and agile models on flexibility.
4. Describe the testing phase and its purpose.
5. Draw a simple waterfall lifecycle chart showing all phases.

Key vocabulary

• Software development life cycle: the ordered stages of building software.
• Phase: one stage in the development process.
• Waterfall: a linear model moving strictly through stages once.
• Agile: an iterative model repeating cycles of planning, building and testing.
• Testing phase: verification checking the product works correctly.
• Verification: confirming the product meets requirements.
• Validation: confirming the product meets user needs.
• Linear model: a model progressing strictly through stages without loops.

Common misconceptions

• "Waterfall never revisits earlier phases." Waterfall revisits earlier phases on major defects.
• "Agile is chaotic development." Agile has disciplined iteration cycles inside loops.
• "Testing happens only at the end." Testing runs throughout the life cycle continuously.

Teacher activities

1. Starter: display a waterfall chart and an agile chart side by side and ask which suits a school assignment.
2. Define the software development life cycle and state the eight phases in order.
3. Compare waterfall and agile on flexibility and documentation.
4. Explain the testing phase and its relation to verification and validation.
5. Draw a simple waterfall lifecycle chart on the board.
6. Close with the model-choice task and exit question.

Student activities

1. Choose the starter item and explain the preference reason.
2. Define the software development life cycle in their own words and list the eight phases.
3. Compare waterfall and agile on flexibility and documentation.
4. Explain the testing phase and relate it to verification and validation.
5. Draw a waterfall lifecycle chart showing all eight phases.
6. Choose the model suited to a small team project and justify it.
7. Answer the exit question in one sentence about waterfall revisits.

Practical / learning evidence

An eight-phase waterfall chart, a waterfall versus agile comparison and a one-paragraph testing explanation. Submit all three for marking.

Resources and preparation

Printed chart templates, blank comparison sheets and sample project scenarios. Offline route: paper versions, no device needed. Display diagrams carefully and avoid touching any hardware used in demos.

Assessment for learning

Inspect the waterfall chart for eight distinct phases in order. Mark the waterfall versus agile comparison for equal criteria. Check the testing explanation for verification and validation linkage. Flag any learner who claims waterfall never revisits earlier phases.

Inclusion and homework

Provide the chart prefilled for learners who need scaffolding and allow oral comparison. Extend confident learners with seven more phases and a seven-scenario comparison. Homework: describe one real application built with the waterfall model in one paragraph.

Lesson objectives

By the end of the week, learners should be able to:

1. Define e-commerce and state its main types.
2. Name three payment methods and describe each.
3. Explain how online transactions work from checkout to delivery.
4. List four security measures protecting online payments.
5. Judge whether a given scenario fits retail, service or wholesale commerce.

Key vocabulary

• E-commerce: buying and selling goods or services online.
• Retail commerce: direct sale to individual buyers.
• Wholesale commerce: bulk sale to businesses.
• Service commerce: selling digital or services rather than physical goods.
• Payment method: the channel used to settle an order.
• Checkout: the final stage entering payment details.
• Delivery: physically or digitally delivering the purchased item.
• Security measure: a safeguard against transaction risk.
• Fulfillment: completing an order including shipping.

Common misconceptions

• "E-commerce means buying and selling only products." Service commerce also counts.
• "Every payment goes through banking only." Payments happen through many channels.
• "Online payments are always safe." Fraud and chargebacks remain common risks.

Teacher activities

1. Starter: display three commerce types and ask which fits a typical supermarket.
2. Define e-commerce and name three types with examples.
3. Name three payment methods and demonstrate each.
4. Walk through an online checkout from order to delivery.
5. Explain four security measures protecting online payments.
6. Close with the scenario classification task and exit question.

Student activities

1. Choose the starter item and explain the reason.
2. Define e-commerce in their own words and name three types.
3. Name three payment methods and state each role in one sentence.
4. Walk through an online checkout from order to delivery in one paragraph.
5. Name four security measures protecting online payments.
6. Classify a scenario as retail, service or wholesale commerce.
7. Answer the exit question in one sentence about payment methods.

Practical / learning evidence

A three-type definition sheet, a payment-methods chart and a checkout-walkthrough worksheet. Submit all three for marking.

Resources and preparation

Printed chart templates, blank payment-method cards and sample scenarios. Offline route: paper versions, no device needed. Display any secure payment gateway carefully and avoid accessing live systems.

Assessment for learning

Inspect the type definitions for three distinct types with examples. Mark the payment methods for correct roles. Check the checkout walkthrough for a sensible order-to-delivery path. Flag any learner who classifies every commerce as retail.

Inclusion and homework

Provide the type definitions prefilled for learners who need scaffolding and allow oral payment methods. Extend confident learners with five commerce types and two payment methods. Homework: describe one e-commerce platform serving retail commerce in one paragraph.

Lesson objectives

By the end of the week, learners should be able to:

1. Name five cyber threats such as phishing, malware and ransomware.
2. State the protection for each threat.
3. Name emerging digital technologies such as AI and IoT.
4. Describe how emerging technologies change daily life in one area.
5. Judge whether a given technology is mature or emerging.

Key vocabulary

• Cyber threat: anything that can harm systems, data or users.
• Phishing: a fake message tricking users into revealing credentials.
• Malware: malicious software installed without permission.
• Ransomware: malware encrypting files until payment is made.
• Protection: a safeguard against a harmful activity.
• Emerging technology: a recent technology not yet fully mature.
• Mature technology: an established technology with widespread adoption.
• Artificial intelligence: computer systems mimicking human reasoning.
• Internet of Things: networked devices embedded in daily objects.
• Daily life: ordinary routines at home, school and work.

Common misconceptions

• "All threats come from clicking unknown links." Malware enters through removable drives and email attachments too.
• "Emerging technologies are dangerous by definition." Most emerging technologies benefit society when governed properly.
• "Only adults need to worry about cyber threats." Learners face the same threats wherever they use devices.

Teacher activities

1. Starter: display two threat cards, one phishing and one ransomware, and ask which you prefer avoiding.
2. Name five cyber threats and pair each with a protection rule.
3. Name emerging technologies such as artificial intelligence and the internet of things.
4. Describe how one emerging technology changes daily life.
5. Contrast emerging and mature technologies on adoption and governance.
6. Close with the classification task and exit question.

Student activities

1. Choose the preferred threat-avoidance starter and justify the reason.
2. Name five cyber threats and state the protection for each.
3. Name emerging technologies and describe how one changes daily life.
4. Contrast emerging and mature technologies on adoption and governance.
5. Classify a given technology as emerging or mature with a reason.
6. Answer the exit question comparing emerging and mature technologies in one sentence.

Practical / learning evidence

A five-threat-with-protection chart, an emerging versus mature comparison and a one-paragraph emerging technology summary. Submit all three for marking.

Resources and preparation

Printed threat cards, blank comparison templates and sample emerging technologies. Offline route: paper versions, no device needed. Keep screenshots on the projector only during demonstration.

Assessment for learning

Inspect the threat chart for five distinct threats with matched protections. Check the emerging versus mature comparison for sensible distinctions. Mark the classification for a defensible emerging or mature judgement. Flag any learner who claims all emerging technologies are dangerous.

Inclusion and homework

Provide the threat cards prematched for learners who need scaffolding and allow oral emerging-technology description. Extend confident learners with seven emerging technologies and a sixth comparison homework. Homework: name one emerging technology you find most useful and state how it changes daily life.

Lesson objectives

By the end of the week, learners should be able to:

1. Recall the full curriculum across all three terms without notes in ten minutes.
2. Test objective knowledge with a short recall quiz.
3. Practise database schema, logic-gate and program skills under timed conditions.
4. Prepare three practical stations ready for the examination week.
5. Organise their materials for examinations.

Key vocabulary

• Full summary: a one-page recap of the entire term's vocabulary.
• Recall quiz: a short test of definitions and concepts from memory.
• Timed conditions: a restricted time allowance for practice.
• Practical station: a setup point for examination practical tasks.
• Materials organisation: keeping tools ready before an examination.

Common misconceptions

• "Revision is just reading notes again." Revision means testing and practising, not passive reading.
• "Tomorrow is the exam so today is fine." A full day before leaves almost no preparation time.
• "Better to be relaxed than busy preparing." Preparation reduces anxiety and improves performance.

Teacher activities

1. Starter: ten rapid-fire recall questions from the full term, no notes allowed.
2. Run a timed objective quiz and mark it as a class, explaining distractors.
3. Demonstrate the three practical stations and remind learners of the materials checklist.
4. Walk through a morning materials organisation checklist.
5. Confirm that every learner can reach the exam room and has stationery.
6. Close with a brief announcement of the Third Term starting Monday.

Student activities

1. Answer the ten recall questions and note any slips.
2. Mark their own quiz answers and record scores for review.
3. Prepare the three practical stations and run through the materials checklist.
4. Practise database schema, logic-gate and program tasks for ten minutes each.
5. Pack stationery, identification and any permitted materials for examination day.
6. Write one sentence on what revision helped you feel ready for Monday.

Practical / learning evidence

A scored objective quiz, a completed revision grid covering all terms and an materials-organisation checklist signed by the learner. All three handed to the teacher for marking.

Resources and preparation

Quiz sheet, revision grid and materials checklist. Confirm the examination room, three machines and one invigilator per station are booked before the week.

Assessment for learning

Use the quiz scores to plan the Third-Term reteach if class averages are below target. Check the revision grid for completeness. Verify the materials checklist is signed and ready for examination day.

Inclusion and access

Provide the quiz in large print and allow extra time where approved. Pair learners for the practical rehearsal so a confident partner can model the steps. Homework: pack everything needed for the examination week and store it safely.

Lesson objectives

By the end of the examination week, learners should be able to:

1. Demonstrate recall of the term's concepts under examination conditions.
2. Apply knowledge to unfamiliar examples in objective and short-answer questions.
3. Complete a practical task within the time allowance using correct procedure.
4. Name, save and submit files correctly.
5. Explain their practical output when questioned by the examiner.

Examination design

For Senior Secondary 3 the totals are: Section A objective 20 marks, Section B short answer 30 marks, Section C essay 10 marks, Section D practical 20 marks, total 80. Section A samples recall. Section B samples explanation, comparison and classification. Section D samples practical database schema, logic gate construction and program execution.

Section	Format	Marks
A	Objective (20 four-option items)	20
B	Short answer (definitions / diagrams / classification / conversions)	30
C	Essay (definition / comparison / application)	10
D	Practical (database schema / logic gate truth table / program)	20
Total	80

Teacher activities

1. Confirm the approved timetable, venue, seating and invigilation before the week begins.
2. Brief learners on the paper structure, the time for each section and the materials allowed.
3. Set out three practical stations: database schema, logic gate construction and program execution, with one invigilator per station where possible.
4. Prepare offline equivalents for learners without device access: printed sketchbook, paper truth-table template and paper program tracing task.
5. Mark using the agreed scheme, moderate a sample of scripts and record scores.
6. Return scripts with feedback and hand over to SSCE preparation.

Student activities

1. Attend the briefing and note the time allowed per section.
2. Complete Section A, then Section B, allocating time as instructed.
3. Move through the practical stations in the assigned order.
4. Save work with the correct filename and confirm it opens before leaving the station.
5. Answer the examiner's question on their practical output.
6. Collect marked scripts and record the topics to revise in SSCE preparation.

Practical / learning evidence

The completed examination script, the saved practical file for each candidate and the practical rubric sheets. Retain scripts, marking guides and representative learner work for moderation as required by the assessment framework.

Resources and preparation

Printed question papers and answer sheets, a marking guide and rubric per station, working computers with a database tool or spreadsheet and a graphics package, a stopwatch and printed sketchbooks. Check every machine the day before, and prepare two spare machines where possible. Ensure power backup and an offline alternative for each station.

Assessment for learning

Mark Section D against the practical rubric: task interpretation, procedure, technical accuracy, schema correctness, truth table and program, file naming and saving, organisation and explanation. Moderate a sample of scripts across all sections, and flag any question where more than a third of learners scored zero for review of the teaching rather than the learners.

Inclusion and access

Provide extra time and large-print papers where approved, seat learners with visual or hearing needs appropriately, and allow the offline equivalent for any learner without device access so that no candidate loses practical marks because of equipment. Keep the practical criteria identical across the digital and paper routes.

After the examination

Record scores against the class list, return scripts with brief feedback, and hand over to SSCE preparation: corel draw, arrays, language review, data representation, security ethics, mock examinations and SSCE past questions. Note any topic where the class average fell below the school's threshold and schedule it as a Third-Term retrieval starter.