1.UML Diagrams Jung Woo

2. What is UML? Standard language for specifying, visualizing,constructing, and documenting the artifacts of softwaresystems, business modeling and other non-softwaresystems. The UML represents a collection of best engineeringpractices that have proven successful in the modeling oflarge and complex systems. The UML is a very important part of developing objectoriented software and the software developmentprocess. The UML uses mostly graphical notations to express thedesign of software projects. Using the UML helps project teams communicate,explore potential designs, and validate the architecturaldesign of the software. 3. Overview of UML DiagramsBehavioralStructural: behavioral features of a system / businessprocess: element of spec. irrespective of time Activity State machine Class Use case Component Interaction Deployment Object Composite structure Interaction : emphasize object interaction PackageCommunication(collaberati on)SequenceInteraction overviewTiming 4. Class diagramUML class diagrams show the classes of the system, their inter-relationships, and the operations and attributes of the classes Explore domain concepts in the form of a domain model Analyze requirements in the form of aconceptual/analysis model Depict the detailed design of object-oriented or object-based software 5. Class diagram 6. Class diagram 7. Component diagramUML component diagrams shows the dependencies among software components, including the classifiers that specify them (for example implementation classes) and the artifacts that implement them; such as source code files, binary code files, executable files, scripts and tables. 8. Component diagram 9. Deployment diagramUML deployment diagram depicts a static view of the run-time configuration of hardware nodes and the software components that run on those nodes. Deployment diagrams show the hardware for your system, the software that is installed on that hardware, and the middleware used to connect the disparate machines to one another. 10. Deployment diagram 11. Deployment diagram 12. Object diagram UML 2 Object diagrams (instancediagrams), are useful for exploring realworld examples of objects and therelationships between them.It showsinstances instead of classes. They areuseful for explaining small pieces withcomplicated relationships, especiallyrecursive relationships. 13. Object diagram 14. Package diagram UML 2 Package diagrams simplifycomplex class diagrams, it can groupclasses into packages. A package is acollection of logically related UMLelements. Packages are depicted as filefolders and can be used on any of theUML diagrams. 15. Package diagram 16. Composite structure diagram UML 2 Composite structure diagramsused to explore run-time instances ofinterconnected instances collaboratingover communications links. It shows theinternal structure (including parts andconnectors) of a structured classifier orcollaboration. 17. Composite structure diagram 18. Activity diagram UML 2 Activity diagrams helps to describethe flow of control of the target system,such as the exploring complex businessrules and operations, describing the usecase also the business process. It isobject-oriented equivalent of flow chartsand data-flow diagrams (DFDs). 19. Activity diagram 20. Activity diagram 21. State machine diagram UML 2 State machine diagrams can showthe different states of an entity also howan entity responds to various events bychanging from one state to another. Thehistory of an entity can best be modeledby a finite state diagram. 22. State machine diagram 23. State machine diagram 24. Use cases diagramUML 2 Use cases diagrams describes the behavior of thetarget system from an external point of view. Use casesdescribe "the meat" of the actual requirements. Use cases. A use case describes a sequence ofactions that provide something of measurable value toan actor and is drawn as a horizontal ellipse. Actors. An actor is a person, organization, or externalsystem that plays a role in one or more interactions withyour system. Actors are drawn as stick figures. Associations. Associations between actors and usecases are indicated by solid lines. An association existswhenever an actor is involved with an interactiondescribed by a use case. 25. Use cases diagram 26. Use cases diagram 27. Use cases diagram 28. Communication diagram UML 2 Communication diagrams used tomodel the dynamic behavior of the usecase. When compare to SequenceDiagram, the Communication Diagram ismore focused on showing thecollaboration of objects rather than thetime sequence. 29. Communication diagram 30. Sequence diagram UML 2 Sequence diagrams models thecollaboration of objects based on a timesequence. It shows how the objectsinteract with others in a particular scenarioof a use case. 31. Sequence diagram 32. Timing diagram UML 2 Timing diagrams shows thebehavior of the objects in a given period oftime. Timing diagram is a special form of asequence diagram. The differencesbetween timing diagram and sequencediagram are the axes are reversed so thatthe time are increase from left to right andthe lifelines are shown in separatecompartments arranged vertically. 33. Timing diagram 34. Timing diagram 35. Interaction overview diagram UML 2 Interaction overview diagramsfocuses on the overview of the flow ofcontrol of the interactions. It is a variant ofthe Activity Diagram where the nodes arethe interactions or interaction occurrences.It describes the interactions wheremessages and lifelines are hidden. 36. Interaction overview diagram 37. Interaction overview diagram 38. UML diagram hierarchy 39. References http://www.agilemodeling.com/ http://www.visual-paradigm.com/VPGallery/diagrams/index.html http://bdn.borland.com/article/0,1410,31863,00.html http://en.wikipedia.org/wiki/Unified_Modeling_Language http://pigseye.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/index.htm