Conceptual Data Modeling. What Is a Conceptual Data Model? A detailed model that shows the overall structure of organizational data A detailed model.

Slides:



Advertisements
Similar presentations
Entity, Attribute, and Relationship DATA ENTITY TYPE: a noun, i.e. roles, events, locations, people, tangible things about which we wish to maintain.
Advertisements

Ch5: ER Diagrams - Part 1 Much of the material presented in these slides was developed by Dr. Ramon Lawrence at the University of Iowa.
Modern Systems Analysis and Design Third Edition
1 © Prentice Hall, 2002 Chapter 3: Modeling Data in the Organization Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
System Analysis - Data Modeling
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 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
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
Systems Analysis and Design in a Changing World, 6th Edition
Chapter 8 Structuring System Data Requirements
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
Entity Relationship Diagrams
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
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.
1 Web-Enabled Decision Support Systems Entity-Relationship Modeling Prof. Name Position (123) University Name.
3.1 CSIS 3310 Chapter 3 The Entity-Relationship Model Conceptual Data Modeling.
DeSiamorewww.desiamore.com/ifm1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 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.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 7.1.
Segment 5 Database Review International Islamic University Chittagong Campus.
Module Title? Data Base Design 30/6/2007 Entity Relationship Diagrams (ERDs)
Chapter 5 Entity–Relationship Modeling
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.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Conceptual Data Modeling, Entity Relationship Diagrams
R McFadyen Chapter 7 Conceptual Data Modeling.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 - Domain Classes.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 Domain Classes.
7-1 © Prentice Hall, 2004 Chapter 7: Conceptual Data Modeling Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
7-1 © Prentice Hall, 2007 Chapter 7: Conceptual Data Modeling Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
Unit 3 Conceptual Data Modeling. Key Concepts Conceptual data modeling process Classes and objects Attributes Identifiers, candidate keys, and primary.
7-1 © Prentice Hall, 2007 Week 5: Conceptual Data Modeling Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
Chapter 12 Entity-Relationship Modeling Pearson Education © 2009.
Chapter 9 Structuring System Data Requirements. Objectives:  Define key data modeling terms.  Draw entity-relationship (E-R) and class diagrams to represent.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
DeSiamorePowered by DeSiaMore1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
Msigwaemhttp//:msigwaem.ueuo.com/1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
Data modeling using the entity-relationship model Chapter 3 Objectives How entities, tuples, attributes and relationships among entities are represented.
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.
Chapter 8 Entity-Relationship Modeling Pearson Education © 2009.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Data Modeling Using the Entity- Relationship (ER) Model
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Business System Development
Business System Development
Modern Systems Analysis and Design Third Edition
Chapter 6 Structuring System Requirements: Conceptual Data Modeling
Tables and Their Characteristics
Entity Relationship Diagrams
Chapter 9 Structuring System Data Requirements
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Modern Systems Analysis and Design Third Edition
Chapter 3: Modeling Data in the Organization
Modern Systems Analysis and Design Third Edition
Chapter 7 Structuring System Requirements: Conceptual Data Modeling
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Lecture 10 Structuring System Requirements: Conceptual Data Modeling
Presentation transcript:

Conceptual Data Modeling

What Is a Conceptual Data Model? A detailed model that shows the overall structure of organizational data A detailed model that shows the overall structure of organizational data It is independent of any database management system or other implementation considerations. It is independent of any database management system or other implementation considerations. Represented by UML class diagrams Represented by UML class diagrams

Use cases are key inputs to conceptual data modeling.

Conceptual Data Model Elements Classes Classes Attributes Attributes Identifiers Identifiers Associations, aggregations, compositions Associations, aggregations, compositions Generalizations Generalizations Time dimensions Time dimensions Integrity rules Integrity rules Security controls Security controls

Object/Class/Instance Class : Class : – A person, place, thing, event, or concept in user environment about which organization wishes to maintain data. – It is a set of objects that share the same attributes, operations, relationships, and semantics (abstract). Object : Object : – A single occurrence of a class; encapsulates data and behavior. (Examples: product, employee, order, line item) Instance: Instance: – A single object (concrete). (i.e. John Smith, student)

Class Instances

UML Class symbol has three parts: 1)Name 2)List of attributes 3)List of operations

Types of Attributes Simple attributes – contain single data item (i.e. name) Simple attributes – contain single data item (i.e. name) Identifiers (aka Primary Key) – contain unique key value for class (i.e. studentId in Student class) Identifiers (aka Primary Key) – contain unique key value for class (i.e. studentId in Student class) Multivalued attributes – contain multiple values simultaneously (i.e. phone number – may have several phone numbers - home, cell, beeper) Multivalued attributes – contain multiple values simultaneously (i.e. phone number – may have several phone numbers - home, cell, beeper) Composite attributes – group of related attributes Composite attributes – group of related attributes (i.e. address – contains sub-attributes of street, city, state, zip)

Stereotypes in Class Diagrams Stereotype – a construct that extends the UML vocabulary Stereotype – a construct that extends the UML vocabulary Identifier stereotype > for primary key Identifier stereotype > for primary key Multivalued stereotype > Multivalued stereotype > Since there are no standard UML symbols for primary key or multivalued they are created using stereotypes Since there are no standard UML symbols for primary key or multivalued they are created using stereotypes

Primary key is a unique identifier; no two Student instances will have the same studentId value.

Multivalued attribute can contain multiple values; a student may have several phone numbers

Composite attributes have multiple sections (subattributes). They are treated as separate classes in conceptual data models.

Selecting Primary Keys Choose a primary key that will not change its value over the life of each object of the class (i.e. name and address changes so they are not good candidates) Choose a primary key that will not change its value over the life of each object of the class (i.e. name and address changes so they are not good candidates) Choose a primary key such that, for each object of the class, the attribute is guaranteed to have valid values and not be null. (include controls in data entry and maintenance routines to eliminate errors) Choose a primary key such that, for each object of the class, the attribute is guaranteed to have valid values and not be null. (include controls in data entry and maintenance routines to eliminate errors) Avoid the use of so-called intelligent keys. For instance, the 1 st two digits stand for a warehouse location or region. These conditions can change. Avoid the use of so-called intelligent keys. For instance, the 1 st two digits stand for a warehouse location or region. These conditions can change. Consider substituting single-attribute surrogate keys for large composite keys. Consider substituting single-attribute surrogate keys for large composite keys.

What Is A Relationship? A semantic connection between objects of one or more classes A semantic connection between objects of one or more classes In UML, represented as a line connecting two or more class boxes (or connecting one class to itself) In UML, represented as a line connecting two or more class boxes (or connecting one class to itself) Labeled with verb phrases Labeled with verb phrases A relationship is generally described by its name, degree, and multiplicity (minimum and maximum cardinality) A relationship is generally described by its name, degree, and multiplicity (minimum and maximum cardinality)

This is a binary relationship, which indicates that an employee works in a department.

Roles identify the purpose of each class in the relationship.

What Is Relationship Degree? The number of classes that participate in a relationship The number of classes that participate in a relationship Main degrees: Main degrees: –Unary – a relationship between objects of the same class (also called recursive) –Binary – a relationship between objects of two different classes (most common) –Ternary – a relationship between objects of three different classes

Quantity is the amount of a particular Part shipped from a particular Vendor to a particular Warehouse

What Is Relationship Multiplicity? The range of the number of objects in Class A that can or must be associated with each object of Class B. The range of the number of objects in Class A that can or must be associated with each object of Class B. A multiplicity is made up of: A multiplicity is made up of: –A minimum cardinality – the minimum number of Class A objects possible –A maximum cardinality – the maximum number of Class A objects possible

Relationship Multiplicity Relationships can be: Relationships can be: –One – to – one –One – to – many –Many – to – many

Multiplicity notation is: min..max Store stocks more than 1 videotape of a movie 1 instructor teaches 0-6 sections

Roles make it clearer to see which should be on the one side and which should be on the many side of the relationship. 0-1 supervisor manages 0 to many subordinates

What Is an Associative Class? A special purpose class that represents an association (relationship) between classes and contains attributes and/or relationships in its own right A special purpose class that represents an association (relationship) between classes and contains attributes and/or relationships in its own right A many-to-many association that is modeled as a separate class A many-to-many association that is modeled as a separate class Represented as a class connected to an association with a dotted line Represented as a class connected to an association with a dotted line

A Certificate represents a relationship between an employee and a course, and has an attribute pertaining to that relationship (dateCompleted)

Sometimes associative classes have their own relationships with other classes.

Types of Associations Association – no object is subordinate to any other. Association – no object is subordinate to any other. Aggregation – one class represents the whole, and the other represents the part, but it is a loose coupling. Aggregation – one class represents the whole, and the other represents the part, but it is a loose coupling. Composition – an aggregation with a tight coupling. The whole and the part cannot exist without each other. Composition – an aggregation with a tight coupling. The whole and the part cannot exist without each other.

The wholeThe part Course registration needs at least 1 course and vice versa

What Is Generalization? A superclass – subclass relationship in which one class forms a broader category in which the other class is a sub-category A superclass – subclass relationship in which one class forms a broader category in which the other class is a sub-category Inheritance – A subclass will inherit all the attributes and operations of its superclass; an instance of the subclass contains all the same information (plus more) as an instance of the superclass. Inheritance – A subclass will inherit all the attributes and operations of its superclass; an instance of the subclass contains all the same information (plus more) as an instance of the superclass.

Multiple inheritance is complicated and not supported by all object- oriented programming languages.

Any Questions?