In a use case diagram, drag an Association connector shape onto the drawing page. Shows that one use case adds functionality to another.Įxample: To indicate a relationship between an actor and a use case Shows how a use case is broken into smaller steps. Indicates that a use case is a specific way to achieve goals of the general use case. Indicates that one use case has a dependency on another. Shows the relationship of an actor to a use case. Use connector shapes to indicate relationships between shapes in the diagram. To resize the subsystem, select the shape, and then drag a selection handle.ĭrag Use Case shapes from the UML Use Case stencil and place them inside the subsystem boundary, and then drag Actor shapes to the outside of the subsystem boundary. Click outside the shape on the drawing page. The subsystem can represent your entire system or a major component.ĭouble-click the Subsystem shape, and then type a new name for the for it, or press the Delete key to delete the existing name. If you still don’t see it, click the Expand the Shapes window button on the left.)ĭrag a Subsystem shape onto the drawing page. (If you don’t see the Shapes window, go to View > Task Panes and make sure that Shapes is selected. A UML Use Case stencil is open in the Shapes window. You should see the Shapes window next to the diagram. (A description of each one is shown on the right when you select it.) Then select either Metric Units or US Units. In the dialog box, select the blank template or one of the three starter diagrams.

This type of relationship reveals details about the system or application that are usually hidden in the use case.From the search results, select UML Use Case. In UML modeling, you can use an extend relationship to specify that one use case (extension) extends the behavior of another use case (base). A containment relationship supports the reuse of functionality in the use case model. In UML modeling, a Include relationship is a relationship in which one use case (base use case) contains the functionality of another use case (inclusion use case). Generalization relations are used in class diagrams, component diagrams, deployment diagrams, and use case diagrams to indicate that the child element accepts all the attributes, operations, and relationships defined in the parent element.

It indicates that an actor can use the functionality of the business system.Ī generalization relation is a relationship in which one model element (child) is based on another model element (parent). An association is a relationship between an actor and a business use case. For example, the relationship between an actor and a use case illustrates that the actor can use certain functionality of the business system.Īn association is a relationship between two classifiers, such as an actor and use cases, that describes the cause of the relationship and the rules that govern it. Use case diagrams show use cases, actors, and the relationships between them. By reusing existing use cases using different types of relationships, the overall effort required to develop the system is reduced. The relationship between two use cases basically models the dependencies between two use cases. Use cases are also connected to each other in different kinds of relationships.

In UML, relationships are connections between model elements.

Extend in use case diagrams