ComponentNo. C_Description UnitOfMeasure. C_Quantity



Similar documents
RELATIONSHIP STRENGTH

Conceptual Design: Entity Relationship Models. Objectives. Overview

An Example: Video Rental System

Unit 2.1. Data Analysis 1 - V Data Analysis 1. Dr Gordon Russell, Napier University

Database Design. Marta Jakubowska-Sobczak IT/ADC based on slides prepared by Paula Figueiredo, IT/DB

Database Design Process

Database Design Process

A Short Tutorial on Using Visio 2010 for Entity-Relationship Diagrams

ER modelling, Weak Entities, Class Hierarchies, Aggregation

Data Analysis 1. SET08104 Database Systems. Napier University

Database Management Systems

Data Modelling and E-R Diagrams

A brief overview of developing a conceptual data model as the first step in creating a relational database.

Chapter 3. Data Modeling Using the Entity-Relationship (ER) Model

Entity - Relationship Modelling

Designing Databases. Introduction

Foundations of Information Management

DATABASE INTRODUCTION

three Entity-Relationship Modeling chapter OVERVIEW CHAPTER

Welcome to the Data Analytics Toolkit PowerPoint presentation on EHR architecture and meaningful use.

1 Class Diagrams and Entity Relationship Diagrams (ERD)

Foundations of Information Management

Developing Entity Relationship Diagrams (ERDs)

Exercise 1: Relational Model

Using Entity-Relationship Diagrams To Count Data Functions Ian Brown, CFPS Booz Allen Hamilton 8283 Greensboro Dr. McLean, VA USA

Modern Systems Analysis and Design

Lecture 12: Entity Relationship Modelling

Lecture Notes INFORMATION RESOURCES

CIS 631 Database Management Systems Sample Final Exam

Chapter 2: Entity-Relationship Model. E-R R Diagrams

Fundamentals of Database Design

Entity Relationship Diagram

Data Modeling: Part 1. Entity Relationship (ER) Model

Chapter 2: Entity-Relationship Model. Entity Sets. " Example: specific person, company, event, plant

Chapter 2: Entity-Relationship Model

Concepts of Database Management Seventh Edition. Chapter 6 Database Design 2: Design Method

2. Conceptual Modeling using the Entity-Relationship Model

Comp 3311 Database Management Systems. 2. Relational Model Exercises

Lesson 8: Introduction to Databases E-R Data Modeling

Entity-Relationship Model

SCHEMAS AND STATE OF THE DATABASE

EXTENDED LEARNING MODULE A

AS LEVEL Computer Application Databases

7.1 The Information system

Relational Database Concepts

Database Design Basics

The Entity-Relationship Model

Database IST400/600. Jian Qin. A collection of data? A computer system? Everything you collected for your group project?

Introduction to normalization. Introduction to normalization

Preview DESIGNING DATABASES WITH VISIO PROFESSIONAL: A TUTORIAL

Bridge from Entity Relationship modeling to creating SQL databases, tables, & relations

DATABASE MANAGEMENT SYSTEMS. Question Bank:

A Tutorial on Quality Assurance of Data Models 1. QA of Data Models. Barry Williams. tutorial_qa_of_models.doc Page 1 of 17 31/12/ :18:36

A Comparative Analysis of Entity-Relationship Diagrams 1

Converting E-R Diagrams to Relational Model. Winter Lecture 17

Data Modeling Basics

An analysis of structural validity in entity-relationship modeling

Ken Goldberg Database Lab Notes. There are three types of relationships: One-to-One (1:1) One-to-Many (1:N) Many-to-Many (M:N).

not necessarily strictly sequential feedback loops exist, i.e. may need to revisit earlier stages during a later stage

CHAPTER 3: DATA MODELING USING THE ENTITY-RELATIONSHIP MODEL

The E-R èentity-relationshipè data model views the real world as a set of basic objects èentitiesè and

14 Databases. Source: Foundations of Computer Science Cengage Learning. Objectives After studying this chapter, the student should be able to:

THE ENTITY- RELATIONSHIP (ER) MODEL CHAPTER 7 (6/E) CHAPTER 3 (5/E)

The 3 Normal Forms: Copyright Fred Coulson 2007 (last revised February 1, 2009)

Database Design and the E-R Model

Designing a Database Schema

Hotel Management System

2.0 Welcome Introduction What is the Scope? What are the Things of Interest? Creating Entities...

Select the Crow s Foot entity relationship diagram (ERD) option. Create the entities and define their components.

XV. The Entity-Relationship Model

Introduction to ERD modelling using UML Class diagrams with Magicdraw (ver 17)

Databases Model the Real World. The Entity- Relationship Model. Conceptual Design. Steps in Database Design. ER Model Basics. ER Model Basics (Contd.

CSC 742 Database Management Systems

Introduction to Database Systems CS4320/CS5320. CS4320/4321: Introduction to Database Systems. CS4320/4321: Introduction to Database Systems

Chapter 2. Data Model. Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel

CS 451 Software Engineering

Automata Theory. Şubat 2006 Tuğrul Yılmaz Ankara Üniversitesi

Tutorial on Relational Database Design

Access Part 2 - Design

Lecture #11 Relational Database Systems KTH ROYAL INSTITUTE OF TECHNOLOGY

Database Management System

Attribute Data and Relational Database. Lecture 5 9/21/2006

Database Design. Adrienne Watt. Port Moody

NATIONAL OPEN UNIVERSITY OF NIGERIA

Database Setup. Coding, Understanding, & Executing the SQL Database Creation Script

Animated Courseware Support for Teaching Database Design

BİL 354 Veritabanı Sistemleri. Entity-Relationship Model

Outline. Data Modeling. Conceptual Design. ER Model Basics: Entities. ER Model Basics: Relationships. Ternary Relationships. Yanlei Diao UMass Amherst

Microsoft Access 2003 Module 1

Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model

IV. The (Extended) Entity-Relationship Model

Challenges in database design with Microsoft Access

Relational Database Basics Review

Topic: Relationships in ER Diagram and Relationships in MS Access

The Entity-Relationship Model

Creating ER Diagrams with Visio 2010

Entity/Relationship Modelling. Database Systems Lecture 4 Natasha Alechina

MAT College Algebra

Quality Consistency Flexibility Affordability

Transcription:

MIS 322: ERD Exercises Student Name: 1. Assume that at Pine Valley Furniture each product (described by Product No., Description, and Cost) is comprised of at least three components (described by Component No., Description, and Unit of Measure) and components are used to make one or many products (i.e., must be used in at least one product). In addition, assume that components are used to make other components and that raw materials are also considered to be components. In both cases of components being used to make other components, we need to keep track of how many components go into making something else. Draw an E-R diagram for this situation and place minimum and maximum cardinalities on the diagram. This is a version of a bill-of-materials structure in which components are different entities from products, but raw materials are considered components. The exercise also indicates a minimum cardinality of three for the number of components composing a product, but no such restriction is placed on components as part of other components. Microsoft Visio was used to prepared this answer. PE # 1 Product Component Product No ComponentNo Cost P_Description C_Description UnitOfMeasure 3 Comprised Of,FK2,I2 Product No,FK1,I1 Component No C_Quantity GoesInto,FK1,I1 ComponentNo SubComponentNo Quantity 2. A software training program is divided into training modules, and each module is described by module name and the approximate practice time. Each module sometimes has prerequisite modules. Model this situation of training programs and modules with an E-R diagram. This exercise defines two entities TRAINING PROGRAM and TRAINING MODULE with a one-to-many relationship (Composed of) between them, and a unary optional (because some modules do not have a prerequisite, and some modules are not a prerequisite to other modules) many-to-many relationship (Is Prerequisite for) on the TRAINING MODULE entity.

3. Each semester, each student must be assigned an adviser who counsels students about degree requirements and helps students register for classes. Students must register for classes with the help of an adviser, but if their assigned adviser is not available, they may register with any adviser. We must keep track of students, their assigned adviser, and with whom the student registered for the current term. Represent this situation of students and advisers with an E-R diagram. This exercise defines two entities ADVISOR and STUDENT and two relationships Is Assigned Advisor and Registers between ADVISOR and STUDENT. An advisor is assigned to zero to many students, and a student is assigned to exactly one advisor; an advisor registers zero to many students, and a student is registered by exactly one advisor. An important rule in the exercise is that the data model covers only the current term, so no historical records need to be kept. As an alternative, it is also possible to create a data model with the above two entities and a ROLE associative entity in between, where ROLE has an attribute of ROLE PLAYED (which could take on values of Advises, Advises and Registers, and Registers ). Then, we would create a relationship between the entities through the associative entity such that an advisor is associated with zero to many students, and a student is associated with one or two advisors. The problem with this alternative is clarifying on only the data model what combination of ROLE PLAYED values are permitted for a given student.

4. Study the E-R diagram of Figure 7 20. Based on this E-R diagram, answer the following questions: a. How many PROJECTs can an employee work on? b. What is the degree of the Includes relationship? c. Are there any associative entities on this diagram? If so, name them. d. How else could the attribute Skill be modeled? e. Is it possible to attach any attributes to the Includes relationship? f. Could TASK be modeled as an associative entity? An employee can work on one-to-many projects; the Includes relationship is a binary relationship. No associative entities are directly shown by the associative entity symbol. The only many-to-many relationship, Works On, has no attributes, so it does not need to be shown as an associative entity. The SKILL attribute could also be modeled as an attributive or weak entity. It is not possible for the Includes relationship to have attributes because it is a one-to-many relationship. Only one-to-one and many-to-many relationships are allowed to have attributes. TASK could be modeled as an associative entity because it falls at the intersection of mandatory binary relationships between PROJECT, TOOL, and CITY, depending on the meaning of task. As currently modeled, TASK is something done on a project with a tool at a city, so it is not an independent concept. TASK can be modeled as an entity because it has its own primary key independent of the keys of PROJECT, CITY, and TOOL. Some semantic information would be lost if TASK were modeled as an associative entity (e.g., the minimum cardinalities related to task on the Includes, Done at, and Used on relationships).

5. The real estate database contains an entity called PROPERTY, which is a property for sale by the agency. Each time a potential property buyer makes a purchase offer on a property, the agency records the date, offering price, and name of the person making the offer. a. Represent the PROPERTY entity and its purchase offer attributes using the notation for multivalued attributes. b. Represent the PROPERTY entity and its purchase offer attributes using two entity types. c. Finally, assume the agency decides to also keep data about buyers and potential buyers, including their name, address, and phone number. Augment your answer to part b to accommodate this new entity type. Suggested answers are provided below. Microsoft Visio was used to create the answers for this exercise. Problem and Exercise 9, Part a Problem and Exercise 9, Part b Offer {OfferDate} {OfferPrice} {Offer_Name} Description OfferDate OfferPrice Offer_Name Problem and Exercise 9, Part c Offer Description OfferDate OfferPrice Offer_Name PotentialBuyer BuyerNo PhoneNo BuyerName BuyerAddress

6. Draw an ERD for the following Scenario: A Laboratory has several chemists who work on one or more projects. Chemists also may use certain kinds of equipment on each project. Attributes of CHEMIST includes EMPLOYEE_ID (identifier), Name, Phone_No. Attribute of PROJECT include Project_ID (identifier), and Start_Date. Attributes of EQUIPMENT include Serial_No and Cost. The organization wishes to record Assign_Date, which is the date when a given equipment was assigned to a particular chemist working on a specific project. A chemist must be assigned at least to one project and one equipment item. Any given equipment item need not be assigned, and a given project need not be assigned either a chemist or an equipment item. Equipment Serial No () Cost Project Project_ID () Start Date (Non-Key) Chemist Employee_ID () Name, Phone etc (Non-Key) Assignment Assignment No () Project ID (FK) Employee ID (FK) Assign Date (Non Key)