UNIFIED MODELING LANGUAGE

Anoop VJ

HISTORY

• 1980s and 1990s

• Object Oriented Analysis and Design (OOA & D)

• 1997

• Lateste

• Object Oriented Management (OMG) group call for

submission of standards

• Rational Software submitted UML 1.0

WHY UML?

• Common Problem in Software industry

• Communication

• Roles

• Product Owner

• BA

• Architect

• Developer

• QA

• Operation

DEFINITION FOR UML

• "The Unified Modeling Language (UML) is a

graphical language for visualizing,

specifying, constructing, and documenting the

artifacts of a software-intensive system.

The UML offers a standard way to write a system's

blueprints, including conceptual

things such as business processes and system

functions as well as concrete things such

as programming language statements, database

schemas, and reusable software

components.“ • Courtesy- http://www.sparxsystems.com/uml-tutorial.html

KEY CONSIDERATION

• Readable

• Focused

• Precise

BUILDING BLOCKS OF UML

• Things

• Structural

• Behavioral

• Grouping

• Annotation

• Relationships

• Dependency

• Association

• Generalization

• Realization

BUILDING BLOCKS OF UML….. STRUCTURAL

THINGS

• Class

• Stereotypes

• << stereotype name>>

• <<interfaces>>

• <<abstract class>>

• Iconic Stereotypes

BUILDING BLOCKS OF UML….. STRUCTURAL

THINGS

• Use case

• Component

BUILDING BLOCKS OF UML….. STRUCTURAL

THINGS

• Node

BUILDING BLOCKS OF UML….. BEHAVIORAL

THINGS

• Message

• Return

• Asynchronous

BUILDING BLOCKS OF UML….. BEHAVIORAL

THINGS, GROUPING, ANNOTATIONS

• States

• Packages

• Notes

BUILDING BLOCKS OF UML….. RELATIONSHIP

• Association

• Generalization

• Implementation / Realization

• Dependency

TYPES OF UML DIAGRAM

• Structural – Define Framework

• Class Diagram

• Component

• Package

• Deployment

• Behavioral

• Use Case

• Sequence

• State

• Activity

STRUCTURAL – CLASS DIAGRAM

• Static View of application

• Can construct executable code of software

application

STRUCTURAL – CLASS DIAGRAM

STRUCTURAL – COMPONENT DIAGRAM

• Visualize the components of a system.

• Describe the organization and relationships of the

components.

• Identify interfaces

• Replaceable parts

STRUCTURAL – COMPONENT DIAGRAM

STRUCTURAL – PACKAGE DIAGRAM

• Represent either physical or logical relationship

• Support Larger Models

STRUCTURAL – PACKAGE DIAGRAM

Workload Management

STRUCTURAL – PACKAGE DIAGRAM

Workload Management

STRUCTURAL – DEPLOYMENT DIAGRAM

• Models the run-time architecture of a system.

• Nodes

STRUCTURAL – DEPLOYMENT DIAGRAM

BEHAVIORAL DIAGRAM

• Interaction

• Functionality

BEHAVIORAL DIAGRAM – USE CASE

• User Tasks

• System Interaction

• What system do

BEHAVIORAL DIAGRAM – USE CASE

BEHAVIORAL DIAGRAM – SEQUENCE

DIAGRAM

• To model flow of control by time sequence

• System Interaction

• What system do

BEHAVIORAL DIAGRAM – SEQUENCE

DIAGRAM

BEHAVIORAL DIAGRAM – STATE DIAGRAM

• Models state of an object

BEHAVIORAL DIAGRAM – ACTIVITY DIAGRAM

• Workflow

• Operations

BEHAVIORAL DIAGRAM – ACTIVITY DIAGRAM

TOOLS

• Enterprise Architect (License)

• Argo UML(Free)

• Start UML(Free)

THANK YOU

Anoop VJ

Q & A