Chapter 14

Views:
 
Category: Education
     
 

Presentation Description

No description available.

Comments

Presentation Transcript

Chapter 14: Object-Oriented Data Modeling:

© 2005 by Prentice Hall 1 Chapter 14: Object-Oriented Data Modeling Modern Database Management 7 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden

Objectives:

2 Objectives Definition of terms Describe phases of object-oriented development life cycle State advantages of object-oriented modeling Compare object-oriented model with E-R and EER models Model real-world application using UML class diagram Provide UML snapshot of a system state Recognize when to use generalization, aggregation, and composition Specify types of business rules in a class diagram

What is Object-Oriented Data Modeling?:

3 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

Slide 4:

4

OO vs. EER Data Modeling:

5 OO vs. EER Data Modeling 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)

Object:

6 Object 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 Objects exhibit BEHAVIOR as well as attributes  Different from entities

State, Behavior, Identity:

7 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

Slide 8:

8 Class diagram shows the static structure of an object-oriented model: object classes, internal structure, relationships.

Slide 9:

9 Object diagram shows instances that are compatible with a given class diagram.

Operations:

10 Operations A function or service that is provided by all instances of a class Types of operations: 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:

11 Associations Association : 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)

Slide 12:

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

Slide 13:

13 Alternative multiplicity representation: specifying the two possible values in a list instead of a range

Slide 14:

14

Slide 15:

15 Figure 14-5: Object diagram for customer order example

Association Class:

16 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

Slide 17:

17 Binary association class with behavior Unary association with only attributes and no behavior

Slide 18:

18 Object diagram showing link objects Association class instances Figure 14-6a: Association class and link object

Slide 19:

19 Figure 14-7: Ternary relationship with association class

Slide 20:

20 Figure 14-8: Derived attribute, association, and role Derived attributes and relationships shown with / in front of the name Derived relationship (from Registers-for and Scheduled-for) Constraint expression for derived attribute Derived attribute

Generalization/Specialization:

21 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) Abstract Class: no direct instances possible, but subclasses may have direct instances Concrete Class: direct instances possible

Slide 22:

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

Slide 23:

23 Figure 14-9b: Examples of generalization, inheritance, and constraints Abstract patient class with two concrete subclasses Abstract indicated by italics Dynamic means a patient can change from one subclass to another over time A patient MUST be EXACTLY one of the subtypes

Class-Scope Attribute:

24 Class-Scope Attribute Specifies a value common to an entire class, rather than a specific value for an instance. Represented by underlining “=“ is initial, default value.

Polymorphism:

25 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 different classes in different ways

Slide 26:

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

Overriding Inheritance:

27 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

Slide 28:

28 Figure 14-12: Overriding inheritance Restrict job placement Subclasses that do not override place-student use the default behavior

Multiple Inheritance:

29 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

Slide 30:

30 Figure 14-13 Multiple inheritance

Aggregation:

31 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

Slide 32:

32 Figure 14-14: 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

Slide 33:

33 Figure 14-15: Aggregation and Composition (a) Class diagram (b) Object diagram Closed diamond indicates composition. The room cannot exist without the building

Slide 34:

34 Figure 14-16: Recursive aggregation

Business Rules:

35 Business Rules See Chapters 3 and 4 Implicit and explicit constraints on objects – for example: cardinality constraints on association roles ordering constraints on association roles Business rules involving two graphical symbols: labeled dashed arrow from one to the other Business rules involving three or more graphical symbols: note with dashed lines to each symbol

Slide 36:

36 Figure 14-17: Representing business rules Three-symbol constraint Two-symbol constraint

Slide 37:

37

authorStream Live Help