1 / 9

Understanding Use Case Diagrams in Unified Modeling Language (UML)

This document provides an overview of Use Case Diagrams within the Unified Modeling Language (UML), highlighting the relationships between actors and use cases. It defines actors as entities that interact with the system and illustrates how use cases represent specific actions within that system. The diagram includes system boundaries and relationships, such as <<include>> and <<extend>>, which demonstrate how use cases can share functionality. By understanding these concepts, you can better model system interactions and functionalities.

milek
Télécharger la présentation

Understanding Use Case Diagrams in Unified Modeling Language (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. COP 4331 Recitation #1

  2. COP 4331 Recitation #1 • Kia Manoochehri • kiam@knights.ucf.edu

  3. Unified Modeling Language Use Case Diagrams

  4. Use Case Diagram • Describes the relationship between “actors” and use cases • An actor is something that interacts with the system Actors

  5. Use Case Diagram • A use case represents some action that takes place within the system Login

  6. Use Case Diagram • Additionally: • A large box denotes the system boundary • A line between an actor and use case denotes that the actor participates in the use case

  7. Use Case Diagram • <<include>> • A use case includes the functionality described in the previous one. • Represented by a directed arrow having a dotted shaft, labeled with <<include>> Check Fines Pay Fines <<include>>

  8. Use Case Diagram • <<extend>> • A use case may include the functionality described in another use case BorrowItem FindItem <<extend>>

More Related