Your SlideShare is downloading. ×
UML Class Diagrams are Awesome
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

UML Class Diagrams are Awesome

230

Published on

UML Class Diagrams are Awesome

UML Class Diagrams are Awesome

Published in: Software
1 Comment
2 Likes
Statistics
Notes
No Downloads
Views
Total Views
230
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
12
Comments
1
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 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

×