Previous:
What is UML?
- Use Cases describe the behaviour expected of a system from a user's perspective.
- Use Cases provide an ability to understand and model a system from a high-level business viewpoint.
- Functional description of how a business works or how the proposed system's processes should work.
- Graphical representation of types of users (actors) and how they will interact with the system
- Use cases represent the interfaces that a system makes visible to external entities and their interrelationships.
- Use cases are a set of scenarios that enable a common user goal.
- A complete set of use cases specifies all the different ways to use the system,and therefore defines all behaviour required of the system,bounding the scope of the system.
A Use Case Model is a diagram or set of diagrams which together with some additional documentation show what the proposed software system is designed to do. This is from the point of view of the people who will use or interact with the system. Use Cases are the functions that the system is intended to carry out and is a communication tool between users and developers.
Use Cases are the specific functions or services of a system. These Use Cases are visible to the Actors that interact with it. Use Cases are a logical unit of functionality provided by a system,which can be observed by the sequences of messages exchanged with the system and the Actors,together with the activities carried out by the system.
You can think of it as a model that describes the processes of a business - billing or order processing,for example,and their interactions with external parties such as customers and suppliers. It is very helpful in identifying some essential components of a system,i.e.:
- The business processes of the system
