8/28/97Information Organization and Retrieval Database Design University of California, Berkeley School of Information Management and Systems SIMS 202:

Slides:



Advertisements
Similar presentations
Exercise 1 Consider the ER diagram below. Assume that an employee may work in up to two departments or may not be assigned to any department. Assume that.
Advertisements

Entity-Relationship (ER) Modeling
Ch5: ER Diagrams - Part 1 Much of the material presented in these slides was developed by Dr. Ramon Lawrence at the University of Iowa.
Information Systems Planning and the Database Design Process
SLIDE 1IS 202 – FALL 2005 Prof. Ray Larson UC Berkeley SIMS SIMS 202: Information Organization and Retrieval Normalization & The Relational.
Database Design University of California, Berkeley
SLIDE 1IS 257 – Fall 2006 Database Design: Conceptual Model and ER Diagramming Ray R. Larson University of California, Berkeley School of.
System Analysis - Data Modeling
9/6/2001Database Management – Fall 2000 – R. Larson Information Systems Planning and the Database Design Process University of California, Berkeley School.
SLIDE 1IS 202 – FALL 2002 Prof. Ray Larson & Prof. Marc Davis UC Berkeley SIMS Tuesday and Thursday 10:30 am - 12:00 pm Fall 2002
SLIDE 1IS Fall 2002 Database Design: Conceptual Model and ER Diagramming University of California, Berkeley School of Information Management.
SLIDE 1IS 257 – Fall 2004 Database Design: Conceptual Model and ER Diagramming Ray R. Larson University of California, Berkeley School of.
Introduction to Database ISYS 363. File Concepts File consists of a group of records. Each record contains a group of fields. Example: Student file –SIDSnameMajorSexGPA.
9/7/1999Information Organization and Retrieval Database Design: Conceptual Model and ER Diagramming University of California, Berkeley School of Information.
11/28/2000Information Organization and Retrieval Introduction to Databases and Database Design University of California, Berkeley School of Information.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model.
Concepts of Database Management Sixth Edition
SLIDE 1IS Fall 2010 Information Systems Planning and the Database Design Process Ray R. Larson University of California, Berkeley School.
8/29/2000Database Management -- Fall R. Larson Database Management: Introduction University of California, Berkeley School of Information Management.
Introduction to Database ISYS 363. File Concepts File consists of a group of records. Each record contains a group of fields. Example: Student file –SIDSnameMajorSexGPA.
The Relational Database Model:
1 1 Concepts of Database Management, 4 th Edition, Pratt & Adamski Chapter 1 Introduction to Database Management.
SLIDE 1IS Fall 2002 Information Systems Planning and the Database Design Process University of California, Berkeley School of Information.
8/28/97Information Organization and Retrieval Intergalactic Courier Service: Database and Application Design University of California, Berkeley School.
8/28/2001Database Management -- Fall R. Larson Database Management: Introduction University of California, Berkeley School of Information Management.
8/28/97Information Organization and Retrieval Database Design: Normalization University of California, Berkeley School of Information Management and Systems.
Callie’s Birthday SLIDE 1IS 202 – FALL 2004 Prof. Ray Larson & Prof. Marc Davis UC Berkeley SIMS Tuesday and Thursday 10:30 am - 12:00 pm.
SLIDE 1IS 202 – FALL 2005 Prof. Ray Larson UC Berkeley SIMS SIMS 202: Information Organization and Retrieval Introduction to Database Design.
SLIDE 1IS 257 – Spring 2004 Information Systems Planning and the Database Design Process Ray R. Larson University of California, Berkeley.
SLIDE 1IS 257 – Spring 2004 Database Design: Conceptual Model and ER Diagramming Ray R. Larson University of California, Berkeley School of.
SLIDE 1IS 202 – FALL 2003 Prof. Ray Larson & Prof. Marc Davis UC Berkeley SIMS Tuesday and Thursday 10:30 am - 12:00 pm Fall 2003
“DOK 322 DBMS” Y.T. Database Design Hacettepe University Department of Information Management DOK 322: Database Management Systems.
8/28/97Information Organization and Retrieval Files and Databases University of California, Berkeley School of Information Management and Systems SIMS.
Concepts of Database Management Seventh Edition Chapter 1 Introduction to Database Management.
10/3/2000SIMS 257: Database Management -- Ray Larson Relational Algebra and Calculus University of California, Berkeley School of Information Management.
Mgt 20600: IT Management & Applications Databases Tuesday April 4, 2006.
SLIDE 1IS Fall 2006 Information Systems Planning and the Database Design Process Ray R. Larson University of California, Berkeley School.
Information Systems Planning and the Database Design Process
Data Modeling Using the Entity-Relationship Model
DeSiamorewww.desiamore.com/ifm1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
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.
Information storage: Introduction of database 10/7/2004 Xiangming Mu.
Concepts of Database Management Seventh Edition
Concepts of Database Management, Fifth Edition Chapter 1: Introduction to Database Management.
CSE 441: Systems Analysis & Design
Database. Basic Definitions Database: A collection of related data. Database Management System (DBMS): A software package/ system to facilitate the creation.
Principles of Database Systems With Internet and Java Applications Today’s Topic Chapter 2: Representing Information with Data Models The lecture notes.
Concepts of Database Management, Fifth Edition Chapter 1: Introduction to Database Management.
9/7/1999Information Organization and Retrieval Database Design: Object- Oriented Modeling University of California, Berkeley School of Information Management.
Module 2: Information Technology Infrastructure Chapter 5: Databases and Information Management.
DeSiamorePowered by DeSiaMore1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
1 CSE 2337 Introduction to Data Management Textbook: Chapter 1.
Msigwaemhttp//:msigwaem.ueuo.com/1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
SLIDE 1IS 202 – FALL 2006 Prof. Ray Larson UC Berkeley SIMS SIMS 202: Information Organization and Retrieval Introduction to Database Design.
Concepts of Database Management Seventh Edition Chapter 1 Introduction to Database Management.
DatabaseIM ISU1 Fundamentals of Database Systems Chapter 3 Data Modeling Using Entity-Relationship Model.
Data Modeling Using the Entity-Relationship (ER) Data Model.
An Introduction to Database Systems دانشگاه علم و فناوری مازندران - طراحی و ایجاد بانک های اطلاعاتی 1.
Copyright (c) 2014 Pearson Education, Inc. Introduction to DBMS.
8/31/99Database Management -- Fall R. Larson Database Models and Introduction to Access University of California, Berkeley School of Information.
12/4/2001Information Organization and Retrieval Database Design University of California, Berkeley School of Information Management and Systems SIMS 202:
Entity- Relationship (ER) Model
Database Design: Conceptual Model and ER Diagramming
Database Requirements and Design
ER MODEL Lecture 3.
Entity – Relationship Model
MIS2502: Data Analytics Relational Data Modeling
Database Design Hacettepe University
Entity-Relationship Diagram (ERD)
Appendix A Data Modeling MANAGEMENT INFORMATION SYSTEMS 8/E
Presentation transcript:

8/28/97Information Organization and Retrieval Database Design University of California, Berkeley School of Information Management and Systems SIMS 202: Information Organization and Retrieval

8/28/97Information Organization and Retrieval Review Database Data Models Database Design Process Basics of ER Diagrams

8/28/97Information Organization and Retrieval Database Data Models Hierarchical Model –Similar to data structures in programming languages. Books (id, title) PublisherSubjects Authors (first, last)

8/28/97Information Organization and Retrieval Database Data Models Network Model –Provides for single entries of data and navigational “links” through chains of data. SubjectsBooks Authors Publishers

8/28/97Information Organization and Retrieval Database Data Models Relational Model –Provides a conceptually simple model for data as relations (typically considered “tables”) with all data visible.

8/28/97Information Organization and Retrieval Database Data Models Object Oriented Data Model –Encapsulates data and operations as “Objects” Books (id, title) PublisherSubjects Authors (first, last)

8/28/97Information Organization and Retrieval Database Design Process Conceptual Model Logical Model External Model Conceptual requirements Conceptual requirements Conceptual requirements Conceptual requirements Application 1 Application 2Application 3Application 4 Application 2 Application 3 Application 4 External Model External Model External Model Internal Model

8/28/97Information Organization and Retrieval Database Design Process Conceptual Model –Merge the collective needs of all applications –Determine what Entities are being used Some object about which information is to maintained –What are the Attributes of those entities? Properties or characteristics of the entity What attributes uniquely identify the entity –What are the Relationships between entities How the entities interact with each other?

8/28/97Information Organization and Retrieval Developing a Conceptual Model Overall view of the database that integrates all the needed information discovered during the requirements analysis. Elements of the Conceptual Model are represented by diagrams, Entity- Relationship or ER Diagrams, that show the meanings and relationships of those elements independent of any particular database systems or implementation details.

8/28/97Information Organization and Retrieval Entity An Entity is an object in the real world (or even imaginary worlds) about which we want or need to maintain information –Persons (e.g.: customers in a business, employees, authors) –Things (e.g.: purchase orders, meetings, parts, companies) Employee

8/28/97Information Organization and Retrieval Attributes Attributes are the significant properties or characteristics of an entity that help identify it and provide the information needed to interact with it or use it. (This is the Metadata for the entities.) Employee Last Middle First Name SSN Age Birthdate Projects

8/28/97Information Organization and Retrieval Relationships Relationships are the associations between entities. They can involve one or more entities and belong to particular relationship types Examples derived from David R. McClanahan “Conceptual Design” DBMS Magazine January 1992, and “Hands-on Design”, February 1992.

8/28/97Information Organization and Retrieval Relationships Class Attends Student Part Supplies project parts Supplier Project

8/28/97Information Organization and Retrieval Types of Relationships Concerned only with cardinality of relationship Truck Assigned Employee Project Assigned Employee Project Assigned Employee 11 n n 1 m

8/28/97Information Organization and Retrieval More Complex Relationships Project Evaluation Employee Manager 1/n/n 1/1/1 n/n/1 Manages Employee Project Assigned Employee 4(2-10)1 SSNProjectDate Manages Is Managed By 1 n

8/28/97Information Organization and Retrieval Today More on Entity-Relationship Diagrams Designing a database

8/28/97Information Organization and Retrieval Weak Entities Owe existence entirely to another entity Order-line Contains Order Invoice # Part# Rep# QuantityInvoice#

8/28/97Information Organization and Retrieval Supertype and Subtype Entities Clerk Is one of Sales-rep Invoice Other Employee Sold Manages

8/28/97Information Organization and Retrieval Many to Many Relationships Employee Project Is Assigned Project Assignment Assigned SSN Proj# SSN Proj# Hours

8/28/97Information Organization and Retrieval Developing a Conceptual Model We will look at a small business Assume that we have done interviews with the business and found out the following information about the forms used and types of information kept in files and used for business operations...

8/28/97Information Organization and Retrieval Primary Business Operations The business sells parts to customers. –Each part has: A part number, A selling price, A description of the part, The count of the part currently in stock.

8/28/97Information Organization and Retrieval Business Operations (cont.) Each sale is on an invoice to one customer. –Invoices contain: Line items for each part ordered, Total amount due for the invoice, Customer information: –Company name, address, and an ID number. –Invoices are written up by one sales representative, who is credited with the sale Sales reps are paid a 5% commission on sales.

8/28/97Information Organization and Retrieval Business Operations (cont.) Information must be kept on inventory of parts. There are multiple suppliers of parts: –The prices charged by different suppliers for a given part may be different. This is the Cost of the part.

8/28/97Information Organization and Retrieval Business Operations (cont.) Employee information includes: –Name, –Social Security Number, –Employee ID number, –Address, –Position. Hourly wages must be tracked for all employees (except sales reps).

8/28/97Information Organization and Retrieval Business Operations (cont.) One account is kept for each customer to track charges, payments, and the current balance. The company needs to know if an order has been shipped. The accounting department must know which invoices have been paid. The total sales for each sales rep must be calculated.

8/28/97Information Organization and Retrieval Business Operations (cont.) We must know if a part is in stock at the company or on order from a supplier. Each hourly employee generates a time-card every Monday morning. Sales Reps don’t turn in time-cards, just their total sales. All employees are paid weekly by check. We need a report each Monday telling us what each employee should be paid for the previous week.

8/28/97Information Organization and Retrieval Entities Customer Invoice Employee Inventory Supplier Account Sales Rep Parts Timecard Check

8/28/97Information Organization and Retrieval Functional areas Ordering Inventory Supplies Shipping Personnel Payroll We will concentrate on Ordering and Inventory

8/28/97Information Organization and Retrieval Ordering Invoice Rep-cust invoice Sales-Rep Customer Simple Ternary Relationship

8/28/97Information Organization and Retrieval Ordering Invoice Orders Customer Cust# Writes Sales-Rep Invoice# Rep# Parts Repeating attribute

8/28/97Information Organization and Retrieval Ordering Normalization Orders Customer Cust# Invoice Writes Sales-Rep Invoice# Rep# Line-Item Contains Part# QuantityInvoice# Cust#

8/28/97Information Organization and Retrieval Parts and Suppliers Part Supplies Supplier Company# Includes Line-Item Part# Count Price Invoice# mn Is this correct? Where does Price belong?

8/28/97Information Organization and Retrieval Parts and Suppliers (alternative 2) Company# Contains Line-Item Part#Invoice# Part Part# Count Price n m Supplier Company# Offers Supplied-Part Part# Cost Supplies Intersection Entity

8/28/97Information Organization and Retrieval Parts and Suppliers (Alternative 3) Company# Contains Line-Item Part#Invoice# Part Part# Count Price Supplier Company# Supplies Supplied-Part Part# Cost

8/28/97Information Organization and Retrieval Parts and Suppliers (Alternative Notation 4) Company# Contains Line-Item Part#Invoice# Part Part# Count Price m Supplier Company# Part# Cost Supplying

8/28/97Information Organization and Retrieval Parts and Suppliers (Alternative Notation 5) Part Part# Count Price m Supplier Company# Cost Supplies

8/28/97Information Organization and Retrieval ER Model Orders Customer Cust# Invoice Writes Sales-Rep Invoice# Sales Rep# Line-Item Contains Part# QuantityInvoice# Cust# Contains Part Part#Count Price Supplier Company# Ordered Part Hourly Employee ISA Emp# Wage Company# Part#Cost Supplied Part Has On-Order Supplies Company# Part#Quantity

8/28/97Information Organization and Retrieval Next Time More on normalization Effectiveness and Efficiency criteria for database designs Advantages and failings of DBMS technology