UML notations and symbols

USE CASE
An use case frequently use another uses case is modelled
using include relationship
Actor:
Staff
ATM Customer
<<include>>
Transaction verification

Add advert
Use case:
An use case is supplemented by another in a certain situation
use case is modelled using extends relationship. Situation
condition is extension point

<<include>>
Calculate Calculate
<<extend>>
payments bonus
<<extend>>

Calculate payments Calculate

<<extend>> bonus
Extension points:
90% attendance

Object/Instance

Object diagram:

Object name compartment

Named object: Object-name:Class-name
Optional Attributes with values compartments

Object without name: :Class-name

Object-name:class-name

Attribute 1 = value
Attribute2 = value
bazl = new TSP(): bazl:TSP

:TSP Named object with attribute values

new TSP():

Sohel Rana: Trainee

Named object with stereotype
Object-name: class-name
ID =
Name = Sohel Rana
Anonymous object with stereotype
:class-name

Anonymous object with attribute values

Sohel Rana: Trainee

ID =
Name = Sohel Rana
Class

Attribute: Attribute-name: type-name = initial value {property string}

Example
Model: String
Balance: Decimal = 0
ID: String {Unique}
Attribute visibility: + public, - private, # protected, ~ package
Derived attribute: /attribute-name
Class-scope attribute: Attribute-name:type-name
Operation: Operation-name (parameter-name: type,..):return-type
Class-scope Operation: Operation-name (parameter-name: type,..):return-type

Stereotypes: Control Boundary Entity

Class diagram:
Class -name

Attributes
Operations

Class diagram with stereotype: <<Stereotype>>

Class -name
Class -name
Attributes
Attributes
Operations
Operations

Abstract class: Class -name

Class -name
{abstract}
Attributes
Attributes
Operations
Operations

Provided/implemented
interface: Inteface-name Class -name

Attributes
Operations
Interface realization
<<Interface>>
dependency: Class -name
InterfaceName
Attributes
-memberName Operations
-memberName

Required Interface:
Inteface-name Class -name

Attributes
Operations

2
 Package:

Package
dependency:

Package
dependency: <<Stereotype>>
Payments

Association
Inheritance/
Generalization: A B

Association:
A B

Association with role

name: A B
Administrator

Association with
name and direction: A B
Adinisters

Association with 1 *
multiplicity: A B

Association with
navigability: A B
One way

A B
Two way

Composition:
A B

Aggregation:
A B

3
Sate chart
Initial State:

Final State:

State: State name

Transition:

Idle

Call event: Event [guard-condition] /action-expression Open (code) [code ok] /showconsole()
Call-action [guard-condition] /action-expression

Active

State with internal Active

event/action:
entry / lighton()
do / watchdoors()
exit / lightoff()

State
Composite State:

Concurrent State:

4
Activity
Initial node:

Final node:

Activity/action:
Action name Action A

Activity flow:

Action B

Guard condition: [condition] Action A Action A

[condition] [condition]
[condition]

Action B Action B Action c

Merge node:
Action A Action B

Action C

Action A
Decision node:

Action B [condition] [condition] Action c

5
 Fork/split:

Join:

Client Order controller

Partition/swimline Region name

Request order

Process order

Acitivity with sub-

activities
Activity name