SLIDE 1IS 257 – Spring 2004 Database Design: Conceptual Model and ER Diagramming Ray R. Larson University of California, Berkeley School of Information Management and Systems SIMS 257: Database Management

SLIDE 2IS 257 – Spring 2004 Lecture Outline Review –Information Systems Planning –Information Systems Architecture –Information Engineering Database Design ER Diagrams Developing the Conceptual Model

SLIDE 3IS 257 – Spring 2004 Lecture Outline Review –Information Systems Planning –Information Systems Architecture –Information Engineering Database Design ER Diagrams Developing the Conceptual Model

SLIDE 4IS 257 – Spring 2004 Review Information Systems Planning Information Systems Architecture Information Engineering Database Design

SLIDE 5IS 257 – Spring 2004 Information Systems Architecture Zachman ISA Framework components –Data The “what” of the information system –Process The “how” of the information system –Network The “where” of the information system –People Who performs processes and are the source and receiver of data and information. –Events and Points in time When processes are performed –Reasons For events and rules that govern processing

SLIDE 6IS 257 – Spring 2004 Information Engineering A formal methodology that is used to create and maintain information systems Starts with the Business Model and works in a Top-Down fashion to build supporting data models and process models for that business model

SLIDE 7IS 257 – Spring 2004 Information Engineering Planning Design Analysis Implementation

SLIDE 8IS 257 – Spring 2004 Lecture Outline Review –Information Systems Planning –Information Systems Architecture –Information Engineering Database Design ER Diagrams Developing the Conceptual Model

SLIDE 9IS 257 – Spring 2004 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

SLIDE 10IS 257 – Spring 2004 Stages in Database Design Requirements formulation and analysis Conceptual Design -- Conceptual Model Implementation Design -- Logical Model Physical Design --Physical Model

SLIDE 11IS 257 – Spring 2004 Database Design Process Requirements formulation and analysis –Purpose: Identify and describe the data that are used by the organization –Results: Metadata identified, Data Dictionary, Conceptual Model-- ER diagram

SLIDE 12IS 257 – Spring 2004 Database Design Process Requirements Formulation and analysis –Systems Analysis Process Examine all of the information sources used in existing applications Identify the characteristics of each data element –numeric –text –date/time –etc. Examine the tasks carried out using the information Examine results or reports created using the information

SLIDE 13IS 257 – Spring 2004 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?

SLIDE 14IS 257 – Spring 2004 Database Design Process Logical Model –How is each entity and relationship represented in the Data Model of the DBMS Hierarchic? Network? Relational? Object-Oriented?

SLIDE 15IS 257 – Spring 2004 Database Design Process Physical (AKA Internal) Model –Choices of index file structure –Choices of data storage formats –Choices of disk layout

SLIDE 16IS 257 – Spring 2004 Database Design Process External Model –User views of the integrated database –Making the old (or updated) applications work with the new database design

SLIDE 17IS 257 – Spring 2004 Lecture Outline Review –Information Systems Planning –Information Systems Architecture –Information Engineering Database Design ER Diagrams Developing the Conceptual Model

SLIDE 18IS 257 – Spring 2004 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

SLIDE 19IS 257 – Spring 2004 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

SLIDE 20IS 257 – Spring 2004 Relationships Relationships are the associations between entities. They can involve one or more entities and belong to particular relationship types

SLIDE 21IS 257 – Spring 2004 Relationships Class Attends Student Part Supplies project parts Supplier Project

SLIDE 22IS 257 – Spring 2004 Types of Relationships Concerned only with cardinality of relationship Truck Assigned EmployeeProject Assigned EmployeeProject Assigned Employee 11 n n 1 m Chen ER notation

SLIDE 23IS 257 – Spring 2004 Other Notations Truck Assigned EmployeeProject Assigned EmployeeProject Assigned Employee “Crow’s Foot”

SLIDE 24IS 257 – Spring 2004 Other Notations Truck Assigned EmployeeProject Assigned EmployeeProject Assigned Employee IDEFIX Notation

SLIDE 25IS 257 – Spring 2004 More Complex Relationships Project Evaluation Employee Manager 1/n/n 1/1/1 n/n/1 Project Assigned Employee 4(2-10) 1 SSNProjectDate Manages Employee Manages Is Managed By 1 n

SLIDE 26IS 257 – Spring 2004 Weak Entities Owe existence entirely to another entity Order-line Contains Order Invoice # Part# Rep# QuantityInvoice#

SLIDE 27IS 257 – Spring 2004 Supertype and Subtype Entities Clerk Is one of Sales-rep Invoice Other Employee Sold Manages

SLIDE 28IS 257 – Spring 2004 Many to Many Relationships Employee Project Is Assigned Project Assignment Assigned SSN Proj# SSN Proj# Hours

SLIDE 29IS 257 – Spring 2004 Lecture Outline Review –Information Systems Planning –Information Systems Architecture –Information Engineering Database Design ER Diagrams Developing the Conceptual Model

SLIDE 30IS 257 – Spring 2004 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. Can also be represented using other modeling tools (such as UML)

SLIDE 31IS 257 – Spring 2004 Developing a Conceptual Model Building the Conceptual Model for the Diveshop database Names for the Diveshop company?

SLIDE 32IS 257 – Spring 2004 Developing a Conceptual Model We will look at a small business -- a diveshop that offers diving adventure vacations 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...

SLIDE 33IS 257 – Spring 2004 Primary Business Operations The shop takes orders from customers for dive vacations. It ships information about the dive vacation to the customers. It rents diving equipment for the divers going on the trips (these may include additional people other than the customer) It bills the customer for the vacation and for equipment rental or sales.

SLIDE 34IS 257 – Spring 2004 Business Operations (cont.) It arranges sub-trips to particular dive sites at the primary location. It provides information about the features of various sites to help customers choose their destinations. –Features include sea life found at the location and shipwrecks

SLIDE 35IS 257 – Spring 2004 Business Operations (cont.) Each dive order (or sale or trip) is on an invoice to one customer. –Invoices contain: Line items for each type of equipment ordered, Total amount due for the invoice, Customer information: –Name, address, phone, credit card info. Information must be kept on inventory of dive equipment. There are multiple types of dive equipment: –The prices charged for sale or rental are maintained.

SLIDE 36IS 257 – Spring 2004 Business Operations (cont.) Destination information includes: –Name of the destination –information about the location (accomodations, night life, travel cost, average temperatures for different times of the year Destinations have associated dive sites. Dive Sites have associated features – Sea life –Shipwrecks

SLIDE 37IS 257 – Spring 2004 Business Operations (cont.) One record is kept for each order by a customer and will include the method of payment, total price, and location information. (I.e. Customers may have multiple orders) The company needs to know how an order is to be shipped. The shop has to keep track of what equipment is on-hand and when replacements or additional equipment is needed

SLIDE 38IS 257 – Spring 2004 Entities Customer Dive Order Line item Shipping information Dive Equipment/ Stock/Inventory Dive Locations Dive Sites Sea Life Shipwrecks

SLIDE 39IS 257 – Spring 2004 Diveshop Entities: DIVECUST Name Customer no Street State/ProvCity ZIP/Postal Code Country First Contact Phone DiveCust

SLIDE 40IS 257 – Spring 2004 Diveshop Entities: DIVEORDS Customer No Order no Sale Date Ship Via Destination CCExpDate CCNumber Payment Method DiveOrds No of People Vacation Cost Return Date Depart Date

SLIDE 41IS 257 – Spring 2004 Diveshop Entities: DIVEITEM Item no Order no Rental/ Sale Qty Line Note DiveItem

SLIDE 42IS 257 – Spring 2004 Diveshop Entities: SHIPVIA Ship Via Ship Cost ShipVia

SLIDE 43IS 257 – Spring 2004 Diveshop Entities: DIVESTOK Description Item No Equipment Class Reorder Point On HandCost Sale Price DiveStok Rental Price

SLIDE 44IS 257 – Spring 2004 Diveshop Entities: DEST Destination name Destination no Avg Temp (F) Spring Temp (F) Avg Temp (C) Summer Temp (C) Summer Temp (F) Travel Cost Winter Temp (C) Fall Temp (F) Fall Temp (C) Dest Winter Temp (F) Accommodations Body of Water Night Life Spring Temp (C)

SLIDE 45IS 257 – Spring 2004 Diveshop Entities: SITES Destination no Site no Site Name Site Notes Site Highlight Distance From Town (M) Distance From Town (Km) Skill Level Visibility(ft) Depth (m) Depth (ft) Sites Visibility (m) Current

SLIDE 46IS 257 – Spring 2004 Diveshop Entities: BIOSITE Species No Site No BioSite

SLIDE 47IS 257 – Spring 2004 Diveshop Entities: BIOLIFE Category Species no Common Name Length (cm) Species Name Length (in) Notes external Graphic external BioLife

SLIDE 48IS 257 – Spring 2004 Diveshop Entities: SHIPWRCK Site no Ship Name Category InterestTypeTonnage Length (ft) Beam (m) Beam (ft) Length (m) Shipwrck Cause Comments external Date Sunk Passengers/ Crew Graphic external Survivors Condition

SLIDE 49IS 257 – Spring 2004 Functional areas Ordering Inventory Supplies Shipping Billing Location/Site Selection –We will concentrate on Ordering and Location/Site Selection (these are joined tasks)

SLIDE 50IS 257 – Spring 2004 Ordering Orders (DIVORDS) Customer (DIVECUST) Customers place Orders Each Order needs Customer information

SLIDE 51IS 257 – Spring 2004 Ordering DiveOrds Orders DiveCust Customer No ship ShipVia Order No Ship Via DiveItem Repeating attribute Customer No

SLIDE 52IS 257 – Spring 2004 Ordering Normalization DiveCust Orders Customer No DiveOrds Ship ShipVia Order No Ship Via DiveItem Contains Item No QtyOrder No Customer No Rental/sale

SLIDE 53IS 257 – Spring 2004 Details of DiveItem DiveStok Supplies Supplier Company# Has DiveItem Item No On Hand Sale Price Order No mn We’re ignoring this part...

SLIDE 54IS 257 – Spring 2004 Ordering: Full ER Customer No ShipVia Dest ShipVia DiveStok DiveItem DiveOrds DiveCust Customer No ShipVia Order No Order No Item No Item No Destination Name Destination no n n n n n

SLIDE 55IS 257 – Spring 2004 Location/Site Selection Dest Going to? DiveOrds Destination No Destination Name Destination

SLIDE 56IS 257 – Spring 2004 Destination/ Sites Dest Sites DiveOrds Customer No Order No Destination Name Destination Site No Destination no Destination no 1 1 n n

SLIDE 57IS 257 – Spring 2004 Sites and Sea Life 1 BioLife Sites Site No Destination no Multiple occurrences of sea life...

SLIDE 58IS 257 – Spring 2004 Diveshop ER diagram: BioSite Species No Site No BioSite

SLIDE 59IS 257 – Spring 2004 Sites and Sea Life 2 Sites BioSite BioLife Species No Site No Destination no Species No 1 1 n n

SLIDE 60IS 257 – Spring 2004 Sites and Shipwrecks Sites ShipWrck Site No Destination no Site No 1/n 1

SLIDE 61IS 257 – Spring 2004 DiveShop ER Diagram Customer No ShipVia Dest Sites BioSite ShipVia ShipWrck BioLife DiveStok DiveItem DiveOrds DiveCust Customer No ShipVia Order No Order No Item No Item No Destination Name Destination Species No Site No Destination no Site No Destination no Species No Site No /n 1 1n n n n n n n n 1

SLIDE 62IS 257 – Spring 2004 What must be calculated? Total price for equipment rental? Total price for equipment sale? Total price of an order? –Vacation price –Equipment (rental or sale) –Shipping

SLIDE 63IS 257 – Spring 2004 What is Missing?? Not really an “enterprise-wide” database –No personnel Sales people Dive masters Boat captains and crew payroll –Local arrangements Dive Boats Hotels –Suppliers/Wholesalers for dive equipment Orders for new/replacement equipment –No history (only current or last order)

SLIDE 64IS 257 – Spring 2004 Next Time TUESDAY: –More on UML database modeling –Designing the Logical Model