UML is a standard language for modeling software systems using graphical diagrams. It was developed in the 1990s in response to issues with communication between different roles in software development. UML uses diagrams to visualize various views of a system, including structural aspects like classes and components, and behavioral aspects like use cases and interactions. The key building blocks in UML are things like classes and use cases, and relationships like associations and generalizations. Common diagram types include class diagrams, use case diagrams, sequence diagrams, and deployment diagrams. UML aims to provide a standardized way to document software system blueprints.

1. UNIFIED MODELING LANGUAGE
Anoop VJ

2. 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

3. WHY UML?
•
Common Problem in Software industry
•
•
Communication
Roles
•
•
•
•
•
•
Product Owner
BA
Architect
Developer
QA
Operation

4. 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

5. KEY CONSIDERATION
•
Readable
•
Focused
•
Precise

6. BUILDING BLOCKS OF UML
•
Things
•
•
•
•
•
Structural
Behavioral
Grouping
Annotation
Relationships
•
•
•
•
Dependency
Association
Generalization
Realization

7. BUILDING BLOCKS OF UML….. STRUCTURAL
THINGS
•
Class
•
Stereotypes
•
•
•
•
<< stereotype name>>
<<interfaces>>
<<abstract class>>
Iconic Stereotypes

8. BUILDING BLOCKS OF UML….. STRUCTURAL
THINGS
•
Use case
•
Component

9. BUILDING BLOCKS OF UML….. STRUCTURAL
THINGS
•
Node

10. BUILDING BLOCKS OF UML….. BEHAVIORAL
THINGS
•
Message
•
Return
•
Asynchronous

11. BUILDING BLOCKS OF UML….. BEHAVIORAL
THINGS, GROUPING, ANNOTATIONS
•
States
•
Packages
•
Notes

12. BUILDING BLOCKS OF UML….. RELATIONSHIP
•
Association
•
Generalization
•
Implementation / Realization
•
Dependency

13. TYPES OF UML DIAGRAM
•
Structural – Define Framework
•
•
•
•
•
Class Diagram
Component
Package
Deployment
Behavioral
•
•
•
•
Use Case
Sequence
State
Activity

14. STRUCTURAL – CLASS DIAGRAM
•
Static View of application
•
Can construct executable code of software
application

15. STRUCTURAL – CLASS DIAGRAM

16. STRUCTURAL – COMPONENT DIAGRAM
•
Visualize the components of a system.
•
Describe the organization and relationships of the
components.
•
Identify interfaces
•
Replaceable parts

17. STRUCTURAL – COMPONENT DIAGRAM

18. STRUCTURAL – PACKAGE DIAGRAM
•
Represent either physical or logical relationship
•
Support Larger Models

19. STRUCTURAL – PACKAGE DIAGRAM
Workload Management

20. STRUCTURAL – PACKAGE DIAGRAM
Workload Management

21. STRUCTURAL – DEPLOYMENT DIAGRAM
•
Models the run-time architecture of a system.
•
Nodes

22. STRUCTURAL – DEPLOYMENT DIAGRAM

23. BEHAVIORAL DIAGRAM
•
Interaction
•
Functionality

24. BEHAVIORAL DIAGRAM – USE CASE
•
User Tasks
•
System Interaction
•
What system do

25. BEHAVIORAL DIAGRAM – USE CASE

26. BEHAVIORAL DIAGRAM – SEQUENCE
DIAGRAM
•
To model flow of control by time sequence
•
System Interaction
•
What system do

27. BEHAVIORAL DIAGRAM – SEQUENCE
DIAGRAM

28. BEHAVIORAL DIAGRAM – STATE DIAGRAM
•
Models state of an object

29. BEHAVIORAL DIAGRAM – ACTIVITY DIAGRAM
•
Workflow
•
Operations

30. BEHAVIORAL DIAGRAM – ACTIVITY DIAGRAM

31. TOOLS
•
Enterprise Architect (License)
•
Argo UML(Free)
•
Start UML(Free)

32. THANK YOU
Anoop VJ

33. Q&A