JSS 3 First Term

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.