1 / 30

UML Representations

UML Representations. Components of the UML. Class Diagram Object Diagram Use Case Diagram State Diagram Sequence Diagram Activity Diagram Collaboration Diagram Component Diagram Deployment Diagram. The Use Case Diagram.

jackv
Download Presentation

UML Representations

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 Representations

  2. Components of the UML • Class Diagram • Object Diagram • Use Case Diagram • State Diagram • Sequence Diagram • Activity Diagram • Collaboration Diagram • Component Diagram • Deployment Diagram

  3. The Use Case Diagram • It contains use cases and actors, illustrating the relationships between the two sets. • These diagrams are usually the starting point of the analysis phase when designing a system. • Use cases show the overall structure and availability in a system to non-technical readers such as management and end users.

  4. A use case consists of: • A System that performs a function. A system has defined boundaries and can be broken down into sub-systems. Microsoft Visio use case diagram for a system is shown below.

  5. A use case consists of (contd.) • An Actor(s) is used to represent something that uses a system. An actor can be a person or another system. Microsoft Visio uses following diagram to represent an actor.

  6. A Use Case Consists of • Use cases which represent actions that a user takes on a system. Use cases are represented by an ellipse. Following diagram represents a use case diagram for a developer developing software.

  7. The Use Case Diagram Use Case (How to use the system And its behavior) Actors System (humans or external Systems)

  8. The Hierarchy of Actors in UseCase

  9. The Class and Object Diagrams • A class diagram is used to represent different classes, their relationship to each other, and which subsystem they belong to. • Object diagram shows instances of classes. • Class diagram is more generic and object diagram is more specific.

  10. Class and Object Diagrams Class Diagram Object Diagrams

  11. Activity Diagram • The activity diagram is used to analyze the behavior within more complex use cases and show their interaction with each other. Activity diagrams are used early in the system’s development process and are usually used to represent more complicated business activities.

  12. A Use Case and Activity Diagram

  13. An Activity Diagram with a Decision

  14. An Activity Diagram with a Fork and a Join for a parallel process

  15. The Sequence Diagram • The sequence diagram is used to show interaction between actors and objects and other objects. Messages are sent from actor to object, object to object and object to actor to show the flow of control through a system. Sequence diagrams are use to realize use cases by documenting how a use case is solved with the current design of the system.

  16. Sequence Diagrams Time

  17. The Sequence • The GUI notifies the operating system about the keystroke. • The operating system notifies the CPU. • The CPU sends a message to the monitor. • The monitor presents the alphanumeric character on screen, providing visual feed back to the user.

  18. The Connections in Sequence Diagrams Asynchronous Connection (The actor can Continue to work while action is taken by the System) Synchronous Connection (The actor has to wait for system approval) Simple Message (Transfers control from one object to another )

  19. Statechart diagrams • Statechart diagrams look similar to activity diagrams and are sometimes confusing. An activity diagram is used to model how different areas of work behave with each other and interact, a statechart diagram is used to represent a single object and how its behavior causes it to change state.

  20. The State Diagram • Class and Object diagrams model system statically. • State Diagram represent the dynamic behavior/flow of the system. • State diagrams are used between systems analysis and design phase.

  21. UML Symbols for State Diagram End Point Initial Starting Point

  22. The State Diagram (object is a PC)

  23. Collaboration Diagram • Collaboration diagrams are used to bring class diagrams to the next step. They represent the interaction and the relationships between the objects created in earlier steps of the domain modeling process. • Collaboration diagrams are often drawn between class and sequence diagrams.

  24. A Colloboration Diagram

  25. Component Diagrams • Component diagrams model software components and their relationships with each other. • A component is a single piece of software. It can be a file, product, executable, script or so on.

  26. A UML Component Diagram

  27. Deployment Diagrams • Deployment diagrams are used to model hardware as it relates to the deployment of the system that you are modeling in UML. • A deployment diagram has only two major pieces of its notation, the node and the communication association.

  28. A deployment diagram The diagram illustrates that a Web Server interacts with a ClientPC via an HTTP protocol, and the ClientPC communicates with a printer via a USB protocol.

  29. Component and Deployment Diagrams

  30. Credits/Further Reading • Some Information was taken and modified from UML: A Beginners Guide by Jason T. Roff, McGraw Hill.

More Related