For the following use cases develop the artifacts using UML notations

1. UML domain model for the Sub-System (must add attributes and relationships with cardinalities)? (5 marks)
2. UML system sequence diagram (SSD) for each of the use case? (5 marks)

Use case: Order a Single Meal

Normal Flow of events:

1. Patron asks to view menu for a specified date.
2. System displays menu of available food items and the daily special.
3. Patron selects one or more food items from menu.
4. Patron indicates that meal order is complete.
5. System displays ordered menu items, individual prices, and total price, including any taxes and delivery charge.
6. Patron confirms meal order or requests to modify meal order (back to step 3).
7. System displays available delivery times for the delivery date.
8. Patron selects a delivery time and specifies the delivery location.
9. Patron specifies payment method.
10. System confirms acceptance of the order.
11. System sends Patron an e-mail confirming order details, price, and delivery instructions.
12. System stores order in database, sends e-mail to notify Cafeteria Staff, sends food item information to Cafeteria Inventory System, and updates available delivery times.

Alternative Flows:

1.1 Order multiple meals (branch after step 4)

1. Patron asks to order another meal.
2. Return to step

1.2 Order multiple identical meals (after step 3)

1. Patron requests a specified number of identical meals.
2. Return to step 4.

1.3. Order the daily special (after step 2)

1. Patron orders the daily special from the menu.

Return to step 5.

Use case: Register for Payroll Deduction

Normal Flow of events:

1. Patron requests to register for payroll deduction.
2. System invokes Authenticate Users Identity use case.
3. System asks Payroll System if Patron is eligible to register for payroll deduction.
4. Payroll System confirms that Patron is eligible.
5. System informs Patron that he is eligible for payroll deduction.
6. System asks Patron to confirm his desire to register for payroll deduction.
7. Patron confirms desire to register for payroll deduction.
8. System asks Payroll System to establish payroll deduction for Patron.
9. Payroll System confirms that payroll deduction is established.

System informs Patron that payroll deduction is established and provides confirmation number of the registration transaction.

Alternative flows:

E.1 Patron identity authentication fails (at step 2)

1. System gives user two more opportunities for correct identity authentication.

2a. If authentication is successful, Patron proceeds with use case.

2b. If authentication fails after three tries, System notifies Patron, logs invalid authentication attempt, and terminates use case.

5.0.E.2 Patron is not eligible for payroll deduction (at step 4)

1. System informs Patron that he is not eligible for payroll deduction and gives the reason why.

2. System terminates use case.

5.0.E.3 Patron is already enrolled for payroll deduction (at step 4)

1. System informs Patron that he is already registered for payroll deduction.

2. System terminates use case.