The document provides an overview of Unified Modeling Language (UML). It discusses that UML is a standard modeling language used to visualize, specify and document artifacts of a software system. It then summarizes the history and evolution of UML from its origins combining different modeling approaches in the 1980s-1990s to the current version. The document also lists and briefly describes the main UML diagram types including class, use case, activity, sequence, collaboration, state chart, component and deployment diagrams. For each diagram type, it highlights the key elements and purpose.

1. What is Unified Modeling
Language (UML)?
 The UML is a graphical / standard
language for visualizing,
specifying, constructing &
documenting the artifacts of a
software system.

2. History of UML
 1980 – 1990  Many different
methodologies
1. Booch method by Grady Booch
2. Object Modeling Technique (OMT) by Jim Rumbaugh
3. Object Oriented Software Engineering (OOSE) by Ivar
Jacobson
 Each method had its strengths &
weaknesses.
1. Booch was great in design
2. OMT & OOSE were great in analysis

3. History of UML
UML 1.0 (January 1997)
UML 1.1 (November 1997)
UML 1.3 (Current Minor revision 1999)
UML 1.4 (Planned Minor revision 2000)
UML 2.0 (Planned Major revision 2004)

4. UML Concepts
 UML can be used to support your
entire life cycle.
1. The interaction of your application with the outside
world (use case diagram)
2. Visualize object interaction (sequence &
collaboration diagrams)
3. The structure of your system (class diagram)
4. View the system architecture by looking at the
defined package.
5. The components in your system (component
diagram)

5. What are Diagrams ?
 Graphical presentation of model
elements.
 A diagram is a graphical means to view
a system’s parts

6. UML Diagrams
 8 diagrams
 You will model the following 5 diagrams only:
1. Use case diagram
2. Activity diagram
3. Sequence diagram
4. Collaboration diagram
5. Class diagram
 The other UML diagrams that can be modeled in
Rose are:
1. State chart diagram
2. Component diagram
3. Deployment diagram
Interaction
diagram

7. Behavior Diagram
 Sequence diagram
 Collaboration diagram
 State chart diagram
 Activity diagram
behavior
diagram

8. UML Diagrams
1. Class diagram
2. Use case diagram
3. Activity diagram
4. Sequence diagram
5. Collaboration diagram
6. State chart diagram
7. Component diagram
8. Deployment diagram

9. 1. Class diagram
 Class  a set of objects that share the
same attributes, operations & relationships.
 It represented by a compartmentalized
rectangle.
 It shows the structure of your software.
 3 compartments
1. Top
2. Middle
3. Bottom

10. 1. Class diagram
1. Top  shows class name
2. Middle  shows class attributes
3. Bottom  shows class operation

11. 1. Class diagram
1. Attributes  defines the characteristics or
structure of a class.
 displayed in the middle of the
compartmentalized rectangle.
Attributes

12. 1. Class diagram
2. Operation  the service provided by the class.
 displayed in the bottom of the
compartmentalized rectangle.
Operations

13. 2.Use case diagram
 It shows a set of use cases and actors and
their relationships.
 Address the static view of a system.
 Actor  user (or) someone / something
outside the system that interacts with the
system (it must be a noun) & it is
represented by a stickman.
……contd

14. 2.Use case diagram
 Use case  a sequences of actions (it must be
a verb) & it is represented by an oval.
 Relationship illustrates a connection among
model elements.
Unidirectional Bi-directional
 It is created to visualize the interaction of your
system with the outside world.
 (e.g.) ATM
……contd

15. 2. Use case diagram (ATM)
CASH
DISPENSER
PRINTER
CHANGE PIN
WITHDRAW
CHECK BALANCE
LOGIN
CUSTOMER

16. 2. Use case diagram (Pay roll)
 Actors  employee & account
 Use case  count leave, disburse
salary, check loans, calculate PF,
prepare IT returns, calculate HRA &
check salary

17. Customer
Calculate PF
Check loans
Disburse salary
Count leave
Prepare IT returns
Check salary
Calculate HRA

18. 3.Activity Diagram
 It shows the flow of events with our
system & what is going on inside a use
case.
 We draw the activity diagram for each
& every use case.
 Login (use case) – (e.g.) ATM
 It is showing flow of control from
activity to activity.

19. 3.Activity Diagram
 Activity  it represents the performance of a
task within the workflow.
 Activity is represented by a lozenge
(horizontal top and bottom with convex sides)
 Start state shows the beginning of a workflow
on an activity diagram.
 There is only one start state.

20. 3.Activity Diagram
 A start state is represented by a solid
circle.
 An end state represents a final or
terminal state on an activity diagram.
 A end state is represented by a bull’s
eye.

21. 3.Activity Diagram
 A state transition shows what activity
follows after another.
 It is represented by a solid line with an
arrow.

22. 3.Activity Diagram
 A decision is a point in an activity diagram
where guard conditions are used to indicate
different possible transitions.
 It is represented by a diamond.
 Guard conditions control the transition of a
set of alternate transitions that follows after
the activity has been completed.

23. 3.Activity Diagram
AND
Joint
Synchronization bar

24. 3.Activity Diagram
 A synchronization bar allows you to
show concurrent threads in a work flow
of a use case.
 It represented by a thick horizontal or
vertical line.

25. 3.Activity Diagram – Login Use case
Customer Enters
the login details
System retrives
the details
System validates
the customer
System welcomes
the customer
System prompts to
reenter
[ True ]
[ False ]

26. 4.Sequence Diagram
 It shows step by step what must happen
to accomplish a piece of functionality
provided by the system.
 It has 2Ds.
1. Vertical dimensions  represents time
2. Horizontal dimensions  represents
different objects.
 Vertical line is called the object’s life line.

27. 4.Sequence Diagram
 Life line  the existence object at a
particular time.
 Objects are shown at the top.
 The object role is shown as a vertical
dashed line, the life line.

28. 4.Sequence Diagram
 A message is the communication between 2
objects that triggers an event.
 It is represented by a labeled arrow.
 Each message is represented by an arrow
between the life lines of 2 objects.

29. 4.Sequence Diagram
 A focus of control shows the period of
time during which an object is
performing an action, either directly or
through a subordinate procedure.
 It represented by a tall, thin rectangle.

30. 4.Sequence Diagram – login
success
: Customer
: Customer : LoginForm
: LoginForm : LoginController
: LoginController : CustomerInfo
: CustomerInfo
Enter Login Detail...
Submit( )
Validate( )
getLoginDetails( )

31. 5.Collaboration Diagram
 It displays objects and their links to one
other.
 It is also known as an interaction diagram.

32. 5.Collaboration Diagram
 It is made up of the following basic
elements :
1. Actors
2. Objects
3. Links
4. Messages

33. 5.Collaboration Diagram
1. Actors  user
2. Objects  data + logic / the representation
of some real world entity.
3. Links  a pathway for communication
between objects.
 represented by a solid line
between 2 objects
4. Messages  the communication between
objects that triggers an event.
 represented by a labeled arrow
above
the link.

34. 5.Collaboration Diagram –
Login use case
: Customer
: LoginForm
: LoginController
: CustomerInfo
1: Enter Login Details( )
2: Submit( )
3: Validate( )
4: getLoginDetails( )

35. 6. State Chart Diagram
 It shows the sequence of states.
 A state is represented as a rounded box,
which may contain one or more
compartments.
 Name compartment  holds the name of
the state.
 Internal transition compartment  list of
actions / activities
 Start & end states

36. 7.Component Diagram
 It shows relationship between the
components in the system.
 A component may be a software
component [for (e.g.) a.h file in C++
(or) a .java file in Java], a run time
component [for (e.g.) a.DLL file]

37. 8. Deployment Diagram
 It shows the configuration of run time
processing elements & the software
components, processes & objects that
live in them.
 It shows the nodes in the system & the
connections between them.

38. Thank You!