Module 3 Object Oriented Data Models Object Oriented notations

23
ER Diagramming Models for OO Relationships DOEACC B-Level OODBMS 2011 Taher S. 3.Object Oriented Data Model

description

Module 3 Object Oriented Data Models- Object Oriented notations.

Transcript of Module 3 Object Oriented Data Models Object Oriented notations

Page 1: Module 3  Object Oriented Data Models Object Oriented notations

ER Diagramming Models for OO Relationships

DOEACC B-Level OODBMS 2011Taher S.

3.Object Oriented Data Model

Page 2: Module 3  Object Oriented Data Models Object Oriented notations
Page 3: Module 3  Object Oriented Data Models Object Oriented notations
Page 4: Module 3  Object Oriented Data Models Object Oriented notations
Page 5: Module 3  Object Oriented Data Models Object Oriented notations
Page 6: Module 3  Object Oriented Data Models Object Oriented notations
Page 7: Module 3  Object Oriented Data Models Object Oriented notations

Models as Analysis and Design MethodsObject technology has many different

methodologies to help analyze and design computer systems.  

 In most cases these methodologies are very similar, but each has its own way to graphically represent the entities.

To understand and use these methodologies would become difficult, if not impossible, for all projects.  If need be, it is possible to use concepts from one method with concepts from another technique, basically creating your own object development technique.

The most important point is to remember is that the final outcome is what really matters, not the choice of one analysis technique over another technique.

Page 8: Module 3  Object Oriented Data Models Object Oriented notations

Methodologies: Coad-Yourdon

Developed in the late 80’s

Five-step analysis method

Shlaer-MellorDeveloped in the late 80’s

Emphasizes modeling information and state, rather than

object interfaces

OMT NotationUML NotationBooch Notation

Page 9: Module 3  Object Oriented Data Models Object Oriented notations

Coad- YourdonTheir methodology is based on a technique called

"SOSAS", which stands for the five steps that help make up the analysis part of their methodology.

Following analysis, Coad and Yourdon define four parts that make up the design part of their methodology. The steps of system design are:The problem domain component - This will define

the classes that should be in the problem domain. The human interaction component - These steps

defines the interface classes between objects. The task management component - This is where

system-wide management classes are identified. The data management component - This design

step identifies the classes needed for database access methods.

Page 10: Module 3  Object Oriented Data Models Object Oriented notations

Coad Yourdon- Analysis Part

Page 11: Module 3  Object Oriented Data Models Object Oriented notations

Coad Subject Diagrams

Gen- Spec Relationship Whole- Part Relationship

Page 12: Module 3  Object Oriented Data Models Object Oriented notations

Shlaer- MellorShlaer-Mellor methodology has its primary

strength in system design and is considered somewhat weak on analysis.

The Shlaer-Mellor methodology includes three models; the information model, the state model, and the process model. 

Developed by Sally Shlaer and Stephen Mellor, this system is also known as the Object-Oriented Systems Analysis (OOSA).

OOSA contains a wide variety of diagrams including: a domain chart diagram, object information model diagram, state transition model, an action data flow diagram, a class diagram, and a class structure chart.

Page 13: Module 3  Object Oriented Data Models Object Oriented notations

Shlaer- Mellor

Page 14: Module 3  Object Oriented Data Models Object Oriented notations

Shlaer Mellor- Domain Chart

Page 15: Module 3  Object Oriented Data Models Object Oriented notations

Shlaer- Mellor- Relationships

Page 16: Module 3  Object Oriented Data Models Object Oriented notations

Shlaer Mellor - Inheritance

Page 17: Module 3  Object Oriented Data Models Object Oriented notations

OMT NotationJames Rumbaugh's Object Modeling Technique

(OMT) is one of the precursors to the Unified Modeling Language (UML). There are three main diagrams in OMT: object, dynamic, and functional.

Object View DiagramsThe OMT object model illustrates the static relationship

among classes and objects in a system. This diagram is similar to the UML object and class diagrams.

The OMT Dynamic Diagram NotationsThe OMT dynamic models resemble UML sequence and

UML statechart diagrams. The OMT Static Diagram Notations

The OMT static models consist of multiple data flow diagrams.

Page 18: Module 3  Object Oriented Data Models Object Oriented notations

OMT – Object Diagram

Page 19: Module 3  Object Oriented Data Models Object Oriented notations

OMT- Other Diagrammatic NotationsObjects: Draw an object using a rectangle

with rounded corners. Attributes must have values assigned to them.

Linked Attribue: To describe the properties of a link or association, you can use an arc to attach an attribute to the relationship.

Page 20: Module 3  Object Oriented Data Models Object Oriented notations

OMT- Other Diagrammatic NotationsQualified associations: Qualifier used to

distinguish among the set of objects in the many end of the association.

 The qualified association is unique to the OMT notation. Place the qualifier box at the end of the association, near the class you want to qualify.

Page 21: Module 3  Object Oriented Data Models Object Oriented notations

Booch NotationGrady Booch's Object-Oriented Design (OOD),

also known as Object-Oriented Analysis and Design(OOAD), is a precursor to the Unified Modeling (UML). The Booch method includes six types of diagrams: class, object, state transition, interaction, module, and process.

Booch Class and Object Diagrams: Classes: Illustrate classes using a cloud shape

with a dashed border.Objects: Draw objects using a cloud shape with a

solid border.

Page 22: Module 3  Object Oriented Data Models Object Oriented notations

Booch Class and Object Diagrams:

Class Adornments: Use adornments to provide additional information about a

class. You can create an adornment notation using the basic triangle shape.

Place a letter inside the triangle to represent the following: A - Abstract. An abstract class cannot be instantiated

because it represents a wide variety of object classes and does not represent any one of them fully. For example, mammal could be thought of as an abstract class.F - Friend. A friend class allows access to the nonpublic functions of other classes.S - Static. A static class provides data.V - Virtual. A virtual class is a shared base class, the most generalized class in a system.

Page 23: Module 3  Object Oriented Data Models Object Oriented notations

Booch Class and Object Diagrams:

A Booch class Diagram