| | 1 | = Application Design - Use Cases and Database Access Scenarios - SQL Views = |
| | 2 | |
| | 3 | == Actors == |
| | 4 | * **User** - The user is a person (or entity) who uses the application to make reservations and place orders. They can browse the offerings, conduct searches, and track their reservations and orders. |
| | 5 | Example: A user who wants to book a table at a restaurant or place an online food order. |
| | 6 | * **Manager** - The manager has extended permissions to administer the system. They can create/manage employee shifts, review reservations, generate reports, and make administrative decisions (such as adding new products, changing price lists, etc.). |
| | 7 | Example: A person in a managerial role responsible for organizing and overseeing daily operations. |
| | 8 | * **Employee** - The employee is part of the operational aspect of the system (e.g., waiter, cook, receptionist), and is responsible for carrying out user requests. They create bills, add ordered items to those bills, and ensure orders are properly fulfilled. |
| | 9 | Example: A waiter who receives an order from a user and updates the bill. |
| | 10 | |
| | 11 | == Most Important Use Cases == |
| | 12 | [wiki:ImportatntUseCase001 Employee clocks in]\\ |
| | 13 | [wiki:ImportatntUseCase002 Manager creates and assigns shift]\\ |
| | 14 | [wiki:ImportatntUseCase003 Employee manages order]\\ |
| | 15 | [wiki:ImportatntUseCase004 Employee transfers tab]\\ |
| | 16 | [wiki:ImportatntUseCase005 Customer makes order]\\ |
| | 17 | [wiki:ImportatntUseCase006 Customer makes reservation]\\ |
| | 18 | |
