UML CLASS DIAGRAMS ARE AWESOME

THEY’RE SIMPLE AND EASY TO MAKE

ALL YOU NEED ARE RECTANGLES AND ARROWS

UP TO 3 RECTANGLES CAN REPRESENT A CLASS

PUT YOUR CLASS NAME IN THE FIRST RECTANGLE

MyClass

YOUR VARIABLES IN THE SECOND RECTANGLE

MyClass

myVariable: String

AND YOUR METHODS IN THE THIRD RECTANGLE

MyClass

myMethod(): String

myVariable: String

YOU CAN ASSOCIATE A CLASS TO ANOTHER

WITH A DASHED OPEN ARROWMyClass

myVariable: MyOtherClass

myMethod(): String

MyOtherClass myVariable: String anotherMethod()

<< uses >>

YOU CAN INHERIT

FROM A CLASS WITH A CLOSED

ARROWMyChild

myVariable: String

myMethod()

MyParent myMethod()

DO YOU REALLY NEED TO INHERIT

FROM A CLASS?

!

REALLY?

CAN’T YOU JUST USE AN ASSOCIATION INSTEAD?

ALWAYS FAVOR ASSOCIATION

OVER INHERITANCE

BUT WHEN YOU DO USE INHERITANCE, REMEMBER…

THE RELATION IS NOT “IS A” BUT “CAN REPLACE”

DON’T USE POLYMORPHISM TO CHANGE STRUCTURE!

USE IT TO CHANGE BEHAVIOR

WITH GREAT POWER COMES GREAT

RESPONSIBILITIES

GREAT UML CLASS DIAGRAMS …

ARE SHORT

THEY COMMUNICATE A SINGLE

AND IMPORTANT CONCEPT

THEY ARE NOT DETAILED PROGRAMMING INSTRUCTIONS

WORRY ABOUT COMMUNICATION

LET THE PROGRAMMER FILL IN THE DETAILS

ALWAYS INCLUDE A LITTLE TEXT EXPLAINING WHAT YOU WANT

TO COMMUNICATE

AND ALWAYS KEEP IN MIND…

UML DOES NOT COMPILE

UML DOES NOT CRASH

GOOD LUCK MODELLING SOFTWARE