Relational database system for restaurant
- 1. Relational Database System for Java Coffee House LUSALA LOGEDI VICTOR Msc GIS 23RD NOVEMBER 2016
- 2. Java Coffee House: Love Is Here • Nairobi's Most Prestigious Eatery • Has 44 branches across Kenya, Uganda, Rwanda and still expanding • Serves Freshly Brewed Coffee as its signature Brand • Also Serve Main Dish, Pastries, Snacks and other beverages 07/12/2016Lusala Logedi Victor F56/87608/2016 2
- 3. Relational Database •A relational database organizes data in tables (or relations). •A table is made up of rows (Record/tuple) and columns (Field/Attribute). •The Relational Database enables effective input, storage, manipulation and retrieval of data 07/12/2016Lusala Logedi Victor F56/87608/2016 3
- 4. Java Coffee House: Database Design Process External Modelling • User Needs Requirements Conceptual Modelling • Entity Relationship Diagram • Cardinalities Logical Modelling • Normalization • Perform Data Integrity 07/12/2016Lusala Logedi Victor F56/87608/2016 4
- 5. The External model: User Needs Analysis JAVA COFFEE HOUSE DATABASE Java Id Java Name Java Location Employee ID Employee Name Product ID Product Name Stock Order ID Order Details Quantity OrderAmount Sales USER 1: Manager Java Name Orders Products Sales Stock Employees Employee Duty USER 2: Cashier/Accountant Orders Quantity Customer Sales USER 4:Waiter Customer Order Quantiry Sales USER 3: Chef/Barristar Product Order Quantity USER 5: Customer Product Order Amount 07/12/2016Lusala Logedi Victor F56/87608/2016 5
- 6. Conceptual Model: E-R Diagram 07/12/2016Lusala Logedi Victor F56/87608/2016 6 Customer 1-n Pays 1-1 Cahier 1-n Serves 1-1 Waiter Places Order 1-n Prepares 1-1 Chef/ Barrister 1-1 Contains 1-n Products 1-1 Works in 1-1 Java 1-1 Has 1-1 Manager 1-1 Handles Taken by 1-n Works in1-n 1-1 Customer ID Customer Name Customer Location Order ID Product Amount Order Date Quantity Employee IDEmployee Name Sex Employee ID Employee Name Sex 1-n Java ID Java Name Java Location Employee ID Employee Name Sex Product ID Product Name Unit Price Sales Employee ID Employee Name Sex
- 7. Logical Design: Data Normalization CustName CustLoctn JavaName OrderName PrdctName EmplName Sales Paul Kasarani JavaTRM Breakfast 2 Coffee, 2 MeatPie John,Tim 500 Victor Roysambu GardenCity Main Dish Chicken, Chips John, Peter 450 CustID CustName CustLoctn JavaID JavaName OrderID OrderName PrdctID PrdctName Qty EmplID EmplName UnitPrice Sales J042 Paul Kasarani Jav25 TRM 021 Breakfast 001 Coffee 2 254,020 John,Tim 100 200 J042 Paul Kasarani Jav25 TRM 021 Breakfast 002 Meat pie 2 254,020 John,Tim 150 300 J043 Victor Roysambu Jav26 GardenCity 022 Main Dish 003 Chicken 1 265,010 John, Peter 300 300 J043 Victor Roysambu Jav26 GardenCity 021 Main Dish 004 Chips 1 265,010 John, Peter 150 150 1. Identification Of Primary Keys 2. Normalizing tables to 1NF CustID CustName CustLoctn CustAdress J042 Paul Kasarani 1037 J043 Victor Roysambu 1048 JavaID (PK) JavaName JavaLoctn Jav25 TRM TRM Mall Jav26 Garden City Garden City Mall Relation 1: Customer Relation 2: Java 07/12/2016 Lusala Logedi Victor F56/87608/2016 7
- 8. OrderID OrderName PrdctID PrdctName Qty EmplID EmplName EmpDuty Unit Sales 021 Breakfast 001 Coffee 2 254 John Waiter 100 200 021 Breakfast 001 Coffee 2 020 Tim Barrister 100 200 021 Breakfast 002 Meat pie 2 254 John Waiter 150 300 021 Breakfast 002 Meat Pie 2 020 Tim Barrister 150 300 022 Main Dish 003 Chicken 1 265 John Waiter 300 300 022 Main Dish 003 Chicken 1 010 Peter Chef 300 300 022 Main DIsh 004 Chips 1 265 John Waiter 150 150 022 Main Dish 004 Chips 1 010 Peter Chef 150 150 3. Normalizing tables to 2NF EmplID(PK) JavaID(FK) EmplName EmpDuty Sex 254 Jav25 John Waiter Male 020 Jav25 Tim Barrister Male 265 Jav26 John Waiter Male 010 Jav26 Peter Chef Male PrdctID(PK) PrdctName UnitPrice Stock 001 Coffee 100 20 002 Meat pie 150 30 003 Chicken 300 15 004 Chips 150 10 OrderID(PK) CustID (FK) OrderName OrderDate 021 J042 Breakfast 16/11/16 022 J043 Main Dish 17/11/16 OrderID(PK) PrdctID(FK) EmplID(FK) Qty Sales 021 001 255 2 200 021 002 255 2 200 022 003 255 1 300 022 004 255 1 150 4. Normalizing tables to 3NF Relation 5: Order Relation 6: SalesPrimary key Relation 3: Employee Relation 4: Product 07/12/2016Lusala Logedi Victor F56/87608/2016 8
- 9. Logical Design: Data Integrity Relation3: Order OrderID CustID OrderDate Relation6: Customer CustID EmplID CustName CustLoctn CustAddress Relation1: Java JavaID JavaName JavaLoctn Relation2: Employee EmplID JavaID EmplName EmplDuty Sex Relation4: Sales OrderID SalesID PrdctID EmplID Qty Sales Relation5: Product PrdctID PrdctName UnitPrice Stock n 1 n 1 1 n 1 n 1 n n 1 1 n 07/12/2016Lusala Logedi Victor F56/87608/2016 9
- 10. References 1. Thalheim, B. Entity-relationship Modeling: Foundations of DatabaseTechnology. Berlin: Springer, 2000. Print. 2. Garmany, John, Jeff Walker, andTerry Clark. Logical Database Design Principles. Boca Raton, FL: Auerbach Publications, 2005. Print. 07/12/2016Lusala Logedi Victor F56/87608/2016 10