7-1 © Prentice Hall, 2007 Chapter 7: Conceptual Data Modeling Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,

Slides:



Advertisements
Similar presentations
Chapter 9 Structuring System Data Requirements
Advertisements

Object-Oriented Analysis and Design: Object Modeling – Class Diagrams
Data Modeling is an Analysis Activity
1 © Prentice Hall, 2002 Chapter 3: Modeling Data in the Organization Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred.
2-1 © Prentice Hall, 2007 Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
System Analysis - Data Modeling
Chapter 14 (Web): Object-Oriented 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.
Chapter 4 ENTITY-RELATIONSHIP MODELLING.
Chapter 3: Modeling Data in the Organization
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
Systems Analysis and Design in a Changing World, 6th Edition
Chapter 8 Structuring System Data Requirements
2-1 © Prentice Hall, 2004 Chapter 2: Introduction to Object Orientation (Adapted) Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra,
Chapter 4 Entity-Relationship modeling Transparencies © Pearson Education Limited 1995, 2005.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Chapter 3 © 2005 by Prentice Hall 1 Objectives Definition of terms Definition of terms Importance of data modeling Importance of data modeling Write good.
Chapter 14: Object-Oriented 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.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
© 2007 by Prentice Hall (Hoffer, Prescott & McFadden) 1 Entity Relationship Diagrams (ERDs)
1 © Prentice Hall, 2002 CMIS564: E/R Modeling Dr. Bordoloi Based on Chapter 3; Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott,
1 © Prentice Hall, 2002 Chapter 3: Modeling Data in the Organization Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred.
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.
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.
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. What Is a Conceptual Data Model? A detailed model that shows the overall structure of organizational data A detailed model.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
R McFadyen Chapter 7 Conceptual Data Modeling.
© Pearson Education Limited, Chapter 7 Entity-Relationship modeling Transparencies.
CHAPTER 13 (ONLINE): OBJECT-ORIENTED DATA MODELING © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition.
1 © Prentice Hall, 2002 Chapter 14: Object-Oriented Data Modeling Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R.
7-1 © Prentice Hall, 2004 Chapter 7: Conceptual Data Modeling Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 15: Object-Oriented Data Modeling Modern Database Management 9 h Edition Jeffrey A.
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,
© 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 13 (Online): Object-Oriented Data Modeling Modern Database Management 10 th Edition.
Chapter 12 Entity-Relationship Modeling Pearson Education © 2009.
CHAPTER 13: OBJECT-ORIENTED DATA MODELING (OVERVIEW) © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition.
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.
Chapter 9 Structuring System Data Requirements Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A.
Chapter 3: Modeling Data in the Organization. Business Rules Statements that define or constrain some aspect of the business Assert business structure.
CHAPTER 13: OBJECT-ORIENTED DATA MODELING (OVERVIEW) Modern Database Management 11 th Edition Jeffrey A. Hoffer, V. Ramesh, Heikki Topi © 2013 Pearson.
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: Modeling Data in the Organization Modern Database Management 9 th Edition Jeffrey.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
2-1 © Prentice Hall, 2004 Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Data Modeling Using the Entity- Relationship (ER) Model
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Business System Development
Business System Development
Chapter 6 Structuring System Requirements: Conceptual Data Modeling
Chapter 7 Structuring System Requirements: Conceptual Data Modeling
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Chapter 20 Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Chapter 3: Modeling Data in the Organization
Chapter 7 Structuring System Requirements: Conceptual Data Modeling
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Appendix A Object-Oriented Analysis and Design
Presentation transcript:

7-1 © Prentice Hall, 2007 Chapter 7: Conceptual Data Modeling Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer

Chapter © Prentice Hall, 2007 Chapter Objectives – Determine how to develop conceptual data models from use cases. – Understand UML notations for conceptual data modeling. – Explain relationship characteristics such as degree and multiplicity. – Describe data relationships such as association, aggregation, and generalization. – Describe different kinds of attributes such as identifier, multivalued, and derived.

Chapter © Prentice Hall, 2007

Chapter © Prentice Hall, 2007 What Is a Conceptual Data Model? A detailed model that shows the overall structure of organizational data; it is independent of any database management system or other implementation considerations. Represented by UML class diagrams

Chapter © Prentice Hall, 2007 Use cases are key inputs to conceptual data modeling.

Chapter © Prentice Hall, 2007 Conceptual model sets the stage for more detailed model, and ultimately system design

Chapter © Prentice Hall, 2007 Conceptual Data Model Elements Classes Attributes Identifiers Associations, aggregations, compositions Generalizations Time dimensions Integrity rules Security controls

Chapter © Prentice Hall, 2007 What Is an Object? An entity that encapsulates data and behavior Examples: product, employee, order, line item Class – a set of objects that share the same attributes, operations, relationships, and semantics (abstract) Instance – a single object (concrete)

Chapter © Prentice Hall, 2007 Class Instances

Chapter © Prentice Hall, 2007 UML Class symbol has three parts: 1)Name 2)List of attributes 3)List of operations

Chapter © Prentice Hall, 2007 What is an Attribute? A named property of a class that describes a range of values that instances of the attribute may hold

Chapter © Prentice Hall, 2007 Types of Attributes Simple attributes – contain single data item Identifiers – connect unique key value Multivalued attributes – contain multiple values simultaneously Composite attributes – group of related attributes

Chapter © Prentice Hall, 2007 Stereotypes in Class Diagrams Stereotype – a construct that extends the UML vocabulary Identifier stereotype > for primary key Multivalued stereotype >

Chapter © Prentice Hall, 2007 Primary key is a unique identifier; no two Student instances will have the same studentId value.

Chapter © Prentice Hall, 2007 Identifiers and Keys Identifier – an attribute or combination of attributes that is selected as the unique characteristic for a class Candidate key – an attribute or combination of attributes that uniquely identifies each object of a class Primary key – a candidate key that is selected as the unique identifier of the class

Chapter © Prentice Hall, 2007 Multivalued attribute can contain multiple values; a student may have several phone numbers

Chapter © Prentice Hall, 2007 Composite attributes have multiple sections (subattributes). They are treated as separate classes in conceptual data models.

Chapter © Prentice Hall, 2007 What Is a Relationship? 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)

Chapter © Prentice Hall, 2007 What Is Relationship Degree? The number of classes that participate in a relationship Main degrees: – Unary – a relationship between objects of the same class – Binary – a relationship between objects of two different classes – Ternary – a relationship between objects of three different classes

Chapter © Prentice Hall, 2007 This is a binary relationship, which indicates that an employee works in a department.

Chapter © Prentice Hall, 2007 Roles identify the purpose of each class in the relationship.

Chapter © Prentice Hall, 2007 Unary relationships exist between instances of the same class

Chapter © Prentice Hall, 2007 Note: a ternary relationship is not the same as three binary relationships. It is a relationship that links three separate classes simultaneously.

Chapter © Prentice Hall, 2007 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. 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

Chapter © Prentice Hall, 2007 Relationship Multiply Relationships can be: – One – to – one – One – to – many – Many – to – many

Chapter © Prentice Hall, 2007 Multiplicity notation is: min..max This shows that one movie can be stocked as any number of videotapes, or none at all

Chapter © Prentice Hall, 2007 Fixed cardinality involves an actual number instead of the generic n This indicates that the maximum number of sections an instructor can teach is 6

Chapter © Prentice Hall, 2007 Roles make it clearer to see which should be on the one side and which should be on the many side of the relationship.

Chapter © Prentice Hall, 2007

Chapter © Prentice Hall, 2007 What Is an Associative Class? A many-to-many association that the data modeler chooses to model as a class Particularly useful if the association contains attributes of its own Represented as a class connected to an association with a dotted line

Chapter © Prentice Hall, 2007 A Certificate represents a relationship between an employee and a course, and has an attribute pertaining to that relationship

Chapter © Prentice Hall, 2007 Sometimes associative classes have their own relationships with other classes.

Chapter © Prentice Hall, 2007 Types of Associations 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. Composition – an aggregation with a tight coupling. The whole and the part cannot exist without each other.

Chapter © Prentice Hall, 2007 Closed diamond indicates composition (course line item cannot exist without course registration) Open diamond indicates aggregation (A player is part of a team, but could also exist without being part of a team)

Chapter © Prentice Hall, 2007 What Is a Composite Structure Diagram? A diagram that shows how a whole is made up of its parts, especially in cases where the whole has a large number of interating parts Useful to reduce clutter in diagrams with many associations Introduced in UML 2

Chapter © Prentice Hall, 2007

Chapter © Prentice Hall, 2007 What Is Generalization? 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 is an “is-a” relationship

Chapter © Prentice Hall, 2007

Chapter © Prentice Hall, 2007

Chapter © Prentice Hall, 2007 Multiple inheritance is complicated and not supported by all object- oriented programming languages.