Purpose of Use Case Modeling 1

To visualize the system from the perspective of different viewers. The better we understand
the better we can build the system

UML -One of the popular modeling language successor of object-oriented (OO) analysis and
design.
2 Key Models are used 2

Structural Modeling Behavioral Modeling

Common UML Diagrams in a single Page 3

Diagram Type Purpose Who Uses

To model the static view of an application.

Class Diagram Structural Can be directly mapped with object-oriented languages and thus widely used at the time of construction Developers
Base for component and deployment diagrams

Component diagrams can also be described as a static implementation view of a system

Component Diagram Structural Developers
These components are libraries, packages, files, etc.

Developers,
Package Diagram Structural To view components as logical container
Deployment Team
Deployment diagrams are used for describing the hardware components, where software components are
Deployment Diagram Structural Deployment
deployed
Business Analyst
A single use case diagram captures a particular functionality of a system highlighting association between
Solution Architect
Use-Case Diagram Behavioral use-cases.
Development Team
Show the interaction among the requirements and actors
Testing
Business Analyst
Solution Architect
Sequence Diagram Behavioral To model the flow of control by time sequence
Development Team
Testing
Business Analyst
The most important purpose of Statechart diagram is to model lifetime of an Solution Architect
State Diagram Behavioral
object from creation to termination the different states. Development
Testing
Business Analyst
Activity Diagram Behavioral Activity diagram is suitable for modeling the activity flow of the system
Solution Architect
UML Model Common Notations 4

Use Case Diagram Notations

Activity Diagram Notations Sequence Diagram Notations

Class Relationship Notations

State Diagram Notations Other Notations

Structural Modeling:Class Diagram 5

 Represents an Entity consists of

• attributes
• Operations

 Base for component and

deployment diagrams

 Represent relationships between

classes
Structural Modeling: Component Diagram
Help:

 Identify interfaces

 Represent Identify loosely or

tightly connected components
Structural Modeling: Package Diagram
Can contain:

 Classes

 Interfaces

 Components

 Packages

 Etc...
Structural Modeling: Deployment Diagram

 Map components to physical

Systems

 Visualize hardware and Network

Dependencies
Behavioral Modeling: Use Case Diagram

 User Tasks Example 1: Extends relationship to Receive Order

 System interactions

 Factor out common processes

(<<include>>)

 Identify optional additions

(<<extend>>)

Example 2: Include relationship between use-cases for Check out

Behavioral Modeling: Activity Diagram
Represents :

 Activity Flow of system

Behavioral Modeling: State Diagram
Represents :

 States of an object in it’s

lifetime
Behavioral Modeling: Sequence Diagram
Represents :

 Object Interaction

 Focus on object life time

• Creation
• Termination

 Message
• Return
• Self
• Asynchronous

 Looping

 Optional

 Conditional

 Parallel