The last two decades of the twentieth century proved to be the advent of the Unified Modeling Language. The UML can be narrated as “a language for specifying, visualizing and constructing the artifacts of software systems, as well as for business modeling.” (UML Document Set, 2001). On lighter note, the UML is a graphical means of depicting the design models with respect to specific environments.

via agilemodeling.com

via agilemodeling.com

Use Case Modeling is a subset of Unified Modeling Language. It can be narrated as a method whereby the requirements of the stakeholders can be incorporated into the system’s design.

The functional requirements of an existing or proposed system are described in detail via use case modeling techniques. The process modeling is done in the early stages of system development. User input can be altered at every stage of development in a use case that is developed as a result of the execution of the modeling technique.

The subsequent development stages are all based upon the use cases that are generated in the initiation. The components of a use case model are mainly actors and use cases.

An Actor is any external interaction with the system. It may be a person or an entity that exchanges data with the system. An actor may also be a user of the system though all users are not necessarily actors. A use case is a series of steps that gets initiated when an actor interacts with the system under consideration.

The goal that is achieved by use case modeling is the creation of a conceptual system regarding the observable behavior of the concerned system. This conceptual model is basically aimed at representing the real world scenario within the information system. The model also supports communication between the users and the developers of the system, enables better analytical understanding of the system and proves to be a point of initiation for the designers of the system. (Wand and Weber, 2002)