1 Database Design Victor Matos. 2 Phases of Database Design u Conceptual design begins with the collection of requirements and results needed from the.

Slides:



Advertisements
Similar presentations
ER Modeling Case Studies
Advertisements

The Entity-Relationship Model
Entity-Relationship Models
The Entity-Relationship (ER) Model
Ch5: ER Diagrams - Part 1 Much of the material presented in these slides was developed by Dr. Ramon Lawrence at the University of Iowa.
Draw an ER Diagram for the following (record any assumptions):
1 The Entity-Relationship Model Chapter 2. 2 Overview of Database Design  Conceptual design: (ER Model is used at this stage.) –What are the entities.
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.
From Class Diagrams to Databases. So far we have considered “objects” Objects have attributes Objects have operations Attributes are the things you record.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model.
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.
Modeling Data The Entity Relationship Model (ER) For Database Design.
Entity-Relationship Model and Diagrams (continued)
Data Modeling ISYS 464. Database Design Process Conceptual database design: –The process of creating a data model independent of implementation details.
WELL-DESIGNED DATABASES Process faster Easy to develop and maintain Easy to read and write code.
Slides adapted from A. Silberschatz et al. Database System Concepts, 5th Ed. Entity-Relationship Model Database Management Systems I Alex Coman, Winter.
8/28/97Information Organization and Retrieval Files and Databases University of California, Berkeley School of Information Management and Systems SIMS.
ENTITY RELATIONSHIP DATA MODEL ELIZABETH GEORGE. INTRODUCTION Architect Aeronautical engineers Computer architects Traffic engineers.
1 Data Modelling Which data to include in the database.
Data modeling using the entity-relationship model Winter 2006Ron McFadyen Entity-relationship model (ER model) P. 49: “This model and its variations.
LECTURE 2 DATABASE SYSTEM CONCEPTS AND ARCHITECTURE.
Chapter 3 Data Modeling Using the Entity- Relationship (ER) Model Dr. Bernard Chen Ph.D. University of Central Arkansas.
1 Database Requirements and Design. 2 DATA PEOPLE PROCEDURES HARDWARE SOFTWARE The Product: a working system.
Data Modeling Using the Entity-Relationship Model
DeSiamorewww.desiamore.com/ifm1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
CSE314 Database Systems Data Modeling Using the Entity- Relationship (ER) Model Doç. Dr. Mehmet Göktürk src: Elmasri & Navanthe 6E Pearson Ed Slide Set.
Advanced Entity Relationship Concepts. Advanced Concepts UIDs Intersection Entities Recursive Relationships Roles Subtypes Exclusivity Historical Fan.
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.
11 1 Object oriented DB (not in book) Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Learning objectives: What.
Practice of ER modeling
Principles of Database Systems With Internet and Java Applications Today’s Topic Chapter 2: Representing Information with Data Models The lecture notes.
Conceptual Design and Data Modeling Chapter 2. 10/15/2015Chapter 22 of 37 Database Design Process Conceptual Design Conceptual Design Investigate business.
Chapter 3 Data Modeling Using the Entity- Relationship (ER) Model Dr. Bernard Chen Ph.D. University of Central Arkansas Fall 2008.
1 Relational Databases and SQL. Learning Objectives Understand techniques to model complex accounting phenomena in an E-R diagram Develop E-R diagrams.
CS370 Spring 2007 CS 370 Database Systems Lecture 4 Introduction to Database Design.
Overview of Database Development Data Modeling and Relational Database Design.
Msigwaemhttp//:msigwaem.ueuo.com/1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
1 A Demo of Logical Database Design. 2 Aim of the demo To develop an understanding of the logical view of data and the importance of the relational model.
Data modeling using the entity-relationship model Chapter 3 Objectives How entities, tuples, attributes and relationships among entities are represented.
IT 21103/41103 System Analysis & Design. Chapter 04 Data Modeling.
ITEC 3220A Using and Designing Database Systems Instructor: Prof Z. Yang Course Website: 3220a.htm
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model.
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.
Data Modelling Using Entity-Relationship (ER) Model
1 The Entity- Relationship Model Instructor: Mohamed Eltabakh
Instructor: Jinze Liu Fall Phases of Database Design u Conceptual design begins with the collection of requirements and results needed from the.
1 Database Systems Entity Relationship (E-R) Modeling.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model.
Entity Relationship Diagram (ERD). Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship.
Introduction to Database Systems
CSE 412/598 DATABASE MANAGEMENT COURSE NOTES 3. ENTITY-RELATIONSHIP CONCEPTUAL MODELING Department of Computer Science & Engineering Arizona State University.
2 1 Database Systems: Design, Implementation, & Management, 7 th Edition, Rob & Coronel Data Models Why data models are important About the basic data-modeling.
Example COMPANY Database
Database Development Lifecycle
ER model Ashima Wadhwa.
Entity-Relationship Model
Database Requirements and Design
Entity-Relationship Modeling
بسم الله الرحمن الرحيم.
Entity-Relationship Model and Diagrams (continued)
Practice of ER modeling
Entity-Relationship Modeling "Extended"
Conceptual Data Modeling Using Entities & Relationships
ITEC 3220A Using and Designing Database Systems
ER Modeling Case Studies
CS 505: Intermediate Topics to Database Systems
Entity-Relationship Modeling "Extended"
Some examples of simple business rules:
Entity-Relationship Modeling "Extended"
Presentation transcript:

1 Database Design Victor Matos

2 Phases of Database Design u Conceptual design begins with the collection of requirements and results needed from the database (ER Diag.) u Logical schema is a description of the structure of the database (Relational, Network, etc.) u Physical schema is a description of the implementation (programs, tables, dictionaries, catalogs

3 Models A data model is a collection of objects that can be used to represent a set of data and operations to manipulate the data u Conceptual models are tools for representing reality at a very high-level of abstraction u Logical models are data descriptions that can be processed by computers

4 Conceptual model: Entity-Relationship Diagrams  Entities represent classes of real-world objects. Person, Students, Projects, Courses are entities of a University database u Relationships represent interactions between two or more entities

5 Example: u Every employee works in at least one project u Every project has employees working on it.

6 Higher-Order Relationships A relationship may involve more than two entities

7 Recursive relationships Relationships could be mapped from one entity to itself

8 Attributes Attributes represent elementary properties of the entities or relationships. The stored data will be kept as values of the attributes

9 Generalizations An entity could be seen from many different viewpoints Each viewpoint defines a set of roles in a generalization Example below uses SEX to classify the object “Person”

10 Generalizations u A classification could be disjoint or overlapping u An entity could have more than one classification

11 Example: Department Store 1/2 u A department store operates in several cities u In a city there is one headquarter coordinating the local operations u A city may have several stores u Stores hold any amount of items u Customers place their orders for any number of items to a given store GOAL: Optimize shopping in each city

12 Example: Department Store 2/2

13 Example: University Database u Professors work for only one department u Departments have many professors u Each course is taught by only one professor u Students make a plan or program of study u A course could meet in several rooms/times u Graduate students must have an advisor u Cities are categorized as resident/BirthPlace u Visiting prof. need an End/Start date

14 University Database University database

15 Soccer Database u A team has players, one coach, fans u Teams play according to a schedule u Teams need to practice in a Stadium u Attendance and scores must be recorded

16 Soccer Database

17 Research Project Database u Some employees are researchers u Every project has a leader investigator u Every project must be funded by an agency u A project may include several topics u A topic could appear in several projects u Researchers must produce report(s) u Each employee must have a supervisor

18 Research Projects Database

19 Contract-Supplies System 1/3 u A company negotiates contracts with suppliers to provide certain amount of items at a fixed price u Orders are placed against any of the already negotiated contracts u A contract could provide items to any number of orders

20 Contract-Supplies System 2/3 u An order may include any number of items negotiated in the contract u Orders should not exceed the maximum amount of items quoted in the contract u All items in an order must be provided as part of a single contract and a single project

21 Contract-Supplies System 3/3

22 Manufacturing: Requisitions 1/3 u Projects are broken into tasks u Tasks are assigned to departments u A task is created for one project and assigned to one department u Requisitions are made for projects u Each requisition could ask for any number of items

23 Manufacturing: Requisitions 2/3 u Each requisition is for one project and is made to one supplier u Items could be: equipment or materials and are coded in a similar way u Suppliers send periodic price notices to advise the company of any changes in their prices

24 Manufacturing: Requisitions 3/3

25 Job-Shop Accounting System 1/4 u The system is used by a company that manufactures special-purpose assemblies for customers u To manufacture assemblies the company creates a sequence of processes (steps) u Each process is supervised by a department u Assume there are three type of processes: PAINT, FIT, CUT

26 Job-Shop Accounting System 2/4 u During manufacturing an assembly could pass through any sequence of processes, in any order; it may pass through the same process more than once u A unique Job# is given to any new assembly. u Costs and started-terminated dates must be recorded

27 Job-Shop Accounting System 3/4 u An accounting system is used to keep track expenditure for each: u DEPT, u PROCESS, u ASSEMBLY u As a job proceeds, cost transactions can be recorded against it.

28 Job-Shop Accounting System 4/4