View MODAF:OV-6c Operational Event-Trace Description View



The OV-6c Operational Event-Trace Description View is part of the MODAF Operational Viewpoint and one of the 47 MODAF views*.

Version & Date

Version 1.2.004.

* =  changed at 1.2.004

+ =  new at 1.2.004

The change history is derived from the definition of each MODAF view within the The MODAF Operational Viewpoint viewpoint defining document from

See MODAF Release History.


From The MODAF Operational Viewpoint p39:

The OV-6c Operational Event-Trace Description provides a time-ordered examination of the information exchanges between participating Operational Nodes as a result of a particular scenario. Each event-trace diagram will have an accompanying description that defines the particular scenario or situation.

Subject to Crown Copyright


From The MODAF Operational Viewpoint p39:

Operational Event-Trace Descriptions, sometimes called sequence diagrams, event scenarios or timing diagrams, allow the tracing of interactions between nodes in a scenario or critical sequence of events. The node interactions usually correspond to flows of information, but may optional describe flows of energy, materiel or people. The OV-6c, along with OV-6b, Operational State Transition Description, and OV-5, Operational Activity Model, specify the behaviour of nodes.

OV-6c is valuable for increasing the level of detail from the initial operational concepts, and can help define node interactions and operational threads. It can also help ensure that each participating node has the necessary information it needs at the right time in order to perform its assigned operational activity.

Subject to Crown Copyright


From The MODAF Operational Viewpoint p40:

OV-6c allows the tracing of interactions in a scenario or critical sequence of events and can be used by itself or in conjunction with OV-5, Operational Activity Model, and/or an OV-6b to describe the dynamic behaviour of nodes in a mission or operational thread.

MODAF does not generally endorse a specific modelling methodology, however in the case of OV- 6c, UML sequence diagrams seem the most appropriate. If UML cannot be used, an OV-6c may be developed using any modelling notation that supports the layout of timing and sequence of activities along with the information exchanges that occur between Nodes for a given scenario. Different scenarios will be depicted by separate diagrams.

Subject to Crown Copyright

Data Objects*

From The MODAF Operational Viewpoint p39:

The data in an OV-6c can include:


Full size:File:MODAF OV6c mm dataObjects.gif

Subject to Crown Copyright


From The MODAF Operational Viewpoint p39:

  • UML sequence diagram

Subject to Crown Copyright

Configuration History



Other Frameworks

See also:



Category:Framework -> View
Category:MODAF -> View



© 2010 Eclectica Systems Ltd.