Prepared by Katie Girmus Fall 2012. Step 1: Define Entity Classes and Primary Keys Step 2: Define Relationships Among Entity Classes Step 3: Define Fields.

Slides:



Advertisements
Similar presentations
Connection Patterns & Functions.2
Advertisements

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.
Extended Learning Module C Designing Databases and Entity-Relationship Diagramming McGraw-Hill/Irwin Copyright © 2010 by the McGraw-Hill Companies, Inc.
RELATIONSHIP  THE WAY TABLES ARE RELATED  A TABLE MUST PARTICIPATE IN AT LEAST ONE RELATIONSHIP  IN A BINARY RELATIONSHIP TWO ENTITIES PARTICIPATE 
Database Design Chapter 2. Goal of all Information Systems  To add value –Reduce costs –Increase sales or revenue –Provide a competitive advantage.
The Computer Super Store A Sample Presentation Depicting the Requirements of Your Group Project.
Database – Part 2a Dr. V.T. Raja Oregon State University.
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.
Microsoft Access Review for Access Exam. Columns are called FIELDS Rows are called RECORDS Navigation Pane:  On left; used to organize DB objects  Collapsable.
ระบบฐานข้อมูลขั้นสูง (Advanced Database Systems) Lecturer AJ. Suwan Janin Phone:
Creating Entity Relationship Diagrams. Identify data stores The data stores are easy to identify if you have already created a data flow diagram If you.
CITY UNIVERSITY / Vysoká Škola Manažmentu.:IS Information Systems :. © Martina Cesalova, 2005 MS ACCESS 1 Start Microsoft Access – New - Blank Database.
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.
DATABASES Pindaro Demertzoglou – Lally School of Management and Technology.
MIS 301 Information Systems in Organizations Dave Salisbury ( )
MIS 301 Information Systems in Organizations Dave Salisbury ( )
IT354 Database Design Seminar 5: May 19, 2011 Physical Database Design Entity-Relationship Diagrams.
1.NET Web Forms Business Forms © 2002 by Jerry Post.
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.
Forms and Subforms 5.02 Understand database queries, forms, and reports used in business.
All Powder Board and Ski Microsoft Access Workbook Chapter 3: Database Tables Jerry Post Copyright © 2003.
Order Database – ER Diagram Prepared by Megan Foster Fall Semester 2014.
CS263 Lecture 5: Logical Database Design Can express the structure of a relation by a Tuple, a shorthand notation Name of the relation is followed (in.
MIS 301 Information Systems in Organizations Dave Salisbury ( )
1 DATABASE TECHNOLOGIES (Part 2) BUS Abdou Illia, Fall 2015 (September 9, 2015)
DirtBike Order Database– ER Diagram Prepared by (Rahul Dhami) Fall 2012.
DirtBike Order Database– ER Diagram Prepared by Dustin Withee Fall 2012.
data modeling with visio
* 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.
Exploring Microsoft Access Chapter 5 One-to-Many Relationships: Subforms and Multiple Table Queries.
IST 220 – Intro to Databases Database Design I. DB Design – Sports League The league needs to keep track of Teams Players Coaches Sponsors How many tables.
Order Database – ER Diagram Prepared by Bryan Borcher Spring 2014.
Teanna Clarke 6aQ What is a Entity-Relationship Diagram?  An Entity-Relationship Diagram (ERD) is a tool that graphically shows the connections among.
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
Creating a Relational Database
Order Database – ER Diagram
How to: SQL By: Sam Loch.
Database Constraints Ashima Wadhwa.
Entity Relationship Diagrams - 1
Information Systems in Organizations 2. 1
Order Database – ER Diagram
Order Database – ER Diagram
Order Database – ER Diagram
Order Database – ER Diagram
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
Information Systems in Organizations 2. 1
Customer Order Entry Database Version: 1.1 by: R. Holowczak
Order Database – ER Diagram
Entity Relationship Diagram Prepared by: Lobna Morsy
Order Database – ER Diagram
ER Diagram Master How to use this template
Information Systems in Organizations 2. 1
MIS2502: Data Analytics Relational Data Modeling 3
Presentation transcript:

Prepared by Katie Girmus 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 CustomerCustomerID OrderOrderID ProductProductID DistributorDistID 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 one 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 multiple products A distributor can supply multiple products A distributor has to supply at least one product Each product has to have a distributor

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 CustomerID LastNameFirstNameAddressCityStateZipPhone Customer OrderID CustomerIDOrderDate Order ProductID ProductName 255 Manufacturer 255 Color 50 MSRP Currency Ignition 50 Weight Number QOH Number DistID Number Product DistID Number Distributor 255 Distributor OrderID Number ProductID Number Quantity Number Detailed Orders

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