Finding Entities.

Slides:



Advertisements
Similar presentations
Systems Analysis and Design with UML Version 2.0, Second Edition
Advertisements

Copyright © 2015 Pearson Education, Inc. Database Design Chapters 17 and
FIS 431/631 Financial Information Systems: Analysis and Design REA Modeling Joe Callaghan Oakland University Department of Accounting & Finance.
Entity Relationship Diagrams
Entity-Relationship Model and Diagrams (continued)
The Relational Database Model:
Ch5: Software Specification. 1 Descriptive specifications  Describe desired properties of system  Three types:
© 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke
1 The Accounting REA Model as an Information Engineering Interaction Model Slides 5.
A Quick Review of Analysis Stages of the Systems Development Life Cycle Planning Analysis Design Construction.
Chapter 3: Data Modeling
Keys Chapter 8 Database Design for Mere Mortals. Why Keys Are Important They ensure that each record in a table can be properly identified. They help.
Creating an ERD John Wright Where to Start We need a description of some kind from interviews, questionnaires, etc Armed with the description we can.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Data Modeling 1 Yong Choi School of Business CSUB.
Practical tips for creating entity relationship diagrams (ERDs) Chitu Okoli Associate Professor in Business Technology Management John Molson School of.
Entity Relationship Modeling Objectives: To illustrate how relationships between entities are defined and refined. To know how relationships are incorporated.
Entity Relationship Modelling. What is Entity Relationship Modelling? The Entity-Relationship model is – ” “ a data model for high-level descriptions.
Database Design Concepts
COMM 226 Practical tips for creating entity relationship diagrams (ERDs) Chitu Okoli Associate Professor in Business Technology Management John Molson.
Database Design Principles of database design. Relational Models Relational databases are designed to provide efficient structures for transaction processing.
Business Process Modeling
CSE 441: Systems Analysis & Design
Phase 2: Systems Analysis
ITEC224 Database Programming
Conceptual Design versus Logical Design. Conceptual Data Design Prepared at beginning of project High level view of how the client sees the data Top down.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 6 Structuring.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
1 Relational Database Development Alison Taylder Consultant ITC-ILO, Turin 25 th November 2004.
Database Processing: Fundamentals, Design and Implementation, 9/e by David M. KroenkeChapter 3/1 Copyright © 2004 Please……. No Food Or Drink in the class.
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Rob and Coronel Adapted for INFS-3200.
Normalization (Codd, 1972) Practical Information For Real World Database Design.
Copyright Ó Oracle Corporation, All rights reserved. Normalization Use the student note section below for further explanation of the slide content.Use.
1 Analysis Extracting from Use Cases to Create Diagrams.
Database Design Principles – Lecture 3
1 The Relational Database Model. 2 Learning Objectives Terminology of relational model. How tables are used to represent data. Connection between mathematical.
Normalization Well structured relations and anomalies Normalization First normal form (1NF) Functional dependence Partial functional dependency Second.
Domain Modeling Part1: Entity Relationship Diagram Chapter 4 pp part 1 1.
1 A Guide to MySQL 2 Database Design Fundamentals.
Relational Database. Database Management System (DBMS)
1 Entity-Relationship Diagram. 2 Components of ERD: –Entity –Relationship –Cardinality –Attributes.
Data Modeling Basics. GENERAL PROGRESSION DEVELOP BASIC MODEL ENHANCE BASIC MODEL REFINE THE MODEL VALIDATE THE MODEL.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
Database Design – Lecture 8
Description and exemplification of entity-relationship modelling.
 An entity-relationship diagram (ERD) is a specialized graphic that illustrates the interrelationships between entities in a database.
The University of Akron Dept of Business Technology Computer Information Systems The Relational Model: Concepts 2440: 180 Database Concepts Instructor:
Database Design – Lecture 4 Conceptual Data Modeling.
Use Case Textual Analysis
CTFS Workshop Shameema Esufali Asian data coordinator and technical resource for the network
1 DATABASE TECHNOLOGIES (Part 2) BUS Abdou Illia, Fall 2015 (September 9, 2015)
Entity-Relationship Diagram Presentation Gianna-lee Williams 6AQ Ms. Anderson.
Lecture 91 Introduction to Data Analysis and Logic Specification Objectives l Draw an entity-relationship diagram, and explain the types of entity relationships.
Entity Relationship Diagram (ERD). Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship.
EntityRelationshipDiagrams. Entity Relationship Models The E-R (entity-relationship) data model views the real world as a set of basic objects (entities)
Microsoft Access 2010 Chapter 11 Database Design.
E.R Diagrams Tiffany Shaw 6AQ
Chapter 3 The Relational Model. Objectives u Terminology of relational model. u How tables are used to represent data. u Connection between mathematical.
IT 5433 LM3 Relational Data Model. Learning Objectives: List the 5 properties of relations List the properties of a candidate key, primary key and foreign.
Business Process Modeling What is a process model? – A formal way of representing how a business system operates. – Illustrates the activities that are.
Copyright © 2014 Pearson Canada Inc. 5-1 Copyright © 2014 Pearson Canada Inc. Application Extension 5a Database Design Part 2: Using Information Technology.
C_ITIP211 LECTURER: E.DONDO. Unit 4 : DATA MODELING.
Business Process Modeling
Entity-Relationship Model and Diagrams (continued)
ERD’s REVIEW DBS201.
Entity-Relationship Diagram (ERD)
Shelly Cashman: Microsoft Access 2016
Entity-Relationship Design
Database Design Chapter 7.
Presentation transcript:

Finding Entities

What is an Entity An entity is a person, place, object, event, or concept about which the organization wishes to record data. Entities should be things that are readily recognized by anyone working in the enterprise.

Some Entity Rules An Entity 1. Must be within the scope of the system 2. Must have at least one non-key attribute

Where to Begin To begin, we must have some form of information that we can use in our analysis. Collect information about the major business functions and processes. We can use questionnaires, interviews, observations etc.

Where to Begin Another good source of information for data modeling can be obtained by collecting any forms that are used by the enterprise. These forms provide valuable information on what data is important to the enterprise and how it is grouped. In an academic environment our job can be very much simplified. We are normally provided with a “Case Study” that contains a concise statement of the business processes we are to model. Using this case study we can proceed to identify the entities that we will need to model. However, in the real world, we will need to spend some time gathering facts and distilling these facts into the primary information and processes that need to be modeled.

Where to Begin Once we have a concise picture of the processes we are going to model, we can begin the iterative process of finding the entities that are necessary to support the enterprise.

The Steps Involved 1. Identify the system information a. User interviews b. Paper and screen documents c. Previous system documentation

The Steps Involved 2. Identify entities a. Analysis of English grammar --> Entity-Relationship Diagrams b. Heuristics c. Normalization process

Analyze the Grammer Using the table on the next slide, find the entities, attributes and relationships from the description and other information we have gathered about the enterprise.

Use this table to start English (If the word is a) ERD (On the ERD we will show) Proper Noun Entity (“Name” of an Entity) Common Noun Entity or Entity-Type Transitive Verb M-ary Relation (M>1) Intransitive Verb Unary Relationship or Attribute Value Adjective Attribute of an Entity Adverb Attribute of a Relationship

Sentence Restructuring Next we do some sentence restructuring: Convert any sentence in the following form: “There are . . . X in Y” into “Y has . . . X”

Sentence Restructuring Example “There are more than 200 employees in every department.” “Every department has more than 200 employees.” X Y X Y

More Restructuring If the English sentence says, “The X of Y is Z” Y is an Entity X is either an Attribute or an Entity, depending on what type of “Z” it is. If “Z” is a proper noun, then X is a Relationship between Y and Z Otherwise, X is an Attribute of Y

More Examples (x) (y) (z) (x) (y) (z) The birthdate of the student is 10/22/71. (x) (y) (z) Attribute Entity not a proper noun The advisor of John Smith is Dr. Greene. (x) (y) (z) Relationship Entity Proper noun

Candidate Entities The preceeding steps have provided a list of Candidate Entities. Now we need to apply a few more rules to ensure we have only those entities that are essential to the enterprise.

Paring Down the List First, eliminate any duplicate entities. These can be entities with different names but representing the same thing. For example Patron and Customer. These may both represent the same entity. Second, eliminate and entities that are not important to the enterprise. This may require some analysis and work with the user/end customer.

Now add some Heuristics When is an entity an entity? Any entity with only one evident instance (e.g. The National Basketball League, NHL, NFL etc.) is not a ‘good’ entity because it is modeling business context or the business itself. If one ENTITY is in the center of everything and is connected to everything else it is probably the view point or context rather than an entity.

Finely Remember that eventually: entities become Tables in a relational database, with attributes become as columns in the table table cells contain the allowed value for a given attribute instance