Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Published byHoward Scott Modified over 9 years ago

Similar presentations

Presentation on theme: "Database Design II (Case Studies: Step 2) IST 210: Organization of Data IST2101."— Presentation transcript:

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

2 COURSE REGISTRATION SYSTEM Case study IST2102

3 3 STUDENT(StudentID, Name, Email, DepartName) DEPARTMENT(DepartName, Building, Phone) COURSE(CourseID, CourseName, Instructor, DepartName) GRADE(StudentID, CourseID, Grade)

4 IST2104 STUDENT(StudentID, Name, Email, DepartName) DEPARTMENT(DepartName, Building, Phone) COURSE(CourseID, CourseName, Instructor, DepartName) GRADE(StudentID, CourseID, Grade) Column NameData TypeKeyRequiredRemarks DepartName Building Phone DEPARTMENT

5 IST2105 STUDENT(StudentID, Name, Email, DepartName) DEPARTMENT(DepartName, Building, Phone) COURSE(CourseID, CourseName, Instructor, DepartName) GRADE(StudentID, CourseID, Grade) Column NameData TypeKeyRequiredRemarks StudentID Name Email DepartName STUDENT

6 IST2106 STUDENT(StudentID, Name, Email, DepartName) DEPARTMENT(DepartName, Building, Phone) COURSE(CourseID, CourseName, Instructor, DepartName) GRADE(StudentID, CourseID, Grade) Column NameData TypeKeyRequiredRemarks CourseID CourseName Instructor DepartName COURSE

7 IST2107 STUDENT(StudentID, Name, Email, DepartName) DEPARTMENT(DepartName, Building, Phone) COURSE(CourseID, CourseName, Instructor, DepartName) GRADE(StudentID, CourseID, Grade) Column NameData TypeKeyRequiredRemarks StudentID CourseID Grade GRADE

8 LISA’S BOOKSTORE Case study IST2108

9 9 PUBLISHER(PublisherName, Location, Phone) BOOK(BookID, Title, Year, PublisherName) AUTHOR(AuthorID, Name, Country) BOOK_AUTHOR(BookID, AuthorID) PURCHASE(PurchaseID, Price, Date, BookID, EmailAddress) CUSTOMER(EmailAddress, Name, Address, Phone) EVENT(EventID, Name, Date, Type) CUSTOMER_EVENT(EmailAddress, EventID) E-R diagram is transformed into a database with 8 tables

10 IST21010 PUBLISHER(PublisherName, Location, Phone) BOOK(BookID, Title, Year, PublisherName) AUTHOR(AuthorID, Name, Country) BOOK_AUTHOR(BookID, AuthorID) PURCHASE(PurchaseID, Price, Date, BookID, EmailAddress) CUSTOMER(EmailAddress, Name, Address, Phone) EVENT(EventID, Name, Date, Type) CUSTOMER_EVENT(EmailAddress, EventID) Column NameData TypeKeyRequiredRemarks PublisherName Location Phone PUBLISHER

11 IST21011 PUBLISHER(PublisherName, Location, Phone) BOOK(BookID, Title, Year, PublisherName) AUTHOR(AuthorID, Name, Country) BOOK_AUTHOR(BookID, AuthorID) PURCHASE(PurchaseID, Price, Date, BookID, EmailAddress) CUSTOMER(EmailAddress, Name, Address, Phone) EVENT(EventID, Name, Date, Type) CUSTOMER_EVENT(EmailAddress, EventID) Column NameData TypeKeyRequiredRemarks BookID Title Year PublisherName BOOK

12 IST21012 PUBLISHER(PublisherName, Location, Phone) BOOK(BookID, Title, Year, PublisherName) AUTHOR(AuthorID, Name, Country) BOOK_AUTHOR(BookID, AuthorID) PURCHASE(PurchaseID, Price, Date, BookID, EmailAddress) CUSTOMER(EmailAddress, Name, Address, Phone) EVENT(EventID, Name, Date, Type) CUSTOMER_EVENT(EmailAddress, EventID) Column NameData TypeKeyRequiredRemarks AuthorID Name Country AUTHOR

13 IST21013 PUBLISHER(PublisherName, Location, Phone) BOOK(BookID, Title, Year, PublisherName) AUTHOR(AuthorID, Name, Country) BOOK_AUTHOR(BookID, AuthorID) PURCHASE(PurchaseID, Price, Date, BookID, EmailAddress) CUSTOMER(EmailAddress, Name, Address, Phone) EVENT(EventID, Name, Date, Type) CUSTOMER_EVENT(EmailAddress, EventID) Column NameData TypeKeyRequiredRemarks BookID AuthorID BOOK_AUTHOR

14 IST21014 PUBLISHER(PublisherName, Location, Phone) BOOK(BookID, Title, Year, PublisherName) AUTHOR(AuthorID, Name, Country) BOOK_AUTHOR(BookID, AuthorID) PURCHASE(PurchaseID, Price, Date, BookID, EmailAddress) CUSTOMER(EmailAddress, Name, Address, Phone) EVENT(EventID, Name, Date, Type) CUSTOMER_EVENT(EmailAddress, EventID) Column NameData TypeKeyRequiredRemarks EmailAddress Name Address Phone CUSTOMER

15 IST21015 PUBLISHER(PublisherName, Location, Phone) BOOK(BookID, Title, Year, PublisherName) AUTHOR(AuthorID, Name, Country) BOOK_AUTHOR(BookID, AuthorID) PURCHASE(PurchaseID, Price, Date, BookID, EmailAddress) CUSTOMER(EmailAddress, Name, Address, Phone) EVENT(EventID, Name, Date, Type) CUSTOMER_EVENT(EmailAddress, EventID) Column NameData TypeKeyRequiredRemarks PurchaseID Price Date BookID EmailAddress PURCHASE

16 IST21016 PUBLISHER(PublisherName, Location, Phone) BOOK(BookID, Title, Year, PublisherName) AUTHOR(AuthorID, Name, Country) BOOK_AUTHOR(BookID, AuthorID) PURCHASE(PurchaseID, Price, Date, BookID, EmailAddress) CUSTOMER(EmailAddress, Name, Address, Phone) EVENT(EventID, Name, Date, Type) CUSTOMER_EVENT(EmailAddress, EventID) Column NameData TypeKeyRequiredRemarks EventID Name Date Type EVENT

17 IST21017 PUBLISHER(PublisherName, Location, Phone) BOOK(BookID, Title, Year, PublisherName) AUTHOR(AuthorID, Name, Country) BOOK_AUTHOR(BookID, AuthorID) PURCHASE(PurchaseID, Price, Date, BookID, EmailAddress) CUSTOMER(EmailAddress, Name, Address, Phone) EVENT(EventID, Name, Date, Type) CUSTOMER_EVENT(EmailAddress, EventID) Column NameData TypeKeyRequiredRemarks EmailAddress EventID CUSTOMER_EVENT

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

Similar presentations

ER Model For a college DB

ER Model For a college DB
SQL Database for a Book Store Clinton McKay. Explanation The database contains information about the books held in stock, their authors, publishers, customers,

SQL Database for a Book Store Clinton McKay. Explanation The database contains information about the books held in stock, their authors, publishers, customers,
Example 2 – Schemas ES1 and ES2 Student(studentId, name, address, tutorId) Staff(tutorId, name, deptName) Lecturer(lecturerId, name, deptName) Course(courseId,

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

Online Course Withdrawal
Lab Exercise This Week PHP Basics See last Friday’s slides for requirements Make sure you show the final results to TA to get credit 1IST210.

Lab Exercise This Week PHP Basics See last Friday’s slides for requirements Make sure you show the final results to TA to get credit 1IST210.
Draw an ER Diagram for the following (record any assumptions):

Draw an ER Diagram for the following (record any assumptions):
Dr. Mahmut Parlar Bus Q600 (EC01) Tue., 7:00 p.m. Course Materials & Resources.

Dr. Mahmut Parlar Bus Q600 (EC01) Tue., 7:00 p.m. Course Materials & Resources.
Data Modeling with ERD ISYS 363. Entity-Relationship Diagram An entity is a “thing” in the real world, such as a person, place, event for which we intend.

Data Modeling with ERD ISYS 363. Entity-Relationship Diagram An entity is a “thing” in the real world, such as a person, place, event for which we intend.
Case study Lisa’s Bookstore IST210.

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

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

School of Business Administration
CSE 441: Systems Analysis & Design

CSE 441: Systems Analysis & Design
CHAPTER 2. FUNDAMENTAL OF ENTITY RELATIONSHIP (ER)

CHAPTER 2. FUNDAMENTAL OF ENTITY RELATIONSHIP (ER)
DATABASE DESIGN I IST 210: Organization of Data IST210 1.

DATABASE DESIGN I IST 210: Organization of Data IST210 1.
IST 210: ORGANIZATION OF DATA Chapter 1. Getting Started IST210 1.

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.

Normalization Process: Exercise 1: Step 1 IST2101 Step 1. Identify all the candidate keys of the relation. StudentNumber.
SQL 101 for Web Developers 14 November 2012. What is a database and why have one? Tables, relationships, normalization SQL – What SQL is and isn’t – CRUD:

SQL 101 for Web Developers 14 November What is a database and why have one? Tables, relationships, normalization SQL – What SQL is and isn’t – CRUD:
Students who use Connect & LearnSmart are proven to be more successful in the course and receive higher grades than their peers not using Connect. Want.

Students who use Connect & LearnSmart are proven to be more successful in the course and receive higher grades than their peers not using Connect. Want.
©Silberschatz, Korth and Sudarshan1Database System Concepts - 6 th Edition E-R Diagram for a University Enterprise.

©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.

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.

Similar presentations

Ads by Google