Material : Introduction to UML

By
Kamalakannan.J
AP(SG),SITE,VIT

FOUR PHASES OF OO PROJECT DEVELOPMENT

[Rational Unified Process]

1.INCEPTION
2.ELABORATION
3.CONSTRUCTION
4.TRANSITION

INCEPTION
It is the beginning of the project.
It gives answer to the following
How long it would take?
How much it will cost?
How feasible the project Is?

ROSE SUPPORT TO PROJECT

Create actors and use cases
Produce use case diagram

INCEPTION (Contd)
Inception is only done only once on a project.
Other task in inception is the development of
an iteration plan.
It describes the order of the use case
implementation (which will be implemented during
which iteration)

ELABORATION
It includes planning, analysis, and architectural
design.
It is done for each use case .
It includes several aspect of the project
Coding proofs-of-concepts
Developing test cases
Making design decisions

ELABORATION (contd)

tasks are
Refining the initial estimates
Reviewing the SRS and use case model for quality
Investigating risks

ROSE SUPPORT TO ELABORATION

Refining the use case model

The sequence and collaboration
(to show the graphical flow of processing)
The class diagram
(showing the objects to be built)

This phase is completed when the system is

designed,reviewed,and ready for the developers.

CONSTRUCTION
It includes the process of developing and testing the
software
This helps the project team carry out parallel
development
Parallel development
Multiple developers can work on the different objects in
the software

We design the Objects and how they will interact

Putting the design into action rather than making
new design decisions

CONSTRUCTION (Contd)
Rose support
Generate code
Components and component diagram

Component diagram
To show compile time dependencies between the
components.

The model can be synchronized with the code

through reverse engineering.
Construction is over when the software is complete
and tested.

TRANSITION
It begins when the completed software product is turned over
to the user community

Tasks are

Completing the final software product

Completing final acceptance test
Completing user documentation
Preparing for user training

Rose support
Helps plan the deploy (deployment diagram)

What Is Visual Modeling?

Order

Modeling captures essential

parts of the system.

Item

Dr. James Rumbaugh

Ship via

Business Process

Visual Modeling is modeling

using standard graphical
notations

Computer System

Visual Modeling Captures Business

Processes
Use-case analysis is a technique to capture business
processes from a users perspective.

Visual Modeling Is a Communication

Tool
Use visual modeling to capture business objects and logic.

Use visual modeling to analyze and design your application.

Visual Modeling Manages Complexity

Visual Modeling Promotes Reuse

Multiple Systems

Reusable
Components

How Do I Construct a Model?

Models are constructed using views to depict

different perspectives and diagrams to depict a
systems building blocks.

Views

A view is a perspective of the model that is

meaningful to specific stakeholders.

Use-Case View
The Use-Case View is the heart of the
other views because it specifies WHAT the
system should do.

Logical View
The Logical View supports the functional
requirements of the system.

Process View
The Process View addresses the performance,
scalability, and throughput of the system.

Component View (Implementation

View)
In Rose, the Implementation View is called the
Component View.
The Component View addresses ease of
development, management of software assets,
reuse, sub-contracting, and off-the-shelf
components.

Deployment View
The Deployment View addresses issues like
deployment, installation, and performance.

History of the UML

UML 2.0

Planned major revision (2001)

UML 1.4

Planned minor revision (2000)

UML 1.3

Current minor revision 1999

Public
Feedback

OMG Acceptance, Nov 1997

Final submission to OMG, Sept 1997
First submission to OMG, Jan 1997
UML partners

Web - June 1996

OOPSLA 95

UML 1.1

UML 1.0

UML Concepts
The UML may be used to visually model
The interaction of your application with the
outside world.
The behavior of your application.
The structure of your system.
The architecture of your enterprise.
The components in your system.

Use-Case Diagram
A use-case diagram is created to visualize the
interaction of your system with the outside
world.
Request Course Roster
Professor

Student
Register for Courses

Billing System

Maintain Course Information

Registrar

Activity Diagram

An activity diagram shows the flow of

Create
events within our
curriculum
Select courses
system.
to teach
Create
catalog

Place catalog
in bookstore

Mail catalog
to students

Open
registration
[ Registration time period expired ]
Close
registration

Sequence Diagram
A sequence diagram shows step by step what
must happen to accomplish a piece of
functionality provided by the system.
: Student

registration
form

registration
manager

math 101

math 101
section 1

1: fill in info
2: submit
3: add Joe to Math 101
4: add Joe
5: are you open?
6: add Joe

Collaboration Diagram
A collaboration diagram displays object
interactions organized around objects and
their links to1: one
another. course form :
set course info
2: process

CourseForm

3: add course

: Registrar

theManager :
CurriculumManager

aCourse :
Course
4: new course

Class Diagram
A class diagram shows the structure of your
software.
ScheduleAlgorithm

RegistrationForm
0..*

1 RegistrationManager
addStudent(Course, Student)

1
RegistrationUser
name

Student

Course
name
0..* numberCredits
open()

addStudent(StudentInfo)

major

1
3..10
Professor
tenureStatus

1..*
4 CourseOffering
location
0..4
open()

addStudent(Student)

Statechart Diagram
A statechart diagram shows the lifecycle of a
single class.
Add student[ count < 10 ]
Initialization
do: Initialize course

Add Student /
Set count = 0

Open
entry: Register student
exit: Increment count

Cancel
Cancel
Canceled
do: Notify registered
students

Cancel

[ count = 10 ]

Closed
do: Finalize course

Component Diagram
A component diagram illustrates the
organization and dependencies among
software components.
Register.exe

Billing.exe
Billing
System

People.dll
User

Course.dll
Course

Deployment Diagram
A deployment diagram visualizes the
distribution of components across the
enterprise.
Registration

Database

Main
Building

Library

Dorm