Department of Defense Architecture Framework: Difference between revisions

Revision as of 09:51, 16 April 2025

Latest revision as of 14:06, 9 August 2025

Line 58:

<ref name="Dodaf2Capability">{{cite web|title=DODAF 2.0 Capability Viewpoint|url=https://dodcio.defense.gov/Library/DoD-Architecture-Framework/dodaf20_capability/}}</ref>

The Mission or Course of Action is described by a [[Concept of operations|Concept of Operations]] (CONOPS), and is organized by Capabilities.

* Capabilities are described by Threads.

* Threads are described by Activities executed in serial or parallel.

Line 158:

: Renamed from Technical Standards View. Articulates the applicable operational, business, technical, and industry policies, standards, guidance, constraints, and forecasts that apply to capability and operational requirements, system engineering processes, and systems and services.

; Systems Viewpoint (SV)

: Articulates, for [[legacy system|legacy support]], the design for solutions articulating the systems, their composition, interconnectivity, and context providing for or supporting operational and capability functions. Note, ''System'' has changed in DoDAF V2.0 from DoDAF V1.5: System is not just [[computer hardware]] and computer software. System is now defined in the general sense of an assemblage of components - machine, human - that perform activities (since they are subtypes of Performer) and are interacting or interdependent. This could be anything, i.e., anything from small pieces of equipment that have interacting or interdependent elements, to Family of Systems (FoS) and System of Systems (SoS). Note that Systems are made up of Materiel (e.g., equipment, aircraft, and vessels) and Personnel Types.

The architectures for DoDAF V1.0 and DoDAF V1.5 may continue to be used. When appropriate (usually indicated by policy or by the decision-maker), DoDAF V1.0 and V1.5 architectures will need to update their architecture. When pre-DoDAF V2.0 architecture is compared with DoDAF V2.0 architecture, concept differences (such as Node) must be defined or explained for the newer architecture. In regard to DoDAF V1.5 products, they have been transformed into parts of the DoDAF V2.0 models. In most cases, the DoDAF V2.0 Meta-model supports the DoDAF V1.5 data concepts, with one notable exception: Node. Node is a complex, logical concept that is represented with more concrete concepts.

Line 242:

:The planned incremental steps toward migrating a suite of services to a more efficient suite or toward evolving current services to a future implementation.

;SvcV-9 Services Technology & Skills Forecast

:The [[emerging technologies]], software/hardware products, and skills that are expected to be available in a given set of time frames and that will affect future service development.

;SvcV-10a Services Rules Model

:One of three models used to describe service functionality. It identifies constraints that are imposed on systems functionality due to some aspect of system design or implementation.