1 / 19

UML

UML. http://bdn.borland.com/article/0,1410,31863,00.html Also see http://www-106.ibm.com/developerworks/rational/library/content/03July/2000/2256/2256_PWN.pdf http://pigseye.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/index.htm http://www.omg.org/gettingstarted/what_is_uml.htm. Structural

zeheb
Download Presentation

UML

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. UML http://bdn.borland.com/article/0,1410,31863,00.html Also see http://www-106.ibm.com/developerworks/rational/library/content/03July/2000/2256/2256_PWN.pdf http://pigseye.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/index.htm http://www.omg.org/gettingstarted/what_is_uml.htm

  2. Structural Class Object Component & Deployment Behavioral Use case Sequence Activity Collaboration Statechart Model Management Packages Subsystems Models Nine Kinds of Diagrams

  3. Use Case

  4. Lift Truck Driver Use Case Enter load data Get destination WMS Driver Confirm Putaway “user” could be broadly interpreted to include computer systems

  5. Class Diagram

  6. (Partial) Warehouse Classes 1 0.. 0.. 1 1 1 Location Unit Load SKU InvRecord LocationID UnitID SkuID Name SkuID SkuID QtyOH Note: it may be easier to define the classes in parallel with defining the activities! Receiving Storage IsEmpty Content

  7. Packages

  8. Warehouse Packages Receiving OrderEntry Putaway OrderPick Packages may be primarily an implementation issue Ship

  9. Objects

  10. Activity

  11. Put-Away Activity WMS Terminal Driver Scan Load Select Location Transmit Load ID Pick Up Load Send Dispatch Display Location Travel to Location Display Confirmation Scan Location Confirm Send Confirmation Update Inventory Return

  12. Sequence

  13. Driver Terminal WMS InvRecord Scan location Display confirmation window Confirm Putaway Send confirm putaway Send inventory change

  14. Collaboration

  15. State Chart

  16. Driver State Chart Move to p/d station “state” here is quite different from, say, a petri net or finite state automata model—here “state” indicates what some entity is doing; the arcs primarily are “signs” to indicate the transition from one kind of activity to another So it’s important to identify all the “active” entities, all their “states” (activities) and what causes or indicates their transition between activities Returning Loading Receive location dispatch Confirm Putaway Unloading Traveling Scan destination location

  17. Component & Deployment

  18. Some Observations • UML does give us • Structure: classes and objects • Behavior: use cases, activity, sequence, state chart • The rest is largely implementation oriented • UML does NOT give us the precise methods for making decisions, or even the precise ways for performing a physical activity

  19. Questions • Are there good (free) tools for developing the use cases, class, object, activity, and state charts? • Should these be part of the IE/OR toolkit?

More Related