Database Implementation The Brick Tavern Inn

Download Report

Transcript Database Implementation The Brick Tavern Inn

Database
Implementation
The Brick Tavern Inn
Alonzo Harding, Eric Lukens, Tony Wu
Brick Tavern Inn Database System
• This Database System was created for a local restaurant called the Brick Tavern
Inn.
• We chose this particular business, because my group member is an employee
the Brick Tavern Inn.
• We developed forms, tables, queries, reports and finally a switchboard. To
implement a database system that will propel the Company's logistics and
hospitality.
Justification
• A Database System is needed for the Brick Tavern Inn because
technology is evolving at an extremely rapid pace. It is very
competitive and hard to sustain profitability in the restaurant
industry without technological advancements. By implementing our
database, immediate quantitative improvements will be noticed
from Top management, and mutually improve the qualitative side
as well.
Benefits and Drawbacks
Benefits
• Reduced updating errors
• Increased consistency of information
• Upgraded data access for the Brick Tavern Inn
• Efficient communication between customer and The Brick Tavern
Drawbacks
• Database System may be difficult for employees to manage and operate
• Time consuming to train users to use DBMS
• Hardware and software are costly, thus adding additional expenses for the
Server Food Order Form
Date:
Table
Number:
# of Guests:
Time:
Course Number
Category
Item/Name
Quantity
Price
“Course 1”
“Appetizers”
“Calamari”
1
10.95
“Course 2”
“Soups/Salads
”
“Crab Bisque”
2
7.90
“Course 3”
“Entrees”
“Beef Brisket”
3
22.95
“Course 4”
“Desserts”
“Lava Cake”
2
14.00
# of courses:
Side Notes:
Sub
Total:
$55.80
Tax:
$2.23
Total:
$58.03
Order Form Normalization
Tables: Brick Tavern Order Forms
1NF: Food Order form( order id, date, time, table number of guests, number of courses Server, first name,
last name)
Item Id (item #, name, quantity, price category)
2NF: order item (ordered, item id, item #, name quantity, price, category)
3NF: items (item id, Quantity, price, name)
Order Item (order id, id item, Category, name)
4NF: Food order form (order id, date, time, # of guests, # of courses
Order item (ordered, itemid, name category)
Items (items id, Quantity, Price name)
Server (server id, first name, Last name)
Consulting Form
Consulting Form Normalization
Tables: Brick Tavern Inn Consulting Form
1NF: Consultation form (client id, client name) First name, Last name< phone number, address, city, state,
zip, date, Consultant, first name, last name, purchasers, first name, last name, payment, credit card, cash,
expected date.
Party: (Party id, party #, Name, menu selection, beverage selection, duration room assignment, service cost)
2NF: Consultation party (client id, Party id, name, menu section, beverage section, duration, room
assignment, service cost)
3NF: Parties (party id, duration, room assignment, service cost)
Consulting Party (Consulting ID, Party id, menu selection, beverage selection)
4NF: Consulting Form (consulting id, date, time)
Parties (party id, duration, room assignment, service cost)
Consulting party (consulting id, party id, name, menu selection, beverage selection)
Client (Client id, First name, Last name)
Credit card (credit card id, credit card #, Expiration date)
Brick Tavern Inn Forms Diagram
(1..1)
(1:*)
Order
Item
Order id
Order ID
Employee ID
(0..*)
(1:*)
Date
(1..*)
Item id
Name
Food Order Form
Time
# of guest
(0..*)
# of courses
Category
Items
Item id
Item/Name
(1:*)
(1..1)
Category
Price
Class Diagram Cont...
Consulting
form
Employee
Employee ID
(1:*)
(1..1)
(1..1)
(1..*)
Name
Client
Client id
Form ID
(1..*)
(1:*)
Client id
Date
Title
(1..1)
Item Menu
(1:*)
Form ID
Item ID
Beverage
(1..*)
Room
Assignment
Description (1:1)(1:*)
(0…*)
(1:*)
Beverage ID
(1:*)
Address
Phone
Credit Card
(1:*)
(1..1)
Quantity
Beverage ID
(1:*)
Banquet Type
Duration
Menu
(1..1)
Item id
Description
List Price
List Price
First Name
Last Name
Time
Employee ID
(1..1)
Credit Card
id
Credit Card
#
Exp Date
Email
Website
Banquet Timing Query
• Due to time constraints in the restaurant industry it is paramount to know
exactly how long a certain party is going to occupy a particular room. This
query creates a more efficient scheduling procedure for the restaurant and
upcoming events.
Banquet Timing Views
Menu Price Query
• Customers do not have unlimited budgets, therefore they need to be
cautious of the items they are selecting. This Query sorts items in a
customer's price range, therefore displaying cost feasible items.
Menu Price Views
Number of Courses Query
• This query answers the question of how many courses will be served to a
particular order form.
Number of Courses views
Sub-Query
• This Sub Query is derived from the previous query, It computes the overall
average number of courses based on the current clientele order forms.
Subquery Views
Room Assignment Query
• With multiple Rooms and constant Parties occurring, confusion can become
easy. This query can quickly and effectively categorize designated room
assignments, and the exact dates of these events.
Room Assignment Views
Credit Card Validation Query
• The frequency of credit card errors and invalid transactions are substantial in
the restaurant industry. We added this query so management could quickly
and easily pick out any invalid credit cards and transactions.
Credit Card Validation Views
Baby Shower Query
• This Query allows the Top Management team to view how many of a
particular event is taking place. This will result in the proper preparation
involving inventory and staff.
Baby Shower Views
Consulting Form
Order Form
Clientele Report
Employee Report
Brick Tavern Inn SwitchBoard