You are on page 1of 32

The main phases of building a software system are

Requirements Gathering, Analysis, Design, Development and Testing.

These steps are done iteratively to produce incremental versions of
software. The important part of creating an application is Analysis and

Analysis is the decomposition of an
application into its constituent parts.

It can also be described as separation or
breaking up of a whole into its
fundamental elements or component

The Design Phase helps a project
progress to the Coding Phase in a smooth

A Design phase consists of a set of
decisions that determine how the Design
Model will be implemented.

Software applications require a more sound
approach in designing and writing the

OOAD provides a solution to analyze and
design an application using the Object
Oriented principles, well defined notations
and diagrams like UML.

It defines a process that is well suited for large
and complex applications.

Requirements can be understood easily
as the Analysis and Design is done
Faster Development
Simple early designs may be inadequate
to solve the entire problem

The process of Analysis and Design may
become very heavy weight

UML is a language that helps to visualize,
specify, construct, and document models. In
building a visual model for a system, many
different diagrams are needed to represent
different views of the system. UML provides a
rich notation for visualizing the models
The UML is a generic modeling language.

With UML, one can produce blueprints for any kind of
software system. Graphic notations are used for Object
Oriented construction of systems in Software
Development Life Cycle (SDLC).

UML provides a set of graphical notations for different
entities & terms used in Object Oriented Modeling and
Analysis of any system.
Visual Paradigm for the Unified Modeling Language
(VP-UML) is a full-featured UML CASE tool
supporting real-time code-model synchronization.

VP-UML is a powerful UML case tool. it provides an
environment to carry out various activities of Object
Oriented Analysis and Design through easy drag and drop
operations to create UML diagrams.

VP-UML has powerful features that can be used to perform
a detailed modeling and analysis of any given problem.

VP-UML is capable of generating Java and .NET persistent code.

VP-UML provides an extension for the major Integrated Development
Environments (IDEs), including Eclipse, Borland JBuilder0,
NetBeans/Sun. ONE etc.

It is designed for a wide range of users, including Software Engineers,
System Analysts, Business Analysts, and System Architects alike
Use-Case diagrams describe what the system will do.

They serve as a contract between the users and the system

It allows the users to validate the system for what they expect
from the system.

It allows the system developers to build what is expected out of

The Use-Case model consists of Use-Cases and Actors with
System Boundary and Connectors.

A system boundary element signifies a classifier, such as a
class, component or sub-system, to which the enclosed
Use-Cases are applied.

By depicting a boundary, its referenced classifier does not
reflect ownership of the embodied Use-Cases, but instead
indicates usage.

An Actor represents anything that interacts with
the system.

An actor is not part of the system. It can be referred
to as an External entity that acts on the system.

It represent roles a user can play in the system.

An Actor can represent a human, a machine or
another system.

A connector represents the line connecting two shapes on
the diagram. A connector element is used to connect
different elements of a use-case diagram.

Stereotypes allow one to extend the basic UML notation by
allowing a new modeling element to be defined based on an
existing modeling element.

The name of a stereotype is shown in guillemots, for example,
<<stereotype name>>.

Use-Case is provided by default with the UML standard
stereotypes (metaclass, powertype, process, and thread, utility)
for classifiers.