Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,

Slides:



Advertisements
Similar presentations
Copyright 2001 Prentice-Hall, Inc. Object Oriented Aproach to System Requirements: Process Modeling 7.1 Chapter 7.
Advertisements

Modern Systems Analysis and Design Third Edition
Systems Development Life Cycle
1 © Prentice Hall, 2002 Chapter 3: Modeling Data in the Organization Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred.
Modeling the Data: Conceptual and Logical Data Modeling
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
System Analysis - Data Modeling
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Systems Analysis Requirements structuring Process Modeling Logic Modeling Data Modeling  Represents the contents and structure of the DFD’s data flows.
Entity Relationship Diagrams Basic Elements and Rules.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Chapter 10 Structuring System Requirements: Conceptual Data Modeling.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Entity Relationship Diagrams
Chapter 3: Modeling Data in the Organization
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
Chapter 8 Structuring System Data Requirements
Data Modeling Introduction. Learning Objectives Define key data modeling terms –Entity type –Attribute –Multivalued attribute –Relationship –Degree –Cardinality.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Modern Systems Analysis and Design Third Edition
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Entity Relationship Modeling Objectives: To illustrate how relationships between entities are defined and refined. To know how relationships are incorporated.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
1 © Prentice Hall, 2002 Chapter 3: Modeling Data in the Organization Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred.
Computer System Analysis Chapter 10 Structuring System Requirements: Conceptual Data Modeling Dr. Sana’a Wafa Al-Sayegh 1 st quadmaster University of Palestine.
3.1 CSIS 3310 Chapter 3 The Entity-Relationship Model Conceptual Data Modeling.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
Segment 5 Database Review International Islamic University Chittagong Campus.
Data Modeling ERM ERD.
Chapter 8 Structuring System Data Requirements
Chapter 8 Structuring System Data Requirements
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 6 Structuring.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 8 Slide 1 Chapter 9 Structuring System Data Requirements.
BIS 360 – Lecture Six (Part 2) Conceptual Data Modeling (Chapter 10 and partial Chapter 12)
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Chapter 9 Structuring System Data Requirements Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 7 Structuring System Requirements: Conceptual Data Modeling 7.1.
Unit 3 Conceptual Data Modeling. Key Concepts Conceptual data modeling process Classes and objects Attributes Identifiers, candidate keys, and primary.
3 & 4 1 Chapters 3 and 4 Drawing ERDs October 16, 2006 Week 3.
Data Modeling Using the Entity-Relationship (ER) Model.
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management
Chapter 9 Structuring System Data Requirements Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Modern Systems Analysis and Design Third Edition
Chapter 3: Modeling Data in the Organization. Business Rules Statements that define or constrain some aspect of the business Assert business structure.
Entity Relationship Diagram (ERD). Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
ERD :: 19 / 1 / Entity-Relationship (ER) Modeling. ER Modeling is a top-down approach to database design. Entity Relationship (ER) Diagram –A.
ENTITY RELATIONSHIP DIAGRAM. Objectives Define terms related to entity relationship modeling, including entity, entity instances, attribute, relationship.
Distribution of Marks For Second Semester Internal Sessional Evaluation External Evaluation Assignment /Project QuizzesClass Attendance Mid-Term Test Total.
C_ITIP211 LECTURER: E.DONDO. Unit 4 : DATA MODELING.
Entity Relationship Modeling
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Business System Development
Modern Systems Analysis and Design Third Edition
Chapter 6 Structuring System Requirements: Conceptual Data Modeling
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Chapter 7 Structuring System Requirements: Conceptual Data Modeling
Chapter 7 Structuring System Requirements: Conceptual Data Modeling
Chapter 9 Structuring System Data Requirements
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Modern Systems Analysis and Design Third Edition
Review of Week 1 Database DBMS File systems vs. database systems
Entity-Relationship Diagram (ERD)
Modern Systems Analysis and Design Third Edition
Modern Systems Analysis and Design Third Edition
Chapter 7 Structuring System Requirements: Conceptual Data Modeling
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
ER MODELING Instructor: SAMIA ARSHAD
Lecture 10 Structuring System Requirements: Conceptual Data Modeling
Presentation transcript:

Lecture 4 Conceptual Data Modeling

Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship, cardinality, and foreign key. Describe the entity modeling process. Discuss how to draw an entity relationship diagram.

Overview Data modelers use a variety of tools and techniques to understand an organization’s data. In order to understand how to properly model data, you must become familiar with a modeling approach known as entity relationship modeling. Entity-relationship (E-R) modeling is one approach to semantic modeling. We use E-R modeling to carry out conceptual data modeling ER modeling, which consists of a number of activities that help database designers understand the objects the organization wants to store information about, the important characteristics of these objects and the associations among various objects.

Deliverables and Outcomes 1.The entity-relationship diagram – 4 E-R diagrams produced and analyzed during conceptual data modeling – Covers just data needed in the project’s application – E-R diagram for system being replaced – An E-R diagram for the whole database from which the new application’s data are extracted – An E-R diagram for the whole database from which data for the application system being replaced are drawn 2.Project dictionary – Set of entries about data objects to be stored in repository or – Repository links data, process and logic models of an information system – Data elements that are included in the DFD must appear in the data model and conversely – Each data store in a process model must relate to business objects represented in the data model

The Entity Relationship Diagram The end result of E-R modeling is the E-R diagram (ERD), a graphical representation of the logical structure of a database. An ERD serves several purposes. First, the database analyst/designer gains a better understanding of the information to be contained in the database through the process of constructing the ERD. Second, the ERD serves as a documentation tool. Finally, the ERD is used to communicate the logical structure of the database to users. In particular, the ERD effectively communicates the logic of the database to users. The E-R modeling process identifies three basic elements: entities, attributes and relationships.

Entities An entity is a thing that can be distinctly identified. In database design, entities are the “things” about which the database stores information. Entities can include, but are not limited to – tangible items, such as equipment, – concepts, such as accounts, – people, such as employees – events, such as sales, or – places, such as business locations.

Entities An entity is a thing that can be distinctly identified. In database design, entities are the “things” about which the database stores information. Entities can include, but are not limited to – tangible items, such as equipment, – concepts, such as accounts, – people, such as employees – events, such as sales, or – places, such as business locations. The term entity type refers to a number of related items, while an entity instance refers to a single occurrence of an entity type. For example, employee number refers to a single occurrence, or entity instance, of the entity EMPLOYEE.

Attributes An attribute is a single data value that describes a characteristic of an entity. Other terms such as data item and field, describe the same essential concept. Each entity has a corresponding set of attributes that represent the information about the entity that the organization is interested in. For example, a UNIVERSITY may wish to know the name, address, phone number, and major of each student. A STUDENT is the entity of interest, and NAME, ADDRESS, PHONE, and MAJOR are the attributes of interest. Attributes are represented by ellipses in the ER diagram. The name of the attribute is shown inside the ellipse and a line is drawn from the attribute to its entity.

Primary Keys Every entity must have a primary key. The primary key is an attribute or combination of attributes that uniquely identifies an instance of the entity. In other words, no two instances of an entity may have the same value for the primary key. When a primary key for an entity is made up of more than one attribute the key is called a composite key.

Relationship A relationship is an association among two or more entities. For example, a STUDENTS entity might be related to a COURSES entity, or an EMPLOYEES entity might be related to an OFFICES entity. An ellipse connected by lines to the related entities indicates a relationship in an ERD.

Degree of Relationship The degree of a relationship refers to the number of entities involved in the relationship. Although others exist, it is often sufficient to understand the meaning of three relationship degrees, unary, binary and ternary. A unary relationship (also called a recursive relationship) is a relationship involving a single entity. A Binary Relationship is a relation between two entities. A Ternary Relationship is a relation between three entities. n-ary relationships is a Relation between more than three entities.

Degree of Relationship Examples The degree of a relationship refers to the number of entities involved in the relationship. Although others exist, it is often sufficient to understand the meaning of three relationship degrees, unary, binary and ternary. A unary relationship (also called a recursive relationship) is a relationship involving a single entity. A Binary Relationship is a relation between two entities. A Ternary Relationship is a relation between three entities. n-ary relationships is a Relation between more than three entities.

Degree of Relationship Degree – Number of entity types that participate in a relationship To avoid clusters of symbols in E-R, not place relation diamond, only place verb phrases Three cases – Unary A relationship between the instances of one entity type – Binary A relationship between the instances of two entity types – Ternary A simultaneous relationship among the instances of three entity types Not the same as three binary relationships

Degree of Relationship Examples The degree of a relationship refers to the number of

Cardinality the number of elements in a set or other grouping, Relationships can also differ in terms of their cardinality. Maximum cardinality refers to the maximum number of instances of one entity that can be associated with a single instance of a related entity. Minimum cardinality refers to the minimum number of instances of one entity that must be associated with a single instance of a related entity.

Cardinality

Determining Cardinalities

Creating an E-R Diagram A number of steps are required to create an E-R diagram that accurately represents the organizational data. These steps are summarized in Figure 8 and discussed in this section.

Gathering Information for Conceptual Data Modeling Two perspectives – Top-down : Data model is derived from an intimate understanding of the business – Bottom-up : Data model is derived by reviewing specifications and business documents

Introduction to E-R Modeling Notation uses three main constructs Data entities - Relationships - Attributes Entity-Relationship (E-R) Diagram – A detailed, logical and graphical representation of the entities, associations and data elements for an organization or business Entity – A person, place, object, event or concept in the user environment about which the organization wishes to maintain data Person: EMPLOYEE, STUDENT, PATIENT Place: STATE, REGION, COUNTRY Object: MACHINE, BUILDING, AUTOMOBILE Event: SALE, REGISTRATION, RENEWAL Concept: ACCOUNT, COURSE, WORK CENTER – Represented by a rectangle in E-R diagrams – A rule to avoid confusion with Data Flow Diagram E-R diagram has possible many instances

E-R Modeling - Key Terms Entity Type – A collection of entities that share common properties or characteristics – Use noun to name an entity type – Use capitals to name an entity type Attribute – A named property or characteristic of an entity that is of interest to an organization

Double-lined ellipse Weak entity

Cardinality The number of instances of entity B that can be associated with each instance of entity A Minimum Cardinality – The minimum number of instances of entity B that may be associated with each instance of entity A Maximum Cardinality – The maximum number of instances of entity B that may be associated with each instance of entity A. A relationship that the data modeler chooses to model as an entity type

Electronic Commerce Development: Conceptual Data Model Conceptual data modeling for Internet applications is no different than the processed followed for other types of applications Pine Valley Furniture WebStore – Four entity types defined Customer Inventory Order Shopping cart

Summary Process of conceptual data modeling – Deliverables – Gathering information Entity-Relationship Modeling – Entities – Attributes – Candidate keys and identifiers – Multivalued attributes Degree of relationship Cardinality Associative entities Conceptual data modeling and Internet development