Component 4/Unit 6b Topic II Relational Databases Keys and relationships Data modeling Database acquisition Database Management System (DBMS) Database.

Slides:



Advertisements
Similar presentations
Chapter # 4 BIS Database Systems
Advertisements

Chapter 2 Entity-Relationship Data Modeling: Tools and Techniques
Data Modeling and the Entity-Relationship Model
Data Modeling and the Entity-Relationship Model
Entity Relationship (ER) Modeling
Database Processing: Fundamentals, Design, and Implementation, 9/e by David M. KroenkeChapter 5/1 Copyright © 2004 Please……. No Food Or Drink in the class.
Ch5: ER Diagrams - Part 1 Much of the material presented in these slides was developed by Dr. Ramon Lawrence at the University of Iowa.
Entity Relationship (ER) Modeling
4 1 Chapter 4 Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 4 Entity Relationship (ER) Modeling.
IT420: Database Management and Organization
Entity-Relationship Model
Data Modeling and the Entity-Relationship Model
Data Modeling and the Entity-Relationship Model
Concepts of Database Management Sixth Edition
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 COS 346 Day 6.
Fundamentals, Design, and Implementation, 9/e COS 346 Day 8.
Fundamentals, Design, and Implementation, 9/e Chapter 5 Database Design.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 David M. Kroenke Database Processing Tenth Edition Chapter 5 Data.
Chapter Five Data Modeling with the Entity-Relationship Model.
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 COS 346 Day 6.
Data Modeling Entity - Relationship Models. Models Used to represent unstructured problems A model is a representation of reality Logical models  show.
Fundamentals, Design, and Implementation, 9/e COS 346 Day 2.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 David M. Kroenke’s Chapter Five: Data Modeling with the Entity-Relationship.
Data Modeling and the Entity-Relationship Model Chapter Four DAVID M. KROENKE and DAVID J. AUER DATABASE CONCEPTS, 5 th Edition.
Concepts of Database Management Seventh Edition
Chapter 4 Entity Relationship (ER) Modeling
Database Systems: Design, Implementation, and Management Tenth Edition
Entity-Relationship Model
Chapter 4 Entity-Relationship modeling Transparencies © Pearson Education Limited 1995, 2005.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 David M. Kroenke’s Chapter Five: Data Modeling with the Entity-Relationship.
Chapter 5 Database Processing.
ระบบฐานข้อมูลขั้นสูง (Advanced Database Systems) Lecturer AJ. Suwan Janin Phone:
1. 2 Data Modeling 3 Process of creating a logical representation of the structure of the database The most important task in database development E-R.
4 1 Chapter 4 Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
IS 325 Notes for Wednesday September 4, Syllabus Change I eliminated quizzes I increased the points allocated to homework assignments.
Database Processing: Fundamentals, Design and Implementation, 9/e by David M. KroenkeChapter 2/1 Copyright © 2004 Please……. No Food Or Drink in the class.
4 1 Chapter 4 Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
Component 4: Introduction to Information and Computer Science Unit 6: Databases and SQL Lecture 2 This material was developed by Oregon Health & Science.
Component 4: Introduction to Information and Computer Science Unit 6: Databases and SQL Lecture 4 This material was developed by Oregon Health & Science.
Concepts of Database Management Sixth Edition Chapter 6 Database Design 2: Design Method.
© Pearson Education Limited, Chapter 7 Entity-Relationship modeling Transparencies.
Entity-Relationship Modeling Based on Chapter 12.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall, modified by Dr. Lyn Mathis 5-1 David M. Kroenke’s, 10 th ed. Chapter.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 4 Entity Relationship (ER) Modeling.
Chapter 4 Entity Relationship (ER) Modeling.  ER model forms the basis of an ER diagram  ERD represents conceptual database as viewed by end user 
Data Modeling IST210 Class Lecture.
3 & 4 1 Chapters 3 and 4 Drawing ERDs October 16, 2006 Week 3.
Chapter 9: Logical Database Design and the Relational Model (ERD Mapping)
Component 4: Introduction to Information and Computer Science Unit 6a Databases and SQL.
1 © Prentice Hall, 2002 Chapter 5: Logical Database Design and the Relational Model Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B.
Database Systems: Design, Implementation, and Management Ninth Edition Chapter 4 Entity Relationship (ER) Modeling.
Component 4/Unit 6d Topic IV: Design a simple relational database using data modeling and normalization Description and Information Gathering Data Model.
Databases Illuminated Chapter 3 The Entity Relationship Model.
AL-MAAREFA COLLEGE FOR SCIENCE AND TECHNOLOGY INFO 232: DATABASE SYSTEMS CHAPTER 4 ENTITY RELATIONSHIP (ER) MODELING Instructor Ms. Arwa Binsaleh 1.
1 DATABASE TECHNOLOGIES (Part 2) BUS Abdou Illia, Fall 2015 (September 9, 2015)
Entity-Relationship Modeling. 2 Entity Type u Entity type –Group of objects with same properties, identified by enterprise as having an independent existence.
Chapter 8 Entity-Relationship Modeling Pearson Education © 2009.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Chapter Five: Data Modeling with the Entity-Relationship.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Appendix H: The Semantic Object Model.
Lecture # 14 Chapter # 5 The Relational Data Model and Relational Database Constraints Database Systems.
Copyright © 2014 Pearson Canada Inc. 5-1 Copyright © 2014 Pearson Canada Inc. Application Extension 5a Database Design Part 2: Using Information Technology.
Chapter 5 Database Design
Requirements Become the E-R Data Model
Tables and Their Characteristics
Review of Week 1 Database DBMS File systems vs. database systems
Database Processing: David M. Kroenke’s Chapter Five:
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
Presentation transcript:

Component 4/Unit 6b Topic II Relational Databases Keys and relationships Data modeling Database acquisition Database Management System (DBMS) Database development

Connecting Data Candidate keys Primary key – Natural key – Surrogate key Foreign key Relationship Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Data Modeling: Database Design Entities Entity-relation diagram (ER diagram) Maximum cardinality of the relationship Attributes Crow’s foot diagrams Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Database Acquisition Data is stored in and retrieved from a database by using SQL (Structured Query Language) Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

The Database Management System (DBMS) Metadata Administration of the database Carries out SQL statements and procedures Stored procedures Triggers Security (permissions) Handles processing problems Carries out backup & restore/recovery Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Database Development From scratch – Existing data – Data model eventually becomes DB design – Merge existing databases Modification of existing database – Most databases have already been developed Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Phases of Database Development 1.Gathering specifications 2.Design – Data modeling to Database design 3.Testing 4.Implementation 5.Maintenance 6.Modification (starts process all over again) Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Gathering Specifications Attribute domains – Data type, length, legitimate values Business rules Input from users Forms and reports Existing files Outcome of this phase is a beginning data model Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Design More definitive specifications are gathered The data model is perfected toward the database design Entities become tables Candidate keys are identified and finally primary keys are chosen Attributes are added subtracted as needed Finally relationships are indicated with the addition of foreign keys Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Multiple Views of the Database Each user will have a different need/view of the database Forms, files and reports will all be of different views of the database All views of the database need to be resolved into the data model. The data model will not look like any one of the views. Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Testing First evaluate design Confirm that data model contains all the information that users will need – Converse with users – Show them data model – Express “known” facts to users Users can make objections Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Implementation Database is created Tables are created with attributes, primary and foreign keys – This completes the relationships between tables. Business rules are carried out – SQL procedures – Triggers – Built-in DBMS features Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

DBMS Restrictions The database design may have to be adjusted to meet with any database DBMS restrictions. Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Testing Again The database is populated with real and/or test data SQL is written that accommodates what the users have requested and the SQL is run against the database Bad results means that the database must be fixed. This can mean going all the way back to the design phase or it could be something more elementary Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Entity Relationship model ER model (Peter Chen, 1976) Extended ER model Information Engineering (IE) (James Martin, 1990) or Crow’s foot version of ER Model Integrated Definition 1, Extended Version (IDEF1X) – government standard National Institute of STDs and Technology (NIST) 1993 Unified Modeling Language (UML) Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Entities Potential table Things that the user needs to keep track of – People, places, things, documents Object Classes (idea) – Actual occurrence is an instance of an entity class Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Attributes Descriptors of entities Have to have a direct relationship with the entity. – Customer entity might have customer name as an attribute Can be shown in entity relationship model as balloons or be listed under the entity name. Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Attributes Continued Composite attributes Multi-value attributes Attribute domains Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Attributes Continued Identifiers Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Primary Keys Primary key is the way to uniquely define a record – It must be unique within the table column. Composite key sometimes is necessary. – It’s more efficient if it’s short and numeric – It should not change (at least not often) Natural vs. Surrogate keys – A natural primary key should be something that the user is familiar with and/or is readily available. Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Relationship Classes One-to-one One-to-many Many-to-many Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Relationships Maximum cardinality Parent-Child Minimum cardinality Recursive relationship Weak and strong entities ID shared relationship Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Relationships Continued Subtype and super type entities – Inheritance – Discriminator – Exclusive Vs Inclusive (Crow’s Foot) – Complete Vs Incomplete (IDEF1X) Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall

Relationships Continued Naming a relationship – Used to distinguish two relationships between the same two entities – Used to help clarify the relationship – Can be made up of a short phrase that describes the parent to child relationship followed by a short phrase that describes the child to parent relationship. Component 4/Unit 6b Health IT Workforce Curriculum Version 1.0/Fall