DoDAF Architecting
- Overview: DoDAF Architecting
- DoDAF Architecture Design Process
- Capability Viewpoint (CV)
- Data and Information Viewpoint (DIV)
- Operational Viewpoints (OV)
- Systems Viewpoints (SV)
 
- AV-1 Overview and Summary
- AV-2 Integrated Dictionary
- Capability Viewpoint (CV)
- CV-1 Vision
- CV-2 Capability Taxonomy
- CV-3 Capability Phasing
- CV-4 Capability Dependencies
- CV-5 Cap to Org Development Mapping
- CV-6 Cap to Op Activity Mapping
- CV-7 Cap to Services Mapping
- Data and Information Viewpoint (DIV)
- DIV-1 Conceptual Data Model
- DIV-2 Logical Data Model
- DIV-3 Physical Data Model
- DoD Architecture Registry System
- DoDAF Meta Model (DM2)
- Enterprise Architecture
- Functional Architecture
- Operational Viewpoints (OV)
- OV-1 High Level Concept Graphic
- OV-2 Op Resource Flow Description
- OV-3 Op Resource Flow Matrix
- OV-4 Organizational Relationship Chart
- OV-5a Op Activity Decomposition Tree
- OV-5b Op Activity Model
- OV-6a Operational Rules Model
- OV-6b State Transition Description
- OV-6c Event-Trace Description
- Physical Architecture
- Project Viewpoints (PV)
- PV-1 Project Portfolio Relationship
- PV-2 Project Timelines
- PV-3 Project to Capability Mapping
- Reference Architecture (RA)
- Standards Viewpoint (StdV)
- StdV-1 Standards Profile
- StdV-2 Standards Forecast
- Services Viewpoint (SvcV)
- Systems Viewpoints (SV)
- SV-1 Systems Interface Description
- SV-2 Sys Resource Flow Description
- SV-3 Systems-Systems Matrix
- SV-4 Systems Functionality Description
- SV-5a Activity/Funct Traceability Matrix
- SV-5b Op Activity Traceability Matrix
- SV-6 System Resource Flow Matrix
- SV-7 Systems Measures Matrix
- SV-8 Systems Evolution Description
- SV-9 Systems Tech & Skills Forecast
- SV-10a Systems Rules Model
- SV-10b Systems Transition Description
- SV-10c Systems Trace Description
DoDAF Architecting
OV-6a Operational Rules Model
 

An OV-6a "Operational Rules Model" specifies operational or business rules that are constraints on the way that business is done in the enterprise. At a top-level, rules should at least embody the concepts of operations defined in OV-1 "High Level Operational Concept Graphic" and provide guidelines for the development and definition of more detailed rules and behavioral definitions that should occur later in the Architectural definition process.  

DoDAF Architecture Framework Version 2.02 - Page 154


The intended usage of the OV-6a includes:

 

At the mission-level, OV-6a may be based on business rules contained in doctrine, guidance, rules of engagement, etc. At lower levels, OV-6a describes the rules under which the architecture behave under specified conditions. Such rules can be expressed in a textual form. These rules are contrasted with the business or doctrinal standards themselves, which provide authoritative references and provenance for the rules (see StdV-1 Standards Profile). Operational Rules are statements that constrain some aspect of the mission or the architecture. Rules may be expressed in natural language (English) in one of two forms:

 

AcqTips:  
- The DoDAF descriptions in this website are very generic and are mostly taken from the DoDAF Architecture Framework website. Make sure you visit the actual website for the most update information and a more thorough explanation of each viewpoint.  
- DoDAF Version 1.0, although outdated, has some good examples on how to construct AV's, OV's, SV's and TV's.

AcqLinks and References:
- [1] DoDAF Architecture Framework Version 2.02
- DoD Architecture Framework Working Group Version 1.0, Volume 1: Definition and Guideline, 9 Feb 04 (Old Version)
- DoD Architecture Framework Version 1.0, Volume 2: Product Description, 9 Feb 04 (Old Version)
- Website: DoDAF Architecture Framework - DoD Deputy Chief Information Officer
- Website: Wikipedia - Department of Defense Architecture Framework
- Website: DoDAF Version 2.02 Journal



 

Click Here!

Sponsors

Click Here!