JSS 3 Second Term

Lesson objectives

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

1. Recall the full First Term across all three terms without notes.
2. Identify weak areas and request targeted reteaching.
3. Complete a consolidated review worksheet covering prior weeks.
4. Practise recall under timed conditions.
5. State one improvement action per flagged weakness.

Key vocabulary

• First-Term work: material from junior secondary classes feeding into this term.
• Consolidated review: bringing together previously taught material into one document.
• Weak area: a topic where recall falls below target.
• Reteaching: focused instruction on a weak area before further revision.
• Timed conditions: a restricted time allowance for practice.
• Improvement action: a concrete step addressing a weakness.

Common misconceptions

• "Review means rereading." Review means testing and reapplying, not passive reading.
• "Everything must reappear in the revision." The revision covers enough prior material to demonstrate retention.
• "A draft is final immediately." Drafts are refined before submission.

Teacher activities

1. Starter: display the twelve First-Term week titles and ask pairs to recall one definition each without notes.
2. Share recalled definitions and flag the three weakest areas as targets.
3. Model writing one consolidated review item step by step.
4. Run a timed recall quiz and mark it as a class.
5. Assign an improvement action per each flagged weakness.
6. Close with the revision plan announcement.

Student activities

1. Recall one First-Term definition per week without notes and note any misses.
2. Identify your weakest areas and note two improvement actions.
3. Complete the consolidated review worksheet covering prior weeks.
4. Take the timed recall quiz and self-mark.
5. Plan two improvement actions targeting two weaknesses.
6. Submit the review, quiz and plan together.

Practical / learning evidence

A completed consolidated review worksheet, a self-marked timed recall quiz and a revision plan with two improvement actions. All three submitted for marking.

Resources and preparation

Printed review worksheet, sample quiz sheets and a revision-plan template. Offline route: paper versions, no device needed. Display examples carefully and avoid exposing sensitive learner information.

Assessment for learning

Check the review worksheet for completeness across prior weeks. Mark the self-quiz for honest scoring. Evaluate the revision plan for two specific, actionable improvements. Flag any learner who lists no weaknesses.

Inclusion and homework

Provide the review worksheet prefilled for learners who need scaffolding and allow oral completion. Allow extra time on the timed quiz. Extend confident learners with four more review items and a second plan homework. Homework: write two sentences describing how prior knowledge supports senior work.

Lesson objectives

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

1. Open CorelDRAW and name its main drawing tools.
2. Draw a symmetric design using rectangles, polygons and text.
3. Apply colour fills and outline styles to shapes.
4. Export the artwork as a PNG or PDF file.
5. Describe why symmetric design reads better visually.

Key vocabulary

• Graphics package: software creating images with shapes and colours.
• Drawing tool: a command that creates a basic shape element.
• Symmetric design: artwork mirrored across an axis for balance.
• Rectangle tool: a tool that draws rectangular outlines.
• Polygon tool: a tool that draws polygon outlines.
• Colour fill: applying a solid colour to a selected shape.
• Outline style: the line weight and colour around a shape.
• Export: saving a copy in another format.
• PNG: a bitmap image format widely used online.
• PDF: a fixed layout document matching printed pages.

Common misconceptions

• "Every design must be perfectly symmetric." Asymmetric designs are equally valid and sometimes stronger visually.
• "One shape per composition is enough." Thoughtful arrangements of several elements read better.
• "Export only changes the file format." Export preserves the artwork content in a different container.

Teacher activities

1. Starter: display two symmetric designs and ask which uses more interesting arrangement.
2. Open CorelDRAW and name the main drawing tools one by one.
3. Model drawing a symmetric design using rectangle and polygon tools.
4. Demonstrate applying colour fills and outline styles.
5. Show exporting the artwork as a PNG or PDF and confirming the file.
6. Close with the exit question about symmetry value.

Student activities

1. Choose the more interesting arrangement from the starter and explain the reason.
2. Open CorelDRAW and name the main drawing tools displayed.
3. Draw a symmetric design using at least two shape types.
4. Apply colour fills and outline styles to selected shapes.
5. Export the artwork as a PNG or PDF and confirm the file opens.
6. Answer the exit question in one sentence about symmetry value.

Practical / learning evidence

A saved symmetric artwork plus an inspection checklist confirming the export file renders correctly. Submit both for marking.

Resources and preparation

Computers with CorelDRAW available, blank templates and sample symmetric templates. Check CorelDRAW starts reliably. Disable Caps Lock before drawing. Provide large printed templates for low-vision learners.

Assessment for learning

Inspect the artwork for at least two distinct shape types arranged symmetrically. Check the inspection checklist for correct export rendering. Ask a learner to describe why symmetry helps visual balance. Flag any learner who insists symmetry is mandatory.

Inclusion and homework

Provide the symmetric template prearranged so learners focus on colours and shapes. Allow extra time for the export. Extend confident learners with three shape types and a second homework listing one advantage of asymmetric designs. Homework: list one advantage and one disadvantage of symmetric versus asymmetric designs.

Lesson objectives

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

1. Define a one-dimensional array and state its indexing rule.
2. Name three use cases for arrays such as storing scores.
3. Declare an array of ten elements and index correctly.
4. Explain why arrays help organise repeated data.
5. Trace an indexed access returning the correct value.

Key vocabulary

• Array: a sequence stored in consecutive memory slots.
• One-dimensional array: an array storing values along one axis.
• Index: the position number of an element in the array.
• Indexing rule: the convention assigning position numbers to elements.
• Repeated data: values occurring multiple times in a task.
• Consecutive slots: memory positions stored contiguously.
• Declaration: stating the size and type of an array explicitly.
• Access: retrieving a stored element by its index.

Common misconceptions

• "Arrays store text separately." Arrays store homogeneous values; text often sits in a string type separately.
• "Index starts at one always." Zero-based indexing is common but some languages start elsewhere.
• "An array stores unrelated rows." Related rows belong together because of shared field types.

Teacher activities

1. Starter: show ten number cards and ask where they would store them.
2. Define an array and explain indexing by showing a zero-based declaration.
3. Name three use cases such as storing exam scores or inventory.
4. Demonstrate declaring an array of ten elements step by step.
5. Explain why arrays help organise repeated data efficiently.
6. Close with the index-access task and exit question.

Student activities

1. Answer the starter and identify the array as the right storage.
2. Define an array in their own words and name the indexing convention.
3. Name three use cases for arrays in their own words.
4. Declare an array of ten elements and index correctly.
5. Trace an indexed access and write the returned value.
6. Answer the exit question comparing arrays with separate variables in one sentence.

Practical / learning evidence

A declared array worksheet with indexing exercises, a three-use-case chart and an index-access trace. 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 size and indexing. Mark the use cases for genuine relevance. Check the index-access trace for correct retrieval. Flag any learner who thinks arrays store text only.

Inclusion and homework

Provide the array template predeclared for size and allow oral completion of indexing. Extend confident learners with two arrays and a second use case homework. Homework: declare two arrays of different sizes and compare memory usage in one paragraph.

Lesson objectives

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

1. Write a program using an array to compute totals and averages.
2. Locate the largest and smallest value in an array.
3. Use iteration through array indices safely.
4. Debug an array program if errors appear.
5. Save the runnable program and confirm the output.

Key vocabulary

• Iteration: repeating steps through a loop over array indices.
• Loop: a repeatable block of instructions.
• Iteration through indices: stepping the loop counter over array positions.
• Totals: the sum collected across all array values.
• Average: the mean computed from totals and count.
• Largest value: the greatest entry in the array.
• Smallest value: the lowest entry in the array.
• Debug: finding and fixing mistakes in a program.
• Confirm: verifying output matches expectations.

Common misconceptions

• "Arrays replace loops." Arrays handle storage; loops handle repeated iteration over those stores.
• "An array holds only numbers." Some languages allow mixed types inside arrays if declared loosely.
• "Every loop uses the same counter." Counters may start, increment and reset differently.

Teacher activities

1. Starter: show an array totaling a sum and ask whether the totals come from the array directly.
2. Demonstrate a simple array summation loop.
3. Show computing averages and locating the largest value.
4. Demonstrate debugging a broken array program step by step.
5. Save the corrected program and confirm the output.
6. Close with the runnable-program task and exit question.

Student activities

1. Answer the starter and state why a loop collects totals.
2. Write a program using an array to compute totals and averages.
3. Locate the largest and smallest value in an array manually.
4. Debug the broken array program and confirm the corrected output.
5. Save the corrected program under a clear filename and reopen it to confirm.
6. Answer the exit question in one sentence about arrays versus loops.

Practical / learning evidence

A saved runnable array program computing totals, average, largest and smallest, plus the confirmed output. Submit both the program and output for marking.

Resources and preparation

Computers with the interpreter, blank program windows and sample broken programs. Prebuild the interpreter in a read-only folder. Disable Caps Lock before typing. Verify the computer starts reliably.

Assessment for learning

Inspect the program for correct loop structure and array access. Check the confirmed output for sensible totals and averages. Ask a learner to describe the difference between a loop iteration and direct array access. Flag any learner who conflates arrays with loops.

Inclusion and homework

Provide the broken program in a read-only folder for learners needing scaffolding and allow extra debugging time. Extend confident learners with two array programs and a second homework locating an array's median value. Homework: write a second program computing the mode of an array by counting frequencies.

Lesson objectives

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

1. Recall five high-level language families introduced this term.
2. Compare high-level and assembly languages on ease and readability.
3. Explain why schools teach high-level programming first.
4. Name one real application written in each language family.
5. Judge which language suits a named scenario.

Key vocabulary

• High-level language: closer to human speech than machine code.
• Language family: a group of closely related languages.
• Ease and readability: how simply a human can understand source code.
• First programming: introducing high-level languages before assembly.
• Real application: an actual software product built with a language.
• Suit: choosing a language for a specific context.
• Breadth: how many related languages exist in a family.

Common misconceptions

• "All programming languages are equally suitable." Different languages suit different scenarios.
• "Schools must always teach assembly first." Schools usually introduce high-level first.
• "Every language family has no differences." Related languages vary in syntax and purpose.

Teacher activities

1. Starter: hold up two languages, one high-level and one assembly, and ask which students find easier to learn.
2. Recall the five language families one by one.
3. Compare high-level and assembly on ease and readability with examples.
4. Explain why schools teach high-level programming first.
5. Name one real application written in each language family.
6. Close with the scenario-suit choice task and exit question.

Student activities

1. Pick the easier-to-learn language from the starter and explain the reason.
2. Recall five high-level language families in their own words.
3. Compare high-level and assembly on ease and readability briefly.
4. Explain why schools teach high-level programming first in one paragraph.
5. Name one real application written in each language family.
6. Judge which language suits a named scenario and justify it.
7. Answer the exit question in one sentence about school sequencing.

Practical / learning evidence

A five-family comparison chart, a high-level versus assembly comparison and a one-paragraph school-sequencing explanation. Submit all three for marking.

Resources and preparation

Printed comparison templates, blank charts and sample language names. Offline route: paper versions, no device needed. Display language examples carefully and avoid recommending unsupported packages.

Assessment for learning

Inspect the comparison chart for five distinct families compared across criteria. Mark the high-level versus assembly comparison for equal criteria. Check the school sequencing explanation for a sensible rationale. Flag any learner who claims all languages are equally suitable.

Inclusion and homework

Provide the chart prefilled for family names and allow oral comparisons. Extend confident learners with six families and a six-scenario choice homework. Homework: name two related languages within one family and state why they differ slightly.

Lesson objectives

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

1. Recall conversions between decimal, binary, octal and hexadecimal.
2. Recall bit patterns for characters, images and audio samples.
3. Describe why binary is the natural language of digital electronics.
4. Correct previous mistakes on conversion worksheets.
5. Judge whether a given encoding scheme is efficient.

Key vocabulary

• Conversion: changing the base of a number representation.
• Bit pattern: the binary encoding of one piece of data.
• Natural language: the native form a system uses internally.
• Efficient: carrying out a task with minimal waste.
• Encoding scheme: the rules mapping data to bits.
• Decimal: base ten using digits 0 through 9.
• Binary: base two using digits 0 and 1.
• Octal: base eight using digits 0 through 7.
• Hexadecimal: base sixteen using digits 0 through 9 and letters A through F.

Common misconceptions

• "Decimal converts directly to binary." Decimal must be grouped by powers of two for correct conversion.
• "Hexadecimal adds new symbols randomly." Hexadecimal maps cleanly onto four bits each.
• "More bits always mean higher quality." Resolution and encoding matter more than absolute bit count for small images.

Teacher activities

1. Starter: display a wrong conversion and ask which direction gives the error.
2. Recall each conversion method one by one.
3. Show the bit patterns for a letter, a pixel and an audio sample again.
4. Collect previous mistakes and model correcting one conversion.
5. Explain why fewer hexadecimal digits carry the same information as more binary digits.
6. Close with the efficiency judgment task and exit question.

Student activities

1. Spot the wrong conversion from the starter and state the correct method.
2. Recall each conversion between bases and write one worked example.
3. Recall the bit patterns for a letter, a pixel and an audio sample.
4. Correct the mistakes identified on previous worksheets.
5. Judge whether a given encoding scheme is efficient in one sentence.
6. Answer the exit question comparing binary bits to hexadecimal digits in one sentence.

Practical / learning evidence

A corrected conversion ladder, a recalled bit-pattern worksheet and an efficiency-judgment worksheet. Submit all three for marking.

Resources and preparation

Printed conversion ladders, blank bit-pattern templates and sample encoding schemes. Offline route: paper versions, no device needed. Display encodings carefully and avoid exposing sensitive learner information.

Assessment for learning

Inspect the corrected ladder for fixed errors and consistent method. Mark the bit-pattern worksheet for correct mappings. Check the efficiency judgment for a defensible rationale. Flag any learner who skips grouping and guesses conversions.

Inclusion and homework

Provide the conversion ladder prefilled for the first example and allow oral correction of the rest. Reduce the bit-pattern worksheet to two items. Extend confident learners with base conversions beyond octal and hexadecimal and a fourth homework judging encoding efficiency. Homework: convert one decimal number to binary and verify the result by grouping.

Lesson objectives

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

1. Recall five common cyber threats and their protections from earlier terms.
2. Name three emerging technologies such as artificial intelligence and IoT.
3. Explain how emerging technologies change daily life in one area.
4. Contrast emerging and mature technologies on adoption and governance.
5. State one rule limiting internet use based on personal risk awareness.

Key vocabulary

• Cyber threat: anything that can harm systems, data or users.
• 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.
• Adoption: how widely a technology is used today.
• Governance: rules governing how a technology operates.
• Rule: a behaviour guideline restricting risky activity.

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 security." Learners face the same threats wherever they use devices.

Teacher activities

1. Starter: display two threat cards, phishing and ransomware, and ask which you prefer avoiding.
2. Recall the five cyber threats and their protections from earlier terms.
3. Recall three emerging technologies and how one changes daily life.
4. Contrast emerging and mature technologies on adoption and governance.
5. State one rule limiting internet use based on personal risk awareness.
6. Close with the security-and-ethics consolidation task and exit question.

Student activities

1. Choose the preferred threat-avoidance starter and justify the reason.
2. Recall five cyber threats and state the protection for each.
3. Recall three emerging technologies and describe how one changes daily life.
4. Contrast emerging and mature technologies on adoption and governance.
5. State one rule limiting internet use based on personal risk awareness.
6. Consolidate the security-and-ethics topics in one written summary.
7. Answer the exit question in one sentence about emerging technologies.

Practical / learning evidence

A five-threat-with-protection sheet, an emerging versus mature comparison and a one-paragraph security-and-ethics 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 sheet for five matched threats and protections. Check the emerging versus mature comparison for sensible distinctions. Mark the security-and-ethics summary for genuine coverage. Flag any learner who dismisses emerging technologies as 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 fifth homework naming one emerging technology you find most useful. Homework: name one security threat outside the list and state the protective measure.

Lesson objectives

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

1. Test objective knowledge with a short mock quiz.
2. Identify weak areas from the mock results.
3. Practise recall and short-answer skills under timed conditions.
4. Prepare for the examination week materials and stationery.
5. State a clear examination strategy per section.

Key vocabulary

• Mock quiz: a timed test styled after the upcoming examination.
• Weak area: a topic where recall falls below target.
• Short-answer skills: techniques producing concise written responses.
• Timed conditions: a restricted time allowance for practice.
• Examination strategy: a plan allocating time and effort per section.
• Stationery: physical writing supplies kept for examinations.

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: run a timed mock quiz and share the class results anonymously.
2. Identify the three weakest topics by class consensus.
3. Run a second timed recall quiz and compare marks.
4. Demonstrate the examination strategy and break it down section by section.
5. Confirm the materials checklist and the examination room booking.
6. Close with the strategy-announcement and exit question.

Student activities

1. Take the timed mock quiz and record personal marks.
2. Identify your weakest topic from the mock results.
3. Practise short-answer writing for ten minutes on two questions.
4. Plan an examination strategy per section.
5. Pack stationery and prepare the materials checklist.
6. Answer the exit question in one sentence about your strategy.

Practical / learning evidence

The timed mock quiz, the personal revision plan and the materials checklist signed by the learner. All three submitted for marking.

Resources and preparation

Mock quiz sheets, revision-plan templates and materials checklists. Confirm the examination room, machines and invigilators booked before the week.

Assessment for learning

Inspect the mock quiz for honest timing. Check the revision plan for specific weak areas and strategies. Verify the materials checklist is signed and ready. Record any learner with persistent weaknesses for reteaching.

Inclusion and access

Provide the mock quiz in large print and allow extra time where approved. Pair learners for short-answer practice. Homework: pack everything needed for the examination week and store it safely.

Lesson objectives

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

1. Demonstrate recall under examination conditions.
2. Apply knowledge to unfamiliar short-answer questions.
3. Complete one practical task within the time allowance.
4. Name, save and submit files correctly.
5. Explain their practical output when questioned.

Mock 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	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 and seating before the week begins.
2. Brief learners on the mock paper structure, time for each section and materials allowed.
3. Set out two practical stations: database schema and logic-gate construction.
4. Prepare offline equivalents for learners without device access: printed sketchbooks and paper templates.
5. Mark using the agreed scheme and moderate a sample of scripts.
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 mock script, the saved practical file for each candidate and the practical rubric sheets. Retain scripts for moderation as required by the assessment framework.

Resources and preparation

Mock question papers and answer sheets, a marking guide and rubric per station, working computers with a database tool or spreadsheet and graphics package, printed sketchbooks and paper templates. 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 mock

Return marked scripts with brief feedback and hand over to SSCE preparation: corel draw, arrays, language review, data representation, security ethics, intensive revision, past questions and final SSCE strategy. Note any topic where the class average fell below the school threshold and schedule it as a targeted retrieval starter.