Skip to content

Casi d'uso

GaiaVezzolo edited this page May 1, 2021 · 40 revisions

UC1: Gestione dell’ordinazione al tavolo

Scope: management software application af a restaurant
Level: user goal
Primary Actor: Waiter, Chef
Stakeholders and Interests:

  • Waiter: wants to easily communicate the orders of tables to the kitchen.
  • Chef: wants to receive the list of orders and communicate to the waiter when dishes are ready.
  • Cashier: wants to close every bill correctly.
  • Table: wants to receive the ordered dishes.
  • Chief: wants to keep track of every bill clearly.
  • Revenue Agency: wants to receive notification of every paid bill to provide for a correct taxation.

Main Success Scenario:

  1. The full table asks for a waiter and waits his arrival to order.
  2. Upon arrival of the waiter the table communicates the dishes.
  3. The waiter communicates the command to the chef through the interaction with software.
  4. The chef prepares the ordered dishes.
  5. After the command has been completely realized the chef informs the waiter through the software.
  6. The waiter receives the notify and takes the dishes from the kitchen.
  7. The waiter delivers the dishes to the table and notifies the update to the software.
  8. When the members of the table have finished to consume the first ordered dishes the waiter is recalled and the table can choose between two possibilities:
    1. If at least a member of the table decides to order again there is a repetition of steps 2 – 8.
    2. If no member wants to make a new order the waiter closes the order and it is possible to move to step 9.
  9. The table goes to the cashier’s desk and communicates the id to the cashier.
  10. The cashier gains access to the table’s bill and gives a pre-bill.
  11. The table pays the bill.
  12. The bill is closed and the amount is communicated to the Revenue Agency; the tax receipt is printed.

Extensions / Alternative Flows:

  1. The chef is not able to cook a dish.
    1. The chef interacts with the software and notifies the problem to the waiter.
    2. The waiter communicates the problem to the table.
    3. The table makes a new order.
  2. The table wants to modify the order.
    1. The table asks for the waiter to communicate the change.
    2. The waiter interacts with the software and notifies the request to the chef.
    3. The chef verifies the state of the modified order and commnicates it to the waiter.
    4. If the dish is not in preparation the waiter confirms to the table the change made, otherwise he gives the possibility to choose whether to maintain the original order or modify it by maintainig the additional charges.
    5. The waiter updates the command according to what the table has chosen.
  3. The table wants to leave before the end of the service.
    1. The table communicates its decision to the waiter.
      1. If the table has already ordered something the waiter verifies its states. The potential orders in preparation are charged on the preexisting order.
      2. If the table has not made any order the bill is closed with no additional charges.
  4. The table can’t pay the bill or the method of payment is rejected.
    1. The cashier gives the opportunity to change the method of payment.
      1. If the payment succeeds the extension is concluded.
      2. If the payment is rejected again step 1 is repeated.
      3. If the table refuses to find a solution step 2 is made.
    2. The cashier checks if the customers have debts.
      1. If the customers have no debts the bill is charged.
      2. It the customers have debts they are expelled from the restaurant.

UC2: Gestione delle prenotazioni
Portata: Applicazione gestionale di un ristorante
Livello: Obiettivo utente
Attore primario: Cassiere
Stakeholders e interessi:

  • Cassiere: Vuole chiudere correttamente ciascun conto.
  • Capo: Vuole massimizzare i profitti dato il numero di coperti.
  • Clienti: Vogliono prenotare un tavolo adatto al gruppo di cui fanno parte.

Un cliente contatta il locale per prenotare il tavolo. Il cassiere accede al software e verifica la disponibilità del locale in base all’orario scelto e alla tipologia di tavolo da riservare, infine comunica l’esito al cliente.

UC3: Gestione dell’accesso al locale
I clienti si recano alla cassa. Il cassiere verifica l’eventuale prenotazione. Se questa è presente i clienti sono accompagnati al tavolo, altrimenti il cassiere verifica la disponibilità in base ai tavoli momentaneamente liberi e alle prenotazioni precedentemente accordate. Il cassiere comunica ai clienti l’esito della ricerca.

Clone this wiki locally