Ioose Uml Diagrams

8/2/2019 Ioose Uml Diagrams

1/36


2/36

UML Concepts

UML can be used to support your entire life

cycle.1. The interaction of your application with the outside world (use

case diagram)2. Visualize object interaction (sequence & collaboration diagrams)

3. The structure of your system (class diagram)

4. View the system architecture by looking at the defined package.

5. The components in your system (component diagram)


3/36

What are Diagrams ?

Graphical presentation of model elements.

A diagram is a graphical means to view a systems

parts


4/36

UML Diagrams

8 diagrams

You will model the following 5 diagrams only:

1. Use case diagram

2. Activity diagram

3. Sequence diagram

4. Collaboration diagram

5. Class diagram

The other UML diagrams that can be modeled in Rose are:

1. State chart diagram

2. Component diagram3. Deployment diagram

Interactiondiagram


5/36

Behavior Diagram

Sequence diagram

Collaboration diagram

State chart diagram Activity diagram

Interactiondiagram

behaviordiagram


6/36

UML Diagrams

1. Class diagram

2. Use case diagram

3. Activity diagram

4. Sequence diagram

5. Collaboration diagram

6. State chart diagram

7. Component diagram

8. Deployment diagram


7/36

1. Class diagram

Class a set of objects that share the same

attributes, operations & relationships.

It represented by a compartmentalized rectangle.

It shows the structure of your software.

3 compartments1. Top

2. Middle

3. Bottom


8/36

1. Class diagram

1. Top shows class name2. Middle shows class attributes

3. Bottom shows class operation


9/36

1. Class diagram

1. Attributes defines the characteristics orstructure of a class.

displayed in the middle of thecompartmentalized rectangle.

Attributes


10/36

1. Class diagram

2. Operation the service provided by the class. displayed in the bottom of the

compartmentalized rectangle.

Operations


11/36

2.Use case diagram

It shows a set of use cases and actors and

their relationships.

Address the static view of a system.

Actor user (or) someone / something

outside the system that interacts with the

system (it must be a noun) & it is represented

by a stickman.

contd


12/36

2.Use case diagram

Use case a sequences of actions (it must be a

verb) & it is represented by an oval.

Relationshipillustrates a connection among modelelements.

Unidirectional Bi-directional

It is created to visualize the interaction of your

system with the outside world. (e.g.) ATM

contd


13/36

2. Use case diagram (ATM)

CASH

DISPENSER

PRINTER

CHANGE PIN

WITHDRAW

CHECK BALANCE

LOGIN

CUSTOMER


14/36

2. Use case diagram (Pay roll)

Actors employee & account

Use case

count leave, disburse salary, checkloans, calculate PF, prepare IT returns,

calculate HRA & check salary


15/36

Customer

Calculate PF

Check loans

Disburse salary

Count leave

Prepare IT returns

Check salary

Calculate HRA


16/36

3.Activity Diagram

It shows the flow of events with our system &what is going on inside a use case.

We draw the activity diagram for each & every

use case. Login (use case) (e.g.) ATM

It is showing flow of control from activity to

activity.


17/36

3.Activity Diagram

Activity it represents the performance of a task

within the workflow.

Activity is represented by a lozenge (horizontal top

and bottom with convex sides) Start state shows the beginning of a workflow on an

activity diagram.

There is only one start state.


18/36

3.Activity Diagram

A start state is represented by a solid circle.

An end state represents a final or terminalstate on an activity diagram.

A end state is represented by a bulls eye.


19/36

3.Activity Diagram

A state transition shows what activity follows

after another.

It is represented by a solid line with an arrow.


20/36

3.Activity Diagram

A decision is a point in an activity diagram where

guard conditions are used to indicate different

possible transitions.

It is represented by a diamond. Guard conditions control the transition of a set of

alternate transitions that follows after the activity

has been completed.


21/36

3.Activity Diagram

AND

Joint

Synchronization bar


22/36

3.Activity Diagram

A synchronization bar allows you to show

concurrent threads in a work flow of a use

case.

It represented by a thick horizontal or vertical

line.


23/36

3.Activity Diagram

A swimlane is used to partition an activity

diagram to help us better understand who or

what is initiating an activity.


24/36

3.Activity Diagram Login Use case

Customer Enters

the login details

System retrives

the details

System validates

the customer

System welcomes

the customer

System prompts to

reenter

[ True ]

[ False ]


25/36

4.Sequence Diagram

It shows step by step what must happen toaccomplish a piece of functionality provided

by the system.

It has 2Ds.1. Vertical dimensions represents time

2. Horizontal dimensions represents different

objects.

Vertical line is called the objects life line.


26/36

4.Sequence Diagram

Life line the existence object at a

particular time.

Objects are shown at the top.

The object role is shown as a vertical dashedline, the life line.


27/36

4.Sequence Diagram

A message is the communication between 2

objects that triggers an event.

It is represented by a labeled arrow.

Each message is represented by an arrow between

the life lines of 2 objects.


28/36

4.Sequence Diagram

A focus of control shows the period of time

during which an object is performing an

action, either directly or through a

subordinate procedure.

It represented by a tall, thin rectangle.


29/36

4.Sequence Diagram login success

: Customer: Customer : LoginForm: LoginForm : LoginController: LoginController : CustomerInfo: CustomerInfo

Enter Login Detail...

Submit( )

Validate( )

getLoginDetails( )


30/36

5.Collaboration Diagram

It displays objects and their links to one other.

It is also known as an interaction diagram.


31/36


It is made up of the following basic elements

:

1. Actors

2. Objects

3. Links

4. Messages


32/36


1. Actors user

2. Objects data + logic / the representation

of some real world entity.

3. Links a pathway for communication

between objects.

represented by a solid line

between 2 objects

4. Messages the communication between

objects that triggers an event.

represented by a labeled arrow above

the link.


33/36

5.Collaboration Diagram Login use case

: Customer: LoginForm

: LoginController

: CustomerInfo

1: Enter Login Details ( )2: Submit( )

3: Validate( )

4: getLoginDetails( )

h


34/36

6. State Chart Diagram

It shows the sequence of states. A state is represented as a rounded box, which

may contain one or more compartments.

Name compartment holds the name of thestate.

Internal transition compartment list of

actions / activities Start & end states


35/36

7.Component Diagram

It shows relationship between the

components in the system.

A component may be a software component

[for (e.g.) a.h file in C++ (or) a .java file in

Java], a run time component [for (e.g.) a.DLL

file]


36/36

8. Deployment Diagram

It shows the configuration of run time

processing elements & the software

components, processes & objects that live in

them.

It shows the nodes in the system & the

connections between them.

Documents

Ioose Uml Diagrams