DirtBike Order Database– ER Diagram Prepared by (Rahul Dhami) Fall 2012.

Slides:



Advertisements
Similar presentations
Banking Business Scenario
Advertisements

ER Model For a college DB
Data Modeling. What are you keeping track of? You begin to develop a database by deciding what you are going to keep track of. Each thing that you are.
BUSINESS DRIVEN TECHNOLOGY Plug-In T4 Designing Database Applications.
McGraw-Hill/Irwin Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. Extended Learning Module C Designing Databases and Entity-Relationship.
Extended Learning Module C
© McGraw-Hill Companies, Inc., McGraw-Hill/Irwin Extended Learning Module C Designing Databases and Entity-Relationship Diagramming.
DirtBike Order Database– ER Diagram Prepared by Shaylee Thar Fall 2012.
Concepts of Database Management Seventh Edition Chapter 6 Database Design : ERD Model.
IT420: Database Management and Organization
Copyright © 2015 Pearson Education, Inc. Database Design Chapters 17 and
Extended Learning Module C Designing Databases and Entity-Relationship Diagramming McGraw-Hill/Irwin Copyright © 2010 by the McGraw-Hill Companies, Inc.
Database – Part 2a Dr. V.T. Raja Oregon State University.
APPENDIX C DESIGNING DATABASES
ER Diagram Notation. E-R Diagram: Chen Model Entity – represented by a rectangle with its name in capital letters. Relationships – represented by an active.
Chapter 5 Database Processing.
ระบบฐานข้อมูลขั้นสูง (Advanced Database Systems) Lecturer AJ. Suwan Janin Phone:
MIS2502: Data Analytics Coverting ERD into a DB Schema David Schuff
McGraw-Hill/Irwin Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. Extended Learning Module C Designing Databases and Entity-Relationship.
Principles of Database Design, Part II AIMS 2710 R. Nakatsu.
Next Back A-1 Management Information Systems for the Information Age Second Canadian Edition Copyright 2004 The McGraw-Hill Companies, Inc. All rights.
C-1 Management Information Systems for the Information Age Copyright 2004 The McGraw-Hill Companies, Inc. All rights reserved Extended Learning Module.
DirtBike Order Database– ER Diagram Prepared by (Your Name) Summer 2013.
Prepared by Trevor Scherlin Fall 2012 DIRTBIKE ORDER DATABASE– ER DIAGRAM.
An Entity Relationship (ER) Diagram is a graphic that shows the interrelationship between entities in a database.
 An entity-relationship diagram (ERD) is a specialized graphic that illustrates the interrelationships between entities in a database.
Prepared by Katie Girmus Fall Step 1: Define Entity Classes and Primary Keys Step 2: Define Relationships Among Entity Classes Step 3: Define Fields.
ENTITY RELATIONSHIP DIAGRAM ENTITY RELATIONSHIP DIAGRAM IS A SPECIALIZED GRAPHIC THAT ILLUSTRATES THE INTERRELATIONSHIPS BETWEEN ENTITIES IN A DATABASE.
Order Database – ER Diagram Prepared by Megan Foster Fall Semester 2014.
INTRODUCTION TO DATABASE DESIGN. Definitions Database Models: Conceptual, Logical, Physical Conceptual: “big picture” overview of data and relationships.
MIS2502: Data Analytics Relational Data Modeling
Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin APPENDIX C DESIGNING DATABASES APPENDIX C DESIGNING DATABASES.
DirtBike Order Database– ER Diagram Prepared by Dustin Withee Fall 2012.
* Database is a group of related objects * Objects can be Tables, Forms, Queries or Reports * All data reside in Tables * A Row in a Table is a record.
DirtBike Order Database– ER Diagram Prepared by Dyan Strausheim Fall 2012.
Order Database – ER Diagram Prepared by Bryan Borcher Spring 2014.
Test SEITA.
Conversion from ER diagram to relational model 1 ER is a visual model The relational model is a matemathical model.
ENTITY – RELATIONSHIP MODEL Melissa Ann D. Callejo Chairmane Abanilla.
Order Database – ER Diagram Prepared by Evan Hollister Spring 2016.
Data Base Design Steps 1.Define Entity Classes (Relations/Tables) and Keys. 2.Define Relationships between Entity Classes. Normalization Steps Eliminate.
DirtBike Order Database– ER Diagram Prepared by William Sircin Fall 2012.
©2005 The McGraw-Hill Companies, All rights reserved McGraw-Hill/Irwin
Order Database – ER Diagram
Roadmap Week 1: Intro to MIS Week 2: Systems Analysis
Entity Relationship Diagrams - 1
Information Systems in Organizations 2. 1
Order Database – ER Diagram
Information Systems in Organizations 2. 1
Order Database – ER Diagram
Order Database – ER Diagram
CSCI-100 Introduction to Computing
Information Systems in Organizations 2. 1
Order Database – ER Diagram
Information Systems in Organizations 2. 1
Information Systems in Organizations 2. 1
Information Systems in Organizations 2. 1
5.02 Understand database queries, forms, and reports used in business.
Information Systems in Organizations 2. 1
Entity-Relationship Modeling "Extended"
Information Systems in Organizations 2. 1
Information Systems in Organizations 2. 1
Order Database – ER Diagram
Entity Relationship Diagrams - 2
Order Database – ER Diagram
Information Systems in Organizations 2. 1
Information Systems in Organizations 2. 1
Information Systems in Organizations 2. 1
Entity-Relationship Modeling "Extended"
Entity-Relationship Modeling "Extended"
Presentation transcript:

DirtBike Order Database– ER Diagram Prepared by (Rahul Dhami) Fall 2012

Step 1: Define Entity Classes and Primary Keys Step 2: Define Relationships Among Entity Classes Step 3: Define Fields for each Relationship Step 4: Create Database Designing Databases with Entity Relationship Diagrams

Entity ClassPrimary Key CustomerCustomer ID OrderOrder ID ProductProduct ID DistributorDistributor ID Step 1: Define Entity Classes and Primary Keys Business Rules Each order is made by a single customer Each customer can have multiple orders Each customer can have on order Customers can be in your database without any orders Products can be listed in your database but not purchased Orders cannot be blank Orders can have more than one (multiple) products A distributor can supply multiple products A distributor has to supply at least one product Each product has to have a distributor

E-R Diagrams Use 5 symbols 1.Rectangle – entity class 2.Dotted line – relationship 3.| - single relationship 4.0 – zero/optional relationship 5.Crow’s foot (  ) – multiple relationship

PRODUCT CUSTOMER ORDER Step 2: Define Relationships Among Entity Classes DISTRIBUTOR Detailed Orders

Step 3: Define Fields for each Relationship Customer IDLastNameFirstNameAddressCityStateZipPhone ENTITY Product IDProduct Name ManufacturerMSRPIgnitionWeightQOHDistributor ID Product Order IDCustomer IDOrder Date Order Distributor IDDistributo r Order IDProduct IDQuantity Detailed Orders

Step 4: Create Database (At this point we will begin working with our DBMS system, which will be Microsoft Access)