Unified Modeling Language - 5

8/9/2019 Unified Modeling Language - 5

1/24

Unified Modeling Language


2/24

The Unified Modeling Language (UML) is used to specify,

visualize, modify, construct and documentthe artifacts of an object-oriented software intensive

system under development. UML offers a standard way

to visualize a system's architectural blueprints, including

elements such as: Actors

Business processes

Components

Activities

Reusable software components


3/24

UML Diagrams Classification

Behaviour Diagrams : A type of diagram that depictsbehavioural features of a system or business process. This

includes Activity, State Machine, and Use Case Diagrams as

well as the Four interaction Diagrams

Interaction Diagrams : A subset of behaviour diagrams whichemphasize object interactions. This includes Communication,

Interaction Overview, Sequence and Timing diagrams.

Structure Diagrams : A type of diagram that depicts the

elements of a specification that are irrespective of time. Thisincludes Class, Composite Structure, Component,

Deployment, Object, and Package Diagrams


4/24


5/24


6/24

An actor is represents a user or another system thatwill interact with the system you are modeling.

A use case is an external view of the system that

represents some action the user might perform inorder to complete a task.


7/24


8/24

The Relationships between Use Cases

Include : The base use case explicitly incorporates thebehavior of another use case.

Oder Confirmation

Check Inventory

Get Credit

Approval


9/24

Extend: Shows the optional behavior of a use case

PlaceOrder Request Catalogue


10/24

Generalization : Child use case inherits

PayBill

Pay by Cash

Pay by Credit Card


11/24

Class Diagram

Class diagrams are widely used to describe thetypes of objects in a system and their

relationships.

Classes are composed of three things. Below is

an example of a class.


12/24

Object Diagram

Depicts actual object instances and their relationshipsat a point in time

Use a notation similar to class diagrams

Objects in a object diagram can be named using 3

conventions as follows,

Object Name : Class Name Object Name

: Class Name

1. 2.

3.


13/24

Sequence Diagram

Models the sequential logic, in effect of the

time ordering of messages between

classifiers

Depicts the sequence of actions that occur in

a system


14/24

S1 :Student BIT : Course

get courseDetails()


15/24

Collaboration Diagram

Shows the instances of classes, their

interrelationships, and the message flow

between them

Focus on the structural organization of objects

that send and receive messages

Also called as Communication Diagram


16/24


17/24

State Diagram

Describes the states of an object or interaction

may be in, as well as the transitions between

states.

Also called as State Chart Diagram, State

Machine Diagram, State Transition Diagram


18/24


19/24

Activity Diagram

Depicts high level business processes,

including data flow, or to model the logic of

complex logic within a system

Graphical representations of workflows of

stepwise activities and actions with support

for choice, iteration and concurrency


20/24

Insert Card

EnterPin

Enter Amount DisplayError Message

Release Cash Update Account

Print Receipt

DisplayBalance

Eject Card


21/24

Component Diagram

Depicts the components that compose an

application, system or enterprise.

The components, their relationships,interactions and their public interfaces are

depicted


22/24

OracleDatabase

Student Registration

Application


23/24

Deployment Diagram

Shows the execution architecture of the

system.

This includes nodes, either hardware or

software execution environments as well as

the middleware connecting them


24/24

Unified Modeling Language - 5

Documents