Timing Diagrams

 Timing diagrams are a type of interaction diagram.

 Their purpose is to show how the states of an element or elements change over
time and how events change those states.
They have one or more lifelines, one or more objects (or other UML classifier), two or
more states, messages, and so forth.

Timing diagrams have some major components they are explained

below:
Lifeline
Lifeline depicts an entity( it represents only one entity), which is part of
the interaction. It represents the classifier's name or the instance it
portrays.
A lifeline can be placed within a diagram frame or "swimlane."

State or Condition Timeline

These are continuous timelines. These are used in scenarios where
entities undergo constant state changes, such as temperature or
density. The condition and state timelines are used to represent the
cooperation of attributes and classifier states.
 Source: UML-diagrams
Duration Constraint
It is an interval constraint that refers to a duration interval. Duration
interval is duration to determine whether the given condition is satisfied
or not. The semantic of a duration constraint is inherited from a normal
constraint(if the constraint is violated, trace becomes negative, and the
system fails).
Duration constraint is depicted in the diagram below with the construct it
constrains.

Source: UML-diagrams
Time Constraint
Time constraint is an interval constraint that refers to a time interval. It is
a time expression that depicts if the constraint is satisfied or not. The
semantic of a time constraint is inherited from a normal constraint(if the
constraint is violated, trace becomes negative, and the system fails).
Time constraint is shown between a time interval and the construct it
constrains.
Destruction Constraint
Destruction constraint is a message occurrence representing the
destruction of the instance described by the lifeline. No other occurrence
can appear after the destruction event of a given lifeline.
Note: Destruction may result in the subsequent destruction of other
objects that the parent object owns by composition.
Timing diagrams are used to explore the behaviors
of objects throughout a given period of time. UML
timing diagrams are used to detail interactions
based on time. With Timing Diagrams you'll
describe when an event occurs, how long it takes
for other participants to react and how long
they'll take to complete an interaction. UML
timing diagrams are used to display the change in
state or value of one or more elements over time.
It can also show the interaction between timed
events and the time and duration constraints that
govern them.

Here is an example of UML timing diagram:

Here is some things to retain:

- IT Developer and IT analyst there are 2
resources. You can see their states over time and
how the state of one can influence the state of
the other.
- You can add time constraints (for instance
where the brown line is drawn).
- You can draw an arrow to show the event which
cause the other resource to switch their state
(For instance between A and B).