It is Exam. Attached are sample exam question and answer. The exam will be the same format, with different case question. I am not allowed the exam before the exam date. I can send the question right after I start the exam. It is April 26 at 11am in EST.
CS360 Spring 2021 Prof. Heikki Topi In-class exercise on use case modeling Days 15 and 16 Model answer 1. Casual Use Case Dining service customer who is registered with the dining service and has either access to a web- based application or the service’s mobile app indicates his/her interest in placing a food order at the cafeteria by selecting this choice in the desired application environment. The system presents to the user the meal category options at the cafeteria. The customer selects one of the options, after which the system shows the user the available meal element options and asks the user to select the desired meal elements from that station. The customer makes the selection and confirms it to the system. The system asks whether or not the customer wants to add food items from other stations to the order. If the answer is affirmative, the system will move back to the station selection, keeping the prior choices in the shopping cart. Once the order is completed, the system asks the user to select a payment option, including credit card, university dining service card, and cash (at pickup). The user selects the payment option and receives the estimated pick-up time from the system. 2. Fully Dressed Use Case Use Case: Place Food Order Scope: Food Service System Level: User Goal Primary Actor: Dining service customer Stakeholders and interests: Dining service customer is interested in a convenient, efficient, and accurate way to place a food order allowing a quick pick-up. Dining service management is interested in using the cafeteria workforce more efficiently, particularly at the peak times. University is interested in offering its customers the smoothest possible dining experience. Pre-conditions: The customer is registered with the dining service and has access to either a mobile app or a web-based application. Minimal guarantee: The customer’s account is not charged without corresponding food delivery request in the system. A failed transaction should not lead to any chances in the system of interest. Success guarantee: The customer places an order, which is captured in the system with a high level of accuracy and leads to a correct meal delivery. Trigger: User expresses his/her intent to place a food order. Main Success Scenario 1. User launches the dining service app either on the web or on a mobile device. 2. The system presents the available food categories to the user. 3. User selects a food category. 4. The system presents to the users the meal options available for that food category. 5. User selects the desired meal options. 6. The system presents the selected meal options to the user for verification. 7. User verifies the selected meal options. 8. The system asks whether or not the user wants to add options from another food category. If the answer is affirmative, the use case continues from step 2. Steps 2 to 8 are repeated until the user has chosen all desired meal components. 9. The system presents the total order to the user for approval with a pick-up time estimate. 10. User approves the order. 11. The system asks the user to select from available payment options. 12. User enters payment details. 13. The system asks the user to confirm the payment details. 14. User confirms the payment details. 15. The system confirms the completion of the order and gives the user a confirmation number. Extensions 3a. The user does not find any food categories of interest. 3a1. The user selects the option to cancel the order process. 3a2. The use case ends. 7a. The user does not want to verify the selected meal options. 7a1. The system asks the user to modify the food order related to the current category. 7a2. The process returns back to Step 5 of the main success scenario. 10a. The user does not accept the order because of an unacceptable pick-up time. 10a1. The system presents a revised pick-up time. 10a1a. The system indicates that an earlier pick-up time is not possible. 10a1a1. The system cancels the order. 10a1a2. The use case ends. 10a2. The process returns back to Step 9 of the main success scenario. 13a. Payment is rejected by the payment processor. 13a1. The system asks the user to provide new payment details. 13a2. The process returns to Step 11 of the main success scenario. 14a. The user rejects the payment details 14a1. The system returns back to Step 11 of the main success scenario. CS360 Spring 2021 Prof. Heikki Topi In-class exercise on use case modeling Class meetings 15 and 16 1. Casual Use Case Please develop a casual system use case at the user goal level based on the following description. Many details are intentionally missing; please make the necessary assumptions. A university dining service cafeteria located on a busy university campus would like to develop its service further and help those diners who want to place their food orders using a web-based or mobile application so that the diners do not have wait for the preparation of their food in line. Dining service customers will use the application themselves. It applies to four of the stations at the cafeteria: grilled foods, sandwiches, salads, and sushi. The intent is that once a customer has placed the order, s/he can pick up their meal at a specified time from the cafeteria without any delays. The dining service would also like to improve their customer service with the system, making the customer’s experience as good as possible. Thus, think about various details of the food service process that could be improved with the application. 2. Fully Dressed Use Case Expand the use case from Question 1 into a fully dressed use case including at least four extensions. 3. Use Case Diagram There are, of course, many other goals that the university dining service system could support. The system could allow various aspects of managing a university- specific payment system, managing customer preferences, providing feedback to the employees and management, advertising special deals particularly for frequent customers, providing nutritional information, etc. Feel free to be innovative and add other functionality that you think could improve such a system. Please draw a use case diagram that present the system use cases at the user goal level in the system level context. Identify possible
> and > relationships between the use cases. 1. Casual Use Case 2. 2. Fully Dressed Use Case · Use Case: · Scope · Level: User Goal · Primary Actor: · Stakeholders and interests: · Pre-conditions: · Minimal guarantee: · Success guarantee: · Trigger: 3. Main Success Scenario: He/she has to answer based on the case about the user and the system interface