Documente Academic
Documente Profesional
Documente Cultură
OF
TECHNOLOGY AND SCIENCE
SUBMITTED BY:
V.RAGHUVEER,
III B.TECH, CSE,
SVITS.
CONTACT ME AT:
Object Model:
INTRODUCTION TO UML :
NEED OF UML :
So we already observed the need of modeling in software design
Basically there are two approaches:
1. Algorithmic approach
2. Object oriented approach
In algorithmic approach where the main building block of
all software is procedure or function. This focuses on issue of
control & decomposition of larger algorithms into smaller
once. But in this view as requirements changes it becomes
hard to maintain.
But in Object Oriented approach the main building block of
all software systems is the object or class. Object is athing
and class is a description of a set of common objects. Every
object has an identity or name, state and behavior.
WHY UML ?
Here our intention is to highlight the usage of UML in
contrast with other languages.
Before UML was introduced there is not a perfect way
efficient way to design software , such that a particular
design of software was unable to meet the clients(user)
expectations, since it had become very difficult task to both
client & designer to communicate each other to produce a
good software design.
So by using the tools of UML by adopting to any recent
platforms of UML like RATIONAL ROSE or by VISUAL
PARADIGM, ‘ we can best depict the software intensive
system by using different diagrams available in UML.
Generally software design will be done by dividing problem
domain in modules since each module will be handeled by
some part of software development teams, as apart it is very
important to communicate among them, since it had become
very easy to them to communicate by using simple diagrams
in UML, which will be documented in a simple language
understandable for software designers I different modules
and even for common user, since the diagrams with
documentation, user is now in a stage to understand the
design of software, but with out UML it is not possible.
GOALS OF UML:
The Unified Modeling Language (UML) aims to:
SCOPE OF UML:
o Fuses concepts of Booch, OOSE/Jacobson and
OMT/Rumbaugh (the ‘three amigos’)
o Development began in October 1994 at Rational Software
Corporation, by Booch and Rumbaugh
o Jacobson (and his Objectory company) joined Rational in
October 1995
o First releases of UML in 1996
• Structural things are the nouns of Uml models. These are static
parts of model, which might be either conceptual or physical.
Since there are seven types of structural things.
• Behavioral things are dynamic part of UML model. These are
verbs of a model, representing behavior time and space, since
these are two types.
• Grouping things are the organizational part of the UML. These
are boxes into which a model can be decomposed (eg: package).
• Annotational things are explanatory parts of UML models. These
are comments to describe about any element is a model.
BELOW FIGURE DEPICTS ALL THE INFORMATION
In the above tabular column it is specified the use case model of UML
which is a very important task in modeling the software ,in this type
model it particularly specifies Use Case, Actor, System boundaries as its
constructs ,since its description is mention briefly with appropriate
diagrams.
UML Concepts and Notation
Operations
Operations
(public)
(public)
Respon-
sibilities Respon-
(public) sibilities Package
(public) Name
Note
Textual
content
Sequence Diagram
• Used during requirements analysis
• To refine use case descriptions
• to find additional objects (participating objects)
• Used during system design o refine subsystem interfaces
• Classes are represented by columns
• Messages are represented by arrows
• Activations are represented by narrow rectangles to sent the message, and is as long as all
nested activations
• Lifelines are represented by dashed lines
• Captures dynamic behavior (time-oriented) in terms of interaction
• Model flow of control
• Illustrate typical scenarios
• Complement the class diagrams which represent structure.
Statechart Diagram
• Captures dynamic behavior (event-oriented)
• Purpose
• Model object lifecycle
• Model reactive objects (user interfaces, devices, etc.)
Activity Diagrams
• A special case of a state chart diagram in which states are
activities (“functions”)
• Model business workflows, flow control within a system, and
operations,Captures dynamic behavior (activity-oriented)
.
A COMPONENTE DIAGRAM:
A DEPLOYMENT DIAGRAM:
• Captures the topology of a system’s hardware
• Built as part of architectural specification
• Purpose
-Specify the distribution of components
-Identify performance bottlenecks
• Developed by architects, networking engineers, and system
engineers
SEQUENCE DIAGRAM :
• Mainly emphasizes on time ordering of messages between object
• Used during requirements analysis
• To refine use case descriptions
• Purpose
-Captures dynamic behavior (time-oriented) in terms
of interaction.
COLLABORATION DIAGRAM :
• Mainly emphasizes on structural organization of messages
between objects
• Captures dynamic behavior (message-oriented)
• Purpose
-Model flow of control
-Illustrate coordination of object structure and
control
Diagrams
Class
Diagrams
Use Case
Diagrams Object
Sequence Diagrams
Diagrams
Collaboration Component
Diagrams Models Diagrams
Statechart Deployment
Diagrams Diagrams
Activity
Diagrams
How all diagrams are useful in a software project
development?
CONCLUSION:
Since UML had best supported Object Oriented
Analysis and Design concepts with its nine diagrams by which we can
best design the software graphically which is a very easy and effective
medium to communicate, even for ordinary user (client) with designer
since then it considerably decreased the lack of communication between
client and designer and between software teams which work by dividing
the software as separate modules.
BIBLOGRAPHY: