Problems 7/27/02. 3, p5 Student Course Student-Course Stu-ID Course-ID Grade.

Slides:



Advertisements
Similar presentations
ER Model For a college DB
Advertisements

Relational Database Modeling II We dont live in a world of reality, we live in a world of perceptions. J. Gerald Simmons.
Chapter 4 Database Processing. Agenda Purpose of Database Terminology Components of Database System Multi-user Processing Database Design Entity-relationship.
1 Quiz 2. 2 One instructor cannot be at two or more class rooms at the same time. One class room cannot be shared by two or more instructors at the same.
1 Assignment 4 Map entities with relationships to relational schemas. Use DBDL to describe the table schemas.
Assignment Design Methodology A structured approach that uses procedures, techniques, tools, and documentation aids to support and facilitate the.
Enhanced Entity-Relationship Modeling. Strong and Weak Entity Types Strong entity: Each object is uniquely identifiable using primary key of that entity.
Entity, Attribute, and Relationship DATA ENTITY TYPE: a noun, i.e. roles, events, locations, people, tangible things about which we wish to maintain.
Introduction to MS Access, building tables, creating keys, creating relationships BSAD 141 Dave Novak.
Mapping an ERD to a Relational Database To map an ERD to a relational database, five rules are defined to govern how tables are constructed. 1)Rule for.
Data modeling using the entity-relationship model Sept. 2012Yangjun Chen ACS Outline: Data modeling using ER-model (Chapter 3 - 3rd, 4th, 5th ed.)
Review Questions What is data modeling? What is the actual data model that is created called? Data modeling is a technique for organizing and documenting.
The Relational Database Model:
Enhanced Entity-Relationship Modeling
Sept ER-to-Relational Mapping Principles ER-to-Relational Mapping And examples.
CS424 PK, FK, FD Normalization Primary and Foreign Keys Primary and foreign keys are the most basic components on which relational theory is based. Primary.
Entity PrimaryKey Attribute relationship Cardinality: zero to many Cardinality: one and only one Cardinality: one to many Explanation Entity Relationship.
Chapter 2 Modeling Data in the Organization
Database Management COP4540, SCS, FIU Database Modeling Using the Entity-Relationship Model (Chapter 3)
Entity-Relationship Design
ETL and Metadata. The ETL Process Source Systems Extract Transform Staging Area Load Presentation System.
COURSE REGISTRATION SYSTEM Case study IST2101. Case Study: Course Registration (1) IST2102 You are helping Penn State create a course registration system.
DATA MODELING AND DATABASE DESIGN DATA MODELING AND DATABASE DESIGN Part 1.
Relational databases and third normal form As always click on speaker notes under view when executing to get more information!
Tutorial 3. This tutorial went through how to convert multiplicity numbering used in UML modelling to ERD, and vice versa. In the exam and assignments,
What we’ve learnt Doc 5.69 Doc 5.70 Section 1-3. A simple database Related objects Tables hold the data Forms, reports, queries to access the data.
BIS 360 – Lecture Eight Ch. 12: Database Design and Normalization.
Constraints - primary and foreign keys in Oracle Please use speaker notes for additional information!
MS Access. Access is a DBMS/RDMS DBMS = Database Management System RDMS = Relational Database Management System.
3 & 4 1 Chapters 3 and 4 Drawing ERDs October 16, 2006 Week 3.
The Hong Kong University of Science and Technology COMP3311 Spring 2013 Tutorial 1 ER Diagrams.
3 & 4 1 Database Systems: Design, Implementation, & Management, 7 th Edition, Rob & Coronel Keys Consists of one or more attributes that determine other.
COMP231 Tutorial 1 ER Model and ER to Relational Schema.
ITEC 3220A Using and Designing Database Systems Instructor: Prof Z. Yang Course Website: 3220a.htm
ITEC 3220A Using and Designing Database Systems Instructor: Gordon Turpin Course Website: Office: CSEB3020.
Weak Entity Sets A weak entity is an entity that cannot exist in a database unless another type of entity also exists in that database. Weak entity meets.
WXGE 6101 DATABASE CONCEPTS & IMPLEMENTATIONS. Lesson Overview The Relational Model Terminology of relational model. Properties of database relations.
OS App. 1 App. 2 App. 3 OS App. 1 App. 2 App. 3 DBMSDBMS OS App. 1 App. 2 App. 3 O-O D B M S Data Design Files & Databases.
Database Design – Lecture 6 Moving to a Logical Model.
Exam 1 Review: ERDs, Schemas, SQL Out Describe Elements of an ERD Create Schema from ERD Notes: Associative Entities.
Week 7-8 DBMS ER-Relational Mapping. ER-Relational Mapping.
MIS 3053 Database Design & Applications The University of Tulsa Professor: Akhilesh Bajaj ER Model Lecture 2 © Akhilesh Bajaj, 2000, 2002, 2003, 2004,
Database Design 4: Deriving Tables From Data Models CS 320.
Database Design. Database Design Process Data Model Requirements Application 1 Database Requirements Application 2 Requirements Application 4 Requirements.
Howard Paul. Sequential Access Index Files and Data File Random Access.
DATA MODELING AND DATABASE DESIGN DATA MODELING AND DATABASE DESIGN Part 2.
IMS 6217: Database Design & Entities 1 Dr. Lawrence West, MIS Dept., University of Central Florida Database Design--Topics DB Design.
1 R. Ching, Ph.D. MIS California State University, Sacramento Week 9 October 24 Modeling with ERDModeling with ERD.
Microsoft Access CS 110 Fall Entity Relationship Model Entities Entities Principal data object about which information is to be collectedPrincipal.
DATA MODELING AND ENTITY-RELATIONSHIP MODEL II IST 210: Organization of Data IST210 1.
Lecture # 14 Chapter # 5 The Relational Data Model and Relational Database Constraints Database Systems.
Database Development Lifecycle
COP5725 Database Management ER DIAGRAM AND RELATIONAL DATA MODEL
Tables and Their Characteristics
Introduction to MS Access: creating tables, keys, and relationships
Chapter 5 STUDENT-COURSE
Assignment 4 Map entities with relationships to relational schemas.
ERD’s REVIEW DBS201.
Entity Relationship Diagrams ERDs
Foreign key (FK) is defined as follows:
Information Systems CS-507 Lecture 25
Data Modeling with Entity Relationship Diagrams (Cont.)
Example A university registrar’s office maintains data about the following entities: (a) courses, including number, title, credits, syllabus, and prerequisites;
Chapter 2 Modeling Data in the Organization
ITEC 3220A Using and Designing Database Systems
The University of Tulsa Professor: Akhilesh Bajaj
1.(5) Describe the working process with a database system.
Mapping an ERD to a Relational Database
Database Management system
Presentation transcript:

Problems 7/27/02

3, p5 Student Course Student-Course Stu-ID Course-ID Grade

4, p5 Course CourseID InstrID Instructor InstrID Teaches

5, p5 (Weak Entity) Course CourseID Name HoursCredit Section CourseID SectionID Time Days Term IsOneOf MIS = CourseID-SectionID MIS Weak Entity: Has the key of another entity as part of its key. Cannot exist in life without the other one. 0 MIS5113 MIS

P6, #7 SalesOffice, Employee, Property, Owner SalesOffice Employee ID Name SOID (FK) MGR? Works In Property PropertyID (PK) SOID (FK) Listed by Owner OwnerID Property-Owner OwnerID (FK) (PK) PropertyID (FK) (PK) Assumes Property ID is unique across all offices.

P6, #7 SalesOffice, Employee, Property, Owner SalesOffice MGRID(FK) Employee ID Name SOID (FK) Works In Managed by

Narrative List a property Assign to a sales office Record ownership information Record property data Record listing agent Hire an employee Record employee data Assign to an office Indicate manager Create sales office Assign manager Record data

P6, #7 Level 0 DFD List a property Listing Agent Property & Ownership Info Property Data Office Office Info Hire an Employee Create Sales Office Office Info Owner Owner Data Property-Owner Ownership Data Management New Office Data

P6, #7 Level 0 DFD List a property Listing Agent Property & Ownership Info Property Data Office Office Info Create Sales Office Office Info Owner Owner Data Property-Owner Ownership Data Management New Office Data Employee Table ManagerID EmployeeData

Narrative List a property Assign to a sales office Record ownership information Record property data Record listing agent Hire an employee Record employee data Assign to an office Indicate manager Create sales office Record data

Metadata Flows Analysis: names of attributes or elements Design: names + design parameters