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

Slides:

Advertisements

Similar presentations

ER Model For a college DB

Advertisements

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

ER Modeling Case Studies

Entity, Attribute, and Relationship DATA ENTITY TYPE: a noun, i.e. roles, events, locations, people, tangible things about which we wish to maintain.

Online Course Withdrawal

Data Modeling and Entity- Relationship Model II. IST2102 I want a database to maintain departments in my company. Store information about my employees,

Database BA471 – Fall 2007 Dr. V.T. Raja Oregon State University.

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

The (min,max) notation (1,1) (0,1) (1,N) (1,1). SUMMARY OF ER-DIAGRAM NOTATION FOR ER SCHEMAS Meaning ENTITY TYPE WEAK ENTITY TYPE RELATIONSHIP TYPE IDENTIFYING.

Databases Dr. V.T. Raja Oregon State University. Databases – Part 1: Outline Introduction Data Hierarchy Traditional file management Terminology Database.

Case study Lisa’s Bookstore IST210.

Chapter 4 Tutorial.

Entity/Relationship Modelling

Data Modeling and Entity- Relationship Model I IST2101.

Amity School of Engineering & Technology E-R Diagram for a University Enterprise.

Data Modeling using Entity Relationship Diagramming (ERD)

1 Class Agenda (04/09 through 04/16)  Review HW #8  Present normalization process Enhance conceptual knowledge of database design. Improve practical.

1 Class Agenda (11/07 and 11/12)  Review HW #8 answers  Present normalization process Enhance conceptual knowledge of database design. Improve practical.

Instructor :Huda Al-Omair

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

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.

1 CMPT 275 Phase: Design. Janice Regan, Map of design phase DESIGN HIGH LEVEL DESIGN Modularization User Interface Module Interfaces Data Persistance.

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.

MIS 3053 Database Design & Applications The University of Tulsa Professor: Akhilesh Bajaj ER Model Lecture 1 © Akhilesh Bajaj, 2000, 2002, 2003, 2004.

Syllabus Highlights Spring Full syllabus is on myCourses! Exams (3 hourly + 1 final – drop one) : 300 points Attendance 12 points Homework 60 points.

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.

MIS 3053 Database Design & Applications The University of Tulsa Professor: Akhilesh Bajaj InClass ER Examples.

Database Design 3: Advanced Data Modeling Concepts CS 320.

The Hong Kong University of Science and Technology COMP3311 Spring 2013 Tutorial 1 ER Diagrams.

Normalization Exercise. First Normal Form Second Normal Form.

 An entity-relationship diagram (ERD) is a specialized graphic that illustrates the interrelationships between entities in a database.

COMP231 Tutorial 1 ER Model and ER to Relational Schema.

E-R to Relational - Basic

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

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

THE RELATIONAL MODEL I IST 210: Organization of Data IST210 1.

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

Howard Paul. Sequential Access Index Files and Data File Random Access.

Database System Concepts, 6 th Ed. ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 7: Entity-Relationship.

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

Data Modeling and Entity-Relationship Model I

Database Design I IST 210: Organization of Data IST2101.

Information System Design “Student Registration System Example”

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

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

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

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

CCT395, Week 5 Translating ER into Relations; Normalization This presentation is licensed under Creative Commons Attribution License, v To view a.

Translating ER into Relations; Normalization

Case Studies: Data Modeling

E-R Diagram (Cont.) Draw ER Diagram for the following scenario:

IST 210: Organization of Data

ER Diagram Practical Example

Chapter 5 STUDENT-COURSE

Order Database – ER Diagram

Web-Based Learning Management System

Announcements End of SQL today (Hopefully) Comments on midterm

تحليل انظمة و تصميمها الوحدة الخامسة أ.محمد زكي شبير.

ERD (Entity Relationship Diagrams)

Functional Dependencies

Example A university registrar’s office maintains data about the following entities: (a) courses, including number, title, credits, syllabus, and prerequisites;

Instructor: Mohamed Eltabakh

Weak Entity Sets An entity set that does not have a primary key is referred to as a weak entity set. The existence of a weak entity set depends on the.

MIS2502: Data Analytics Relational Data Modeling

Agenda and Resources Agenda Resource

This is an example of Object-Oriented Modeling diagram.

Conceptual modeling of databases

Presentation transcript:

COURSE REGISTRATION SYSTEM Case study IST2101

Case Study: Course Registration (1) IST2102 You are helping Penn State create a course registration system. Store information about all students, including their student IDs, names, s, and their major departments. The department should have information about department name, building name, and phone number.

IST2103 StudentID Name STUDENT DepartName Building Phone DEPARTMENT

Case Study: Course Registration (2) IST2104 A course should have information about course ID, course name, and instructor name. Students can take many courses and a course can be registered by many students. We also need to store the final grade for a student in a course.

IST2105 StudentID Name STUDENT DepartName Building Phone DEPARTMENT CourseID CourseName Instructor COURSE Any problem with this design?

Attributes on Relationships? When you need to store some information about a relationship, the relationship should actually be designed as an entity. If we want to store the grades for the relationship between COURSE and STUDENT, we need to make GRADE as a separate entity. If we only want to store which student taking which course, we don’t need a separate entity to capture their relationship. IST2106

7 StudentID Name STUDENT StudentID CourseID Grade GRADE DepartName Building Phone DEPARTMENT CourseID CourseName Instructor COURSE

Case Study: Course Registration (3) IST2108 A course is offered by a department. We also want to store this information.

IST2109 StudentID Name STUDENT StudentID CourseID Grade GRADE DepartName Building Phone DEPARTMENT CourseID CourseName Instructor COURSE Complete E-R Diagram