Use Case 3 Update orders - Tonnius/Tiim14-50 GitHub Wiki

Title

Update orders

Functional requirement

allow head waiters to keep track of all orders and to edit them

Precondition

Database of orders is not empty; The system has a subsystem where to view and edit order information;

Primary Actor

Head waiter

Main Success Scenario

Head waiter accesses the corresponding subsystem where to see information about already existing orders; User modifies the information in necessary fields or removes necessary products from the order and chooses the option to save the updated information into the order database.

Extensions

  1. User makes invalid modifications and inserts invalid information: The system shows a notification and shows what information is invalid; The system gives a chance to modify the invalid information.

  2. Connection/insertion to the necessary database fails: The system shows a notification and asks the user to try again later.