Mn404 Operating Systems: Country Kitchen Assessment Answers

Business case study: Country Kitchen Classics Web User Interface

Preview:

In this case study, you will design the classes that support the interface to the Country Kitchen Classics database (written in Java programming language). After your class design is completed, you are asked to provide implementation of your design as specified in the case study.

Background:

Your cousin Alice and her business partner, Rachel, plan to sell quality, gourmet frozen meals over the Internet. Alice and Rachel had been studying the market and see a need for these meals, especially among the elderly and busy working families. Alice knows that you are proficient in Java programming and graphical user interface design. She hires you for the summer to help create this exciting business.

Alice envisions the business to include these parameter: customers, meals, orders and shipping costs.

• Customerswill be ordering their meals via the Internet, so the business needs to track their name, shipping address, telephone number, credit card details and email address.
• Mealswill be categorized by their unique ID number. Each meal has a name, specific price and description, and this information must also appear in the database.
• Ordersdetails need to include the specific meal(s), quantities, customer and whether the order requires overnight shipping.
• Shipping costsincludes two flat-rate costs: one for regular shipping and one for overnight shipping.

Alice wants web interface to accomplish certain tasks. First, she wants you to create Internet order form for ordering meals. (The form should show basic order headings, such as Order Number, Customer ID, Date and a check box to indicate whether the customer needs overnight delivery.) In a suborn, the order information required to order meals should include headings for Order Number, Meal ID and Quantity.

In addition, Alice, as an administrator, wants the following features as queries:

• Potential customers might telephone the office and ask for more details about certain menu items. So, Alice would like the office staff to be able to make queries that will display the description and price of each meal.
• Alice would also like an easy way to calculate the number of meals sold on a particular day. She would like to be able to input the date and see a list showing meals with highest to lowest sales. This information is to ensure adequate inventory in the future.
• The shipping clerk needs to see which of today’s orders require overnight delivery so he can meet the pick-up deadline.

Finally, Alice requires you to create a daily report that lists each customer’s ID number, last name, their order, the dollar amount of the order, shipping cost and total order, which includes both meals and shipping costs.

Your report should provide detailed answers for the following questions.

• Specify Use cases (minimum of six) for the design of Country Kitchen Classics Web User Interface specifying the  Provide possible scenarios (minimum of two) for each Use case. (Use UML notation)

Cases:

Customer order meal

Change meal

Cancel meal

Change meal manually

Change my email

Change my phone

• Determine the classes that are required for the design (minimum of four classes). All classes need to be given a meaningful name.

Assumption: only one customer can order one type of meal

• Assign attributes for the classes specifying the datatype, the possible range of values (meaningful names should be given).

The attributes are displayed in the classes above

Possible range of values:

In Shipping, overnight is a booleam type (yes or not)

Price is from 0

• Provide the class declaration for three of the classes and a simple implementation of initialization of datatypes of the classes. And provide a display () method that outputs the datatypes to the console.

Five classes are defined for Country Kitchen, they are Customer, Meal, Staff, Order and Shipping.

• Customer: Customer_ID, Customer_Name, Shipping_Address, Phone,  CreditCard, email, Customer_Overnight,

• Order
• Meal
• Shipping
• Staff

Introduction:

The study includes the information regarding the system design features of the country kitchen system. The system is designed for taking orders from the consumers and processing the orders until the order is sent for delivery. The Use Case diagram, Class identification and simple Class has been covered within the study.

1: Use Case Diagram and Scenario 

2: Determination of Classes

Customer: These classes are the base of the design. The customers can order meals and select the delivery method. The order class will be called if the customer chooses to order meal. The customer must login to the system for making a order.

Order: The order class will hold the information regarding the current order that is being placed by the customer. If the class is connected to a database then Alice can see the historical data of the order.

Shipping Clerk: It may seem that this class is not required but in order to track the business processes, it is essential to store the activities of the shipping clerk. If any order is not sent to the customer by the shipping clerk then this calls will serve as the proof which clerk was responsible for making the delivery.

Meal: As the orders will contain the id of the meals, it is important the system has a meal class. The meal class will hold the information of the meals.

3. Assigning Attributes:

4: Class Implementation

Customer:

Shipping Clerk: 

Meal:  

Conclusion:

The study concludes that the system design process is a vital phase in the development procedure as it provides a outline of the system in advance. The use case diagram has provided the knowledge regarding the interactions between the user and system. Based on the identified data, the classes are designed and created.

Bibliography:

Carpenter, B., Gelman, A., Hoffman, M., Lee, D., Goodrich, B., Betancourt, M., ... & Riddell, A. (2016). Stan: A probabilistic programming language. Journal of Statistical Software, 20.

Flanagan, C., Leino, K. R. M., Lillibridge, M., Nelson, G., Saxe, J. B., & Stata, R. (2013). PLDI 2002: Extended static checking for Java. ACM Sigplan Notices, 48(4S), 22-33.

Nanthaamornphong, A., Carver, J., Morris, K., & Filippone, S. (2015). Extracting uml class diagrams from object-oriented fortran: Foruml. Scientific Programming, 2015, 1.

Sharma, C., Sabharwal, S., & Sibal, R. (2014). Applying genetic algorithm for prioritization of test case scenarios derived from UML diagrams. arXiv preprint arXiv:1410.4838.

Slaughter, E., Lee, W., Treichler, S., Bauer, M., & Aiken, A. (2015, November). Regent: A high-productivity programming language for hpc with logical regions. In Proceedings of the International Conference for High Performance Computing, Networking, Storage and Analysis (p. 81). ACM.

Störrle, H. (2014). On the impact of layout quality to understanding UML diagrams: size matters. In International Conference on Model Driven Engineering Languages and Systems (pp. 518-534). Springer International Publishing.