View MODAF:OV-1a High-Level Operational Concept Graphic View



The OV-1a High Level Operational Concept Graphic 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 p4:

The OV-1a provides a graphical view of what the architecture is addressing and an idea of the players and operations involved. Its main use is to aid human communication, and it is intended for presentation to high-level decision makers.

Subject to Crown Copyright


From The MODAF Operational Viewpoint p4:

The OV-1a provides a graphical, scenario-based, description of a mission or class of mission could fulfil a business objective. It shows the main nodes (see the definition in OV-2, Operational Node Relationship Description) and interesting or unique aspects of operations. It describes the interactions between the subject architecture and its environment (including external systems), in order to convey the right amount of information to stakeholders. Its main utility is to communicate the purpose of the architecture to non-technical, high-level decision makers.

Unlike an OV-2, an OV-1a may show elements of the solution (physical) architecture – in other words, OV-1a is not strictly speaking a logical view.

Subject to Crown Copyright


From The MODAF Operational Viewpoint p5:

Each operational view describes one or more Enterprise Phases.

An OV-1a depicts the mission or domain covered by the architecture. In simple terms, an OV-1a will communicate the purpose of architecture is about and provide an idea of the players and operations involved.

The OV-1a provides a graphical executive summary of the architectural endeavour, which describes the interactions between the subject architecture and its environment, and between the architecture and external systems. A textual description accompanying the graphic is essential, with labels on the graphic and a detailed description in the OV-1b.

Graphics alone are not sufficient for capturing the necessary architecture data.


The content of an OV-1a depends on the scope and intent of the architecture, but in general it describes the missions, high-level operations, organisations, and geographical distribution of assets. It will provide an overview of the operational concept (what happens, who does what, in what order, to accomplish what goal) and highlight interactions to the environment and other external systems. The content should, however, reflect the executive summary level of the OV-1a, as the other OVs provide the detail of the interactions and sequencing.


Subject to Crown Copyright

Data Objects

From The MODAF Operational Viewpoint p4:

An OV-1a is typically just a graphic, but MODAF allows each symbol in the graphic to be traced back to elements and relationships in the M3. The data to be included in an OV-1a can be any business objects of interest, including:*

Subject to Crown Copyright


From The MODAF Operational Viewpoint p4:

  • Graphic
  • Structured graphic
  • UML class diagram (context diagram)
  • UML use case

Subject to Crown Copyright

From The MODAF Operational Viewpoint p5:

OV-1a is the most general of the architectural views and the most flexible in format. Because the format is freeform and variable, no template is shown for this view. An OV-1a product will usually, however, consists of graphics and/or text presented in a form that best communicates the idea of the architecture to the stakeholders.

Subject to Crown Copyright

Configuration History


One of the big changes in 1.2.004 is the ability to describe not just information flows but energy, materiel and people flows in both the operational viewpoint and the system viewpoint (the solution that realises the logical or implementation-free definition). This doesn’t, however, get reflected in the view definition because it only recognises information flows - see Information Exchange.

The Needline that connects a pair of operational nodes is defined as a bundle of information flows and therefore can’t be used to represent materiel, energy or people flows. It would make far more sense if Needline were defined to represent a need for ... information, energy, materiel or people.

Other Frameworks

See also:


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



© 2010 Eclectica Systems Ltd.