Example 2 – Schemas ES1 and ES2 Student(studentId, name, address, tutorId) Staff(tutorId, name, deptName) Lecturer(lecturerId, name, deptName) Course(courseId,

Slides:

Advertisements

Similar presentations

ER Model For a college DB

Advertisements

Aims and benefits of a structured approach to personal tutoring in professional healthcare programmes Mike McIvor Lecturer Department of Inter-professional.

ZEIT2301 Design of Information Systems Relational Database Schema School of Engineering and Information Technology Dr Kathryn Merrick.

Teaching and Learning Programme at Bristol University.

Database Design (Data Modeling) DCO11310 Database Systems and Design By Rose Chang.

Name A A R H U S U N I V E R S I T E T Department The University’s organisation.

2008/1/161 Extended Entity Relationship(EER) Model The ER model has been widely used but does not have some shortcomings. It is difficult to represent.

Entity PrimaryKey Attribute relationship Cardinality: zero to many Cardinality: one and only one Cardinality: one to many Explanation Entity Relationship.

©Silberschatz, Korth and Sudarshan3.1Database System Concepts - 6 th Edition SQL Schema Changes and table updates instructor teaches.

Chapter 4 Tutorial.

Entity/Relationship Modelling

Databases Tom Morgan.

Data Definition, Relational Manipulation and Data Control Using SQL.

SQL Operations Aggregate Functions Having Clause Database Access Layer A2 Teacher Up skilling LECTURE 5.

COURSE REGISTRATION SYSTEM Case study IST2101. Case Study: Course Registration (1) IST2102 You are helping Penn State create a course registration system.

Subqueries. So far when data has been filtered the filter has been known and simply added to the Where clause but often you don’t know what the filter.

July 12, 2011 Kansas State Department of Education Personal Financial Literacy.

Database Design II (Case Studies: Step 2) IST 210: Organization of Data IST2101.

CS 3630 Database Design and Implementation. 2 Mathematical Relation A mathematical relation is a subset of a Cartesian Product. A1  A2  A3  …  An.

Deanery of Business & Computer Sciences Transformation of Logical Diagram into Database Design Language Lecture 6 Database Technology Level.

Schema Refinement and Normal Forms 20131CS3754 Class Notes #7, John Shieh.

IST 210: ORGANIZATION OF DATA Chapter 1. Getting Started IST210 1.

Normalization Process: Exercise 1: Step 1 IST2101 Step 1. Identify all the candidate keys of the relation. StudentNumber.

©Silberschatz, Korth and Sudarshan1Database System Concepts - 6 th Edition E-R Diagram for a University Enterprise.

1 Mathematical Relation A mathematical relation is a subset of a Cartesian Product. A1  A2  A3  …  An = {(x1, x2, x3, …, xn): xi  Ai} R  A1  A2.

ITEC 3220A Using and Designing Database Systems Instructor: Gordon Turpin Course Website: Office: CSEB3020.

Relational Algebra – Constraints CIS 4301 Lecture Notes Lecture /02/2006.

GEOG3025 Introduction to online resources. GEOG3025 Introduction to online resources Lecture overview: Objectives of lecture Introductory questions Registration.

Chapter 2. The Relational Model (cont.)

COMP231 Tutorial 1 ER Model and ER to Relational Schema.

IDEF1X (Integrated Definition 1, Extended  IDEF1X narrows the definition of entities, attributes, and relationships  IDEF1X adds the notion of domains.

Chapter 2: Intro to Relational Model. 2.2 Example of a Relation attributes (or columns) tuples (or rows)

Database Design I (In-Class Exercise Answer) IST 210: Organization of Data IST2101.

Entity/Relationship Modelling. Entity Relationship Modelling In This Lecture Entity/Relationship models Entities and Attributes Relationships Attributes.

Database Systems Avoiding Database Anomalies Tutor:Ian Perry Tel: Web:

Burson Building Renovation Overview of Project Needs Department of Chemistry Sherman L. Burson, Jr. December 24, 1923 – December 3, 2012 Bernadette Donovan-Merkert,

Relational Databases. SQL Sub-queries: queries within queries  So far when data has been filtered the filter has been known and simply added to the Where.

DERIVING TABLES FROM MODELS CS 260 Database Systems.

Course Outline How is International Finance being Taught elsewhere? Western, Economics Department

CS 3630 Database Design and Implementation. 2 Mathematical Relation A mathematical relation is a subset of a Cartesian Product. A1  A2  A3  …  An.

Chapter 1. Getting Started IST 210: Organization of Data IST2101.

Arkansas’ Active Course Rosters 1 W. Cody Decker Director of Information Systems Arkansas Department of Education 25 th Annual.

DATA MODELING AND ENTITY-RELATIONSHIP MODEL II IST 210: Organization of Data IST210 1.

Chapter 7: Relational Database Design. ©Silberschatz, Korth and Sudarshan7.2Database System Concepts.

DATABASE DESIGN II IST 210: Organization of Data IST210 1.

 Includes all modeling concepts of basic ER  Additional concepts: subclasses/superclasses, specialization/generalization,

The Relational Model.

Case Studies: Data Modeling

Chapter 3 Introduction to SQL(3)

Ureply integration with Blackboard

Lorain County Community College

Chapter 5 STUDENT-COURSE

Chapter 2: Intro to Relational Model

Database Structure Chapter 16.

Index Structure.

Web-Based Learning Management System

Announcements End of SQL today (Hopefully) Comments on midterm

פקודות לטיפול בנתונים (Data Manipulation)

FSSE-G RESULTS Faculty Survey of Student Engagement for Graduate Student Instructors.

Instructor: Mohamed Eltabakh

Database Systems Instructor Name: Lecture-8.

A Very Brief Introduction to Relational Databases

Chapter 27: Formal-Relational Query Languages

Student Information System Enrolling Students

Database Management System

Presentation transcript:

Example 2 – Schemas ES1 and ES2 Student(studentId, name, address, tutorId) Staff(tutorId, name, deptName) Lecturer(lecturerId, name, deptName) Course(courseId, name, programme) Teaches(lecturerId, studentId) Department(deptName, deptHead) Course(courseId, courseName, units) Enrollment(studentId, year) Staff(staffId, name, deptName) Teaches(staffId, courseId) CourseEnrollments(studentId,year, courseId)

Example 2 – Schemas ES1 and ES2 Student(studentId, name, address, tutorId) Staff(tutorId, name, deptName) Lecturer(lecturerId, name, deptName) Course(courseId, name, programme) Teaches(lecturerId, studentId) Department(deptName) Department(deptName, deptHead) Course(courseId, courseName, units) Enrollment(studentId, year) Staff(staffId, name, deptName) Teaches(staffId, courseId) CourseEnrollments(studentId,year, courseId)

Example 2 – Schemas ES1 and ES2 Student(studentId, name, address, tutorId) Staff(tutorId, name, deptName) Lecturer(lecturerId, name, deptName) Course(courseId, name, programme) Teaches(lecturerId, studentId) Department(deptName) Department(deptName, deptHead) Course(courseId, courseName, units) Enrollment(studentId, year) Lecturer(staffId, name, deptName) Teaches(staffId, courseId) CourseEnrollments(studentId,year, courseId)

Example 2 – Schemas ES1 and ES2 Student(studentId, name, address, tutorId) Staff(tutorId, name, deptName) Lecturer(lecturerId, name, deptName) Course(courseId, name, programme) Teaches(lecturerId, studentId) Department(deptName) Department(deptName, deptHead) Course(courseId, courseName, units) Enrollment(studentId, year) Lecturer(lecturerId, name, deptName) Teaches(lecturerId, courseId) CourseEnrollments(studentId,year, courseId)

Example 2 – Schemas ES1 and ES2 Student(studentId, name, address, tutorId) Staff(tutorId, name, deptName) Lecturer(lecturerId, name, deptName) Course(courseId, courseName, programme) Teaches(lecturerId, studentId) Department(deptName) Department(deptName, deptHead) Course(courseId, courseName, units) Enrollment(studentId, year) Lecturer(lecturerId, name, deptName) Teaches(lecturerId, courseId) CourseEnrollments(studentId,year, courseId)

Example 2 – Schemas ES1 and ES2 Student(studentId, name, address, tutorId) Staff(tutorId, name, deptName) Lecturer(lecturerId, name, deptName) Course(courseId, courseName, programme) TeachesStudents(lecturerId, studentId) Department(deptName) Department(deptName, deptHead) Course(courseId, courseName, units) Enrollment(studentId, year) Lecturer(lecturerId, name, deptName) Teaches(lecturerId, courseId) CourseEnrollments(studentId,year, courseId)

Merging ES1 and ES2 Student(studentId, name, address, tutorId) Staff(tutorId, name, deptName) Lecturer(lecturerId, name, deptName) Course(courseId, courseName, units, programme) TeachesStudents(lecturerId, studentId) Department(deptName, deptHead) Enrollment(studentId, year) Teaches(lecturerId, courseId) CourseEnrollments(studentId,year, courseId)

Improving the merged schema Student(studentId, name, address, tutorId) Staff(tutorId, name, deptName) Lecturer(lecturerId, name, deptName) Course(courseId, courseName, units, programme) TeachesStudents(lecturerId, studentId) Department(deptName, deptHead) Teaches(lecturerId, courseId) CourseEnrollments(studentId,year, courseId)

Improving the merged schema Student(studentId, name, address, tutorId) Staff(tutorId, name, deptName) Lecturer(lecturerId, name, deptName) Course(courseId, courseName, units, programme) Department(deptName, deptHead) Teaches(lecturerId, courseId) CourseEnrollments(studentId,year, courseId)