Use the Style tab to change the connector’s Pattern. Solid connectors from the actors (or to the actors) represents them performing that task.ĭotted or dashed connectors between tasks can show a relationship. These shapes are available in the General shape library in draw.io. Tasks or actions are represented by an oval with a verb phrase describing the task as a label.ĭata stores are typically represented by the database shape. These are typically represented by stick figures, or another shape that may better represent an external system. UML use case shapesĮxternal actors are users (or external processes) that interact with your system. UML use case diagrams are not used for scheduling or broad planning purposes as they are highly technical and specific, but instead function as the foundation for a system’s technical documentation.Įach goal or task that a user wants to achieve with your system or program is a separate use case diagram. These diagrams are used to establish your system requirements, whether that be a software system or an interaction with another person or team.Ĭustomer updates their account - open this use case diagram in our diagram viewer There are several ways you can customize your chart: add a color scheme, change the font, or add notes.UML use case diagrams show all of the ways an end-user interacts with your systems, with all of its pre- and post-conditions, exceptions and alternate paths. Now you should have a simple use case diagram. Drag lines from the actors to the use cases by pulling out a line from the red dots that appear when you hover over the shape. For instance, if your check-in app does not support taking photos, but it's on the agenda for a future release, put it outside the system.

Place each use case in the system that supports it, and draw use cases not supported by your system outside the box. Start with major activities or transactions, leaving sub-activities for later. Possible use cases would be checking in, searching for a nearby venue, and finding friends. For example, if you're developing a check-in mobile application, the system would be the app, and the actor would be the user. These ovals represent the activities that actors will perform with the help of your system. Now it's time to drag use cases onto your system. Rename your actors to reflect their role. Actors are represented by stick figures, a fitting symbol since actors are often people. Your use case diagram should reflect the actor's perspective, so ask yourself what the end user wants from the system. In a development use case, systems represent what you are developing, such as a software component or a complete suite. In Lucidchart, this shape is labeled as a rectangle container. Begin by dragging a system boundary box onto your canvas.

Draw use case diagrams online free