Country Kitchen Classics Web User Interface: A Java Programming Case Study

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.

Name	Login
ID Save Time On Research and Writing Hire a Pro to Write You a 100% Plagiarism-Free Paper. Get My Paper	User-UC1
Associated Actors	Customer
Description	The customer is logging into the system
Organizational Advantages	Better track of customer activity
Frequency of use	Frequent
Associative Use Case	None
Flow of Activities	Actors	System
	The customer access the login page
	The customer input the id and password and submit	The system will check if the id and password is valid
		The system will start a session if the data is valid
Triggers	The system is about to create a session against a particular id
Precondition	The customer must have a valid id and password
Post-condition	The customer is logged in
Exception	The system cannot identify a valid id

Name	Order Meal
ID	User-UC3
Associated Actors	Customer
Description	The customer is making an order through the system
Organizational Advantages	Increase in sales
Frequency of use	Frequent
Associative Use Case	Login
Flow of Activities	Actors	System
	The customer selects the meals	The meals are sent to cart
	The customer clicks on order	The system calculates the order amount and asks for delivery address and payment
	The customer input address and makes payment	The system confirms order and stores into the database
Triggers	Adding a new row in the order table
Precondition	The ordered meals must be available
Post-condition	The order is confirmed
Exception	The system cannot deliver to the specific address

Name	Select Delivery Method
ID	User-UC4
Associated Actors	Customer
Description	The customer may choose the overnight shipping
Organizational Advantages	The flexibility in customer service increase customer loyalty
Frequency of use	Frequent
Associative Use Case	Order Meal
Flow of Activities	Actors	System
	The customer makes a order	The system provide the option of overnight shipping
	The customer chooses the option	The system receive the input
	The customer makes the order	The overnight sleeping options is saved as delivery method in the database
Triggers	The customer chooses a delivery method
Precondition	The product have the feature
Post-condition	The overnight delivery of order is confirmed
Exception	Overnight delivery is available but is not approving due to shipping clerk unavailability

Name	Pickup Order
ID	User-UC7
Associated Actors	Shipping Clerk
Description	The shipping clerk will pick the product that is mentioned in the order
Organizational Advantages	The delivery of product result in sales
Frequency of use	Regular
Associative Use Case	None
Flow of Activities	Actors	System
	Shipping clerk receives the order	The system checks if the product is same
	The clerk put the order number
Triggers	The clerk receives product from warehouse
Precondition	The order must be valid
Post-condition	Product is successfully picked up
Exception	The product is not available in the warehouse

Name	Sales of Meals
ID	Admin-UC1
Associated Actors	Alice
Description	The admin is requesting to view sales details
Organizational Advantages	Monitoring sales data improves decision making quality
Frequency of use	Twice a weak
Associative Use Case	Order Meal
Flow of Activities	Actors	System
	Alice click on the view sales button	The system retrieves data from database
	Alice view the data
Triggers	Alice monitors sales data
Precondition	The database must hold some order detail
Post-condition	The sales data is shown
Exception	No sale made on a particular date

Name	Order Detail
ID	User-UC6
Associated Actors	Shipping Clerk
Description	The shipping clerk receives the order detail
Organizational Advantages	Better and accurate delivery of order
Frequency of use	Frequent
Associative Use Case	Order Meal
Flow of Activities	Actors	System
		The system sent the order detail to available clerk
Triggers	A sales order is going to delivered
Precondition	The order must be confirmed
Post-condition	Order details are sent successfully
Exception	No clerk is present on that day

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.

Customer
CustomerID	INT	1
FirstName	String	Jay
LastName	String	Harijan
Address	String	12^th Street, New Jersey
Contact	INT	77

Shipping Clerk
ClerkID	INT	1
FirstName	String	Megan
LastName	String	Fox
Address	String	4^th Crossing, New Jersey
Contact	INT	77
Salary	Double	234.00

Order
OrderNumber	INT	1
Date	Date	17-04-17
DeliveryMethod	String	Overnight
DeliveryAddress	String	12^th Street, New Jersey
TotalCost	Double	57.89
MealID	INT	1
CustomerID	INT	1
ClerkID	INT	1

Meal
MealID	INT	1
Price	Double	35.59
Name	String	Chicken Roast
Type	String	Non-vegetable

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.

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.

Turn in your highest-quality paper
Get a qualified writer to help you with

“ Country Kitchen Classics Web User Interface: A Java Programming Case Study ”

Get high-quality paper

NEW! AI matching with writer