Using the project that you have been assigned for $($U$-$University Restaurant, U$-$University Library, Voting application$),$ please do the following:

$1.$ Determine all the use cases of your projects.

$2.$ Determine the top $5$ of your use cases that are most complex and explain why.

$3.$ Describe in detail using the template table given in class each of the top $5$ complex use cases. Please notice that questions $3$ and $4$ are bound, you must pick the most complex use cases.

$4.$ Each described use case must mention the solved functional requirements.

$5.$ Build the full use case diagram with all use cases you discovered.

$6.$ For each complex use case, determine the corresponding class diagram.

Here is the project you will use:

### Project $1$: Build a U$-$University Restaurant database

U$-$University$$s Housing and Auxiliary Services want to build a database to collect useful information that may help improve their services. To achieve this, they requested having a database design team to fulfill this objective. Your team has been allocated the project, and your first task was to collect U$-$University Restaurant business processes.

$1.*$Restaurant Concurrency$*$

Restaurant selection is done every two years. The last selection took place in August $2014,$ and based on restaurant submissions that were made, U$-$University selected one restaurant named $$Toujours Meilleur.$$ To automatically renew the contract of a current restaurant service supplier, the restaurateur must get students' satisfaction of at least $80\%.$

$2.*$Menu Item and Price Policy$*$

U$-$University$$s Housing and Auxiliary Services request that the selected restaurateur apply the same price to all menu items that are part of a daily menu. The price for a menu is $2000$ FCFA. A menu consists of three items: an entry, a main plate, and a dessert. During a week, the restaurateur must ensure that a menu item is presented no more than twice, and daily, the same menu item can be presented only once. A menu item must have a unique code, name, description, creation date, and expiration date.

$3.*$Ticket Purchase$*$

Students, administrative personnel, or academic personnel may purchase tickets individually or buy a pack of $10$ tickets. A visitor can purchase only one ticket at a time. When someone buys a ticket, the database must register the person's name $($first and last$)$ who bought the ticket. As the restaurant serves U$-$University students and personnel, only people in that category are allowed to buy tickets. A ticket has a code number, a logo image, and a last validity date.

$4.*$Buying a Menu Item$*$

Students, administrative personnel, or academic personnel must give the restaurant agent a ticket to get a menu item. The restaurant checks the logo image and the validity date, then saves in the buying menu item entity the ticket code number, the daily service sequence code, the service date, the selected menu item code, and the student, personnel, or visitor code. The daily service sequence must record the following fields: code, daily sequence name $($e$.$g$.,$ morning, noon, or evening$).$

$5.*$Service Appreciation$*$

Students, administrative personnel, or academic personnel are allowed to provide daily or weekly feedback about the restaurant services they received, respectively, during the day or the current week. The service appreciation must contain the service appreciation code, the date of the appreciation, appreciation frequency $($daily$/$weekly$),$ appreciation content, appreciation percentage, and improvement suggestions.