1 / 9

UML Diagrams Overview

UML Diagrams Overview. by Brian Lawler Brian.Lawler@JHU.edu. System Model. Process Model. Logical Model. Use Case Model. Deployment Model. Physical Model. Diagrams Are Views to a Model. Sequence Diagrams. Collaboration Diagrams. Use Case Diagrams. Activity Diagrams.

buswell
Download Presentation

UML Diagrams Overview

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 Diagrams Overview by Brian Lawler Brian.Lawler@JHU.edu

  2. System Model Process Model Logical Model Use CaseModel Deployment Model Physical Model Diagrams Are Views to a Model Sequence Diagrams Collaboration Diagrams Use Case Diagrams Activity Diagrams ObjectDiagrams State Diagrams Class Diagrams DeploymentDiagrams ComponentDiagrams Brian.Lawler@JHU.edu

  3. Establishes the system boundary Identifies the users of the system Identifies interfaces and dependencies on external systems Summarizes the high-level functional requirements Summarizes the external interfaces Essential to release planning Used by everyone <<extend>> Executive Executive Education Enroll in Courses Student <<include>> Employer Verify University Participation <<include>> Parent Assign Instructors Professor Registrar Scheduling System Use Case Diagram Brian.Lawler@JHU.edu

  4. Drives the construction process. Defines what will be built. Used at many levels of abstraction. With modern tools and languages (C++, Java, C#, XML, SQL, etc.) code can be generated from this diagram. Usually, in the end, the class diagram wins. The other diagrams capture what you wanted but the class diagram describes what you got. Class Diagram Brian.Lawler@JHU.edu

  5. Similar to flow charts Can be used at a high-level, associated with use cases, and including “swim lanes”. Can also be used at a low level – typically to detail an operation. Activity Diagrams Brian.Lawler@JHU.edu

  6. Convey a scenario or sequence of events. Used at a high-level - associated with a possible scenario for a use of the system. Used at a low level – associated a collaboration of system components or a low-level operation. Sequence Diagram Brian.Lawler@JHU.edu

  7. Provides the scenarios for a single class Shows many, perhaps all, the scenarios in a single diagram In high-end tools, can be used to generate code Widely used or required for high-value systems State Diagram Hired Fired Un-Employed Employed Hired Retired State Diagram for the PersonInfo classof a corporate HR system. Brian.Lawler@JHU.edu

  8. Seen in several formats Good for capturing examples to drive the system design Good for describing the system state at a point of time Object Diagrams Brian.Lawler@JHU.edu

  9. Only 3D diagram Shows physical model of system(s) Software components get allocated to nodes or processors Deployment Diagrams Brian.Lawler@JHU.edu

More Related