Gallery

csAH OOP up-skill

Tutor initial call

Concept Sequence: csAH SDD-OOP upskill

OOP Scenarios

Sports Team

Webinar Tutorial Plan

Notes from core team

Course Materials

Tutor Materials

Explore

Concept Sequence: csAH SDD-OOP upskill

Logical design for topic sequence

Brendan McCart

Last edited 554 days ago by Brendan McCart

Scenarios for considering OOP concepts

1 UML with single class

Person

class, properties and data types, encapsulation, access modifiers, methods, constructor, instantiation, object and reference variable

2 UML Superclass and sibling subclasses

Person, Player, Coach

subclass, inheritance relationship, (super class, over-ride)

3 UML Class with associate class featuring an array of objects

Team Class with squad array of Player

storing references in an array for multiple objects of the same type

(associate relationship)

4 UML with array of superclass references to subclass objects (polymorphism)

PassengerList with Person array of Player and Coach objects

storing references in an array for multiple objects of different types

Features for consideration regarding OOP concepts in each scenario

UML of class(es)

code to create and use objects, no problem solving

visualisation of creation and use of objects instantiated from class(es)

related misconceptions for each scenario: symptoms

example: objects can be treated as records (based on similar dot syntax), encapsulated fields can be used without accessor method

a property (UML class) is the same as an instance variable (object)

A class is the same as an object

each object has its own copy of the method code

variables are storing multiple values, for each object

formative assessment questions to explore misconceptions in each scenario

(There are examples of formative assessment questions on CodeHS)

read and interpret UML,

read and interpret sample SQARL code for class(es)

simple code which leads to exposing correct and incorrect understanding

sample questions

consider using values from a class without accessor methods

consider UML and some code: how many classes are there, how many objects are there, how many methods, how many properties

read and interpret simple code, secure use of OOP terminology

constructor

setter methods

display

requirements based problem solving

exam style presentation, summative assessment

CD or music playList model

develop UML

create a method to compare two tracks and determine which has had most plays, display the title

calculate average number of plays

how to coach students to read the requirements, identify and explain requirements

how to coach code development

Scenarios for considering OOP concepts

Features for consideration regarding OOP concepts in each scenario

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.