This first milestone is designed to assist you with determining the requirements for the provided scenario. This milestone aligns with Section I of the final project. You will analyze the scenario in

IT 235 Milestone One Guidelines and Rubric Overview: Database design is an integral step in the overall development of a database solution; a bad design can lead to many issues a nd problems with queries and potential expansion for any database. Getting the database design right is the first and most importa nt step in creating a successful database. For this assignment, you will solve a database design situation as outlined in the scenario do cument . As you read through the narrative, be sure to pay close attention to the business requirements that the business owners note. Prompt: Imagine that you are a consultant database designer and you have taken on a project that will require you to establish a database for a small pizzeria. If you have not already read the final project scenario document, do so now and determine the overall purpose of the database an d the user requirements. Specifically, the following critical elements must be addr essed: I. Requirement Gathering: Read the provided scenario in order to determine the overall purpose of the database and the user requirements, specifically the following: A. Define the purpose, goals, and objectives of the database as determined by the scenar io. B. Assess the user requirements associated with the database according to its owners and stakeholders. C. Explain the business processes and restrictions that the database addresses in support of the user requirements. D. Explain what the end result of the da tabase should be as determined by the scenario. Rubric Guidelines for Submission: Submit assignment as a Word document with double spacing, 12 -point Times New Roman font, and one -inch margins. Critical Elements Proficient (100%) Needs Improvement (70%) Not Evident (0%) Value Requirement Gathering: Purpose, Goals, and Objectives Defines the purpose, goals, and objectives of the database as determined by the scenario Defines the purpose, goals, and objectives of the database as determined by the scenario, but response is incomplete or contains inaccuracies Does not define the purpose, goals, and objectives of the database as determined by the scenario 22.5 Requirement Gathering: User Requirements Assesses the user requirements associated with the database according to its owners and stakeholders Assesses the user requirements associated with the database, but assessment is cursory or incomplete, contains inaccuracies, or lacks accordance with the database’s owners and stakeholders Does not assess the user requirements associated with the database 22.5 Requirement Gathering: Business Processes and Restrictions Explains the business processes and restrictions that the database addresses in support of the user requirements Explains the business proc esses and restrictions that the database addresses, but explanation is cursory, incomplete, or illogical, or it contains inaccuracies or lacks accordance with the user requirements Does not explain the business processes and restrictions that the database addresses 22.5 Requirement Gathering: End Result Explains what the end result of the database should be as determined by the scenario Explains what the end result of the database should be as determined by the scenario, but explanation is cursory or illo gical or contains inaccuracies Does not explain what the end result of the database should be as determined by the scenario 22.5 Articulation of Response Submission has no major errors related to citations, grammar, spelling, syntax, or organization Submission has major errors related to citations, grammar, spelling, syntax, or organization that negatively impact readability and articulation of main ideas Submission has critical errors related to citations, grammar, spelling, syntax, or organization t hat prevent understanding of ideas 10 Total 100%