Description Project 3 - Pizza Ordering - Use Microsoft SQL Server Express 2017 Edition Due: multiple due dates - see below --- use your own calendaring event system to keep you on-track This project is the one which wraps up the class content into a semi-real world concept. Brainstorming, sketching, tables/columns, naming, relationships (1:1, 1:M, M:N), sample data required. Pizza Ordering... Goal 1. To create a design document which describes the data model that will result in relational tables the refined Brainstorm 2. To create a sketch which forms your design into a rough table layout/relationship view - the graphical view 3. To create those tables in Microsoft SQL (e.g. in Virtual Machine) - the product Model a database which enables you to collect necessary data to handle pizza orders (at the counter or via phone orders). FYI - in general, Pizza makers get the phone number when taking a phone order, to enable verification; however, counter orders would not need this information. All orders need to know what is being ordered. It is critical to understand the menu & business policies: - One pizza per order. - Assign cost to each "thing" (size, crust, topping) - 3 types of pizzas - Small, Medium, Large - and each can come in thin or deep dish. - Toppings - some examples: cheese, pepperoni, black olives, Italian sausage, bacon, bell peppers (green, red, or yellow), pineapple, anchovies, onions, etc. - If extra toppings are ordered, then extra charges would apply. - This store does not offer delivery - all orders are picked up or eat-in. Factors to brainstorm: how to store orders, consider storage of price of items (toppings, sizes, etc.), other data of the sale There is zero storage of Customer data (other than There is zero storage of Customer data (other than phone number, if phone order) Evaluate/handle NULL data the best way - based on class discussions Part I - Data Model Sketch Data model (12pts) - in Word (or Notepad) - DUE: 3/9/2023 (12:30pm, before class) (Goal \#1) - Brainstorm data (this is non-structured) - include ideas of what data is stored - Form brainstormed data into a structure which will eventually become tables - Think table names \& bullet points - not lines \& squares \& rectangles - Include ideas for each item in brainstorm (e.g. about the data): - Sample data - What data types - Size of columns - NULL or Not - Use the Crows Feet concept for this sketch Turn in: Data model document file name should include your name and "Project3" (Goal 1) Table Sketch (6pts) - DUE: 3/23/2023 (12:30pm, before class) (Goal \#2) - Form brainstorm data into table format - This is a "sketch" on paper (think lines \& squares \& rectangles) - turn in image file of your paper sketch Turn in: Sketch (Goal 2) Part II - Database 12 points - DUE: 3/30/2023 (12:30pm, before class) (Goal \#3) - Take your data model and create your database using the Virtual Machine Microsoft SQL system - Turn in the following scripts: - CREATE - tables - INSERT - for data in each table - SELECT - to display all orders (the result for each order will be multirows of data, based on number of - Turn in the following scripts: - CREATE - tables - INSERT - for data in each table - SELECT - to display all orders (the result for each order will be multirows of data, based on number of toppings selected - don't be surprised) - Not looking for a "receipt". No calculations needed. Just show the data using a SELECT statement. - Once your tables are in - create a database diagram with relationship lines and set Cascade options, if needed. - Enter 1 to 2 sample rows of data in data tables, and 5-10 sample rows of data in your type tables Backup up your database frequently. Turn in: database --- this "backup" file name should include your name and "Project3" (Goal 3) Description Project 3 - Pizza Ordering - Use Microsoft SQL Server Express 2017 Edition Due: multiple due dates - see below --- use your own calendaring event system to keep you on-track This project is the one which wraps up the class content into a semi-real world concept. Brainstorming, sketching, tables/columns, naming, relationships (1:1, 1:M, M:N), sample data required. Pizza Ordering... Goal 1. To create a design document which describes the data model that will result in relational tables the refined Brainstorm 2. To create a sketch which forms your design into a rough table layout/relationship view - the graphical view 3. To create those tables in Microsoft SQL (e.g. in Virtual Machine) - the product Model a database which enables you to collect necessary data to handle pizza orders (at the counter or via phone orders). FYI - in general, Pizza makers get the phone number when taking a phone order, to enable verification; however, counter orders would not need this information. All orders need to know what is being ordered. It is critical to understand the menu & business policies: - One pizza per order. - Assign cost to each "thing" (size, crust, topping) - 3 types of pizzas - Small, Medium, Large - and each can come in thin or deep dish. - Toppings - some examples: cheese, pepperoni, black olives, Italian sausage, bacon, bell peppers (green, red, or yellow), pineapple, anchovies, onions, etc. - If extra toppings are ordered, then extra charges would apply. - This store does not offer delivery - all orders are picked up or eat-in. Factors to brainstorm: how to store orders, consider storage of price of items (toppings, sizes, etc.), other data of the sale There is zero storage of Customer data (other than There is zero storage of Customer data (other than phone number, if phone order) Evaluate/handle NULL data the best way - based on class discussions Part I - Data Model Sketch Data model (12pts) - in Word (or Notepad) - DUE: 3/9/2023 (12:30pm, before class) (Goal \#1) - Brainstorm data (this is non-structured) - include ideas of what data is stored - Form brainstormed data into a structure which will eventually become tables - Think table names \& bullet points - not lines \& squares \& rectangles - Include ideas for each item in brainstorm (e.g. about the data): - Sample data - What data types - Size of columns - NULL or Not - Use the Crows Feet concept for this sketch Turn in: Data model document file name should include your name and "Project3" (Goal 1) Table Sketch (6pts) - DUE: 3/23/2023 (12:30pm, before class) (Goal \#2) - Form brainstorm data into table format - This is a "sketch" on paper (think lines \& squares \& rectangles) - turn in image file of your paper sketch Turn in: Sketch (Goal 2) Part II - Database 12 points - DUE: 3/30/2023 (12:30pm, before class) (Goal \#3) - Take your data model and create your database using the Virtual Machine Microsoft SQL system - Turn in the following scripts: - CREATE - tables - INSERT - for data in each table - SELECT - to display all orders (the result for each order will be multirows of data, based on number of - Turn in the following scripts: - CREATE - tables - INSERT - for data in each table - SELECT - to display all orders (the result for each order will be multirows of data, based on number of toppings selected - don't be surprised) - Not looking for a "receipt". No calculations needed. Just show the data using a SELECT statement. - Once your tables are in - create a database diagram with relationship lines and set Cascade options, if needed. - Enter 1 to 2 sample rows of data in data tables, and 5-10 sample rows of data in your type tables Backup up your database frequently. Turn in: database --- this "backup" file name should include your name and "Project3" (Goal 3)