CSE 441: Systems Analysis & Design ERD – Detailed Study LAB 4 Yusuf Altunel.

Slides:



Advertisements
Similar presentations
Banking Business Scenario
Advertisements

Picking out ERD Entities 14 th March Steps in Constructing ERDs 1.Read and re-read the narrative 2.Make assumptions 3.Identify the entities 4.Define.
Normalisation.
Database development (MIS 533) MBS in Management Information Systems and Managerial Accounting Systems (2007 / 2008) Fergal Carton Business Information.
ER Tutorial 2 Chapter 9 - Questions 3, 4 and 5 V3.0 Napier University Dr Gordon Russell.
BUSINESS DRIVEN TECHNOLOGY Plug-In T4 Designing Database Applications.
ENTITY RELATIONSHIP MODELLING
Relational Database Systems Higher Information Systems.
Normalisation Ensuring data integrity in database design 1.
Robert Libby Patricia A. Libby Daniel G. Short
Revised by Ivor Perry Sept Introduction to Data Modelling.
Data Modelling II. Plan Introduction Structured Methods –Data Flow Modelling –Data Modelling –Relational Data Analysis Feasibility Maintenance.
Entity Relationship Diagrams
Logical Data Structures (Entity Relationship Diagrams)
Data Model Examples USER SPECIFICATIONS.
CSCI 6442 Entity-Relation Data Modeling Copyright 2012, David C. Roberts, all rights reserved.
APPENDIX C DESIGNING DATABASES
Entity Relationship Model Chapter 6. Basic Elements of E-R Model Entity Object of the real world that stores data. Eg. Customer, State, Project, Supplier,
DATA MODELING AND DATABASE DESIGN DATA MODELING AND DATABASE DESIGN Part 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.
Week 4 Lecture Conceptual Data Modeling
Database Design Sections 4 & 5 Subtype, Supertype, Mutually exclusive, non-transferability, transferable, 1:1, 1:M, M:M, Redundant, Intersection entity,
CSE 441: Systems Analysis & Design
Practice of ER modeling
Entity Relationship Diagram (ERD) 22 February 2011.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Message Analysis Table.
Richard Merritt1 Data Modelling Entities, Attributes and Relationships.
Database Management Systems
Normalization A technique that organizes data attributes (or fields) such that they are grouped to form stable, flexible and adaptive entities.
Association Class Generalization/Specialization Whole-Part Page More Associations 1.
Copyright 2008 McGraw-Hill Ryerson 1 TECHNOLOGY PLUG-IN T5 DESIGNING DATABASE APPLICATIONS.
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, All Rights Reserved Plug-In T5: Designing Database Applications Business Driven Technology.
Information Systems & Databases 2.2) Organisation methods.
1.  An introduction to data modelling  The purpose of data modelling  Modelling data relationships 2.
Requirements Analysis and Design Engineering Southern Methodist University CSE 7313.
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Entity relationship diagrams.
Section 08 (a)ER Modelling In Practice1 HSQ - DATABASES & SQL And Franchise Colleges 08 (a) ER Modelling In Practice QUICKHIRE Car Company.
Data Modeling Basics. GENERAL PROGRESSION DEVELOP BASIC MODEL ENHANCE BASIC MODEL REFINE THE MODEL VALIDATE THE MODEL.
1 IRU – database design part one Geoff Leese September 2009.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
Normalization Exercise. First Normal Form Second Normal Form.
Exam 1 Review. Bureau of Labor Statistics, U.S. Department of Labor, Occupational Outlook Handbook, Edition, Computer and Information Systems.
Database Design – Lecture 6 Moving to a Logical Model.
Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin APPENDIX C DESIGNING DATABASES APPENDIX C DESIGNING DATABASES.
Entity/Relationship Modelling. Entity Relationship Modelling In This Lecture Entity/Relationship models Entities and Attributes Relationships Attributes.
Entity-Relationship Diagram Presentation Gianna-lee Williams 6AQ Ms. Anderson.
IS 312: Information Systems for Business Discussion Chapter 3.
E.R Diagrams Tiffany Shaw 6AQ
Dissecting the Problem Document Identify potential s/w classes from a description document--a written description of the system to implement  Identify.
CSE 441: Systems Analysis & Design Basic CASE Models of Visible Analyst Lab2 Yusuf Altunel.
Dr Gordon Russell, Napier University Tutorial - ER2 - V2.0 1 ER Tutorial 2 Questions 3, 4 and 5.
1 Database Design Sections 6 & 7 First Normal Form (1NF), Second Normal Form (2NF), Unique Identifiers (UID), Third Normal Form (3NF), Arcs, Hierarchies.
5 Chapter 5: Modeling Systems Requirements: Events and Things Systems Analysis and Design in a Changing World.
DATA MODELING AND DATABASE DESIGN
Entity/Relationship Modelling
Database Management Systems II
DATA REQIREMENT ANALYSIS
© 2014 by McGraw-Hill Education. This is proprietary material solely for authorized instructor use. Not authorized for sale or distribution in any manner.
© The McGraw-Hill Companies, All Rights Reserved APPENDIX C DESIGNING DATABASES APPENDIX C DESIGNING DATABASES.
DESIGNING DATABASE APPLICATIONS
Dept. of Computer & Information Sciences
Certification for the module on the relational model
Curtain Style QUOTATION Curtain Style
Bookstore DB Requirements
ERD (Entity Relationship Diagrams)
This presentation document has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational.
Software Engineering Lecture # 19
Entity Relationship Model
DATA MODELING AND DATABASE DESIGN
Presentation transcript:

CSE 441: Systems Analysis & Design ERD – Detailed Study LAB 4 Yusuf Altunel

SELECTING ENTITIES Each engineer is allocated one van (which is driven up to a certain mileage and then replaced). Each member has only one address but perhaps many vehicles. Each visit is to deal with only one vehicle. A member can be visited more than once on any given date, and there may be many visits to a member on different dates. A member may only be covered for some of the vehicles they own and not for others.

 The nouns in the description are: engineer, van, mileage, member, address, vehicle, visit and date.  Entities Possible attributes  Engineer: name, address and telephone no  Van: registration number and mileage  Member: membership no, name, address and telephone no  Vehicle: registration no, make and model  Visit: date of visit, purpose of visit and cost of visit

 Other nouns in the description :  mileage is an attribute of the entity van;  address is an attribute of the entity customer;  date is an attribute of the entity visit.

IDENTIFYING RELATIONSHIPS A sale always starts with a customer receiving an estimate. The estimate then becomes an order. An order can be for one or more stock items. Each stock item belongs to a certain stock category taps, sinks, cupboards etc.

EntityKey AttributeSome non-key attributes EstimateEstimate Number or Order Number Date Customer Code Stock Items Code OrderOrder NumberSame as Estimate CustomerCustomer CodeCustomer Name Customer Address Credit Limit Stock ItemStock Item CodeDescription Number in Stock Supplier Code Stock Category Category CodeCategory Description

The relationships between these entities:  an Estimate becomes an Order;  an Estimate is issued to a particular Customer;  an Estimate refers to a Stock Item(s);  an Order is placed by a Customer;  an Order refers to Stock Item(s);  a Stock Item belongs to a particular Stock Category.

EstimateOrderCustomer Stock Item Stock Category Estimate XXX Order XXX Customer XX Stock Item XXX Stock Category X

DEGREES OF RELATIONSHIPS 1) A customer can be issued with one or more Estimates and an Estimate is issued to only one Customer.

2) A customer can place one or more Orders and an Order is placed by only one Customer.

3) An estimate can become only one Order and an Order is derived from only one Estimate.

4) An Estimate refers to one or more Stock Items and a Stock Item may be present on one or more Estimates.

5) An Order refers to one or more Stock Items and a Stock Item may be present on one or more Orders.

6) A stock Item will belong to only one Stock Category and a Stock Category will contain one or more Stock Items.