Date: Fri, 29 Mar 2024 08:46:19 +0100 (CET) Message-ID: <1672766444.1664.1711698379932@nm-docs> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1663_1489183733.1711698379931" ------=_Part_1663_1489183733.1711698379931 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The purpose of a Use Case Diagram is to give a graphical overview of the= functionalities provided by a system in terms of actors, their goals (repr= esented as use cases), and any dependencies among those use cases.
A Use Case Diagram describes the usage of a system. The associations bet= ween actors and use cases represent the communications that occur between t= he actors and the subjects to accomplish the functionalities associated wit= h the use cases. The subject of a use case can be represented through a sys= tem boundary. The use cases enclosed in the system boundary represent the f= unctionalities performed by behaviors (activity diagrams, sequence diagrams= , and state machine diagrams).
Actors may interact either directly or indirectly with the system. They = are often specialized so as to represent a taxonomy of user types or extern= al systems. The only relationship allowed between actors in a use case diag= ram is generalization. This is useful in defining overlapping roles between= actors. Actors are connected to use cases through communication paths, eac= h represented by a relationship. There are four use case relationships:
Communication
A communication path represents an association between two Deployment Ta= rgets. It connects actors to use cases.
Include
An include relationship provides a mechanism for factoring out a common = functionality that is shared among multiple use cases and is always perform= ed as part of the base use case.
Extend
An extend relationship provides an optional functionality, which extends= the base use case at defined extension points under specified conditions.<= /p>
Generalization
A generalization relationship provides a mechanism to specify variants o= f the base use case.
Use cases are often organized into packages with the corresponding depen= dencies among the use cases included in the packages.