The figure below shows an ATM use case diagram example, which is quite a classic example to use in teaching use case diagram.The Document Management System (DMS) use case diagram example below shows the actors and use cases of the system.
After the base use cases have been identified in the first cut, perhaps we could further structuring those use case with A business use case is described in technology-free terminology which treats the business process as a black box and describes the business process that is used by its business actors, while an ordinary use case is normally described at the system functionality level and specifies the function or the service that the system provides for the user.
In other words, business use case represents how the work to be done manually in the currently situation and it is not necessarily done by the system or intend to be automated in the scope of target system.
An extending use case is, effectively, an alternate course of the base use case.
The use case accomplishes this by conceptually inserting additional action sequences into the base use-case sequence. It can not be instantiated, as it contains incomplete information.
Create a professional diagram for nearly any use case using our UML diagram tool.
In the Unified Modeling Language (UML), a use case diagram can summarize the details of your system's users (also known as actors) and their interactions with the system.Use cases are typically initiated by a user to fulfill goals describing the activities and variants involved in attaining the goal.The relationships between and among the actors and the use cases.The system boundary defines the system of interest in relation to the world around it.Note that: to make use case approach more "Agile", do not detail all use cases, but prioritize them in your product backlog, you should refine the use case in different level of details according to the development phase with just-in-time and just-enough manner.A use case is a useful technique for identifying, clarifying, and organizing system requirements.A use case is made up of a set of possible sequences of interactions between systems and users that defines the features to be implemented and the resolution of any errors that may be encountered.With attractive color schemes, text that’s easy to read and edit, and a wide-ranging UML shape library, you’re ready to go! Consider this example: A man with a chainsaw interacts with the environment around him.Depending on the situation and the context of the situation, he might fall into one of many different use cases. Is there anything ominous about the way he is wielding his chainsaw?While a use case itself might drill into a lot of detail (such as, flow of events and scenarios) about every possibility, a use-case diagram can help provide a higher-level view of the system, providing the simplified and graphical representation of what the system must actually do.A use case (or set of use cases) has these characteristics: Actors are usually individuals involved with the system defined according to their roles. A use case describes how actors uses a system to accomplish a particular goal.