sohailimran@yahoo.

com

usd & uml

Ref: Web
 intro
The Unified Software Development Process is a software analysis and design process
derived primarily from the three market leading OOA&D methods, Booch, OOSE (Use-
Case), and OMT with ideas drawn from many other methods and input from many other
parties.
It is a component-based, use case driven, architecture centered, iterative and
incremental developmental process that uses the Unified Modeling Language (UML) to
represent models of the software system to be developed.

The Unified Software Development Process describes, apart from the unified generic
process and the different activities in developing a software system, the different models
developed and evolved during the lifecycle of a system.
It describes in an easy-to-understand way the different higher-level constructs – notation
as well as semantics – used in the models.
Thus stereotypes such as use cases and actors, packages, classes, stereotypes,
interfaces, active classes, processes and threads, nodes, and most relations will be
described intuitively in the context of a model.
The Unified Software Development Process will go further then most OO A&D methods by
describing a family of processes that incorporate the complete life-cycle of software.

Sohail IMRAN ‫ﺳﻬﯿﻞﻋﻤﺮﺍﻥ‬ 1

 Rational Unified Process (RUP)

Sohail IMRAN ‫ﺳﻬﯿﻞﻋﻤﺮﺍﻥ‬ 2

 phases
Critical activities in each phase:
Inception:
• Business case is established
• Establish the project scope and boundary conditions
• Outline the use cases and key requirements that will drive the design tradeoffs
• Identify risks
• Prepare a preliminary project schedule and cost estimate
• The Lifecycle Objective Milestone marks the end of the Inception phase.
Elaboration:
• Develop the architecture
• The primary goals of Elaboration are to address known risk factors and to establish and validate the
system architecture.
• The final Elaboration phase deliverable is a plan (including cost and schedule estimates) for the
Construction phase.
Construction:
• Source code
• User manual
• Verification and validation of code
Transition:
• Deployment of software
• New releases
• Training
Sohail IMRAN ‫ﺳﻬﯿﻞﻋﻤﺮﺍﻥ‬ 3
 workflows
Business modeling Test
• evaluation of the customer’s organization, business • description of test cases;
structure; • test plan;
• specification of business functions; • work plan during the testing phase;
• work plan at the stage of business modeling;
Deployment
Requirements
• placement model – a description of the placement
• the model of user interfaces;
of components on processing nodes.
• a model of the user’s system operation scenarios;
• documents on the installation;
• work plan at the stage of determining the
• description of the system versions;
requirements for the system;
• deployment plan
Analysis and design
• logical and physical data model;
• software architecture;
• specification of software components;
• work plan for the analysis and design phase;
Implementation
• component model of the application.
• the plan for building the application;
• work plan at the implementation stage.

Sohail IMRAN ‫ﺳﻬﯿﻞﻋﻤﺮﺍﻥ‬ 4

 Unified Modeling Language (UML)
UML is a language for visualizing, specifying, constructing and documenting the artifacts of
a software intensive system or simply you can say that UML is a language for modeling
software systems.

UML was developed by Grady Booch, James Rumbaugh and Ivar Jacobson who belong to
Rational Corporation.
UML is a language, not a methodology to develop software systems.

UML is unified across several domains:

• Across historical methods and notations (Booch’s methodology, OMT and Objectory).
• Across the development life cycle phases.
• Across application domains.
• Across implementation languages and platforms.
• Across development platforms.
• Across internal concepts.

Sohail IMRAN ‫ﺳﻬﯿﻞﻋﻤﺮﺍﻥ‬ 5

 types

Sohail IMRAN ‫ﺳﻬﯿﻞﻋﻤﺮﺍﻥ‬ 6

 structural …
Class Diagrams
Class diagrams are the backbone of almost every object
oriented method, including UML. They describe the static
structure of a system. Things naturally fall into categories
(books, trees, computers, …). We refer to these categories as
classes.

Package Diagrams
Package diagrams are a subset of class diagrams, but
developers sometimes treat them as a separate technique.
Package diagrams organize elements of a system into related
groups to minimize dependencies between packages.

Object Diagrams
An object is an instance of a class – a specific thing that has
specific values of attributes, and behavior. Object diagrams
describe the static structure of a system at a particular time.
They can be used to test class diagrams for accuracy.

Sohail IMRAN ‫ﺳﻬﯿﻞﻋﻤﺮﺍﻥ‬ 7

 structural

Component Diagrams
Component diagrams describe the organization of physical
software components, including source code, run-time
(binary) code, and executables.

Deployment Diagrams
This shows the physical architecture of a computer based
system. It can depict the computers and devices, show their
connectivity, and show the software that sits on each
machine. Deployment diagrams depict the physical
resources in a system, including nodes, components, and
connections.

Sohail IMRAN ‫ﺳﻬﯿﻞﻋﻤﺮﺍﻥ‬ 8

 behavioral …
Use Case Diagrams
A use case is a description of a system’s behaviour from a
user’s standpoint. A use case diagram is useful for gathering
system requirements from a user’s point of view. Use case
diagrams model the functionality of system using actors and
use cases.

Sequence Diagrams
Class and object diagrams represent static information. In a
system objects interact with one another and these
interactions occur over time. Sequence diagrams show the
time-based dynamics of interaction. Sequence diagrams
describe interactions among classes in terms of an exchange
of messages over time.

Collaboration Diagrams
Because large scale system development involves different
people working on different components, it’s important to
have a diagram to model these. The elements of a system work
together to accomplish the system’s objectives; this is depicted
with the collaboration diagram. Collaboration diagrams
represent interactions between objects as a series of
sequenced messages. Collaboration diagrams describe both
the static structure and the dynamic behavior of a system.

Sohail IMRAN ‫ﺳﻬﯿﻞﻋﻤﺮﺍﻥ‬ 9

 behavioral

Statechart Diagrams
At any given time, an object is in a particular state. State
diagrams represent these states and their changes over
time. Statechart diagrams describe the dynamic behavior of
a system in response to external stimuli. Statechart
diagrams are especially useful in modeling reactive objects
whose states are triggered by specific events.

Activity Diagrams
The activities that occur within a use case or within an
object’s behaviour typically occur in sequence, which is
represented with activity diagrams. Activity diagrams
illustrate the dynamic nature of a system by modeling the
flow of control from activity to activity. An activity
represents an operation on some class in the system that
results in a change in the state of the system. Typically,
activity diagrams are used to model workflow or business
processes and internal operation.

Sohail IMRAN ‫ﺳﻬﯿﻞﻋﻤﺮﺍﻥ‬ 10