SS 2 Third Term

Lesson objectives

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

1. Define a variable and name at least four data types.
2. Assign values to variables and display them correctly.
3. Convert between string, integer and float types.
4. Store a list of values in a single variable.
5. Trace a simple variable declaration and assignment.

Key vocabulary

• Variable: a named container holding a value.
• Data type: the category defining what values a variable holds.
• Integer: a whole number without fractional parts.
• Float: a number with fractional parts.
• String: text held as an immutable sequence.
• Boolean: a true or false value.
• List: an ordered collection stored in consecutive slots.
• Declaration: stating the size and type of a variable explicitly.
• Assignment: giving a value to a previously declared variable.
• Display: showing a value on screen via print().

Common misconceptions

• "Variables hold text automatically." Text sits in a string type explicitly declared.
• "Every variable holds one value only." Python lists hold multiple values.
• "Assignment copies the value forever." Assignment binds the name to the value; reassignment later changes it.

Teacher activities

1. Starter: display a printed word and a printed number and ask which need explicit typing.
2. Define a variable and state why Python uses explicit typing.
3. Name four data types one by one and assign example values.
4. Demonstrate assigning an integer, a float and a string.
5. Show declaring a list of values.
6. Close with the declaration task and exit question.

Student activities

1. Answer the starter and state why variables need explicit typing.
2. Define a variable in their own words and name four data types.
3. Assign an integer, a float and a string with sample values.
4. Display each assigned value with print() in separate statements.
5. Declare a list of five values and index the first and last.
6. Answer the exit question in one sentence about Python types.

Practical / learning evidence

A declared variable worksheet with type checks, a runnable arithmetic program and a list demonstration. Submit all three for marking.

Resources and preparation

Computers with a Python interpreter installed, blank variables 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 declared variables for correct names and matching types. Mark the runnable program for sensible arithmetic. Check the list demonstration for correct indexing. Flag any learner who assumes variables carry text automatically.

Inclusion and homework

Provide the variable template predeclared for names and allow oral type assignment. Allow extra time on the runnable program. Extend confident learners with three more data types and a seventh homework displaying one boolean variable. Homework: write a second program declaring two variables of different types and combining them with arithmetic.

Lesson objectives

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

1. Use input() to read numeric and text values from the user.
2. Perform addition, subtraction, multiplication and division.
3. Use comparison operators such as greater than and less than.
4. Combine input, operators and conditional logic in one program.
5. Trace a simple runnable program predicting the expected output.

Key vocabulary

• Input: entering data from the user into a program.
• Input statement: the line telling Python to ask for data.
• Output: displaying a result to the user.
• Print statement: the command displaying text or values.
• Arithmetic operator: plus, minus, multiply or divide.
• Comparison operator: greater than, less than or equal.
• Logical operator: and, or, not combining conditions.
• Assignment: giving a value to a variable.
• Value: the data entered or produced by a computation.

Common misconceptions

• "Python reads numeric input as text." Numeric strings must be converted explicitly with int() before arithmetic.
• "Every operator behaves identically." Arithmetic, comparison and logical operators differ fundamentally.
• "Print sends the value only once." Print displays the value each time the statement appears.

Teacher activities

1. Starter: run a simple PRINT statement and display the result without revealing the code.
2. Demonstrate input() reading a number and printing the result.
3. Show performing arithmetic operations on two inputs.
4. Demonstrate using comparison operators in an if statement.
5. Combine input, operators and conditional logic in one program.
6. Close with the combined program task and exit question.

Student activities

1. Guess the PRINT command from the starter RUN.
2. Use input() to read a number from the user.
3. Perform addition, subtraction, multiplication and division on two inputs.
4. Use a comparison operator to decide a result.
5. Combine input, operators and conditional logic in one program.
6. Answer the exit question in one sentence about numeric conversion.

Practical / learning evidence

A combined program demonstrating input, arithmetic, comparison and conditional logic, plus the confirmed expected output. Submit both the program and output for marking.

Resources and preparation

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

Assessment for learning

Inspect the combined program for correct input, arithmetic and conditional syntax. Check the expected output for sensible calculations. Ask a learner to explain why int() converts numeric strings. Flag any learner who performs arithmetic on text input directly.

Inclusion and homework

Provide the sample prompts prebuilt for the user so learners focus on operators. Allow extra time for combining components. Extend confident learners with two more operators and a second homework checking whether input is numeric with try/except. Homework: write a second program with a single conditional branch and display the chosen path.

Lesson objectives

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

1. Name the selection statements IF, ELIF and ELSE.
2. Write an if statement deciding between two outcomes.
3. Write an elif statement handling a middle outcome.
4. Combine if, elif and else into one robust branch.
5. Trace a combined selection statement predicting the outcome.

Key vocabulary

• Selection: a branch choosing different paths under conditions.
• IF statement: a condition controlling which branch runs.
• ELIF statement: a second condition checked only after the first fails.
• ELSE statement: the final branch running when no earlier condition matches.
• Branch: one of the paths taken by a selection statement.
• Condition: the boolean expression evaluating the branch.
• Outcome: the result displayed when a condition is true.

Common misconceptions

• "IF runs everything." IF runs only when its condition is true; other branches may still run.
• "ELSE covers everything." ELSE runs only when neither IF nor ELIF matches.
• "Every statement needs both IF and ELSE." A pure IF statement handles two outcomes only.

Teacher activities

1. Starter: display an IF and an ELSE statement and ask which runs when a condition is true.
2. Name IF, ELIF and ELSE one by one and demonstrate each on a live system.
3. Write a simple IF deciding between two outcomes.
4. Add an ELIF handling a middle outcome.
5. Combine IF, ELIF and ELSE into one robust branch.
6. Close with the combined-branch task and exit question.

Student activities

1. Answer the starter and state which statement runs under a true condition.
2. Name IF, ELIF and ELSE in their own words.
3. Write a simple IF deciding between two outcomes.
4. Add an ELIF handling a middle outcome.
5. Combine IF, ELIF and ELSE into one robust branch.
6. Trace the combined branch predicting the outcome for each case.
7. Answer the exit question in one sentence about ELSE coverage.

Practical / learning evidence

A combined IF-ELIF-ELSE program with two cases, plus the confirmed outputs for each. Submit both the program and outputs for marking.

Resources and preparation

Computers with the interpreter, blank program windows 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 combined branch for correct IF, ELIF and ELSE syntax. Check the outputs for sensible outcomes. Ask a learner to describe when ELSE runs. Flag any learner who writes IF without ELSE.

Inclusion and homework

Provide the combined branch template prefilled for the conditions and allow oral tracing. Allow extra time on the tracing task. Extend confident learners with three branches and a second homework nesting two selections. Homework: write a program with two nested if statements and display each branch's path.

Lesson objectives

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

1. Define iteration and state its benefit for repeated tasks.
2. Name the two FOR loop structures in Python.
3. Write a FOR loop counting from one to ten.
4. Write a WHILE loop with a counter guarding termination.
5. Trace both loops predicting the displayed numbers.

Key vocabulary

• Iteration: repeating steps through a loop.
• FOR loop: a loop iterating over an iterable object.
• WHILE loop: a loop repeating while a condition remains true.
• Counter: a variable tracking loop position.
• Guard: the condition preventing a WHILE loop from running forever.
• Sequence: the iterable object a FOR loop traverses.
• Range: the built-in object generating a sequence of numbers.
• Termination: the point a loop stops executing.
• Displayed numbers: the visible output of each iteration.

Common misconceptions

• "FOR loops always count numbers." A FOR loop can iterate over any iterable.
• "WHILE loops never need a guard." Without a guard a WHILE loop runs forever.
• "Two loops cannot count the same range." Two loops can traverse overlapping ranges.

Teacher activities

1. Starter: display a repeated counting task and ask which structure suits it.
2. Define iteration and name the two FOR loop structures.
3. Write a FOR loop counting from one to ten and trace it.
4. Write a WHILE loop with a counter guarding termination.
5. Compare both loops on efficiency and clarity.
6. Close with the both-loops task and exit question.

Student activities

1. Answer the starter and state which structure suits repeated counting.
2. Define iteration in their own words and state its benefit.
3. Write a FOR loop counting from one to ten and display the numbers.
4. Write a WHILE loop with a counter guarding termination.
5. Display both sequences and compare their efficiency and clarity.
6. Answer the exit question in one sentence about WHILE guards.

Practical / learning evidence

A FOR counting loop with displayed numbers, a WHILE counting loop with a guard, and a comparison observation. Submit all three for marking.

Resources and preparation

Computers with the interpreter, blank program windows 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 FOR loop for correct range and displayed numbers one through ten. Check the WHILE loop for a sensible counter guard. Compare both loops for reasonable efficiency and clarity observations. Flag any learner who omits the WHILE guard.

Inclusion and homework

Provide both loops prefilled for the range expressions and allow oral tracing. Allow extra time on the WHILE version. Extend confident learners with two FOR loops and a fourth homework writing a WHILE loop that counts backwards from ten. Homework: write a second FOR loop summing a range and display the total.

Lesson objectives

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

1. Plan a mini-project combining variables, selection and iteration.
2. Write a calculator program taking two inputs and an operator.
3. Handle division safely when the divisor is zero.
4. Display the chosen result clearly.
5. Debug the program if errors appear and confirm the output.

Key vocabulary

• Mini-project: a small applied task exercising multiple skills.
• Calculator: a program accepting operands and an operator.
• Operand: a value entered for calculation.
• Operator: plus, minus, multiply, divide or select.
• Division by zero: attempting to divide by the number zero.
• Safe handling: avoiding crashes on edge cases.
• Display: presenting the computed result.
• Debug: finding and fixing mistakes in a program.
• Confirm: verifying output matches expectations.

Common misconceptions

• "Every operator behaves identically." Division requires special care for zero divisors.
• "Input and operator are optional." Both must arrive from the user to make the program functional.
• "No error handling is needed in a calculator." Division by zero crashes the program.

Teacher activities

1. Starter: display a broken calculator and ask where the error appears.
2. Explain the mini-project requirement and model planning on paper.
3. Demonstrate writing a calculator with input, selection and division handling.
4. Demonstrate debugging a division-by-zero error safely.
5. Save the program and reopen to confirm the output.
6. Close with the combined task and exit question.

Student activities

1. Observe the broken calculator and locate where the error appears.
2. Explain the mini-project requirement in one paragraph.
3. Plan a calculator taking two inputs and an operator.
4. Write the calculator with safe division handling.
5. Debug any division-by-zero errors and confirm the corrected output.
6. Answer the exit question in one sentence about division safety.

Practical / learning evidence

A runnable calculator program handling all five operators safely, plus the confirmed output for normal and division-by-zero cases. Submit both the program and outputs for marking.

Resources and preparation

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

Assessment for learning

Inspect the calculator for all five operators and safe division handling. Check the outputs for sensible calculations including the division-by-zero warning. Ask a learner to describe the division-by-zero check. Flag any learner who lets division by zero crash the program.

Inclusion and homework

Provide the broken calculator prebuilt for learners needing scaffolding and allow extra debugging time. Extend confident learners with three more operators and a second homework extending the calculator to modulus and exponent. Homework: write a second mini-project computing student averages safely with division-by-zero handling.

Lesson objectives

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

1. Define e-commerce and name three commerce types.
2. Compare retail, service and wholesale commerce on criteria.
3. Explain why electronic commerce suits small sellers.
4. Describe one local e-commerce platform serving retail commerce.
5. Judge whether a given scenario fits a commerce type.

Key vocabulary

• E-commerce: buying and selling goods or services online.
• Retail commerce: direct sale to individual buyers.
• Service commerce: selling digital or services rather than physical goods.
• Wholesale commerce: bulk sale to businesses.
• Electronic marketplace: an online platform enabling transactions.
• Small seller: an individual business selling directly.
• Criteria: measurable attributes such as price and scale.
• Platform: the infrastructure enabling the transaction.
• Local commerce: trade occurring within a region.

Common misconceptions

• "E-commerce means selling products only." Service commerce also counts.
• "Electronic commerce replaces local markets." Electronic commerce supplements local markets rather than replacing them.
• "Every seller benefits equally from electronic commerce." Small sellers benefit disproportionately from low overhead.

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. Compare retail, service and wholesale on price, scale and channel.
4. Explain why electronic commerce suits small sellers.
5. Name one local e-commerce platform and describe its retail service.
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. Compare retail, service and wholesale on three criteria.
4. Explain why electronic commerce suits small sellers in one paragraph.
5. Name one local e-commerce platform and describe its retail service.
6. Classify a scenario as retail, service or wholesale commerce.
7. Answer the exit question in one sentence about small sellers.

Practical / learning evidence

A three-type comparison chart, a small-seller explanation paragraph and a one-paragraph local-platform description. Submit all three for marking.

Resources and preparation

Printed chart templates, blank comparison cards and sample scenarios. Offline route: paper versions, no device needed. Display platform examples carefully and avoid citing proprietary commercial details beyond the service description.

Assessment for learning

Inspect the comparison chart for three distinct types compared across criteria. Check the small-seller explanation for a sensible overhead rationale. Mark the local-platform description for genuine retail service. Flag any learner who claims e-commerce means selling products only.

Inclusion and homework

Provide the comparison prefilled for the first two types and allow oral scenario classification. Extend confident learners with five commerce types and a sixth homework describing one electronic commerce platform from another country. Homework: describe one e-commerce service selling services rather than products in one paragraph.

Lesson objectives

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

1. Name four payment systems such as cash on delivery and bank transfer.
2. Describe each payment system on speed, convenience and security.
3. Explain why digital payments dominate modern e-commerce.
4. State three safety measures protecting online transactions.
5. Judge which payment system suits a named scenario.

Key vocabulary

• Payment system: the channel used to settle an online order.
• Cash on delivery: paying when the delivered item arrives.
• Bank transfer: transferring funds between bank accounts.
• Digital wallet: a stored account holding payment credentials.
• Credit card: a card extending a short-term credit line.
• Debit card: a card linked directly to an account balance.
• Domestic transfer: transferring funds within one country.
• International transfer: transferring funds across borders.
• Modern preference: the current dominant payment method.
• Safety measure: a safeguard against transaction risk.

Common misconceptions

• "Every payment goes through banking only." Payments happen through many channels including wallets and cards.
• "Cash on delivery is always safest." COD exposes sellers to fraud until delivery.
• "Digital payments are always faster than older methods." Older methods offer strong guarantees for privacy.

Teacher activities

1. Starter: display two payment methods, one digital and one traditional, and ask which modern sellers prefer.
2. Name four payment systems one by one and describe each.
3. Compare them on speed, convenience and security.
4. Explain why digital payments dominate modern e-commerce.
5. State three safety measures protecting online transactions.
6. Close with the payment-choice task and exit question.

Student activities

1. Choose the starter item and explain the preference reason.
2. Name four payment systems and describe each role in one sentence.
3. Compare them on two criteria each.
4. Explain why digital payments dominate modern e-commerce in one paragraph.
5. Name three safety measures protecting online transactions.
6. Choose the payment system suited to a named scenario and justify it.
7. Answer the exit question in one sentence about modern preferences.

Practical / learning evidence

A four-payment-system chart with descriptions, a modern-preference explanation and a one-paragraph safety summary. 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 secure payment gateways carefully and avoid accessing live systems.

Assessment for learning

Inspect the payment chart for four distinct systems with descriptions. Mark the modern-preference explanation for a sensible dominance rationale. Check the safety summary for three enforceable measures. Flag any learner who claims COD is always safest.

Inclusion and homework

Provide the chart prefilled for the first two payment systems and allow oral completion of the rest. Extend confident learners with six more payment methods and a sixth homework naming one safety measure from your school lab. Homework: choose one payment system for buying groceries locally and justify the choice.

Lesson objectives

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

1. Plan a project combining SDLC stages with Python code.
2. Write a requirements document for the project.
3. Produce a Python artifact satisfying the requirements.
4. Add a README describing the project structure.
5. Save both the Python source and the README together.

Key vocabulary

• Mini-project: a small applied task exercising multiple skills.
• SDLC artifact: a product created through the software development life cycle.
• Requirements document: a short spec stating inputs, outputs and behaviour.
• Artifact: any produced output such as code, documentation or a design.
• README: a short file describing a project's structure.
• Source file: the primary code file holding programme logic.
• Structure: the layout of files and directories.
• Combine: merging several components into one deliverable.
• Plan: the documented outline before building.
• Verify: confirming the deliverable satisfies the requirements.

Common misconceptions

• "The project must reuse every skill learned this term." The project exercises enough skills to demonstrate understanding.
• "The README is optional fluff." The README helps reviewers understand the project structure quickly.
• "A draft is final immediately." Drafts are reviewed and refined before submission.

Teacher activities

1. Starter: display a requirements card and a project artifact and ask which reviewer prefers.
2. Explain the project requirement combining SDLC stages with Python.
3. Model drafting a requirements document on paper.
4. Demonstrate producing a Python artifact satisfying those requirements.
5. Add a README describing the project structure.
6. Close with the submission task and exit question.

Student activities

1. Choose the reviewer-preferred item and explain the reason.
2. Explain the project requirement in one paragraph.
3. Draft a requirements document with aim, inputs and outputs.
4. Produce a Python artifact satisfying those requirements.
5. Add a README describing the project structure.
6. Save both the Python source and the README together.
7. Answer the exit question in one sentence about documentation value.

Practical / learning evidence

A requirements document, a Python artifact satisfying the requirements and a README describing the structure. All three submitted together for marking.

Resources and preparation

Computers with Word or Writer and the Python interpreter, blank templates and sample artifacts. Check the computer starts reliably and that the interpreter exists. Provide sample requirements documents for learners needing scaffolding.

Assessment for learning

Inspect the requirements document for sensible aim, inputs and outputs. Check the Python artifact for the required behaviour. Evaluate the README for clear structure description. Flag any learner who treats the README as optional.

Inclusion and access

Provide the requirements template prefilled for aim, inputs and outputs and allow extra time on the Python artifact. Extend confident learners with three more requirements and a second homework revising the README with one strength and one weakness. Homework: extend the project artifact with a second feature satisfying a second requirement.

Lesson objectives

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

1. Recall the full term's key terms without notes in ten minutes.
2. Test objective knowledge with a short recall quiz.
3. Practise Python, e-commerce and SDLC 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 Final SSCE preparation 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 Python, e-commerce and SDLC 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 Final SSCE 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 2 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 Python execution, e-commerce safety and project artefact.

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 (Python execution / payment-system choice / project artefact)	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: Python execution, e-commerce payment and project artefact, with one invigilator per station where possible.
4. Prepare offline equivalents for learners without device access: printed sketchbooks and paper payment-choices worksheet.
5. Mark using the agreed scheme, moderate a sample of scripts and record scores.
6. Return scripts with feedback and hand over to SSCE / NECO Examinations.

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 return them to the SSCE supervisor for storage.

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 the Python interpreter 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, code execution, payment-system choice, project artefact, 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 keep representative samples for moderation. Note any topic where the class average fell below the school threshold and schedule it as a Final SSCE targeted retrieval starter for the next session.