1. Group 2 BMIS 441-02 Connor Hope Joe Peanasky Emma Bulba Ali Walkley
Manito Tap House
Group 2 BMIS
Connor Hope
Joe Peanasky
Emma Bulba
Ali Walkley

2. Scenario
The Business: Manito Tap House, an eco-friendly restaurant and tavern located on the South Hill in Spokane; serving home-made food, 50 different brews, wine and spirits.
Manito Tap House has four focuses:
Being a neighborhood favorite
Supporting local breweries
Being environmentally friendly
Serving top quality beers in a professional manner
Why choose Manito?
They desire to provide a more efficient and customer friendly environment than the neighborhood college bars and that was very intriguing
Goal: Help the restaurant work on specific areas of their business to provide the Tap House with a easier way of providing excellent customer

3. Data Model Requirements
Manito would benefit from a database system that helps them:
Manage their brew offerings and on tap inventory
Track which beers are sold more often than others and which beers are best-sellers
Efficiently track their membership program
Provide an efficient way of tracking their employees' certifications and education

4. Objective
We will use this database system to provide a more efficient system for Manito Tap House regarding their customers, employees, and inventory specifically:
Efficiently manage inventory regarding Manito's beer suppliers' relationships, prices, and frequency of contact for purchasing brews.
Improve customer service which in turn increase the sales and acquisition rate of new customers and new tap members, thanks to the existing customers being pleased with Manito Tap House's service and eclectic beer menu.
Better manage employee productivity regarding shifts, education, and certifications.
We pledge to improve the company by finding new ways to improve our database and make it as effective as possible to serve the mission as being the community’s favorite place to eat and drink.

5. Systems Development Life Cycle: Analysis
With this database, we can analyze data and make significant changes to the company that will benefit and increase profits in the long run by:
Better serving the needs of its customers and employees
Managing the inventory accounts and prices of numerous supplier relationships
Analyzing consumer purchasing trends to see what are the most profitable items on the beer menu
Track which clients are spending the most money and improve Manito Memberships
Track employee education and skills

6. Systems Development Life Cycle: Design
The team will use the process of normalization to ensure that our database is simple and well structured and that we reduce the relations that contain anomalies.
Our goal is to reduce data redundancy and enforce referential integrity constraints.
Normalizing our database structure will make it easier to maintain the data that we receive and keep track of, and provide a better design that provides a basis for future growth.

7. Entities Needed:
EMPLOYEE (employee_id, employee_fname, employee_lname, year_started, position_id)
The employee table holds information about all of the employees at the restaurant and what their job is.
BEER (beer_id, beer_name, type_id, serve_id, abv, brewer_id)
The beer table keeps data about each specific beer; their name, how it is served, which brewery it came from and how my alcohol is in it.
EDUCATION (employee_id, education_level, certificate)
Education table contains every different employee and if they are certified in specific drinking handling skills.
EMPLOYEE_SHIFT (employee_id, shift_id, supervisor_first_name, supervisor_last_name)
Employee_shift table keeps tracks of when each employee works.
CUSTOMER (customer_id, visit_date, review, employee_id)
Customer table contains when a costumer came in, who served them, and their feedback.

8. Relational Diagram: Before Normalization

9. Normalization
Determine the normal form of the relational diagram: 1NF

10. Relational Diagram: 1NF

11. Normalization Determine the normal form of the relational diagram: 1NF
Convert to 2NF: Remove partial dependencies

12. Relational Diagram: 2NF

13. Normalization Determine the normal form of the relational diagram: 1NF
Convert to 2NF: Remove partial dependencies
Convert to 3NF: Remove transitive dependencies

14. Relational Diagram: 3NF

15. Normalization Determine the normal form of the relational diagram: 1NF
Convert to 2NF: Remove partial dependencies
Convert to 3NF: Remove transitive dependencies
Eliminate deletion anomalies: Create lookup tables

16. Relational Diagram: After Normalization

17. Design: ER-Diagram

18. Implementation DROP TABLE position CASCADE CONSTRAINTS;
DROP TABLE shift
DROP TABLE member
DROP TABLE beer_type
DROP TABLE serve_type
DROP TABLE brewer
DROP TABLE order_date
DROP TABLE employee

19. Create CREATE TABLE beer_item (item# NUMBER(5), beer_id NUMBER(5),
CONSTRAINT beer_item_item#_pk PRIMARY KEY(item#),
CONSTRAINT beer_item_beer_id_fk FOREIGN KEY(beer_id)
REFERENCES beer(beer_id));
CREATE TABLE beer_order
(beer_id NUMBER(5),
order# NUMBER(9),
date_received DATE,
quantity NUMBER(3) NOT NULL,
CONSTRAINT beer_order_beer_id_order#_pk PRIMARY KEY(beer_id, order#),
CONSTRAINT beer_order_beer_id FOREIGN KEY(beer_id)
REFERENCES beer(beer_id),
CONSTRAINT beer_order_order# FOREIGN KEY(order#)
REFERENCES order_date(order#));

20. INSERT INTO position (position_id, wage, description)
VALUES (1, 10.00, 'buster');
VALUES (2, 12.00, 'waiter');
VALUES (3, 12.00, 'host');
VALUES (4, 16.00, 'bartender');
VALUES (5, 18.00, 'supervisor');
VALUES (6, 20.00, 'cook');

21. Queries- #1 Current Employed Cicerones
To track quality of employees
Determine level of expertise and knowledge in bartending
Gain more customers through strong brand positioning

22. Queries- #2 Members for less than a year
Increase Customer Satisfaction
Grow membership base
Track loyal members and create reward system

23. Queries-#3 Employees working for more than two years
Track employees based on seniority

24. Queries- #4 Total amount of Chefs
Prospective hiring decisions
Track staff and employees

25. Queries-#5 Quantity of each beer ordered
To identify best selling beers and ensure availability of popular beers
Smarter Partnerships with suppliers with more favored beer items

26. Queries- #6 Which beers do not sell?
Eliminate Waste
Queries- #6 Which beers do not sell?

27. Better Manage Inventory To Determine Demand for
Queries - #7 View
Better Manage Inventory
To Determine Demand for
our beers

28. Returns higher than average ABV percentage
Queries - #8 Sub Query
Returns higher than average ABV percentage

29. Maintenance
Managers will be trained to monitor and update the database
A manager will provide maintenance to the database by changing any characteristics of the structure due to fluctuating business environments or correcting any errors or incorrect information in the database design.
Frequent maintenance is required in order to not compromise the efficiency of the new database.

30. Managerial and Organizational Impacts
Greatly improved customer satisfaction: at the restaurant and enhanced business operations, while enabling data access and follow-on analysis necessary to make future improvements to the company.
Moral streamlined ordering from suppliers: Database allows Manito Tap House to track usage and inventory based on the type and volume of beer consumed per customer.
Efficiency: More efficient job of analyzing data to improve their customer service and membership program
Improvement of data retrieval: Manito Tap House would be able to make informed, educated decisions based on relevant data.

31. Conclusion
Through the process of creating a database, we were able to learn how data access can improve the way a company makes informed business decisions.
Normalization is key because it is one of the most critical steps when creating a database.
We also realized the necessity of following the System’s Development Life Cycle, as it is crucial for proper database design to keep your data integrity safe.
There is always room for change and growth regarding your data and information, thus proper maintenance is required to keep up with the evolution and growth of a business

32. Thank you and Happy Holidays!