CIS458 Organizational Database Management Sungchul Hong

Slides:



Advertisements
Similar presentations
ER Model For a college DB
Advertisements

More Diagramming & Practice with Relationship Modeling
Information System Analysis Lab 7. ERD entity-relationship diagram is a data modeling technique that creates a graphical representation of the entities,
Business Processes, Data Modeling and Information Systems
Tuesday, February 1, Management of Information Systems: Mini-3 Spring 2000.
Systems Development Life Cycle
Systems Development Life Cycle
The Database Approach u Emphasizes the integration of data across the organization.
Logical Database Design and the Relational Model (part 1)
Saturday May 02 PST 4 PM. Saturday May 02 PST 10:00 PM.
Thursday, January 27, Management of Information Systems: Mini-3 Spring 2000.
Database Design Chapter 2. Goal of all Information Systems  To add value –Reduce costs –Increase sales or revenue –Provide a competitive advantage.
FIS 431/631 Financial Information Systems: Analysis and Design ERD & Normalization Joe Callaghan Oakland University Department of Accounting & Finance.
Terms - data,information, file record, table, row, column, transaction, concurrency Concepts - data integrity, data redundancy, Type of databases – single-user,
Practice of ER modeling
Introduction to Database Systems
Principles of Database Design, Part II AIMS 2710 R. Nakatsu.
Practice of ER modeling - Answer Yong Choi School of Business CSUB.
Entity Relationship Diagrams (ERDs). Entity Relationship Diagram (ERD) documentation technique to represent relationship between entities in system. Think.
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Rob and Coronel Adapted for INFS-3200.
SALINI SUDESH. Primarily a tool to validate and improve a logical design so that it satisfies certain constraints that avoid unnecessary duplication of.
Chapter 9 View Design and Integration. © 2001 The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin Outline Motivation for view design.
Business ByDesign (Case Study II) EGN 5621 Enterprise Systems Collaboration Fall, 2011.
1 Entity-Relationship Diagram. 2 Components of ERD: –Entity –Relationship –Cardinality –Attributes.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
The Hong Kong University of Science and Technology COMP3311 Spring 2013 Tutorial 1 ER Diagrams.
© 2005 by Prentice Hall 1 The Database Development Process Dr. Emad M. Alsukhni The Database Development Process Dr. Emad M. Alsukhni Modern Database Management.
Chapter 3: The Enhanced E-R Model
Database Examples.
Entity-Relationship Model Chapter 3 II COSC 457 Sungchul Hong.
COSC578 Database Management Systems Sungchul Hong
CS263 Lecture 5: Logical Database Design Can express the structure of a relation by a Tuple, a shorthand notation Name of the relation is followed (in.
Database Management Systems
1 The Entity- Relationship Model Instructor: Mohamed Eltabakh
Advanced Data Modeling. Heterogeneous Mapping Heterogeneous Mapping is the ability of MSTR7 tools to join on unlike column names. Heterogeneous Mapping.
Logical Database Design and the Relational Model.
1 The Entity- Relationship Model Instructor: Mohamed Eltabakh Part-2.
More Data Modeling CS 146. Relationship Lower Bounds  Lower bound: minimum number of related instances in a relationship  Value is typically 0 or 1.
Chapter 3: Modeling Data in the Organization. Business Rules Statements that define or constrain some aspect of the business Assert business structure.
Entity Relationship Diagram (ERD). Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship.
Entity Relationship Diagrams (ERDs)
Chapter 4, Part A: Logical Database Design and the Relational Model
Introduction to Database Systems
Chapter 3 1 Chapter 3: Modeling Data in the Organization.
Copyright © 2016 Pearson Education, Inc. Modern Database Management 12 th Edition Jeff Hoffer, Ramesh Venkataraman, Heikki Topi CHAPTER 4: PART C LOGICAL.
Database Management Systems
Order Database – ER Diagram
Order Database – ER Diagram
Basic Database Design COSC 2328 – Web Programming.
Normalization Karolina muszyńska
MIS2502: Data Analytics Relational Data Modeling
Database Requirements and Design
Order Database – ER Diagram
Order Database – ER Diagram
MIS5101: Business Intelligence Relational Data Modeling
Example Question–Is this relation Well Structured? Student
CHAPTER 7: ADVANCED SQL.
ERD Exercises.
Practice of ER modeling
MIS2502: Data Analytics Relational Data Modeling
Technical Module A Data Modeling Definitions
Aggregations Various Aggregation Functions GROUP BY HAVING.
Customer Order Entry Database Version: 1.1 by: R. Holowczak
MIS2502: Data Analytics Relational Data Modeling
Order Database – ER Diagram
Medical Supply Management System
Order Database – ER Diagram
ITEC 3220M Using and Designing Database Systems
Some examples of simple business rules:
Presentation transcript:

CIS458 Organizational Database Management Sungchul Hong ERD Exercise #2 CIS458 Organizational Database Management Sungchul Hong

Creating an ERD from the Investigated Facts Identify all the entities. Identify all the relationships. Identify cardinality and multiplicities (min max). (1..*) (0..1) (0..*) (1..1)

Simple ERD 1 A painter can paint many paintings; each painting is painted by one painter. A gallery can have many paintings. A painting can be exhibited by a gallery. Paint ► (0..*) Displayed (1..1) ► Painter (1,1) (0..*) Painting Gallery

Simple ERD 2 An employee can learn many skills; each sill can be learned by many employees. Expert Level? (L1.. L5) Learn ► (0..*) (0..*) Employee Skills Expert Level

Simple ERD 3 An employee manages one store; each store is managed by one employee Employee Store Manages ► (0..1) (1..1) Employee Store

Simple ERD 4 A College example Students in a typical college or university will discover that each course can have many sections or no section, by each section refers to only one course. For example, an Accounting II course might have two sections: one offered on Monday, Wednesday, and Friday from 10:00 a.m. to 10:50 a.m., and one offered on Thursday from 6:00 p.m. to 8:40 p.m.

Has ► (1..1) (0..*) Course Section

Simple ERD 5 Each student can take many classes (or no class at all) and each class can contain many students. Add Grade Take ► (1..*) (0..*) Student Classes Grade

Combining ERDs A class can be identified with course and section. Has ► (1..1) (0..*) Course Section Take ► (1..*) (0..*) Student Section

Has ► (1..1) (0..*) Course Section (0..*) Take▼ (1..*) Student

Adding Additional Conditions Adding prerequisite, enroll grade Has ► (1..1) (0..*) Course Section (0..*) (0..*) (0..*) Take ▼ Grade ◄Prerequisite (1..*) Student

Case Study (Pine Valley Furniture Company ) 1. The company sells a number of different furniture products. These products are grouped into several product lines. The identifier for a product is Product_ID, while the identifier for a product line is Product_Line_ID. Referring to the customer invoice, we identify the following additional attributes for product: Product_Description, Product_Finish, and Unit_Price. Another attribute fro product line is Product_Line_Name. A product line may group any number of products, but must group at least one product. Each product must belong to exactly one product line.

Case Study 2. Customers submit orders for products The identifier fro an order is Order-ID, and another attribute is Order_Date. A customer may submit any number of orders, but need not submit any orders. Each order is submitted by exactly one customer. The identifier for a customer is Customer_ID. Other attributes include Customer_Name and Customer_Address.

Case Study 3. A given customer order must request at least one product. Any product sold by Pine Valley Furniture may not be requested on any order, or may be requested on one or more orders. An attribute associated with each order and product is Quantity, which is the number of units requested.

Case Study 4. Pine Valley Furniture has established sales territories for its customers. Each customer does business in one or more of these sales territories. The identifier for a sales territory is Territory_ID. A sales territory may have any number of customers, or may not have any customers doing business.

Case Study 5. Pine Valley Furniture Company has several salespersons. The identifier for a salesperson is Salesperson_ID. Other attributes include Salesperson_Name, Salesperson_Telephone, and Salesperson_Fax. A salesperson serves exactly one sales territory. Each sales territory is served by one or more salespersons.

Case Study 6. Each product is assembled from one or more raw materials. The identifier for the raw material entity is Material_ID. Other attributes include Unit_of_Measure and Unit_Price. Each raw material may be assembled into one or more products.

Case Study 7. Raw materials are supplied by vendors. The identifier for a vendor is Vendor_ID. Other attributes include Vendor_Name and Vendor_Address. Each raw material can be supplied by one or more vendors. A vendor may supply any numver of raw materials, or may not supply any raw materials to Pine Valley Furniture. An attribute of the relationship between vendor and raw material is Unit_Price

Case Study 8. Pine Valley Furniture has established a number of work centers. The identifier for a work center is Work_Center_ID. Another attribute is Location. Each product is produced in one or more work centers. A work center may be used to produce any number of products, or may not be used to produce any products.

Case Study 9. The company has over 100 employees. The identifier for employee is Employee_ID. Other attributes are Employee_Name, EmployeeAddress, and Skill. An employee may have more than one skill. A skill can be mastered by many employees

Case Study 10. Each employee works in one or more work centers. A work center must have at least one employee working in that center, but may have any number of employees.

Case Study 11. Each employee has exactly one supervisor. An employee who is a supervisor may supervise any number of employees, but not all employees are supervisors.