Blame
|
1 | > **DRAFT** — under teacher review. |
||||||
| 2 | ||||||||
| 3 | # Object Descriptions and Class Diagrams |
|||||||
| 4 | ||||||||
| 5 | The Hamilton and Alexandra College · Year 12 · 2026 |
|||||||
| 6 | ||||||||
| 7 | If your solution uses **objects and classes**, the fifth design tool is the **object description**. VCAA defines it as a tool that *"describes all of the relevant properties, methods and events in an object or class."* A **class diagram** is the standard way to draw a whole set of object descriptions at once and show how the classes relate. |
|||||||
| 8 | ||||||||
| 9 | This is a **Level 7+** tool in C5-1, and at **Level 9** you are also expected to write pseudocode for the methods inside your classes. |
|||||||
| 10 | ||||||||
| 11 | > [!NOTE] |
|||||||
| 12 | > **Only if you use OOP.** If your solution genuinely does not use classes and objects, you do not need object descriptions. But most SAT projects of any real size have at least a few classes — and a class diagram is the clearest way to show them. |
|||||||
| 13 | ||||||||
| 14 | --- |
|||||||
| 15 | ||||||||
| 16 | ## Reading a class diagram |
|||||||
| 17 | ||||||||
| 18 | Each box is a **class**. The top section lists its **attributes** (properties), the bottom section lists its **methods** (actions), and the arrows show **relationships** between classes. |
|||||||
| 19 | ||||||||
| 20 | ```mermaid |
|||||||
| 21 | --- |
|||||||
| 22 | title: Animal example |
|||||||
| 23 | --- |
|||||||
| 24 | classDiagram |
|||||||
| 25 | note "From Duck till Zebra" |
|||||||
| 26 | Animal <|-- Duck |
|||||||
| 27 | note for Duck "can fly<br>can swim<br>can dive<br>can help in debugging" |
|||||||
| 28 | Animal <|-- Fish |
|||||||
| 29 | Animal <|-- Zebra |
|||||||
| 30 | Animal : +int age |
|||||||
| 31 | Animal : +String gender |
|||||||
| 32 | Animal: +isMammal() |
|||||||
| 33 | Animal: +mate() |
|||||||
| 34 | class Duck{ |
|||||||
| 35 | +String beakColor |
|||||||
| 36 | +swim() |
|||||||
| 37 | +quack() |
|||||||
| 38 | } |
|||||||
| 39 | class Fish{ |
|||||||
| 40 | -int sizeInFeet |
|||||||
| 41 | -canEat() |
|||||||
| 42 | } |
|||||||
| 43 | class Zebra{ |
|||||||
| 44 | +bool is_wild |
|||||||
| 45 | +run() |
|||||||
| 46 | } |
|||||||
| 47 | ``` |
|||||||
| 48 | ||||||||
| 49 | Read it like this: `Animal` is the **base class**. `Duck`, `Fish` and `Zebra` are all *a kind of* Animal, so each one **inherits** Animal's attributes (`age`, `gender`) and methods (`isMammal()`, `mate()`) and then adds its own. `Duck` adds `beakColor`, `swim()` and `quack()`; it doesn't have to redefine `age` because it already has it from `Animal`. |
|||||||
| 50 | ||||||||
| 51 | --- |
|||||||
| 52 | ||||||||
| 53 | ## The notation you need |
|||||||
| 54 | ||||||||
| 55 | | Symbol | Meaning | |
|||||||
| 56 | |---|---| |
|||||||
| 57 | | `+` | **Public** — usable from outside the class | |
|||||||
| 58 | | `-` | **Private** — usable only inside the class | |
|||||||
| 59 | | `age : int` | An **attribute** and its **data type** | |
|||||||
| 60 | | `isMammal()` | A **method** (an action the object can perform) | |
|||||||
| 61 | | `isUpcoming() : bool` | A method and its **return type** | |
|||||||
|
62 | |||||||
| 63 | **Relationships** are shown with arrows between classes. The inheritance arrow `<|--` means *"is a kind of"* — writing `Animal <|-- Duck` says **Duck is a kind of Animal**, so Duck inherits all of Animal's attributes and methods and then adds its own. (Two others you may meet: *composition* `*--`, "is made of", and *association* `-->`, "uses".) |
|||||||
|
64 | |||||||
| 65 | > [!TIP] |
|||||||
| 66 | > Every attribute should have a **data type** and every method should show its **parameters and return type**. "`age`" alone is weak; "`+ age : int`" is design-ready. This is exactly the precision that lifts C5-1 from the middle bands into 7–9. |
|||||||
| 67 | ||||||||
| 68 | --- |
|||||||
| 69 | ||||||||
| 70 | ## Properties, methods — *and events* |
|||||||
| 71 | ||||||||
| 72 | A class diagram shows properties and methods well. But VCAA object descriptions also include **events** — especially for **GUI objects** (buttons, text fields, menus). An event is something the object *responds to*, like a click. |
|||||||
| 73 | ||||||||
| 74 | For a login button you might describe the object like this: |
|||||||
| 75 | ||||||||
| 76 | | Aspect | Example for `btnLogin` (a button) | |
|||||||
| 77 | |---|---| |
|||||||
| 78 | | **Properties** | `caption` = "Log in", `enabled` = true | |
|||||||
| 79 | | **Methods** | `setEnabled(state)` | |
|||||||
| 80 | | **Events** | `onClick` → runs the *Validate User* process | |
|||||||
| 81 | ||||||||
| 82 | So: the class diagram carries your properties and methods; for interface objects, add a short note or table documenting the **events** as well. |
|||||||
| 83 | ||||||||
| 84 | --- |
|||||||
| 85 | ||||||||
| 86 | ## How it connects to your other design tools |
|||||||
| 87 | ||||||||
| 88 | The object description is not an island — it ties the whole detailed design together: |
|||||||
| 89 | ||||||||
|
90 | - **Properties ↔ data dictionary.** Every attribute is a field. `studentID : int` becomes a data-dictionary row with a type, size and format. See [Data Dictionary](/sd/C05/Data%20Dictionary). |
||||||
|
91 | - **Methods ↔ pseudocode.** At Level 9 you write pseudocode for each method. The `is_passing()` example on the pseudocode page is exactly a method from a class diagram, written out. See [VCAA Pseudocode — Not Python](/sd/C05/VCAA%20Pseudocode%20Not%20Python). |
||||||
| 92 | - **Classes ↔ mock-ups and IPO charts.** The objects are what sit *behind* your screens and processes. |
|||||||
| 93 | ||||||||
| 94 | --- |
|||||||
| 95 | ||||||||
| 96 | ## Common mistakes |
|||||||
| 97 | ||||||||
| 98 | ### Mistake 1: An object description with no methods |
|||||||
| 99 | ||||||||
| 100 | > ~~A box listing only attributes~~ |
|||||||
| 101 | ||||||||
| 102 | That is just a data dictionary in disguise. An object description must include the **methods** (and, for GUI objects, the **events**) — that is what makes it an *object*. |
|||||||
| 103 | ||||||||
| 104 | ### Mistake 2: No visibility or data types |
|||||||
| 105 | ||||||||
| 106 | > ~~`beakColor`, `swim`~~ |
|||||||
| 107 | ||||||||
| 108 | Show whether each member is public (`+`) or private (`-`), give every attribute a **type**, and give every method its **parameters and return type**. |
|||||||
| 109 | ||||||||
| 110 | ### Mistake 3: Classes drawn with no relationships |
|||||||
| 111 | ||||||||
| 112 | If `Teacher` is a kind of `Student`, draw the inheritance arrow. A diagram of disconnected boxes hides the design thinking the arrows are meant to show. |
|||||||
| 113 | ||||||||
| 114 | ### Mistake 4 (Level 9): A class diagram but no method pseudocode |
|||||||
| 115 | ||||||||
| 116 | At Level 9 the methods in your diagram must be backed by pseudocode. A diagram on its own caps you below the top band. |
|||||||
| 117 | ||||||||
| 118 | --- |
|||||||
| 119 | ||||||||
| 120 | ## Check Your Understanding |
|||||||
| 121 | ||||||||
| 122 | 1. In the Animal diagram, name two things `Duck` inherits from `Animal`, and one thing `Duck` adds of its own. |
|||||||
| 123 | ||||||||
| 124 | >| **Inherits** (any two): `age`, `gender`, `isMammal()`, `mate()`. **Adds** (any one): `beakColor`, `swim()`, `quack()`. |
|||||||
| 125 | ||||||||
| 126 | 2. What do `+` and `-` mean in front of an attribute or method? |
|||||||
| 127 | ||||||||
| 128 | >| `+` means **public** (accessible from outside the class); `-` means **private** (accessible only inside the class). |
|||||||
| 129 | ||||||||
| 130 | 3. Which design tool turns the *methods* in your class diagram into step-by-step logic — and at which level is it required? |
|||||||
| 131 | ||||||||
| 132 | >| **Pseudocode**, required at **Level 9** (pseudocode for the functions and methods within your classes). See [VCAA Pseudocode — Not Python](/sd/C05/VCAA%20Pseudocode%20Not%20Python). |
|||||||
| 133 | ||||||||
| 134 | --- |
|||||||
| 135 | ||||||||
| 136 | ## Credits |
|||||||
| 137 | ||||||||
| 138 | - Class-diagram example adapted from the [Mermaid](https://mermaid.js.org/) documentation's *Animal* sample. |
|||||||
| 139 | ||||||||
| 140 | --- |
|||||||
| 141 | ||||||||
| 142 | ## See also |
|||||||
| 143 | ||||||||
| 144 | - [VCAA Pseudocode — Not Python](/sd/C05/VCAA%20Pseudocode%20Not%20Python) — write the pseudocode for each method (Level 9) |
|||||||
|
145 | - [Data Dictionary](/sd/C05/Data%20Dictionary) — each attribute is a data-dictionary field |
||||||
|
146 | - [Sketch vs Mock-up](/sd/C05/Sketch%20vs%20Mock-up) |
||||||
| 147 | - [C05 Resources](/sd/Resources/C05-Resources) |
|||||||
| 148 | ||||||||
| 149 | ← Back to [C05 Home](/sd/C05/C05-home) · [VCE Software Development Hub](/sd/VCE%20Software%20Development%20Hub) |
|||||||
