Rationale & Assumption
11 Pages1212 Words460 Views
Added on 2019-09-13
Rationale & Assumption
Added on 2019-09-13
ShareRelated Documents
[Type the documenttitle]Student Name: Student ID: Course Name: Course ID:Faculty Name: University Name:
1ContentsTaskT1: EERD.................................................................................................................................2TaskT2: Rationale & Assumption...................................................................................................2TaskT3: Data Dictionary.................................................................................................................3TaskT4: SQL Tables Create Commands.........................................................................................6
2TaskT1: EERDTaskT2: Rationale & AssumptionI have designed database according to internal system. I have assumed that no duplicate dataentered in database. This is assumed that the staff will be medical staff who assists theparticipants during events. If there are more than one departments in the event ManagementCompany then they can be added in database later, to do this a separate table department iscreated. Here are only two types of events that company arranged race and walk. So a separatetable is not designed for this. There is an event table to store the total events with the eventrelated details. Client table is created to store the details for all sponsors who are associate withthe company. These sponsors invest money to start an event. There is a table which is created forparticipants this table store the participants details like name, two emergencies contact, addressand dietary requirements and total paid amount for the event. A volunteers table is created tostore the volunteer’s details like name, contact, email address and their daily wedges.Event_Medical_Locations table store all the medical centers which are available for this event.Event_Winner table store the winners details in the event_winner table, this table store thewinner rank, winner won medal.
3TaskT3: Data DictionaryTable: EVENTColumn NameDataTypeConstraintseventIDINTPRIMARY KEYeventTypeENUM('RACE','WALK') NOT NULLstartDateTimeTIMESTAMPNOT NULLendDateTimeTIMESTAMPNOT NULLstartLocationVARCHAR(60)NOT NULLendLocationVARCHAR(60)NOT NULLrouteInformationVARCHAR(100)NOT NULLexpectedCostDOUBLENOT NULLactualCostDOUBLENOT NULL
End of preview
Want to access all the pages? Upload your documents or become a member.
Related Documents
Sql Join Columns of Two Tables on Unique Keylg...
|10
|981
|431
Event Management System SQL Tables and Commandslg...
|7
|553
|254