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

IT235FinalProjectGuidelinesandRubricOverviewDatabasedesignisanintegralstepintheoveralldevelopmentofadatabasesolution;abaddesigncanleadtomanyissuesandproblemswithqueriesandpotentialexpansionforanydatabase.Gettingthedatabasedesignrightisthefirstandmostimportantstepincreatingasuccessfuldatabase.Forthisfinalproject,youwillsolveadatabasedesignsituationasoutlinedinthisscenario.Asyoureadthroughthescenario,besuretopaycloseattentiontothebusinessrequirementsthatthebusinessownersnoteinthenarrative.Overthecourseoftwomilestones,youwillneedtodefinetheneedforthedatabaseandpickoutthebusinessrequirements.Next,youwillframetheentity-relationshipmodel(ERM)anddefinetheentitiesandattributesforthebusiness.Yournextstepswillbetonormalizeyourentities,defineprimaryandforeignkeys,andfinally,draftaninitialentity-relationshipdiagram(ERD).Afterreferencingfeedbackfromyourinstructorforappropriaterevisions,youwillsubmitadatabasedesignreportpackage.Thepackagewillcontainyourfinaldesignproposal,includinganERDanddependencydiagrams,anexplanationforthedeterminationsyoumadewhilefillinginyourERDandmakingadjustmentsafternormalization,andasummaryexplanationofhowyourdesignwillallowthedatabasetoachievethedesiredendresult,includingaconsiderationoftheuserrequirements,businessprocesses,andrestrictions.Throughoutthecourse,youwillsubmitmilestonecomponentsthatwillbeevaluatedbyyourinstructor,anddetailedfeedbackwillbeprovided.Thisfeedbackshouldbeusedasthebasisfortherevisionofyourprojectdocumentsandproposal,asitwillserveasafoundationtothesubsequentmilestonesandultimately,yourfinalprojectsubmission.Theprojectisdividedintotwomilestones,whichwillbesubmittedatvariouspointsthroughoutthecoursetoscaffoldlearningandensurequalityfinalsubmissions.ThesemilestoneswillbesubmittedinModulesTwoandFive.ThefinalproductwillbesubmittedinModuleSeven.Note:Duetothenatureoftheprojectwithinthiscourse,youwillnoticethata“StayingonTrack”themeappearsineachmodule.Thisthemewillgiveyoutheinformationyouneedtostayontrackandsuccessfullycompletethefinalproject.Inthisassignment,youwilldemonstrateyourmasteryofthefollowingcourseoutcomes:AssessenduserrequirementsforidentifyingtheappropriatedatabasedesignsandtypesthatsolveinformationmanagementneedsDetermineappropriateentity-relationshipmodels(ERMs),includingunderlyingentitiesandattributes,fordesigningdatabasesolutionsDesignentity-relationshipdiagrams(ERDs)andtablerelationshipsthatmeetenduserrequirementsforappropriatelydesigneddatabasemanagementsolutions1 Completenormalizationprocessesutilizingentity-relationshipdiagrams(ERDs)anddependencydiagramsforproducingappropriatedatabasedesignsPromptYouhavebeenhiredtodesignadatabasethatmeetsanoutlinedsetofrequirementsinordertosolveaninformationmanagementproblem.Afterreadingthroughtheprovidedscenario,youwillfirstdeterminetheoverallpurposeofthedatabaseandtheuserrequirements.Youwillthenworkthroughaconceptualdesignprocess,designrevision,anddesignfinalization.Yourfinalsubmissionshouldbeintheformofafinalentity-relationshipdiagram(ERD)inthirdnormalform(3NF)andanexplanatoryreportthatsummarizesyourprocessandrecommendationsforthedatabasesolution.AlongwithyourfinalERDandnewworkfortheassignment,thedocumentshouldincorporatethetextanddiagramsfromyourmilestones,includingrevisions.Specifically,thefollowingcriticalelementsmustbeaddressed:I.RequirementGathering:Readtheprovidedscenarioinordertodeterminetheoverallpurposeofthedatabaseandtheuserrequirements,specificallythefollowing:A.Definethepurpose,goals,andobjectivesofthedatabaseasdeterminedbythescenario.B.Assesstheuserrequirementsassociatedwiththedatabaseaccordingtoitsownersandstakeholders.C.Explainthebusinessprocessesandrestrictionsthatthedatabaseaddressesinsupportoftheuserrequirements.D.Explainwhattheendresultofthedatabaseshouldbeasdeterminedbythescenario.AI.ConceptualDesign:Usingyouranalysisoftheprovidedscenario,addressthefollowinginordertodetermineanappropriateentity-relationshipmodel(ERM)thatwillinformyourfinaldesign:A.AssessvariousERMsfortheirdesignapplicabilitytoyourdatabasedesign.B.DeterminetheappropriateERMandexplainyourchoice.C.Identifythedatasetsforthedatabase,includingallentitiesandattributes.2 BI.DesignRevision:Duringthisstage,youwilldraftyourentity-relationshipdiagram(ERD),addressingthefollowingelements:A.ConstructyourERD,utilizingyouridentifiedentitiesandattributes.B.DetermineappropriateprimaryandforeignkeysforeachentityandnotethemonyourERD.C.DeterminetablerelationshipsandnotethemonyourERD.D.DetermineappropriatedatatypesandsizesforeachattributeandnotethemonyourERD.E.Completethenormalizationprocessutilizingdependencydiagramsinordertoprovetablesareinthirdnormalform(3NF),andadjustyourERDifnecessary.IV.DesignFinalization:FinalizeyourERDafternormalization,andconcludeyourreportpackage,addressingthefollowingelements:A.DraftyourrecommendedfinalERD,whichaccountsforanyadjustmentsmadetoitselementsasdeterminedthroughthenormalizationprocess.B.Summarizeyourprocessfordevelopingyourdatabasedesign,includinganexplanationforthedeterminationsyoumadewhilefillinginyourERDandmakingadjustmentsafternormalization.C.Explainhowyourdesignwillallowthedatabasetoachieveyourdesiredendresult,includingconsiderationoftheuserrequirements,businessprocesses,andrestrictions.3 MilestonesMilestoneOne:RequirementGathering(SectionI)InModuleTwo,youwillanalyzethescenarioindetailandthendefinethegoalsandobjectivesofthedatabase,assesstheuserrequirements,explainthebusinessprocessandanyrelatedrestrictionsforthedatabase,andexplainwhattheendresultofthedatabaseshouldbe.ThismilestonewillbegradedwiththeMilestoneOneRubric.MilestoneTwo:ConceptualDesign(SectionII)andDesignRevision(SectionIII)InModuleFive,youwillworkthroughthedesignandrevisionprocess,includingdeterminingyourinitialdatasetofentitiesandattributes,draftingandrevisingtheprojectERD,determiningprimaryandforeignkeysandtablerelationships,andcompletingthenormalizationprocessviadependencydiagrams.ThismilestonewillbegradedwiththeMilestoneTwoRubric.FinalSubmission:DatabaseDesignReportPackageInModuleSeven,youwillsubmityourfinalproject.Itshouldbeacomplete,polishedartifactcontainingallofthecriticalelementsofthefinalproduct.Itshouldreflecttheincorporationoffeedbackgainedthroughoutthecourse.ThissubmissionwillbegradedwiththeFinalProjectRubric.FinalProjectRubricGuidelinesforSubmission:SubmitassignmentasaWorddocumentwithdoublespacing,12-pointTimesNewRomanfont,andone-inchmargins.CriticalElementsExemplaryProficientNeedsImprovementNotEvidentValueRequirementMeets“Proficient”criteria,andDefinesthepurpose,goals,andDefinesthepurpose,goals,andDoesnotdefinethepurpose,4.75Gathering:Purpose,responsedemonstrateskeenobjectivesofthedatabaseasobjectivesofthedatabaseasgoals,andobjectivesoftheGoals,andObjectivesinsightintodeterminingthedeterminedbythescenariodeterminedbythescenario,databaseasdeterminedbythegoalsandobjectivesofa(85%)butresponseisincompleteorscenario(0%)database(100%)containsinaccuracies(55%)4 RequirementMeets“Proficient”criteria,andAssessestheuserrequirementsAssessestheuserrequirementsDoesnotassesstheuser4.75Gathering:Userassessmentprovideskeenassociatedwiththedatabaseassociatedwiththedatabase,requirementsassociatedwithRequirementsinsightintotheneedsofaaccordingtoitsownersandbutassessmentiscursoryorthedatabase(0%)database’sownersandstakeholders(85%)incomplete,containsstakeholdersastheyrelatetoinaccuracies,orlackstheuserrequirementsaccordancewiththedatabase’sassociatedwithadatabaseownersandstakeholders(55%)(100%)RequirementMeets“Proficient”criteria,andExplainsthebusinessprocessesExplainsthebusinessprocessesDoesnotexplainthebusiness4.75Gathering:BusinessexplanationmakescogentandrestrictionsthattheandrestrictionsthattheprocessesandrestrictionsthatProcessesandconnectionsbetweenbusinessdatabaseaddressesinsupportdatabaseaddresses,butthedatabaseaddresses(0%)Restrictionsprocessesandrestrictionsandoftheuserrequirements(85%)explanationiscursory,theuserrequirementsofaincomplete,orillogical,oritdatabase(100%)containsinaccuraciesorlacksaccordancewiththeuserrequirements(55%)RequirementMeets“Proficient”criteria,andExplainswhattheendresultofExplainswhattheendresultofDoesnotexplainwhattheend4.75Gathering:EndResultexplanationdemonstrateskeenthedatabaseshouldbeasthedatabaseshouldbeasresultofthedatabaseshouldinsightintodeterminingwhatdeterminedbythescenariodeterminedbythescenario,beasdeterminedbythetheendresultofadatabase(85%)butexplanationiscursoryorscenario(0%)shouldbe(100%)illogicalorcontainsinaccuracies(55%)ConceptualDesign:Meets“Proficient”criteria,andAssessesvariousERMsfortheirAssessesvariousERMsfortheirDoesnotassessvariousERMs7.92DesignApplicabilityassessmentdemonstratesadesignapplicabilitytothedesignapplicabilitytothefortheirdesignapplicabilitytocomplexgraspofthedesigndatabasedesign(85%)databasedesign,butthedatabasedesign(0%)applicabilityofERMs(100%)assessmentiscursoryorillogicalorcontainsinaccuracies(55%)ConceptualDesign:Meets“Proficient”criteria,andDeterminestheappropriateDeterminesanERMandDoesnotdetermineanERMor7.92AppropriateERMexplanationprovidescogentERMandexplainsthechoiceexplainsthechoice,butexplainthechoice(0%)reasoningforchoosingan(85%)determinationisinappropriate,appropriateERM(100%)orexplanationiscursoryorillogicalorcontainsinaccuracies(55%)5 ConceptualDesign:DataSetsDesignRevision:ERDDesignRevision:PrimaryandForeignKeysDesignRevision:TableRelationshipsDesignRevision:DataTypesandSizesIdentifiesthedatasetsfortheIdentifiesthedatasetsfortheDoesnotidentifythedatasets7.92database,includingallentitiesdatabase,butidentificationisforthedatabase(0%)andattributes(100%)incomplete,containsinaccuracies,orlacksinclusionofallentitiesandattributes(55%)ConstructstheERD,utilizingConstructstheERD,butDoesnotconstructtheERD5.94theidentifiedentitiesanddiagramisincomplete,contains(0%)attributes(100%)inaccuracies,orlacksalltheidentifiedentitiesandattributes(55%)DeterminesappropriateDeterminesprimaryorforeignDoesnotdetermineprimary5.94primaryandforeignkeysforkeysforentitiesandnotesandforeignkeysornotethemeachentityandnotesthemonthemontheERD,butontheERD(0%)theERD(100%)determinationisillogicalorincompleteorcontainsinaccuracies,ornotationisincompleteorcontainsinaccuracies(55%)DeterminestablerelationshipsDeterminestablerelationshipsDoesnotdeterminetable5.94andnotesthemontheERDandnotesthemontheERD,relationshipsornotesthemon(100%)butdeterminationisillogicalortheERD(0%)incompleteorcontainsinaccuracies,ornotationisincompleteorcontainsinaccuracies(55%)DeterminesappropriatedataDeterminesdatatypesorsizesDoesnotdeterminedatatypes5.94typesandsizesforeachforattributesandnotesthemandsizesforattributesornoteattributeandnotesthemonontheERD,butdeterminationthemontheERD(0%)theERD(100%)isillogicalorincompleteorcontainsinaccuracies,ornotationisincompleteorcontainsinaccuracies(55%)6 DesignRevision:CompletesthenormalizationCompletesthenormalizationDoesnotcompletethe7.92NormalizationprocessutilizingdependencyprocessutilizingdependencynormalizationprocessutilizingProcessdiagramsinordertoprovediagrams,buttablesarenotindependencydiagrams(0%)tablesareinthirdnormalform3NF,orERDisinappropriately(3NF),andadjuststheERDifadjusted(55%)necessary(100%)DesignFinalization:DraftstherecommendedfinalDraftstherecommendedfinalDoesnotdraftthe7.92FinalERDERD,whichaccountsforanyERD,butdraftisincompleteorrecommendedfinalERD(0%)adjustmentsmadetoitsillogical,containsinaccuracies,elementsasdeterminedorlacksaccordancewithanythroughthenormalizationadjustmentsmadetotheERD’sprocess(100%)elementsasdeterminedthroughthenormalizationprocess(55%)DesignFinalization:Meets“Proficient”criteria,andSummarizestheprocessforSummarizestheprocessforDoesnotsummarizethe7.92Processsummaryisexceptionallycleardevelopingthedatabasedevelopingthedatabaseprocessfordevelopingtheandcontextualized(100%)design,includingandesign,butsummaryiscursory,databasedesign(0%)explanationfortheincomplete,orillogical,oritdeterminationsmadewhilecontainsinaccuraciesorlacksfillingintheERDandmakinganexplanationfortheadjustmentsafterdeterminationsmadewhilenormalization(85%)fillingintheERDandmakingadjustmentsafternormalization(55%)DesignFinalization:Meets“Proficient”criteria,andExplainshowthedesignwillExplainshowthedesignwillDoesnotexplainhowthe4.75AchieveEndResultexplanationprovidescogentallowthedatabasetoachieveallowthedatabasetoachievedesignwillallowthedatabaseconnectionsbetweentheendthedesiredendresult,thedesiredendresult,buttoachievethedesiredendresultofadatabaseandtheincludingconsiderationoftheexplanationiscursoryorresult(0%)userrequirements,businessuserrequirements,businessillogical,containsinaccuracies,processes,andrestrictionsprocesses,andrestrictionsorlacksconsiderationoftheconsideredinadesign(100%)(85%)userrequirements,businessprocesses,orrestrictions(55%)7 ArticulationofSubmissionisfreeoferrorsSubmissionhasnomajorerrorsSubmissionhasmajorerrorsSubmissionhascriticalerrors4.97Responserelatedtocitations,grammar,relatedtocitations,grammar,relatedtocitations,grammar,relatedtocitations,grammar,spelling,syntax,andspelling,syntax,ororganizationspelling,syntax,ororganizationspelling,syntax,ororganizationorganizationandispresented(85%)thatnegativelyimpactthatpreventunderstandingofinaprofessionalandeasy-to-readabilityandarticulationofideas(0%)readformat(100%)mainideas(55%)Total100%8