UML: Unified modeling language
 This language is used for modeling(designing ) and development
of object oriented system.
 Build upon the fundamental of OOPs
 A language for
1.
2.
3.
4.
Visualizing (Abstract Overall structure)
Specifying (Design)
Construction
Documentation
Example: Agro-UML, Rational software architecture, visual paradigm for UML
My-eclipse
1
Overview of UML Diagrams
Behavioral
: behavioral features of a system / business process
•
•
•
•
Activity
State machine
Use case
Interaction
Structural
: element of spec. irrespective of time
•
•
•
•
•
•
Class
Component
Deployment
Object
Composite structure
Package
Interaction
: emphasize object interaction
• Communication(collaberati
on)
• Sequence
• Interaction overview
• Timing
(Use case)A
measurable
Action
Use case Diagram:
Describes the behavior of the
target system from an external
point of view.
(Association) a
solid between
actor and use case
(Actor) that play an
important role in
system like person,
organization or
external system
Activity
Start
node
Action
Activity diagram
Control
flow
End
node
describe the flow of control of the target system (like (DFD)
Name of the
class
Multiplicity
3
Class diagram
Shows the classes of the system, their inter-relationships, and the
operations and attributes of the classes.
Communication(collaboration)
Diagram
Sequence diagram
models the communication of objects based on a
time sequence. It shows how the objects interact with
others in a particular scenario of a use case.
Deployment diagram
Unified Process
In 1990
James Rambaugh,booch,jacobson
UML
Unified method(feature of
oops)
Unified
process
• A framework for object oriented software development
using UML.
Rational Unified Process
• An unified process develop by IBM
• RUP is a risk-driven, use-case-based, and architecturecentric, iterative software development process.
• RUP provides a disciplined approach to assigning tasks
and responsibly within a development of software.
• Its goal is to ensure the production of a high quality
software that meets the need of its end user within a
predictable schedule and budget
And supports
Good practice
Iterative,
UML
Generic
on
prototype
process
specification
models
Elaboration
Inception
planning
modeling
communication
construction
development
construct
ion
Transition
Release
production
11
INCEPTION
• This phase combine both customer communication and planning
Developer
(Analyst)
Communication
for
Requirement
Rough idea
/model
Customer or stake
holder
Plan for
iteration,
resource
risk,
schedule
12
Elaboration
• The input for this phase is Inception
Inception()
Basic use
case
•
•
To refine
Requirement
model
Architectural
Model
/Executable
representation
Design model
Implementati
on model
Deployment
model
13
Construction
Developer
or
programmer
Architectural
Model
/Executable
representation
Implementation
phase
Software
component that
make use case
functional
Unit test
for each
module
14
Version 1
Transition
version
User
manual,
trouble
shooting,
Installation
procedure
Handed over
to customer
for Beta
Testing
Customer
Production phase
(Deployment),maintenance
15