Your SlideShare is downloading. ×
Itt1 sd uml and oo
Itt1 sd uml and oo
Itt1 sd uml and oo
Itt1 sd uml and oo
Itt1 sd uml and oo
Itt1 sd uml and oo
Itt1 sd uml and oo
Itt1 sd uml and oo
Itt1 sd uml and oo
Itt1 sd uml and oo
Itt1 sd uml and oo
Itt1 sd uml and oo
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

Itt1 sd uml and oo

172

Published on

Basic introduction to UML and object oriented thinking.

Basic introduction to UML and object oriented thinking.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
172
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
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 and OO System design 2010 Autumn Morten Bo Nielsen Mon@eal.dk
  • 2. UML and OO ● What is UML? ● Who defines it? ● What does “object oriented” mean? ● What is an object? ● What is a class? ● Why use objects?System design - Mon@eal.dk 2
  • 3. UML ● UML is all about modelling ● And communicating ideas ● Collection of diagrams ● Functional modelling: Use case diagrams ● Structural modelling: Class diagrams ● Behavioural modelling: State machine, sequence diagrams, communication diagrams. ● A lot more exists example projectSystem design - Mon@eal.dk 3
  • 4. Objects and clases ● start hereSystem design - Mon@eal.dk 4
  • 5. OOP words ● Class, Object, Instance, Method/Properties, (Message passing), Inheritance, Abstraction, Encapsulation, Decoupling, PolymorphismSystem design - Mon@eal.dk 5
  • 6. Why classes? ● Encapsulation ● Code reuse ● Use standardized patterns ● Abstraction ● Modularisation of the code Note that much of this is possible without OOPSystem design - Mon@eal.dk 6
  • 7. Software example - IP addresses Class Objects IpAddress* IpAddressOfPc1 = new IpAddress( 192.168.1.100, 255.255.255.0 ); IpAddress* IpAddressOfPc2 = new IpAddress( 192.168.1.101, 255.255.255.0 );System design - Mon@eal.dk 7
  • 8. Physical world - Books Class “Book” covers everything we would call a “book” Which to use depends on context Objects 1. Books as defined by ISBN 2. Books as in “every book is unique” My copy is different from yours8 SD3 - mon@sde.dk 25-10-2009 System design - Mon@eal.dk 8
  • 9. Inheritance design problem Book type is most Book content is most impor tant impor tant Book Book System Analysis and Design Paperback Hardcover with UML version 2.0 book book by A. Dennis et al. ISBN: 978-0-471- Paperback Hardcover 65920-4 book bookSystem design - Mon@eal.dk 9
  • 10. UML use case diagrams ● User ← admin actors example.System design - Mon@eal.dk 10
  • 11. Factory design patternSystem design - Mon@eal.dk 11
  • 12. Example project ● Mashing temperature control.pdf ● Mashing+temperature+control_prcent_2C+part+2.pSystem design - Mon@eal.dk 12

×