Trusted by 2+ million users, 1000+ happy students everyday
Showing pages 1 to 3 of 8 pages
STUDENT NAME04 November, 2016ASSIGNMENT 2
ContentsINTRODUCTION.....................................................................................................................................2ASSUMPTIONS.......................................................................................................................................2DEPENDENCY DIAGRAM........................................................................................................................3ENTITY RELATIONSHIP DIAGRAM..........................................................................................................5RELATIONAL MODEL DIAGRAM.............................................................................................................61 | P a g e
INTRODUCTIONThe scenario is about a food delivery service which provides riders to deliver food from restaurant tothe customer. The system is a traditional paper system or we can say book keeping where all recordsare on paper. Hence this makes it very complex to manage the information on paper and avoid any errors. So the company has decided to get a database management system built for the use. The requirements of the company are to hold information about orders, menus, restaurants, customers, and riders. So to design this we gathered all the available data to create a visual design of the database. The design consists of the entities and the attributes that will be required to fulfil the user needs. From this design, another database design will be built. Although designing makes the entire processsimple that of actual implementation, still there we some difficulties faced. There were large numberof records. We also had to find a way in which all past paper records can be added uniquely to the system and still the information not being altered. Apart from that meeting the requirements in sucha way that future requirements are considered and added was also a complex task. But after careful analysis and designing, the diagrams below have been created.ASSUMPTIONSThe following assumptions were made1.Each menu item will belong to a category2.Category table will hold information about different categories of food like starters, deserts, main course etc.3.Each category will have unique id.4.Each customer will have a unique id5.Customer’s basic info will be stored.6.Each rider will have information in rider table with unique rider id7.Each menu id item will have a unique id2 | P a g e
Found this document preview useful?
You are reading a preview Upload your documents to download or Become a Desklib member to get accesss