Mid term Exam COVERS chapters 1-3, 7-8 Two parts In class Take home part (given on Oct 29 th, Due Nov5th in class)

Slides:



Advertisements
Similar presentations
Chapter # 4 BIS Database Systems
Advertisements

Developing ER-Diagram
Database Systems: Design, Implementation, and Management Tenth Edition
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.
Copyright © 2015 Pearson Education, Inc. Database Design Chapters 17 and
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Database Design (Data Modeling) DCO11310 Database Systems and Design By Rose Chang.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model.
CHAPTER 2: MODELING DATA IN THE ORGANIZATION © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition Jeffrey.
Chapter 4 Entity Relationship (ER) Modeling
Database Systems: Design, Implementation, and Management Tenth Edition
Chapter 4 Entity Relationship (E-R) Modeling
Lecture 3 Entity Relationship diagram (ERD) Cardinalities
Data Modeling 1 Yong Choi School of Business CSUB.
Data Modeling 1 Yong Choi School of Business CSUB.
CSE314 Database Systems Data Modeling Using the Entity- Relationship (ER) Model Doç. Dr. Mehmet Göktürk src: Elmasri & Navanthe 6E Pearson Ed Slide Set.
Chapter 13 (Online): Object-Oriented Databases
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.
Chapter 7 Data Modeling with Entity Relationship Diagrams Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition.
Chapter 4 The Relational Model.
Chapter 3 The Relational Model Transparencies Last Updated: Pebruari 2011 By M. Arief
Mid term Exam COVERS chapters 1-3, 7-8 Two parts In class Take home part (given on Oct 29 th, Due Nov5th in class)
Introduction to Accounting Information Systems
2 1 Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Database Systems: Design, Implementation, and Management Ninth Edition
9/14/2012ISC329 Isabelle Bichindaritz1 Database System Life Cycle.
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )
4 1 Chapter 4 Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Rob and Coronel Adapted for INFS-3200.
Database Design Principles – Lecture 3
1 Relational Databases and SQL. Learning Objectives Understand techniques to model complex accounting phenomena in an E-R diagram Develop E-R diagrams.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 4 Entity Relationship (ER) Modeling.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
Database Design – Lecture 5 Conceptual Data Modeling – adding attributes.
3 & 4 1 Chapters 3 and 4 Drawing ERDs October 16, 2006 Week 3.
1 A Demo of Logical Database Design. 2 Aim of the demo To develop an understanding of the logical view of data and the importance of the relational model.
Database Systems: Design, Implementation, and Management Ninth Edition Chapter 4 Entity Relationship (ER) Modeling.
AL-MAAREFA COLLEGE FOR SCIENCE AND TECHNOLOGY INFO 232: DATABASE SYSTEMS CHAPTER 4 ENTITY RELATIONSHIP (ER) MODELING Instructor Ms. Arwa Binsaleh 1.
Chapter 4 The Semantic Object Model David M. Kroenke Database Processing © 2000 Prentice Hall.
CIS 210 Systems Analysis and Development Week 6 Part I Structuring Systems Data Requirements,
Slide 4-1 Elmasri and Navathe, Fundamentals of Database Systems, Fourth Edition Revised by IB & SAM, Fasilkom UI, 2005 Exercise 1. a property or description.
Chapter 3: Modeling Data in the Organization. Business Rules Statements that define or constrain some aspect of the business Assert business structure.
Detailed Data Modeling. Outline Data Modeling Modeling Constructs –Entities –Relationships –Cardinality Model Basic Rules Advanced Rules Prototyping Process.
2 1 Database Systems: Design, Implementation, & Management, 7 th Edition, Rob & Coronel Data Models Why data models are important About the basic data-modeling.
CSCI 6315 Applied Database Systems Review for Midterm Exam I Xiang Lian The University of Texas Rio Grande Valley Edinburg, TX 78539
Department of Mathematics Computer and Information Science1 CS 351: Database Management Systems Christopher I. G. Lanclos Chapter 4.
Enhanced Entity-Relationship and UML Modeling. 2.
LECTURE TWO Introduction to Databases: Data models Relational database concepts Introduction to DDL & DML.
Data Modeling Using the Entity- Relationship (ER) Model
Database Systems: Design, Implementation, and Management Tenth Edition
Entity Relationship Diagram
Conceptual Design & ERD Modelling
TMC2034 Database Concept and Design
CS311 Database Management system
Database Design – Lecture 4
Database Management system
CS 174: Server-Side Web Programming February 12 Class Meeting
Chapter 4 Entity Relationship (ER) Modeling
Database Systems: Design, Implementation, and Management Tenth Edition
LIS 384K.11 Database-Management Principles and Applications
CHAPTER 4: LOGICAL DATABASE DESIGN AND THE RELATIONAL MODEL
Database Modeling using Entity Relationship Model (E-R Model)
Review of Week 1 Database DBMS File systems vs. database systems
Chapter 4 Entity Relationship (ER) Modeling
Entity-Relationship Diagram (ERD)
Entity Relationship (ER) Modeling
Chapter # 4 Entity Relationship (ER) Modeling.
Presentation transcript:

Mid term Exam COVERS chapters 1-3, 7-8 Two parts In class Take home part (given on Oct 29 th, Due Nov5th in class)

System catalogs Information about database It is automatically created everytime a database is created It contains tables like: Systables Syscolumns Sysindexes Sysviews

In ORACLE User_catalog SQL> desc user_catalog; Name Null? Type TABLE_NAME NOT NULL VARCHAR2(30) TABLE_TYPE VARCHAR2(11) Select * from user_catalog;

USER_TABLES User_objects User_tab_columns User_views You can query using select statements

To get constraints SQL> select owner, constraint_type from user_constraints where table_name ='WROTE'; 2 3 OWNER C AGGARWAL P AGGARWAL R Note P for primary R for referential

Systables in ORACLE tips.com/viewthread.cfm?qid= &page=3 there is no such object as systables in oracle. What you are looking for is dba_tables - All tables in system, only visible to administrators all_tables - All tables in all schema's that the connected user has access to. user_tables - all tables in the connected users schema.oracle Bill Oracle DBA/Developer

Ch 4 Entity Relationship (ER Modeling)

Business rules Business rules are precise statements, derived from a detailed description of the organization's operations. When written properly, business rules define one or more of the following modeling components: –entities –relationships –attributes –connectivities –cardinalities –constraints

Because the business rules form the basis of the data modeling process, their precise statement is crucial to the success of the database design. because the business rules are derived from a precise description of operations, design's success depends on the accuracy of the description of operations.

Examples of business rules are: An invoice contains one or more invoice lines. Each invoice line is associated with a single invoice. A store employs many employees. Each employee is employed by only one store. A college has many departments. Each department belongs to a single college. (This business rule reflects a university that has multiple colleges such as Business, Liberal Arts, Education, Engineering, etc.) A driver may be assigned to drive many different vehicles. A client may sign many contracts. Each contract is signed by only one client.

DATA MODEL Representation of complex real-world. Goal is to create a DB that is accurate representation of data needs and real world data relationships A good DB design begins with a good data model..a method for determining "WHAT" data and relationships should be stored in DB and not "HOW" data will be stored or processed Hardware/software indep. –..development is an iterative process

THE E-R Model: (P 124) Translates different data view into a common framework Defines data processing and constraints requirements Peter Chen (1976) was the first person to introduce the concept of ER modeling. An ER model is a detailed logical representation for an organization ER Building Blocks (p 124)

ENTITIES & ATTRIBUTES Entities: –An object of interest –Person –Place –Event –concept –An entity type consists of entity instances Attributes –Properties of an entity –Describes an entity –Attributes have DOMAINS. –Domain is a set of possible values. Two attributes can share the –same domain

Derived Attributes: These are calculated or extracted from other attributes Ex: total sales Typically a derived field is not stored in the DB, calculated as needed

Relationship: Association between entities 1:1 1:m m:n Unary...within itself Binary..with two entities Ternary..with three entities Unary (recursive): Entity has a relationship to itself 1:1 1:m m:n

Super & sub type entities (used extensively in Object oriented systems) One challenge is to RECOGNIZE and represent entities that are almost the same, i.e., the share some properties but also have distinct properties

Ex: COMPUTER Mainframe Minicomputer personal EMPLOYEE Full time Part time Relationship: IS-A super, sub entity relationships are of the type “IS A”; –Ex: full time employee “IS AN” employee HAS-A: between two entities..STUDENT “HAS A” relationship with CLASS

Inheritance All attributes of a super type become attributes of the subtype Each attribute should be located at the highest level in the hierarchy

CARDINALITY (useful in getting approximate database size) (MIN and Max) Number of instances of one entity that can be associated with each instance of the other entity Place the appropriate number beside the entity Minimum Maximum Student class (1,6) (1,40) student _ _> major patient_------_> pat_history

Database name: Ch03_BeneCo Table name: EMPLOYEETable name: BENEFIT Table name: JOB Table name: PLAN Draw the ERD

Example if you were to develop an ER model for a video rental store, you would note that tapes can be rented more than once and that customers can rent more than one tape.

Q1/136 Entities COMPANY DEPARTMENT DEPENDENT EMPLOYMENT HISTORY

Q2/p136