Você está na página 1de 28

OBJECT MODELLING TECHNIQUE: A PERSPECTIVE

Object Oriented Software Engineering / TU

Madhu Pandey [Roll No: 15] Ramesh Tamang [Roll No: 16] Suresh Kumar Mukhiya [Roll No: 14]
1

AGENDA
Object Oriented Software Engineering / TU

Concept / Introduction What is OMT? Requirement OMT Methodology Object Model/ Dynamic Model /Functional Model Stages of OMT Pros/Cons Summary

CONCEPT /INTRODUCTION-1/3
Object Oriented Software Engineering / TU

A model is an abstraction of something for the purpose of understanding it before building it.

WHY MODELING? -2/3


Object Oriented Software Engineering / TU

To test a physical entity before actually building it. To set the stage for communication between customers and developers. For visualization i.e. for finding alternative representations.

For reduction of complexity in order to understand it.


4

OBJECT ORIENTED METHODOLOGIES-3/3


Object Oriented Software Engineering / TU

Object Oriented Methodology (OOM) is a new system development approach reuse of software components used during the analysis, design and implementation of the system. Popular object oriented methodologies are listed below:

Booch Methodology [1994]: He developed the Object Oriented Analysis and Object Oriented Design (OOA/OOD) concepts. RDD Methodology [1990]: Wirfs-Brock, Wilkerson, and Wiener developed Responsibility Driven Design (RDD) methodology.

OMT methodology [1991]: James Rumbaugh led a team at research labs of General Electric to develop the Object Modeling Technique .
OOSE [1994]: Ivar Jacobson developed the Object Oriented Software .
5

OBJECT MODELING TECHNIQUE-1/2


Object Oriented Software Engineering / TU

object-oriented

software development methodology given by James Rumbaugh et.al. a method for analysis, design and implementation of a system using objectoriented technique. Precursors to the Unified Modelling Language (UML)
6

OBJECT
Object Oriented Software Engineering / TU

testing physical entities before building them (simulation),


communication with customers, visualization (alternative presentation of information), and

complexity reduction.
7

OMT-METHODOLOGY
Object Oriented Software Engineering / TU

1. Object Model

2. Dynamic model

3. Functional Model

OBJECT MODEL-1
Object Oriented Software Engineering / TU

CLASS OBJECTS Object Diagram Attribute Operation Associations and Links Role names Aggregation Generalization or inheritance Homomorphism
9

OBJECT MODEL-C
Classes: A class describes a set of things that have same behavioral characteristics.

LASS, ATTRIBUTES, OPERATIONS

-2
Object Oriented Software Engineering / TU

Attribute: An attribute is a data value held by the objects in a class.


Operation: An operation is a function or transformation that may be applied to or by objects in a class.

10

OBJECT MODEL-L
Links and Associations: A link is a physical or conceptual connection between object instances.

INK AND ASSOCIATIONS

-3
Object Oriented Software Engineering / TU

In, OMT, link is represented by a line labeled with its name. Role names: A role is one end of an association

11

OBJECT MODEL-O

BJECT DIAGRAM

-4

It provides a formal graphic notation for modeling objects, classes and their relationships to one another. TypesClass diagram Instance diagram

12

OBJECT MODEL-CLASS
A class diagram is a schema, pattern or templates for describing many possible instances of data. Describes classes.

DIAGRAM

-5

13

OBJECT MODEL-INSTANCE

DIAGRAM

-6

Describes how a particular set of objects relate to each other. Describes objects

Person Class Diagram

(Person) Ram

(Person) Jai

(Person)

Instance Diagram

14

OBJECT MODEL

GENERALIZATION AND

MULTIPLICITY

-7

Inheritance or Generalization: Generalization refers to refining a super class into subclasses Multiplicity: It specifies how many instances of one class may relate to a single instance of an associated class.

15

DYNAMIC MODELING CONCEPTS


Events represent external stimuli States values of objects State diagram

16

EVENTS
It

is something that happens at a point in time One event may logically precede or follow another or the two events may be unrelated. The two events are casually related. The two events are casually unrelated are said to be concurrent i.e. they have no effect on each other. In modeling a system we do not establish an ordering between concurrent events because they can occur at any order.
17

Airplane flight departs (airline, flight#, city) Mouse button pushed (button, location) Input string entered (text) Phone receiver lifted Digit dialed (digit)

Event classes and attributes

18

A state has duration An event separates two states and a state separates two events. In defining states we ignore those attributes that do not affect the behavior of the objects.

19

STATE DIAGRAM
It relates events and states. When an event is received, the next state depends on the current state as well as the event; a change of state caused by an event is called a transition. State diagram is a graph whose nodes are states and whose directed arcs are transitions labeled by event names.

20

On-hook idle Off-hook Dial tone

On-hook
Timed- out

Digit(n)
dialing Busy tone Fast busy tone Num busy valid connecting routed ringing Called phone answers connected Called phone hangs up disconnected
21

Recorded message Invalid no

Trunk busy

State diagram for phone line

ACTION FOR POP-UP MENU

Right button down/display menu idle Menu visible

Right button up/erase menu

Cursor moved/highlight menu item

22

FUNCTION MODEL
-Specifies the results of a computation without specifying how or when they are computed.
Object Oriented Software Engineering / TU

-Specifies the meaning of the operations in the object model and the actions in the dynamic model.

A functional model consists of multiple data flow diagrams

23

DFD
It

shows the functional relationships. A DFD is a graph showing the flow of data values from their sources in objects through processes that transform them to their destinations in other objects. It does not show control information like time, etc.

24

ELEMENTS OF DFD
Processes -> Action Performed ProcessName Data flow -> move data Actor/External Entity ->objects that produce and consume actorName data. Data store -> objects that store data passively. /repository

25

PROCESS-TRANSFORMS DATA
Object Oriented Software Engineering / TU

Represented by Circle or oval

26

DATA FLOWS -CONNECTS THE OUTPUT OF AN OBJECT OR A PROCESS TO AN INPUT OF AN


OBJECT OR A PROCESS
Object Oriented Software Engineering / TU

Represented as an arrow

27

DFD LAYERS

28

Object Oriented Software Engineering / TU

Você também pode gostar