Object Modeling Technique

OMT is given by James Rambal

It consists of three view points:
1. Static
2. Dynamic
3. Functional Behaviour
There are three modeling technique:-
1. Object Model
2. Dynamic Model
3. Functional Model

1. Object Model:
It describes static, structural and data aspects
of the system.
It describes the object of the model.
Some subtopic which we use in object model or class
diagram.
a. Link & Association:
Association describes a group of link with common structure
and common semantics between two or more class.
Association are Bi-Directional in nature.
b. Multiplicity:
It specifies how many instances of class it may relate to a single
instances of class using line terminator.
 A Solid ball is for Many
o A Hollow ball indicates the meaning 0 or 1.
c. Link Attributes:
An attribute cannot be associate with any two of class but
associated by the association.
d. Role Names:
A Roll names is one of association of a binary association can
have two role each of which has a roll name.
e. Qualification:
It is an association attribute .It reduces effect of multiplicity of
an association.
One to Many or Many to many Qualification are associate.
f. Aggregation:
It is a type of association. It is a part whole or part of
relationship.
 Class diagram of
Hospital Management System
2. Dynamic Model:
It describes those aspects of the system that changes with the
time.
It depicts state , transition ,events and action.
a. State Diagram:
A State Correspond to the interval between two events
received by an object and describes the value of object for that
time period.
b. State Machine:
A state machine is a behavior that specify the sequence of
states an object visit during lifetime in response to an event
together with response to those events.

Components of State Diagram:

a. State:
It is a condition during the life of an object during which it
satisfy some condition, perform some activity.
b. Sub state:
It is a state which is nested in another state. A state that
has sub state is called as composite state. A state which has
no sub state is called Simple state.
c. Event :
It is the specification of a significant occurrence. For a state
machine an event is the occurrence of the stimulus that can
trigger a state transition.
d. Transition:
A Transition is a relationship between two states
Indicating that an object in the first state when a specified
set of events condition are satisfied, performs certain action
and enter the second state. It can be self transition.
e. Action:
It is an executable atomic computation action may include
operation, creation or destruction of others objects, sending
of signals to other objects.
An action is associated with an event.
 State Diagram of
Hospital Management System
 3. Functional Model:
It describes computation & specifies those aspects of the
system concern with transformation of values function, mapping,
constraints & functional dependency.

Functional model captures what the system does without regard to

when it does.

Data Flow Diagrams:

 A Data flow diagram shows a data flow of the

system.
 It views a system as a function that transform the
input into desired output
 A DFD are basically of two types:
1. Physical DFDs are used in analysis phase to
functioning the current system.
2. Logical DFDs are used in design phase for
depicting the flow of data in a proposed system.

Symbols:

1. External entities:
It represent the source data of a system or destination of data
of system.

External Entity
2. Process:
It represent the activity that transform or manipulate the data .
processes are work or action perform on incoming data flows to
produceoutput data flows. Thus all process must have input &
output.
Proces
s

3. Data Store:
Data store are repository for data that are temporarily or
permanently recorded in the system.
It represent the data that not moving.
Only process may connect with data source.
Their can be two or more system that shares a data store.

4. Data Flow:
It represent movement of data .
It represent input of data to(or from) a process , data store or
an actor.
Data flow is only data not control.
It represent minimum essential data that the process needs.
Data flow must begin and/or end at process.

Data flow
5. Control flow:

Control flow is a Boolean value(0/1) in DFD that effects

weather a process is evaluated or not.

The control flow is an input value for the process.

Data Flow Diagram of

Hospital management System
Use Case Diagram:
Symbols:

1. Actor:
Actor is someone interacting with use case.
Actor ha responsibility towards the system(input) and actor have
acceptation from the system output.
2. Process:

3. Interaction:

4. Include:
Include means relation using use case.

<<include>>

5. Extend:
Base Use case implicitly incorporates in behavior of another use
case of certain point.
Linking an optional use case to a standard use case.

<<extend>>

6. System Boundary:
 Use Case Diagram of
Hospital Management System