Introduction
By the name 'Timing Diagram,' one can easily relate to a diagram depicting the time or something similar. But in Software Engineering, they are specialized behavioral modeling diagrams used widely in object-oriented software design.
Source: tenor.com
Timing diagrams are part of UML. UML(Unified Modeling Language) is a modeling language that is most often used for software engineering but has extended its use to business processes and other project workflows. Talking about exact definition, “In UML, timing diagrams are interaction diagrams used to show interactions when the core logic of the diagram is to reason about time. The timing diagram focuses on the conditions changing within(or among) lifelines”.
Basic Elements of the Timing Diagram
The timing diagram depicts how an object underwent a change from one form to another with the passage of time. It consists of a graph or waves that represent the state of a lifeline at a specific point in time.
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."
Source: UML-diagrams
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.
Source: UML-diagrams
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.
Source: UML-diagrams
Also, read about V Model in Software Engineering