Basically, an actor can interact multiple times with a use case or system at a particular instance of time.įollowing are some rules that must be followed while drawing a use case diagram: It identifies the no of times an actor communicates with the system. Once both the actors and use cases are enlisted, the relation between the actor and use case/ system is inspected. It may be a system or a private entity, such that it requires an entity to be pertinent to the functionalities of the system to which it is going to interact. The actors are the person or a thing that invokes the functionality of a system. And once every single functionality is identified, they are then transformed into the use cases to be used in the use case diagram.Īfter that, we will enlist the actors that will interact with the system. It is essential to analyze the whole system before starting with drawing a use case diagram, and then the system's functionalities are found.
It represents how an entity from the external environment can interact with a part of the system.įollowing are the purposes of a use case diagram given below:
It invokes persons, use cases, and several things that invoke the actors and elements accountable for the implementation of use case diagrams. It accumulates the system's requirement, which includes both internal as well as external influences. The main purpose of a use case diagram is to portray the dynamic aspect of a system. It depicts the high-level functionality of a system and also tells how the user handles a system. It models the tasks, services, and functions required by a system/subsystem of an application. It encapsulates the system's functionality by incorporating use cases, actors, and their relationships. A use case diagram is used to represent the dynamic behavior of a system.
0 kommentar(er)
