Learn how to make Use Case Diagrams in this tutorial. Both beginners and intermediate UML diagrammers will find all the necessary training and examples on systems, actors, use cases, and include and extend relationships.
UML Use Case Diagrams show a system or application; then they show the people, organizations, or other systems that interact with it; and finally, they show a basic flow of what the system or application does.
This tutorial explains the four main characteristics of Use Case Diagrams: systems, actors, use cases, and relationships.
A system is whatever you’re developing. It could be a website, a software component, a business process, an app, or any number of other things. You represent a system with a rectangle.
The next aspect of Use Case Diagrams are actors. An actor is going to be someone or something that uses our system to achieve a goal, and they're represented by a stick figure.
Use Cases are elements that really start to describe what the system does. They're depicted with an oval shape and they represent an action that accomplishes some sort of task within the system.
The final element in Use Case Diagrams are relationships, which show how actors and use cases interact with each other. There are different types of relationships (like association, include, extend, and generalization) that are represented by varying types of lines and arrows.
Learn more and sign up: