This is a use case diagram example of a Online Library System.

This is a use case diagram example of a Online Library System

This is a use case diagram example of a Carpark System.

This is a use case diagram that illustrates the idea of how use cases can be broken down into epics and user stories.

We can use use-case approach as the mean to obtain user requirements. We can then break them down into to a set of manageable task, epics or user stories to be manage in the story map

This is a use case diagram example of Packages as Release Plan.

This is a use case diagram example of a Order Process System.

A generalisation relationship between Use Cases indicates that the child Use Cases inherit the properties of the parent Use Case.

In this use case diagram example, we would be indicating that there are some common steps for all Use Cases that handle customer transactions and that the child Use Cases “Return Faulty Goods” and “Take Customer Order” have additional steps that fit into or around them.

This use case diagram example depicts a model of several business use cases (goals) which represents the interactions between a restaurant (the business system) and its primary stakeholders (business actors and business workers). After the base use cases have been identified in the first cut, perhaps we could further structuring those use case with <<extend>> and <<include>> use cases in the second round touch up

UML defines three stereotypes of association between Use Cases:

1. <<include>> - The time to use the «include» relationship is after you have completed the first cut description of all your main Use Cases. You can now look at the Use Cases and identify common sequences of user-system interaction.
2. <<extend>> - An extending use case is, effectively, an alternate course of the base use case. The <<extend>> use case accomplishes this by conceptually inserting additional action sequences into the base use-case sequence.

Let's take a look at this use case diagram example.

This use case diagram example packages use cases according to the actors: Applicant and Insurer