OBJECT ORIENTED ANALYSIS

OBJECT ORIENTED ANALYSIS

A technical approach to analyzing, designing a

system, or business by applying the object-
oriented paradigm.
An activity to create a model of the system’s
functional requirements, that is independent of
implementation constraints.
The goal of object oriented approach is to make
system elements more reusable thus improving
the s/m quality and productivity.
 OBJECT ORIENTED FUNDAMENTALS

Object
– A composite data type.
– It provides for the storage of multiple data values in a
single unit.
Class
– A collection of similar objects.
– It describes how the object is supposed to be created it
what it contains and how it works.
 OBJECT ORIENTED FUNDAMENTALS

Inheritance
– The process of creating new classes from the existing
class.
Encapsulation
– A method of binding data together and hiding them
from outside world.
Polymorphism
– A mechanism to exist in different forms.
 OBJECT ORIENTED ANALYSIS

Various steps are

– Identifying the objects
– Organizing the objects
– Identifying the relationship between the objects.
– Defining the operations of the object.
– Defining the objects.
 OBJECT ORIENTED SDLC

System analysis
– Collects data from the user and analyses the data.
System design
– Designing the physical system.
Object Design
– Objects are identified and designed.
Implementation
– Implementing the system into user site.
 UML

Unified Modelling Language.

A standard language for specifying, visualizing,
constructing, and documenting the artifacts of
software systems.
A pictorial language used to make software blue
prints.
 UML DIAGRAMS

Class diagram
Object diagram
Use case diagram
Sequence diagram
Collaboration diagram
Activity diagram
Statechart diagram
Deployment diagram
Component diagram
 UML MODELLING TYPES

Various types are

– Structural modelling
– Behavioral Modelling
– Architectural Modelling
 STRUCTURAL MODELLING

Structural modelling captures the static features

of a system.
It represents the framework for the system.
It consists of
– Class diagrams
– Objects diagrams
– Deployment diagrams
– Package diagrams
– Component diagram
 BEHAVIOURAL MODELLING

It describes the interaction in the system.

It consists of
– Activity diagrams
– Interaction diagrams
– Use case diagrams
 ARCHITECTURAL MODELLING

It represents the overall framework of the

system.
It contains both structural and behavioral
elements of the system.
It consists of package diagram.
 CLASS DIAGRAM

It graphically represents the static view of an application.

It describes the attributes and operations of a class and
also the constraints imposed on the system.
The class diagram shows a collection of classes, interfaces,
associations, collaborations and constraints.
Each class is represented by a rectangle subdivided into
three compartments
– Name
– Attributes
– Operations
 INSTRUCTIONS FOR DRAWING CLASS
DIAGRAM

The name of the class diagram should be meaningful to

describe the aspect of the system.
Each element and their relationships should be identified
in advance.
Responsibility (attributes and methods) of each class
should be clearly identified.
For each class minimum number of properties should be
specified.
Use notes when ever required to describe some aspect of
the diagram.
 OBJECT DIAGRAM

It represent an instance of a class diagram.

An object diagram represents an instance at a
particular moment.
Object diagrams consist of objects and links to
connect objects.
 INSTRUCTIONS FOR DRAWING OBJECT
DIAGRAM

It should have a meaningful name to indicate its

purpose.
The most important elements are to be identified.
The association among objects should be
clarified.
Values of different elements need to be captured
to include in the object diagram.
Add proper notes at points where more clarity is
required.
 COMPONENT DIAGRAM

Are used to model physical aspects of a system.

Physical aspects are the elements like libraries,
files, documents etc which resides in a node.
Represents the organization and relationships
among components in a system.
 INSTRUCTIONS FOR DRAWING
COMPONENT DIAGRAM

Use a meaningful name to identify the component

Prepare a mental layout before producing using
tools.
Use notes for clarifying important points
 DEPLOYMENT DIAGRAM

Are used to visualize the topology of the physical

components of a system where the software
components are deployed.
It contains various nodes and the relationship
b/w the nodes.
It is related with component diagram.
DEPLOYMENT DIAGRAM
 USE CASE DIAGRAM

Used to capture the dynamic behaviour of the

s/m.
It consists of
– Actor
– Use cases
– Relationships
Actor is the user playing a role with respect to
the s/m.
A use case is a scenario that describes the uses of
a s/m by an actor to accomplish a specific goal.
 IMPORTANT POINTS TO BE CONSIDERED
WHILE DRAWING USE CASE DIAGRAM

The name of a use case should be chosen in such a

way that it can identify the functionalities
performed.
Give a suitable name for actors
Show relationships and dependencies clearly in
the diagram.
Use note when ever required to clarify some
important points.
 INTERACTION DIAGRAM

Are used to visualize the interactive behaviour of

the system.
It describes the interactions among the different
elements in the model.
It uses
– To capture dynamic behaviour of a system
– To describe the message flow in the system.
– To describe structural organization of the objects.
– To describe interaction among objects.
 INTERACTION DIAGRAM

The various interaction diagrams are

– Sequence diagram
– Collaboration diagram.
 SEQUENCE DIAGRAM

An interaction diagram.
Used to visualize the sequence of calls in a system
to perform a specific functionality.
It captures the time sequence of message flow
from one object to another.
SEQUENCE DIAGRAM
 COLLABORATION DIAGRAM

An interaction diagram.
The method call sequence is indicated by some
numbering technique.
The number indicates the order in which the
methods are called one after the other.
It also describes the object organisation.
COLLABORATION DIAGRAM
 ACTIVITY DIAGRAM

It describes the flow of control in a system.

A flow chart to represent the flow from one
activity to another activity.
It contains
– Activities
– Association
– Conditions
– Constraints
ACTIVITY DIAGRAM
 STATECHART DIAGRAM

It describes different states of a component in a

system.
Statechart diagrams are useful to model reactive
systems.
Are used
– To model dynamic aspect of a system.
– To model life time of a reactive system.
– To describe different states of an object during its life
time.
– Define a state machine to model states of an object.
 STATECHART DIAGRAM

It contains
– Identify important objects to be analyzed.
– Identify the states.
– Identify the events.
STATECHART DIAGRAM
 UML ARCHITECTURE

UML plays an important role in defining

different perspectives of a system.
– Design
– Implementation
– Process
– Deployment