1 Class Agenda – 09/20/2011  Answer questions about exam  Evaluate database design homework  Review database design homework for syntax and logic 

Slides:



Advertisements
Similar presentations
ENTITY RELATIONSHIP MODELLING
Advertisements

GCSE Computing#BristolMet Session Objectives# 21 MUST describe methods of validating data as it is input. SHOULD explain the use of key fields to connect.
Chapter 5 Understanding Entity Relationship Diagrams.
DBS201: Introduction to Normalization
ISMT221 Information Systems Analysis and Design Entity-Relationship Diagram Lab 4 Tony Tam.
Fundamentals, Design, and Implementation, 9/e COS 346 Day 8.
Entity Relationship Diagrams Basic Elements and Rules.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Data.
Agenda for Week 1/31 & 2/2 Learn about database design
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 5 Understanding Entity Relationship Diagrams.
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 6 Developing Data Models for Business Databases.
Entity Relationship Diagrams
SLIDE 1IS Fall 2002 Database Management: Discussion Session University of California, Berkeley School of Information Management and.
The Relational Database Model. 2 Objectives How relational database model takes a logical view of data Understand how the relational model’s basic components.
System Analysis and Design
3 1 Chapter 3 The Relational Database Model Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Database – Part 2a Dr. V.T. Raja Oregon State University.
WJEC Applied ICT Databases – Attributes & Entities Entities A database contains one or more related tables. Each table holds all of the information.
Entity Relationship Modeling Objectives: To illustrate how relationships between entities are defined and refined. To know how relationships are incorporated.
Class Agenda – 04/04/2006 Discuss database modeling issues
The Relational Database Model
File and Database Design SYS364. Today’s Agenda WHTSA DBMS, RDBMS, SQL A place for everything and everything in its place. Entity Relationship Diagrams.
Database Design Concepts
U:/msu/course/cse/103 Day 10, Slide 1 Multiple Table Database Review What are entities? What are records ? What are attributes?
Data Modelling – ERD Entity Relationship Diagram’s Entity Relationship Diagrams and how to create them. 1.
The REA Model. The REA model provides structure for developing an accounting database It helps to identify It helps to The REA Model.
CTFS Workshop Shameema Esufali Suzanne Lao Data coordinators and technical resources for the network
PLUG IT IN 3 Fundamentals of Relational Database Operations.
The Relational Database Model
Chapters 15 &16 Conceptual and Logical Database Design Methodology.
IS 475/675 - Introduction to Database Design
1 Entity-Relationship Diagram. 2 Components of ERD: –Entity –Relationship –Cardinality –Attributes.
3 & 4 1 Chapters 3 and 4 Drawing ERDs October 16, 2006 Week 3.
2141-W2013 Mid-term Prep. Next week Monday, Feb 18 – Midterm Covers everything before normalization Wednesday, Feb 20 – Ass 3 (normalization) due – Wrap.
Chapter 9: Logical Database Design and the Relational Model (ERD Mapping)
Btec National - Advanced Databases 1 Advanced Databases Entity Relationship Diagrams.
Jozef Kuper.  Describe a Database  Entities  Atributes  Relationships.
3 1 Chapter 3 The Relational Database Model Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Relational Theory and Design
File and Database Design Class 22. File and database design: 1. Choosing the storage format for each attribute from the logical data model. 2. Grouping.
Database Design – Lecture 4 Conceptual Data Modeling.
INTRODUCTION TO DATABASE DESIGN. Definitions Database Models: Conceptual, Logical, Physical Conceptual: “big picture” overview of data and relationships.
CTFS Workshop Shameema Esufali Asian data coordinator and technical resource for the network
1 Class Agenda (04/06/2006 and 04/11/2006)  Discuss use of Visio for ERDs  Learn concepts and ERD notation for data generalization  Introduce concepts.
CMPT 258 Database Systems Midterm Review. Regarding the Exam Oct 15 Thursday Close book Cheat sheet (1 side of an A4 paper)
* 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.
Btec National - IT SYSTEMS ANALYSIS AND DESIGN 1 IT Systems Analysis and Design Entity Relationship Diagrams.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 3 The Relational Database Model.
September 23 Objective: To know the significance of various molecules involved in metabolic processes and energy conversions that occur in living organisms.
Ch 05. Basic Symbols ( manino ). Cardinalities Cardinality Notation.
Tutorial on E-R Diagrams 1.Learn basic terminology and symbols –See next four slides; refer to as needed in steps 2-4 below 2.Learn the basics of E-R diagramming.
Week 2 Lecture The Relational Database Model Samuel ConnSamuel Conn, Faculty Suggestions for using the Lecture Slides.
5 1 Normalization of Database Tables. 5 2 Database Tables and Normalization Normalization –Process for evaluating and correcting table structures to minimize.
Chapter 5 Understanding Entity Relationship Diagrams.
Hoi Le. Why database? Spreadsheet is not good to: Store very large information Efficiently update data Use in multi-user mode Hoi Le2.
What Is Normalization  In relational database design, the process of organizing data to minimize redundancy  Usually involves dividing a database into.
MIDTERM REVIEW IST 210 Organization of Data IST210 1.
ERD :: 19 / 1 / Entity-Relationship (ER) Modeling. ER Modeling is a top-down approach to database design. Entity Relationship (ER) Diagram –A.
Database Design, Application Development, and Administration, 6 th Edition Copyright © 2015 by Michael V. Mannino. All rights reserved. Chapter 5 Understanding.
IT 5433 LM3 Relational Data Model. Learning Objectives: List the 5 properties of relations List the properties of a candidate key, primary key and foreign.
DEVRY CIS 321 iLab 4 Check this A+ tutorial guideline at For more classes visit
Entity Relationship Modeling
Data Modelling Chapter 7
ERD :: 19 / 1 / Entity-Relationship (ER) Modeling. ER Modeling is a top-down approach to database design. Entity Relationship (ER) Diagram –A.
Relational Model and ER Model: in a Nutshell
Order Database – ER Diagram
The 1:M Relationship (continued)
מודל הנתונים.
DATABASE SYSTEM.
Presentation transcript:

1 Class Agenda – 09/20/2011  Answer questions about exam  Evaluate database design homework  Review database design homework for syntax and logic  Finish class ERD exercise from 9/13??  Demonstrate Visio

2 Evaluate design homework  Break into groups as assigned  Everyone takes out a sheet of paper  Exchange assignments  Put your name (as the “evaluator”)at the top of the sheet of paper  Evaluate the syntax and logic of the designs  Make your comments on the sheet of paper

3 “Syntax” Database Modeling Issues  Does the diagram contain entities, attributes, primary keys and relationships?  Is it structured using the modeling format discussed in this class? (see next slide for modeling format)  Does each entity have a primary key? Is the primary key labeled as a primary key?  Is each relationship labeled with a verb or verb phrase?  Does each relationship have a foreign key? Is the foreign key labeled as a foreign key?

5 “Logic” Database Modeling Issues  Is all necessary data represented on the model? What’s missing?  Is the data grouped correctly with the appropriate entity?  Does each entity have a primary key that will yield a unique value for each row?  Is the primary key reasonable (not too many not too few attributes?)  Are the entities related accurately?  Are the cardinalities of the relationships accurate?  Are there any M:N relationships?  Are the foreign keys accurate and is each placed in the correct entity to sustain a relationship?  Will the design yield redundant data?