View DNDAF:OV-6c Operational Event-Trace Description Subview



OV-6c Operational Event-Trace Description Subview

Version & Date

1.6 See DNDAF Release History


The OV-6c subview is part of the DNDAF Operational View.

The Operational View-6c (OV-6c): Operational Event-Trace Description, sometimes called sequence diagrams, event scenarios, or timing diagrams, allow the tracing of a critical sequence of events.


The OV-6c sub-view is valuable for moving to the next level of detail from the initial operational processes. This sub-view helps define node interactions and operational threads. The OV-6c also helps ensure that each participating operational node has the necessary information it needs at the right time in order to perform its assigned operational activity.


Management needs to understand the governance elements that impact the architecture project. What are the “rules of engagement”? What constraints apply? Important characteristics of the architecture project are only discovered when its dynamic behaviours are defined and described. The dynamic behaviour concerns the timing and sequencing of events that capture the operational behaviour of a process.

Three types of models are needed to refine and extend the project architecture’s operational view to adequately describe the dynamic behaviour and performance characteristics of the architecture project. These three models are:

Software-based project architectures will typically use the suite of OV-6 sub-views to describe and define the pertinent operational rules. The OV-6a captures additional Concept of Operations information introduced by the Operational Process Model (OV-5b) and/or the Logical Data Model (OV-7).

At times, the Operational Process Model (OV-5b) requires more elaboration and specification. OV-6c provides the architect with additional options regarding the means to describe and specify dynamic behaviour of processes.



The Operational Event-Trace Description sub-view (OV-6c) provides a time-ordered examination of the operational processes between participating operational nodes as a result of a particular scenario. Each event-trace diagram should have an accompanying description that defines the particular scenario or situation. In summary, the OV-6c allows the tracing of actions in a scenario or critical sequence of events.

Detailed Description

The OV-6c allows the tracing of activities in a scenario or critical sequence of events. With time proceeding from the top of the diagram to the bottom, a specific diagram lays out the sequence of information exchanges that occur between operational nodes/roles (external and internal), operational processes, for a given scenario. Separate diagrams should depict different scenarios. OV-6c can be used by itself or in conjunction with an OV-6b to describe dynamic behaviour of operational processes.

Subview DADM Elements

The DADM entities and attributes provided below are the elements that this sub-view is responsible for creating:




Any graphical form where time-ordering can be defined:

  • UML Sequence Diagram



  • p71 Figure 3.13.1 in DND/CF Architecture Framework (DNDAF)  Volume 2: DND/CF Views and Sub-Views
  • p36 Figure 2.14.1 in DND/CF Architecture Framework (DNDAF) Volume 4: User Guide.


The OV-5a and OV-6b are the prerequisites for this sub-view:


See DNDAF Subview Dependencies




Other Frameworks

See also:


Category:Framework -> Specification
Category:Framework -> Subview



© 2010 Eclectica Systems Ltd.