The Unified Modeling Language (UML) has been the industry standard for visualizing, specifying, constructing, and documenting the artifacts of a software-intensive system. *1
The UML was originally motivated by the desire to standardize the disparate notational systems and approaches to software design developed by Grady Booch, Ivar Jacobson and James Rumbaugh who are researchers of Object-Oriented modeling and software engineering.
UML 1.0 was proposed in 1997.
UMK Ver.2.0 has 13 diagrams to address various aspect of system, 7 diagrams are for static structures of system, 6 diagrams are for dynamic behavior of system.
The users of UML do not need to use all of 13 diagrams, can choose and combine them according to their objective.
DiD Risk Monitor uses a state chart diagram for modeling the actor’s dynamic behaviors.
The example of state chart Diagram is here.
The state chart diagram is an object-based variant of Harel state chart.*2
DiD Risk Monitor also uses a sequence diagram for describing the interaction among actors.
A sequence diagram is an interaction diagram that emphasizes the time-ordering of messages. A sequence diagram shows a set of roles and the messages sent and received by the instances playing the roles.
The example of the sequence diagram is here.
*1: Grady Booth, James Rumbaugh and Ivan Jacobson, The Unified Modeling Language User Guide Second Edition, Addison Wesley Professional, 2005
*2: D. Harel, Statecharts: A visual formalism for complex systems. Science of Computer Programming, 8(3):231–274, June 2002.