The following table briefly describes the OV products and suggests an order in which to create them.
下面的表格简要地说明了OV产品，并建议了一个创建这些产品的顺序。
The Operational View (OV) focuses on the externally visible structure and behavior of the subject system.
运作视图(OV)着重于主题系统的表面上可见的结构和行为。
The Systems View (SV) describes how the OV is realized.
系统视图(SV)说明了OV是如何实现的。
The OV-2 identifies and models critical operational dependencies between operational nodes.
OV - 2确定并为运作节点之间的运作依赖建模。
The OV-5 clarifies roles, responsibilities, and order of execution with respect to accomplishing key mission objectives in the context of the operational enterprise.
OV - 5阐明了与完成运作企业环境中的关键任务目标有关的角色、责任，和执行顺序。
The OV-7 reflects the structure and flow of key information being used to achieve the functionality expressed in the Enterprise use Cases.
OV - 7反映了用于达到企业用例中所表达的功能的关键信息的结构和流。
The focus of the OV is on those requirements and capabilities that affect the mission.
OV的焦点是影响该任务的那些需求和功能。
The OV-4 models the relationships between organizational entities that affect the operational architecture of the enterprise and its systems.
OV-4 为影响到企业运作架构的组织实体及企业系统之间的关系建模。
The OV-5 is a graphical presentation of the externally visible behavior of the operational enterprise, represented by flows of activities allocated to component systems.
OV - 5是运作企业的外部可视行为的图形表示，由分配到组件系统的活动流表示。
The OV-3 emphasizes the logical and operational characteristics of the information exchanged within the architecture.
OV - 3强调架构中交换的信息的逻辑和运作特性。
OV-1 content is started first, but the OV-1 graphic cannot be completed until OV-2 is complete.
OV - 1的内容首先开始，但到OV - 2完成时才能完成OV - 1的图形。
Where this approach is warranted, the OV-6b is produced.
此处这个方法证明是有效的，生成ov - 6b。
Note: Some implementers have elected to create this diagram but show little, if any, mapping between the OV-4 and the remainder of the DoDAF views.
注意：一些实施者已经选择创建该图，但几乎没有显示出OV - 4和余下的dodaf视图之间的映射。
This latter approach has the additional advantage of guaranteeing consistency between OV-2, OV-3, and OV-6c, since they will all be derived from identical model information.
后一种方法拥有保证OV - 2、OV - 3，和OV - 6c之间的一致性的额外优势，因为它们将来源于同样的模型信息。
Specific organizational elements are likely candidates for the roles; i.e., instantiations of operational nodes in the interaction diagrams comprising the OV-6c (see below).
具体的组织要素可能作为候选角色，即组成OV - 6c(见下)的交互图中的运作节点的实例。
The OV-6a captures constraints upon the operational processes used to achieve mission results within the context of the operational enterprise and the subject system.
OV - 6 a获取对用于达到运作企业的环境和主题系统中的任务结果的运作过程的约束。
The OV-4 is represented by a freeform diagram in which organizational elements may be candidates for the instantiation of operational nodes in the OV-6c sequence diagrams.
OV - 4由自由形式的图表示，在该图中，组织要素可能作为OV - 6 c序列图中运作节点的实例的候选。
Wait until you begin to detail the use-case flows and scenarios and capture them in the OV-6c sequence diagrams (see below).
等到您开始详述用例流和场景并在OV - 6 c序列图(见下)中获得它们的时候。
The content of this product should be directly attributable to the IO Entities identified during construction of the OV-6c.
此产品的内容应该直接归因于ov - 6c构建过程中确定的io实体。
Figure 5: Sample OV-3 Information Exchange matrix.
图5：OV - 3信息交换矩阵示例。
The OV-3 can be generated automatically using the IBM Rational Systems Developer design and development tool by referencing the OV-6c content.
通过参考ov - 6c的内容，可以利用IBMRationalSystemsDeveloper设计和开发工具自动地生成OV - 3。
OV-5: Roles and responsibilities diagram.
OV - 5：角色和指责图。
Figure 3: OV-1 high-level graphic.
图3：OV - 1高层次图形。
Each IER's content represents an instantiation of an OV-6c IO Entity class (see below), where the attributes represent the data characteristics that the DoDAF requires.
每个IER的内容都表示OV - 6cIO实体类(见下)的实例，在此，属性表示DoDAF需要的数据特征。
OV-6a: Operational rules model.
OV - 6 a：运作规则模型。
OV-4: Command relationships chart.
OV - 4：命令关系图表。
OV-2: Operational node connectivity description.
OV - 2：运作节点连接描述。
OV-6b: Operation state transition description.
OV - 6 b：运作状态转换描述。
OV-3: Operational information exchange matrix.
OV - 3：运作信息交换矩阵。
OV-1: High-level operational concept graphic.
OV - 1：高级运作概念图。
应用推荐