Editing Use case (section)

== Business use case ==
In the same way that a use case describes a series of events and interactions between a user (or other types of Actor) and a system, in order to produce a result of value (goal), a business use case describes the more general interaction between a business system and the users/actors of that system to produce business results of value. The primary difference is that the system considered in a business use case model may contain people in addition to technological systems. These "people in the system" are called business workers. In the example of a restaurant, a decision must be made whether to treat each person as an actor (thus outside the system) or a business worker (inside the system). If a waiter is considered an actor, as shown in the example below, then the restaurant system does not include the waiter, and the model exposes the interaction between the waiter and the restaurant. An alternative would be to consider the waiter as a part of the restaurant system (a business worker) while considering the client to be outside the system (an actor).<ref>{{Cite book|title=Business Modeling with UML|last=Eriksson|first=Hans-Erik|publisher=Wiley Computer Publishing|year=2000|isbn=0-471-29551-5|location=New York|pages=[https://archive.org/details/businessmodeling00erik/page/52 52]|url-access=registration|url=https://archive.org/details/businessmodeling00erik/page/52}}</ref>[[File: Use case restaurant model.svg|thumb|320px|center|A business [[Use case diagram]] depicts a model of several ''business use cases'' (goals) which represents the interactions between a restaurant (the business system) and its primary stakeholders (''business actors'' and ''business workers'').]]