1 / 7

UML - Mechanisms for System Boundaries

Explore purchase items in a retail sales system. Covers use case beginning and end scenarios along with system variations. Includes dependencies, interfaces, and diagram notations.

adamevans
Download Presentation

UML - Mechanisms for System Boundaries

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 - Mechanisms for System Boundaries by Brian Lawler Brian.Lawler@JHU.edu

  2. Use Case Narratives Retail Sales System Purchase Items Use Case Begins: This use case begins when…. Ends: This use case ends when… Base Case: Variations: <<System>>Retail Sales System Purchase Items Customer Brian.Lawler@JHU.edu

  3. Dependencies Across Packages net.brianlawler.demos.applets Scope resolution may use the UML syntax “ :: “ or implementation (e.g. Java) syntax “ . “. Brian.Lawler@JHU.edu

  4. Interfaces Between Sub-Systems/Components Brian.Lawler@JHU.edu

  5. “Swim Lanes “ on Activity Diagrams Brian.Lawler@JHU.edu

  6. Top and Bottom of Sequence Diagram Begin End Brian.Lawler@JHU.edu

  7. Start and Stop on State Diagram Start Hired Fired Un-Employed Employed Hired Retired Stop Brian.Lawler@JHU.edu

More Related