UML Basics Department of CSE, SARANATHAN

UML

1. Introduction to UML
Venkat Srinivasan
Dept. of CSE

4. MS-DOS–4000 lines of code
Windows NT–2 million lines of code
Windows 3.1–2 million lines of code
Windows 7–40 million lines of code
Windows XP–45 million lines of code
Windows Vista-50 million lines of code
Windows 10–80 million lines of code
Ubuntu–50 million lines of code
MacOS X–84 million lines of code
Android–12 million lines of code
iOS–12 million lines of code

5. Web browsers
Google Chrome-6.7 million lines of
code
Mozilla Firefox–21 million lines of
code
Office suites
Microsoft Office 2013–45 million
lines of code
Apache OpenOffice–19 million lines
of code
LibreOffice–10 million lines of code
Social networks
Facebook–62 million lines of code
TikTok–80,000 lines of code
SnapChat–60,000 lines of code
Instagram–1 million lines of code
LinkedIn–8 million lines of code
Twitter–10 million lines of code
Messaging apps
WhatsApp–30,000 lines of code
Telegram–50,000 lines of code
Zoom–60,000 lines of code
Media players and audio and video editors
Blender–1.1 lines of code
Audacity–161,007 lines of code
VLC Media Player–599,658 lines of code
Media Player Classic–168,007 lines of code
Image editors
GIMP–726,863 lines of code
Adobe Photoshop–10 million lines of code
Krita–1 million lines of code
P2P programs
Ares Galaxy–1,176,679 lines of code
eMule-2,437,791 lines of code
BitTorrent–its protocol has only 8,633 lines of code
Vuze–967,990 lines of code
Web applications
WordPress–160,636 lines of code
Google Suite(Gmail,Drive, Search, etc.): 2 billion
lines of code
Reddit-139,659 lines of code
Menéame–23,190 lines of code
Video game
Grand Theft Auto V (GTA 5)–36 million lines of code
Red Dead Redemption II (RDR2)–60 million lines of
code
World of Warcraft (WoW)–5.5 million lines of code
Minecraft–500,000 lines of code
Age of Empires Online-1 million lines of code

7. •Model is an abstract representation of
a system, constructed to understand
the system prior to building or
modifying it.
•It is a simplified representation of
reality
•Modeling is used during many phases
of the software life cycles.

8. Triangle for success
Tools
cannot exist
alone
Language (Notation)
Process Tools

9. Computer System
Business Process
Order
Item
Ship via
“Modeling captures essential
parts of the system.”
Dr. James Rumbaugh
Visual Modeling is
modeling
using standard graphical
notations
What is Visual Modeling?

10. Use Case Analysis is a technique to capture
business process from user’s perspective
Visual Modeling Captures
Business Process

11. Visual Modeling is a
Communication Tool
Use visual modeling to capture business objects and logic
Use visual modeling to analyze and design
your application

12. Visual Modeling
Manages Complexity

13. User Interface
(Visual Basic,
Java)
Business Logic
(C++, Java)
Database Server
(C++ & SQL)
Model your system
independent of
implementation language
Visual Modeling Defines Software
Architecture

14. Multiple Systems
Visual Modeling
Promotes Reuse
Reusable
Components

15. Three Important Features of the
Iterative Approach
•Continuous integration
–Not done in one lump near the delivery
date
•Frequent, executable releases
–Some internal; some delivered
•Attack risks through demonstrable progress
–Progress measured in products, not
documentation or engineering estimates

16. Risk
Transition
Inception
Elaboration
Construction
Preliminary
Iteration
Architect.
Iteration
Architect.
Iteration
Devel.
Iteration
Devel.
Iteration
Devel.
Iteration
Transition
Iteration
Transition
Iteration
Post-
deployment
Waterfall
Time
Risk Profile of an Iterative
Development

17. Risk Management
Phase-by-Phase
•Inception
–Bracket the project’s risks by building a proof of
concept
•Elaboration
–Develop a common understanding of the system’s
scope and desired behavior by exploring scenarios
with end users and domain experts
–Establish the system’s architecture
–Design common mechanisms to address system-
wide issues

18. Risk Management
Phase-by-Phase (cont.)
•Construction
–Refine the architecture
–Risk-driven iterations
–Continuous integration
•Transition
–Facilitate user acceptance
–Measure user satisfaction
•Post-deployment cycles
–Continue evolutionary approach
–Preserve architectural integrity

19. Initial Project Risks
Initial Project Scope
Revise Overall
Project Plan
•Cost
•Schedule
•Scope/Content
Plan Iteration N
•Cost
•Schedule
Assess Iteration N
Risks Eliminated
Revise Project Risks
•Reprioritize
Develop Iteration N
•Collect cost and
quality metrics
Define scenarios to
address highest risks
Iteration N
Risk Reduction Drives
Iterations

20. Inception ElaborationConstruction Transition
Iteration 1Iteration 2Iteration 3
Iteration Planning
Rqmts Capture
Analysis & Design
Implementation
Test
Prepare Release
“Mini-Waterfall” Process
Use Cases Drive the
Iteration Process

21. The Iteration Life Cycle: A
Mini-Waterfall
•Results of previous iterations
•Up-to-date risk assessment
•Controlled libraries of models,
code, and tests
Release description
Updated risk assessment
Controlled libraries
Iteration Planning
Requirements Capture
Analysis & Design
Implementation
Test
Prepare Release
Selected scenarios

22. Detailed Iteration Life
Cycle Activities
•Iteration planning
–Before the iteration begins, the general objectives of
the iteration should be established based on
•Results of previous iterations ( if any)
•Up-to-date risk assessment for the project
–Determine the evaluation criteria for this iteration
–Prepare detailed iteration plan for inclusion in the
development plan
•Include intermediate milestones to monitor
progress
•Include walkthroughs and reviews

23. Detailed Iteration Life
Cycle Activities (cont.)
•Requirements Capture
–Select/define the use cases to be
implemented in this iteration
–Update the object model to reflect additional
domain classes and associations discovered
–Develop a test plan for the iteration

24. Copyright © 1997 by Rational Software Corporation
Detailed Iteration Life
Cycle Activities (cont.)
•Analysis & Design
–Determine the classes to be developed or updated in
this iteration
–Update the object model to reflect additional design
classes and associations discovered
–Update the architecture document if needed
–Begin development of test procedures
•Implementation
–Automatically generate code from the design model
–Manually generate code for operations
–Complete test procedures
–Conduct unit and integration tests

25. Detailed Iteration Life
Cycle Activities (cont.)
•Test
–Integrate and test the developed code with the rest of
the system (previous releases)
–Capture and review test results
–Evaluate test results relative to the evaluation criteria
–Conduct an iteration assessment
•Prepare the release description
–Synchronize code and design models
–Place products of the iteration in controlled libraries

26. Work Allocation Within an Iteration
•Work to be accomplished within an iteration is
determined by
–The (new) use cases to be implemented
–The rework to be done
•Packages make convenient work packages for
developers
–High-level packages can be assigned to teams
–Lower-level packages can be assigned to individual
developers
•Use Cases make convenient work packages for test and
assessment teams
•Packages are also useful in determining the granularity
at which configuration management will be applied
–For example, check-in and check-out of individual
packages

27. Iteration Assessment
•Assess iteration results relative to the evaluation criteria
established during iteration planning:
–Functionality
–Performance
–Capacity
–Quality measures
•Consider external changes that have occurred during
this iteration
–For example, changes to requirements, user needs,
competitor’s plans
•Determine what rework, if any, is required and assign it
to the remaining iterations

28. Selecting Iterations
•How many iterations do I need?
–On projects taking 18 months or less, 3 to 6
iterations are typical
•Are all iterations on a project the same
length?
–Usually
–Iteration length may vary by phase. For
example, elaboration iterations may be
shorter than construction iterations

29. Copyright © 1997 by Rational Software Corporation
The First Iteration
•The first iteration is usually the hardest
–Requires the entire development environment and
most of the development team to be in place
–Many tool integration issues, team-building issues,
staffing issues, etc. must be resolved
•Teams new to an iterative approach are usually overly-
optimistic
•Be modest regarding the amount of functionality that can
be achieved in the first iteration
–Otherwise, completion of the first iteration will be
delayed,
–The total number of iterations reduced, and
–The benefits of an iterative approach reduced

30. There Is No Silver Bullet
•Remember the main reason for using the iterative life
cycle:
–You do not have all the information you need up front
–Things will change during the development period
•You must expect that
–Some risks will not be eliminated as planned
–You will discover new risks along the way
–Some rework will be required; some lines of code
developed for an iteration will be thrown away
–Requirements will change along the way

31. Development Cycle
•The development cycle is split into phases.
•Phases are split into iterations.
•Activities are grouped by disciplines.

32. Why Model
•Blueprint for large developments
•Solve problems before building systems
•Construct parts that fit together
•Plan
•Manage resource
•Adapt to change

33. Models help
•“Visualize” the system
•Agreement with customers
•Agreement with sponsors
•Estimation
•Costing
•Scalability and reliability planning

34. Can be built by one person
Requires
Minimal modeling
Simple process
Simple tools
Architecting a dog house

35. Architecting a house
Built most efficiently and timely by a team
Requires
Modeling
Well-defined process
Power tools

36. Modeling a house

37. When not to model?
•Trivial systems
•Over-modelling of modest systems
•Over-modelling of large systems
–diagrams for diagrams sake
–excessive detail

38. Types of models
•Static model –snapshot of a system’s
parameters at rest or at specific point in
time (e.g) class diagram
•A dynamic model can be viewed as
collection of procedures or behavior of a
system over time. It shows how business
objects interact to perform tasks.

39. Defining UML
Modeling with UML
Analyzing UML’s Strengths and
Weaknesses
•Describing the Modeling Process
•Defining the Syntax of UML
•Clarifying with an Example
OUTLINE

40. Unified Modeling Language is a
standard language for writing
software blueprints
WHAT IS UML?
Defining UMLModeling with UML Analyzing UMLExamples

41. WHO DEVELOPED IT?
Object
Management
Group
Grady Booch James Rumbaugh
Ivar Jacobson
Defining UMLModeling with UML Analyzing UMLExamples

42. Booch JacobsonRumbaugh
“The 3 Amigos”

44. UML TOOLS
Defining UMLModeling with UML Analyzing UMLExamples
Rational Rose -IBM
ArgoUML –Tigris
http://argouml.tigris.org/
Visual paradigm suite

45. WHY MODEL?
Visualizing
Specifying
Constructing
Documenting
Defining UMLModeling with UML Analyzing UMLExamples

46. PRESCRIBED PROCESS
Object –Oriented
(although not limited)
Use Case Driven
Architecture-centric
Iterative and Incremental
Defining UMLModeling with UML Analyzing UMLExamples

47. ARCHITECTURE CENTRIC
Design
View
Deployment
View
Process
View
Implementation
View
Use Case
View
Design
View
Use Case
View
Defining UMLModeling with UML Analyzing UMLExamples
End-user
Functionality
Analysts/
Designers
structures Programmers
Software management
System topology
Delivery, installation
communication
Performance
Scalability
Throughput
System Integrators

48. SYNTAX AND DIAGRAMS
Things Relationships
Diagrams
•Structural
•Realization•Annotational
•Grouping
•Behavioral
•Generalization
•Association
•Dependency
class
Window
size
open()
waiting
state
Business
rules
package
Return
copies
notes
dependencyassociation
GeneralizationRealization
Defining UMLModeling with UML Analyzing UMLExamples

50. There are about9 types of diagrams in UML1.5
Sequence
Diagrams
Dynamic views Static views
Collaboration
Diagrams
Activity
Diagrams
Statechart
Diagrams
Class
Diagrams
Object
Diagrams
Component
Diagrams
Deployment
Diagrams
Model
Some part of
the model might
not be visible on
any diagram
Use Case
Diagrams

51. Workflows and Models
Requirements
Design
Implementation
Test
Analysis
Use Case
Model
Design
Model
Deploym.
Model
Impl.
Model
Analysis
Model
Test
Model
UML diagrams provide
views into each model
Each workflow is
associated with one or
more models.

52. Use Case Model
Use Case
Diagrams
Collaboration
Diagrams
Component
Diagrams
Deployment
Diagrams
Object
Diagrams
Statechart
Diagrams
Sequence
Diagrams
Class
Diagrams
Activity
Diagrams
Use Case
Model
Design
Model
Depl.
Model
Impl.
Model
Analysis
Model
Test
Model

53. Analysis & Design Model
Use Case
Diagrams
Collaboration
Diagrams
Component
Diagrams
Deployment
Diagrams
Object
Diagrams
Statechart
Diagrams
Sequence
Diagrams
Class
Diagrams
Activity
Diagrams
Use Case
Model
Design
Model
Depl.
Model
Impl.
Model
Analysis
Model
Test
Model
Incl. subsystems
and packages

54. Deployment and Implementation Model
Use Case
Diagrams
Collaboration
Diagrams
Component
Diagrams
Deployment
Diagrams
Object
Diagrams
Statechart
Diagrams
Sequence
Diagrams
Class
Diagrams
Activity
Diagrams
Use Case
Model
Design
Model
Depl.
Model
Impl.
Model
Analysis
Model
Test
Model
Incl. active classes
and components

55. Test Model
Use Case
Diagrams
Collaboration
Diagrams
Component
Diagrams
Deployment
Diagrams
Object
Diagrams
Statechart
Diagrams
Sequence
Diagrams
Class
Diagrams
Activity
Diagrams
Use Case
Model
Design
Model
Depl.
Model
Impl.
Model
Analysis
Model
Test
Model
Test model refers to
all other models and
uses corresponding
diagrams

56. SYNTAX AND DIAGRAMS
Static Dynamic
Class
Object
Component
Deployment
Use Case
Sequence
Collaboration
Statechart
Activity
Defining UMLModeling with UML Analyzing UMLExamples

57. SYNTAX AND DIAGRAMS
Defining UMLModeling with UML Analyzing UMLExamples
Use Case
Diagrams
Collaboration
Diagrams
Sequence
Diagrams
Class
Diagrams
State
Diagrams
Activity
Diagrams
Deployment
Diagrams
Component
Diagrams

58. SYSTEM DESCRIPTION
Defining UMLModeling with UML Analyzing UMLExamples
On-line Grade Record
•Computerized system in which
teachers record and update
grades and students access their
personal grade records

59. USE CASE DIAGRAM
Defining UMLModeling with UML Analyzing UMLExamples
Student
Teacher
Log in
Save Grades
Load Grades
View Grades
Record Grades
Update Grades
<<include>>
<<include>>
<<include>>
<<include>>
<<include>>
<<include>>

64. ACTIVITY DIAGRAM
Defining UMLModeling with UML Analyzing UMLExamples
Teacher Website
Logon
Validate
Validate(UID,PWD)
Not Validated Validated
[valid][invalid]
Display
Logon Error
Choose
Student
Load Student
InformationLoad Student
…

65. SEQUENCE DIAGRAM
Defining UMLModeling with UML Analyzing UMLExamples
Teacher
Web Interface Log
Login Teacher
Log Logon Attempt
Log Successful Logon
[successful logon]
Log Unsuccessful Logon
[unsuccessful logon]
Lookup Student
[successful logon]
Log Student Lookup
Logout Teacher
[successful logon]

66. COLLABORATION DIAGRAM
Defining UMLModeling with UML Analyzing UMLExamples
1: LoadClass(Name)
:Teacher :Student
:Class :FileSystem
1.1: LoadStudents()
1.2: LoadClassInfo()
1.3: LoadRoom()
2: AddStudent(Name)

67. CLASS DIAGRAM
Defining UMLModeling with UML Analyzing UMLExamples
Teacher
-Username
-Password
-Classes
+ AddClass()
+ RemoveClass()
+ ChangePassword(in
OldPassword: String, in
NewPassword: String) :
Boolean
{if (oldPassword = Password
Attribute) then
Password Attribute =
NewPassword
Return Value = True
Else
Return Value = False}

68. CLASS DIAGRAM
Defining UMLModeling with UML Analyzing UMLExamples
Teacher
Online User
Website
+ Logon()
+ View()
Grades
+ RecordGrades()
+ UpdateGrades()
-SaveGrades()
-LoadGrades()
Maintains >
1 1..*
Displays
>
Uses >

69. STATE DIAGRAM
Defining UMLModeling with UML Analyzing UMLExamples
Ready Saving
Saved Error
Success Failure
SaveGrade

70. UML first pass: Sequence
diagram
:LCDDisplay
blinkHours()
blinkMinutes()
refresh()
commitNewTime()
:Time
incrementMinutes()
stopBlinking()
:Watch
pressButton1()
pressButton2()
pressButtons1And2()
pressButton1()
:WatchUser
Object
Message
Activation
Sequence diagrams represent the behavior as interactions
Actor
Lifeline

71. UML first pass: Class diagrams
1
2
push()
release()
1
1
blinkIdx
blinkSeconds()
blinkMinutes()
blinkHours()
stopBlinking()
referesh()
LCDDisplay Battery
load
1
2
1
Time
now
1
Watch
Class
Association
Multiplicity
Attribute
Operations
Class diagrams represent the structure of the system
state
PushButton

72. UML first pass: Statechart diagrams for
objects with interesting dynamic behaviorBlinkHours
BlinkMinutes
IncrementHrs
IncrementMin.
BlinkSeconds IncrementSec.
StopBlinking
[button1&2Pressed]
[button1Pressed]
[button2Pressed]
[button2Pressed]
[button2Pressed]
[button1Pressed]
[button1&2Pressed]
[button1&2Pressed]
State
Initial state
Final state
Transition
Event
Represent behavior as states and transitions

73. •Show aspects of model
implementation, including source
code structure and run-time
implementation structure
•Kinds
–component diagram
–deployment diagram
Implementation Diagrams

74. •Shows the organizations and
dependencies among software
components
•Components include
–source code components
–binary code components
–executable components
Component Diagram

75. ComponentsDictionary
Spell-check
Synonyms
mymailer: Mailer
+Mailbox
+RoutingList
-MailQueue

76. Planner
Scheduler
GUI
Reservations
Update Component Diagram

77. •Shows the configuration of run-time
processing elements and the
software components, processes and
objects that live on them
•Deployment diagrams may be used
to show which components may run
on which nodes
Deployment Diagram

78. AdminServer:HostMachine
Joe’sMachine:PC
:Scheduler
reservations
:Planner
«database»
meetingsDB Deployment Diagram

79. Node1
Node2
«cluster»
x y
«cluster»
x y
«become»
«database»
w z Deployment Diagram (cont’d)

80. UML’s STRENGTHS
Defining UMLModeling with UML Analyzing UMLExamples
UML is a language which directs us to:
•Visualize
•Specify
•Plan
•Document
Organize,
Structure and
Communicate

81. UML’s STRENGTHS
Defining UMLModeling with UML Analyzing UMLExamples
Which compels us to be:
•More Precise
•More Complete
•Less Ambiguous
Its easy to read and if accepted would
be a language that everyone understood

82. UML’s WEAKNESSES
Defining UMLModeling with UML Analyzing UMLExamples
There is a big difference between:
Compelsand Ensures
•There is insufficient means
for test and verification
(For instance: there is no mean to specify relational tables)

83. Defining UML
Modeling with UML
Analyzing UML’s Strengths and
Weaknesses
•Describing the Modeling Process
•Defining the Syntax of UML
•Clarifying with Examples
SUMMARY

84. Booch, G. et al., The Unified Modeling
Language User Guide, Addison-Wesley,
Toronto, 1998
Roff, J.T., UML A Beginner’s Guide,
McGraw Hill/Osborn, Toronto, 2003
BIBLIOGRAPHY