Lec 3: Object-Oriented Data Modeling

Slides:



Advertisements
Similar presentations
Chapter 9 Structuring System Data Requirements
Advertisements

Object-Oriented Analysis and Design: Object Modeling – Class Diagrams
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall A.1.
UML – Class Diagrams.
Chapter 14 (Web): Object-Oriented Data Modeling
Object-Oriented Databases
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
Chapter 4: Object-Oriented Data Modeling
Databases Illuminated Chapter 7 The Object-Oriented Model.
Chapter 14: Object-Oriented Data Modeling
UML Class Diagrams: Basic Concepts. Objects –The purpose of class modeling is to describe objects. –An object is a concept, abstraction or thing that.
EER vs. UML Terminology EER Diagram Entity Type Entity Attribute
Advanced Information Modeling and Database Systems
Chapter 41 Enhanced Entity-Relationship and Object Modeling.
Chapter 14: Object-Oriented Data Modeling
Chapter 13 (Online): Object-Oriented Databases
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 8 Slide 1 Chapter 9 Structuring System Data Requirements.
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.
Database Management System Prepared by Dr. Ahmed El-Ragal Reviewed & Presented By Mr. Mahmoud Rafeek Alfarra College Of Science & Technology Khan younis.
11 Chapter 11 Object-Oriented Databases Database Systems: Design, Implementation, and Management 4th Edition Peter Rob & Carlos Coronel.
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.
© 2011 Pearson Education 1 Chapter 13 (Online): Object-Oriented Databases Modern Database Management 10 th Edition, International Edition Jeffrey A. Hoffer,
7-1 © Prentice Hall, 2007 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,
Databases : Data Modeling 2007, Fall Pusan National University Ki-Joune Li.
© 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 13 (Online): Object-Oriented Data Modeling Modern Database Management 10 th Edition.
CHAPTER 13: OBJECT-ORIENTED DATA MODELING (OVERVIEW) © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition.
Unified Modeling Language © 2002 by Dietrich and Urban1 ADVANCED DATABASE CONCEPTS Unified Modeling Language Susan D. Urban and Suzanne W. Dietrich Department.
Chapter 9 Structuring System Data Requirements. Objectives:  Define key data modeling terms.  Draw entity-relationship (E-R) and class diagrams to represent.
UML Class Diagram Trisha Cummings. What we will be covering What is a Class Diagram? Essential Elements of a UML Class Diagram UML Packages Logical Distribution.
Lecture 8 Object-Oriented Analysis and Design 20.1 COSC4406: Software Engineering.
Lecture 1: UML Class Diagram September 12, UML Class Diagrams2 What is a Class Diagram? A class diagram describes the types of objects in the system.
Object-Oriented Data Modeling
ITEC 3220A Using and Designing Database Systems Instructor: Gordon Turpin Course Website: Office: CSEB3020.
 Week08.  Review Schedule Weeks 8-14  This week o Review last class o Introduce Class Diagrams o ICE-03 Sheridan SYST Engineering Quality Systems.
CIS 210 Systems Analysis and Development Week 6 Part I Structuring Systems Data Requirements,
Chapter 4 Extended Entity-Relationship (EER)Model Incorporates Set-subset Relationships Incorporates Generalization Hierarchies Constraints: Coverage Constraints:
CHAPTER 13: OBJECT-ORIENTED DATA MODELING (OVERVIEW) Modern Database Management 11 th Edition Jeffrey A. Hoffer, V. Ramesh, Heikki Topi © 2013 Pearson.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
Copyright © 2016 Ramez Elmasri and Shamkant B. Navathe Chapter 12 Outline Overview of Object Database Concepts Object-Relational Features Object Database.
2-1 © Prentice Hall, 2004 Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Entity Relationship (E-R) Model
COP Introduction to Database Structures
Enhanced Entity-Relationship (EER) Model
Appendix 3 Object-Oriented Analysis and Design
Object-Oriented Modeling
Conceptual Design & ERD Modelling
Business System Development
DATA REQIREMENT ANALYSIS
The Movement To Objects
Chapter 2: Entity-Relationship Model
Entity-Relationship Modeling
Chapter 12 Outline Overview of Object Database Concepts
UML UML Data Modeling.
UML Class Diagrams: Basic Concepts
Object Oriented Analysis and Design
Software Engineering Lecture #11.
Chapter 20 Object-Oriented Analysis and Design
Object-Oriented Knowledge Representation
Appendix A Object-Oriented Analysis and Design
Understand and Use Object Oriented Methods
Systems Analysis – ITEC 3155 Modeling System Requirements – Part 2
ITEC 3220A Using and Designing Database Systems
Appendix A Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Appendix 3 Object-Oriented Analysis and Design
Presentation transcript:

Lec 3: Object-Oriented Data Modeling

What is Object Oriented Data Modeling? Centers around objects and classes Involves inheritance Encapsulates both data and behavior Benefits of Object-Oriented Modeling Ability to tackle challenging problems Improved communication between users, analysts, designer, and programmers Increased consistency in analysis and design Explicit representation of commonality among system components System robustness Reusability of analysis, design, and programming results

OO vs. EER Data Modeling EER Class Entity type Object Entity instance Object Oriented EER Class Entity type Object Entity instance Association Relationship Inheritance of attributes Inheritance of attributes Inheritance of behavior No representation of behavior Object-oriented modeling is frequently accomplished using the Unified Modeling Language (UML)

Classes and Objects Class: An entity that has a well-defined role in the application domain, as well as state, behavior, and identity Tangible: person, place or thing Concept or Event: department, performance, marriage, registration Artifact of the Design Process: user interface, controller, scheduler Object: a particular instance of a class Objects exhibit BEHAVIOR as well as attributes  Different from entities

State, Behavior, Identity State: attribute types and values Behavior: how an object acts and reacts Behavior is expressed through operations that can be performed on it Identity: every object has a unique identity, even if all of its attribute values are the same

Figure - UML class and object diagram a) Class diagram showing two classes Class diagram shows the static structure of an object-oriented model: object classes, internal structure, relationships.

Figure - UML class and object diagram (cont.) b) Object diagram with two instances Object diagram shows instances that are compatible with a given class diagram.

Operations A function or service that is provided by all instances of a class Types of operators: Constructor: creates a new instance of a class Query: accesses the state of an object but does not alter its state Update: alters the state of an object Scope: operation applying to the class instead of an instance Operations implement the object’s behavior

Associations Association: Association Role: Multiplicity: Relationship among object classes Association Role: Role of an object in an association The end of an association where it connects to a class Multiplicity: How many objects participate in an association. Lower-bound..Upper bound (cardinality).

Figure - Association relationships of different degrees Unary Lower-bound – upper-bound Represented as: 0..1, 0..*, 1..1, 1..* Similar to minimum/maximum cardinality rules in EER Binary Ternary

Figure – Examples of binary association relationships (a) University example Alternative multiplicity representation: specifying the two possible values in a list instead of a range

Figure - Examples of binary association relationships (cont.) b) Customer Order example

Figure- Object diagram for customer order example

Association Class An association that has attributes or operations of its own or that participates in relationships with other classes Like an associative entity in ER model

Figure – Association class and link object (a) Class diagram showing association classes Unary association with only attributes and no behavior Binary association class with behavior

(b) Object diagram showing link objects Association class instances

Generalization/ Specialization Subclass, superclass similar to subtype/supertype in EER Common attributes, relationships, AND operations Disjoint vs. Overlapping Complete (total specialization) vs. incomplete (partial specialization)

a) Employee superclass with three subclasses Figure - Examples of generalization, inheritance, and constraints a) Employee superclass with three subclasses An employee can only be one of these subclasses Shared attributes and operations An employee may be none of them. Specialized attributes and operations

Polymorphism Abstract Operation: Defines the form or protocol of the operation, but not its implementation. Method: The implementation of an operation. Polymorphism: The same operation may apply to two or more classes in different ways

Figure – Polymorphism, abstract operation, class-scope attribute, and ordering This operation is abstract…it has no method at Student level Class-scope attributes – only one value common to all instances of these classes Methods are defined at subclass level

Overriding Inheritance Overriding: The process of replacing a method inherited from a superclass by a more specific implementation of that method in a subclass. For Extension: add code. For Restriction: limit the method. For Optimization: improve code by exploiting restrictions imposed by the subclass.

Figure – Overriding inheritance Restrict job placement

Multiple Inheritance Multiple Classification: An object is an instance of more than one class. Multiple Inheritance: A class inherits features from more than one superclass.

Figure - Multiple inheritance

Aggregation Aggregation: A part-of relationship between a component object and an aggregate object. Composition: A stronger form of aggregation in which a part object belongs to only one whole object and exists only as part of the whole object. Recursive Aggregation: composition where component object is an instance of the same class as the aggregate object.

Figure – Example aggregation A Personal Computer includes CPU, Hard Disk, Monitor, and Keyboard as parts. But, these parts can exist without being installed into a computer. The open diamond indicates aggregation, but not composition

Figure – Aggregation and Composition (a) Class diagram Closed diamond indicates composition. The room cannot exist without the building (b) Object diagram

Object Query Language (OQL) OQL is an object-based version of SQL designed specifically for Object Oriented Frameworks.The differences between OQL and traditional SQL are: OQL has the ability to support object referencing within tables. It is possible to have objects nested within objects. Not all SQL keywords are supported within OQL; irrelevant keywords have been removed from the syntax. OQL has the ability to perform mathematical computations from within OQL statements.

OQL (cont.) OQL objects - Objects in OQL are created and defined using the CREATE keyword, examples of objects in OQL are database(s), tables contained within the database(s) and elements such as objects, lists, groups, references to objects and atoms contained within the database tables.

OQL (cont.) Follow a similar Select, From, Where format like SQL with a lot of the same features, i.e. subqueries, boolean operators, sorting options, etc. Insert, update, deletion functions are similar to SQL Supports joins in a similar fashion to SQL