1 / 29

Introduction

Explore the principles of object-oriented design and how it relates to the Unified Modeling Language (UML) for system modeling. Understand the concepts of objects, classes, interfaces, and relationships between them. Learn about UML diagrams such as class diagrams, sequence diagrams, and state machines to describe system structures and behaviors.

blumenthal
Download Presentation

Introduction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Introduction • Object-oriented design. • Unified Modeling Language (UML).

  2. System modeling • Need languages to describe systems: • useful across several levels of abstraction; • understandable within and between organizations. • Block diagrams are a start, but don’t cover everything.

  3. Object-oriented design • Object-oriented (OO) design: A generalization of object-oriented programming. • Object = state + methods. • State provides each object with its own identity. • Methods provide an abstract interface to the object.

  4. Objects and classes • Class: object type. • Class defines the object’s state elements but state values may change over time. • Class defines the methods used to interact with all objects of that type. • Each object has its own state.

  5. OO design principles • Some objects will closely correspond to real-world objects. • Some objects may be useful only for description or implementation. • Objects provide interfaces to read/write state, hiding the object’s implementation from the rest of the system.

  6. UML • Developed by Booch et al. • Goals: • object-oriented; • visual; • useful at many levels of abstraction; • usable for all aspects of design.

  7. object name class name comment attributes UML object d1: Display pixels is a 2-D array pixels: array[] of pixels elements menu_items

  8. class name operations UML class Display pixels elements menu_items mouse_click() draw_box

  9. The class interface • The operations provide the abstract interface between the class’s implementation and other classes. • Operations may have arguments, return values. • An operation can examine and/or modify the object’s state.

  10. Choose your interface properly • If the interface is too small/specialized: • object is hard to use for even one application; • even harder to reuse. • If the interface is too large: • class becomes too cumbersome for designers to understand; • implementation may be too slow; • spec and implementation are probably buggy.

  11. Relationships between objects and classes • Association: objects communicate but one does not own the other. • Aggregation: a complex object is made of several smaller objects. • Composition: aggregation in which owner does not allow access to its components. • Generalization: define one class in terms of another.

  12. UML generalization Class derivation • May want to define one class in terms of another. • Derived class inherits attributes, operations of base class. Derived_class Base_class

  13. base class Class derivation example Display pixels elements menu_items pixel() set_pixel() mouse_click() draw_box derived class BW_display Color_map_display

  14. base classes derived class Multiple inheritance Speaker Display Multimedia_display

  15. Links and associations • Link: describes relationships between objects. • Association: describes relationship between classes.

  16. Link example • Link defines the contains relationship: message msg = msg1 length = 1102 message set count = 2 message msg = msg2 length = 2114

  17. # containing message sets # contained messages Association example message message set 0..* 1 msg: ADPCM_stream length : integer count : integer contains

  18. Stereotypes • Stereotype: recurring combination of elements in an object or class. • Example: • <<foo>>

  19. Behavioral description • Several ways to describe behavior: • internal view; • external view.

  20. transition state state name State machines a b

  21. Event-driven state machines • Behavioral descriptions are written as event-driven state machines. • Machine changes state when receiving an input. • An event may come from inside or outside of the system.

  22. Types of events • Signal: asynchronous event. • Call: synchronized communication. • Timer: activated by time.

  23. Signal event <<signal>> mouse_click a leftorright: button x, y: position mouse_click(x,y,button) b declaration event description

  24. Call event draw_box(10,5,3,2,blue) c d

  25. Timer event tm(time-value) e f

  26. start finish Example state machine input/output region = menu/ which_menu(i) mouse_click(x,y,button)/ find_region(region) call_menu(I) region found got menu item called menu item region = drawing/ find_object(objid) highlight(objid) object highlighted found object

  27. Sequence diagram • Shows sequence of operations over time. • Relates behaviors of multiple objects.

  28. Sequence diagram example m: Mouse d1: Display u: Menu mouse_click(x,y,button) which_menu(x,y,i) time call_menu(i)

  29. Summary • Object-oriented design helps us organize a design. • UML is a transportable system design language. • Provides structural and behavioral description primitives.

More Related