IS6125 Database Analysis and Design Lecture 8: Practice with ERDs

Slides:



Advertisements
Similar presentations
ER Modeling Case Studies
Advertisements

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.
Entity-Relationship Modeling (ER-M)
ER Modeling Case Studies
Draw an ER Diagram for the following (record any assumptions):
Case study Lisa’s Bookstore IST210.
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.
Practice of ER modeling
Instructor :Huda Al-Omair
1 Entity-Relationship Diagram. 2 Components of ERD: –Entity –Relationship –Cardinality –Attributes.
ERD ( Conceptual data model From the statement of data requirements a conceptual data model is produced. This describes.
Database Design – Lecture 6 Moving to a Logical Model.
IS6145 Database Analysis and Design Lecture 4: Fine-Granular Design-Specific ER Modelling Rob Gleasure
EntityRelationshipDiagrams. Entity Relationship Models The E-R (entity-relationship) data model views the real world as a set of basic objects (entities)
COMP 430 Intro. to Database Systems Entity-Relationship Diagram Basics Slides use ideas from Chris Ré.
Extra ER. Q1: Draw an ER diagram A construction company wishes to establish a database system to record information about employees. The employee data.
G057 - Lecture 05 From Scenario To Design Mr C Johnston ICT Teacher
DATA MODELING AND ENTITY-RELATIONSHIP MODEL II IST 210: Organization of Data IST210 1.
Contents Design Process Modeling Constraints E-R Diagram Design Issues
IS6145 Database Analysis and Design Lecture 4: Fine-Granular Design-Specific ER Modelling Rob Gleasure
Week 03 – ER Diagram INFOSYS 222.
Let try to identify the conectivity of these entity relationship
Rob Gleasure IS3320 Developing and Using Management Information Systems Lecture 15: Data-Flow Diagrams 2 – Level.
IS6125 Database Analysis and Design Lecture 7: Enhanced Entity-Relationship (EER) Modeling Rob Gleasure
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Entity-Relationship Model
IS6125 Database Analysis and Design Lecture 5: Conceptual Data Modelling 2: ER Modelling and Beyond the Presentation Layer Rob Gleasure
IS6125 Database Analysis and Design Lecture 4: Conceptual Data Modelling 1: The Foundational Concepts Rob Gleasure
IS6145 Database Analysis and Design Lecture 5: Enhanced Entity-Relationship (EER) Modeling Rob Gleasure
E-R Diagram (Cont.) Draw ER Diagram for the following scenario:
Entity-Relationship Model
Entity-Relationship Modelling
Database EER.
IS6125 Database Analysis and Design Examples for exam revision
ER MODEL Lecture 3.
IS6145 Database Analysis and Design Examples for exam revision
ER Modeling Case Studies
بسم الله الرحمن الرحيم.
ERD’s REVIEW DBS201.
Amazom.com “Product/Book Information Management Business Process”
IS6125/IS6145 Database Analysis and Design Lecture 4: Fine-Granular Design-Specific ER Modelling Rob Gleasure
IS6125 Database Analysis and Design Lecture 6: Fine-Granular Design-Specific ER Modelling Rob Gleasure
Extra ER.
IS6125/IS6145 Database Analysis and Design Lecture 2: Conceptual Data Modelling 1: The Foundational Concepts Rob Gleasure
IS6145 Database Analysis and Design Lecture 5: Enhanced Entity-Relationship (EER) Modeling Rob Gleasure
Entity-Relationship Modeling "Extended"
Entity – Relationship Model
Extra ER.
Entity-Relationship Modelling
MIS2502: Data Analytics Relational Data Modeling
Bookstore DB Requirements
IS6145 Database Analysis and Design Lecture 3: Conceptual Data Modelling 2: ER Modelling and Beyond the Presentation Layer Rob Gleasure
Database Modeling using Entity Relationship Model (E-R Model)
IS6125 Database Analysis and Design Lecture 7: Enhanced Entity-Relationship (EER) Modeling Rob Gleasure
Conceptual Data Modeling Using Entities & Relationships
Databases.
ER Modeling Case Studies
Chapter Entity-Relationship Modeling & Enhanced Entity- Relationship Modeling.
MIS2502: Data Analytics Relational Data Modeling 2
Entity Relation Model Tingting Zhang.
Conceptual modeling of databases
Database Management system
Entity Relationship Model
Entity-Relationship Modeling "Extended"
Extra ER.
Entity-Relationship Modeling "Extended"
IS6145 Database Analysis and Design Lecture 6: Practice with ERDs
Extra ER LAB #2.
Recursive Relationship and Weak Entity Examples
Presentation transcript:

IS6125 Database Analysis and Design Lecture 8: Practice with ERDs Rob Gleasure R.Gleasure@ucc.ie www.robgleasure.com

From IS6125 Winter Exam 2015 Draw an Enhanced Coarse Granular Design-Specific Entity-Relationship Diagram using Chen’s notation based on the following narrative: A publisher employs both authors and editors. For authors, data need to be stored for their name, address, and one or more emails. For editors, data need to be stored for their name, employee number, and salary. Some editors are senior editors, in which case their start date in that role will be recorded, as well as possibly an end date. Other editors are associate editors, in which case a domain of interest will be noted. A list of paired editors must also be provided, which provides all data relating to these editors, plus total editor-related salary overheads for that pair. Data also need to be stored for different books, including the book’s unique ISBN, the title, and a list price. Books are mostly horror (in which case they are assigned a violence rating from 1-5), non-fiction (in which case they are assigned a period and possibly a related historic event), or teen fiction (in which case they are assigned an age recommendation of ‘early teens’ or ‘mid-to-late teens’). Books may also be available second hand, in which case a reduced price will be stored. Books are associated with at least one author and at least one editor.

One possible solution

From IS6125 Winter Exam 2014 Draw an Enhanced Entity-Relationship (EER) Diagram* using Chen’s notation: A company is comprised of many branches. Each branch employs numerous managers across a range of functions but managers only work for one branch. Managers are involved in just one function in a branch, including marketing and sales, product development, and human resources. Data that needs to be stored for all managers, regardless of branch, include their employee number, name, qualifications, date of birth, phone number, age, and internal awards. Managers working in marketing and sales also need to have data stored for their dedicated clients, current sales quota, previous sales quota for the same quarter the previous year, and the proportion of sales they have brokered that have later broken down (or ‘breakdown ratio’). Managers working in product development also need to have data stored for each project currently under development, patents registered, and technical qualifications. Managers working in human resources also need to have data stored for the languages they speak, initiatives pioneered, and any reports logged. Note that some managers will be working in a branch on a long-term basis, in which case data will also need to be stored regarding their pension details and dependents. Other managers will be working in a branch as a sponsored exchange with a sister company, in which case the duration and objectives of the exchange will be noted, as well as the relationship to the sister company.

One possible solution