UML Class Diagrams are Awesome

1. UML CLASS DIAGRAMS
ARE AWESOME

2. THEY’RE SIMPLE
AND EASY TO MAKE

3. ALL YOU NEED ARE
RECTANGLES AND ARROWS

4. UP TO 3 RECTANGLES
CAN REPRESENT A CLASS

5. PUT YOUR CLASS NAME
IN THE FIRST RECTANGLE
MyClass

6. YOUR VARIABLES
IN THE SECOND RECTANGLE
MyClass
myVariable: String

7. AND YOUR METHODS
IN THE THIRD RECTANGLE
MyClass
myMethod(): String
myVariable: String

8. YOU CAN ASSOCIATE
A CLASS TO ANOTHER
WITH A DASHED OPEN ARROW
MyClass
myVariable: MyOtherClass
myMethod(): String
MyOtherClass
myVariable: String
anotherMethod()
<< uses >>

9. YOU CAN
INHERIT
FROM A CLASS
WITH A CLOSED
ARROW
MyChild
myVariable: String
myMethod()
MyParent
myMethod()

10. DO YOU
REALLY NEED
TO INHERIT
FROM A CLASS?

11. !
REALLY?

12. CAN’T YOU JUST USE AN
ASSOCIATION INSTEAD?

13. ALWAYS FAVOR
ASSOCIATION
OVER
INHERITANCE

14. BUT WHEN YOU DO USE
INHERITANCE, REMEMBER…

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

16. DON’T USE POLYMORPHISM
TO CHANGE STRUCTURE!
USE IT TO CHANGE BEHAVIOR

17. WITH GREAT POWER
COMES GREAT
RESPONSIBILITIES

18. GREAT UML
CLASS DIAGRAMS …

19. ARE SHORT

20. THEY COMMUNICATE
A SINGLE
AND IMPORTANT
CONCEPT

21. THEY ARE NOT DETAILED
PROGRAMMING
INSTRUCTIONS

22. WORRY ABOUT
COMMUNICATION
LET THE PROGRAMMER
FILL IN THE DETAILS

23. ALWAYS INCLUDE A LITTLE TEXT
EXPLAINING WHAT YOU WANT
TO COMMUNICATE

24. AND ALWAYS KEEP IN MIND…

25. UML DOES NOT COMPILE

26. UML DOES NOT CRASH

27. GOOD LUCK
MODELLING SOFTWARE