A Use Case Diagram is a UML modeling tool that specifically represents the main users of a design

system and the related services that each user interacts with that system design. It is advantageous to
utilize this type of model when you have a system with multiple elements with unique capacities which
must all synchronize. For example, a Use Case Diagram can be helpful in depicting all the actors and
their related services when designing a new restaurant system. Below Figure 1.0 is a Use Case for a new
restaurant, with the box representing the restaurant design. The main actors that are depicted in the
new restaurant design include the Servers; the Cooks/Chefs; the Bus-people; the Patrons; and the
Management. The Servers have multiple Services/Uses encompassing taking orders; listing specials;
inputting orders in the computerized POS (Point of Sale) system; delivering the ordered food; and finally
taking payment. The Cooks/Chefs’ main service of use is of course preparing the ordered food that was
inputted into the POS system; but they also have important services that include keeping all supplies
stocked and ordered. The Bus-people clean off and set new table; restock incoming supplies; and wash
dishes. The Patrons of course order their food, and decide to either dine-in or dine-out. Lastly the
Management oversees all the scheduling; oversees the menu and ordering supplies; and most
importantly deals with customer service issues. It is clear that all of the Actors’ Services directly interact
with one another in order to successfully give the Patron a gratifying dining experience. The Patrons rely
on the Servers doing their tasks as well as the Bus-people, and the Chefs. The Servers rely on the
Patrons’ patronage as well as rely directly on the Chefs and Bus-people. The Chefs rely on the Servers’
orders from the POS system; as well as the Bus-people to restock. Chefs are directly related to the
Patron as the prepared order is ultimately produced for them. Of course, the Manager is directly related
to all Actors as they oversee everything. By visually being able to see all the Actors and Services/Uses
displayed, it is helpful to see how each of the Actors are related to each other's tasks. This helps when
delegating tasks and envisioning the number of Actors needed per task, in order for the restaurant to
work like a symphony.
 Figure 1.0 Use Case Diagram for Restaurant

A Sequence Diagram depicts the chronological order of the action-reaction responses. This can be
helpful in designing a restaurant because a sequence diagram allows one to conceptualize how the
model will interact with the users in a time-frame. Figure 2.0 below represents the Sequence Diagram
for the chain of command that occurs when a Patron places an order for food in the new restaurant.
First the Patron places the order directly with the Server. Next, the Server inputs the order into the POS
system, which in turn notifies the Chef that an order has been placed, who then prepares the order.
When the order is ready, the Chef places it at the pick-up station, where the Server will retrieve and
deliver it to the Patron’s table.
 Figure 2.0 Sequence Diagram for Placing a Food Order

An Activity Diagram is a flowchart depicting the behavior and decisions that are made by a system,
from beginning to end of a process. This can be helpful when designing all the possible decisions that
come into play when making a final determination. Figure 3.0 below shows an Activity Diagram that was
helpful in representing all the decisions involved when one is contemplating what to eat. The first
decision that one would make is whether to eat alone or to entertain company. Afterwards, one will
decide whether they want to have an expensive or cheap dining experience. Next, one will decide on
what type of food purveyor they will patronize, either a restaurant or a grocery store. Finally, if they
decide on a grocery store, they have the option of buying food to cook or buying already prepared food.
On the other hand, if one decides on a restaurant, they must decide whether to dine-in or take-out.
 Figure 3.0 Activity Diagram Showing Dining Decisions

Now that I have experience with UML modeling, I see the benefit of these tools by giving multiple
perspectives. When conceptualizing any design, it is advantageous to be able to break down the users
and services; the chronological order; and the decision-making process. UML modeling can be helpful in
decision making processes both on a personal level as well as in engineering work. Personally, I can use
UML modeling in my interior design and furniture building endeavors by being able to ascertain time-
lines as well as decision making outcomes. In my engineering work at the fabrication shop UML
modeling can also help by ascertaining all actors involved; utilizing chronology sequences; and being
able to visually share decision making processes. It is important for engineers to model the interactions
with users before beginning a design because much insight will be gained involving the specific uses;
user contact with other users; potential abuse or misuse; time-lines; and key decision-making processes.