Includes implementation principles and guidelines for creating and maintaining Enterprise Architectures. Alignment with the reference models ensures that important elements of the FEA are described in a common and consistent way. Serves as the basis for enterprise architecture maturity assessments. Compliance with the EAAF ensures that enterprise architectures are advanced and appropriately developed to improve the performance of information resource management and IT investment decision making. These key support processes are designed to provide uniform, mandated, processes in critical decision-making areas, supplemented by individual agency operations, defined by Architectural Descriptions tailored to support those decisions-making requirements. Joint Capability Integration and Development System The primary objective of the JCIDS process is to ensure warfighters receive the capabilities required to execute their assigned missions successfully.
|Published (Last):||6 September 2016|
|PDF File Size:||6.6 Mb|
|ePub File Size:||13.45 Mb|
|Price:||Free* [*Free Regsitration Required]|
In addition, DoDAF 2. It addressed the Deputy Secretary of Defense directive that a DoD-wide effort be undertaken to define and develop a better means and process for ensuring that C4ISR capabilities were interoperable and met the needs of the warfighter.
It broadened the applicability of architecture tenets and practices to all Mission Areas rather than just the C4ISR community. This document addressed usage, integrated architectures, DoD and Federal policies, value of architectures, architecture measures, DoD decision support processes, development techniques, analytical techniques, and the CADM v1. In April the Version 1. The repository is defined by the common database schema Core Architecture Data Model 2. The developing system must not only meet its internal data needs but also those of the operational framework into which it is set.
The Capability Models describe capability taxonomy and capability evolution. A capability thread would equate to the specific activities, rules, and systems that are linked to that particular capability.
What outcomes are expected to be achieved by a particular capability or set of capabilities? What services are required to support a capability? What is the functional scope and organizational span of a capability or set of capabilities? What is our current set of capabilities that we are managing as part of a portfolio? Capabilities are described by Threads.
Threads are described by Activities executed in serial or parallel. Activities are grouped into Mission Areas. Activities define operations for an Architecture. Architectures are organized by mission areas. Architectures provide proper resourcing of capabilities required by the Mission or Course of Action. Version 1. Only a subset of the full DoDAF viewset is usually created for each system development. The figure represents the information that links the operational view, systems and services view, and technical standards view.
The three views and their interrelationships — driven by common architecture data elements — provide the basis for deriving measures such as interoperability or performance, and for measuring the impact of the values of these metrics on operational mission and task effectiveness.
The OV provides textual and graphical representations of operational nodes and elements, assigned tasks and activities, and information flows between nodes. It defines the type of information exchanged, the frequency of exchanges, the tasks and activities supported by these exchanges and the nature of the exchanges. OV-2 Operational Node Connectivity Description Operational nodes, activities performed at each node, and connectivities and information flow between nodes.
OV-3 Operational Information Exchange Matrix Information exchanged between nodes and the relevant attributes of that exchange such as media, quality, quantity, and the level of interoperability required.
OV-4 Organizational Relationships Chart Command, control, coordination, and other relationships among organizations. In addition, overlays can show cost, performing nodes, or other pertinent information. OV-6a Operational Rules Model One of the three products used to describe operational activity sequence and timing that identifies the business rules that constrain the operation.
OV-6b Operational State Transition Description One of the three products used to describe operational activity sequence and timing that identifies responses of a business process to events. OV-6c Operational Event-Trace Description One of the three products used to describe operational activity sequence and timing that traces the actions in a scenario or critical sequence of events.
Systems and services view[ edit ] Systems and services view SV is a set of graphical and textual products that describe systems and services and interconnections providing for, or supporting, DoD functions. SV products focus on specific physical systems with specific physical geographical locations. The relationship between architecture data elements across the SV to the OV can be exemplified as systems are procured and fielded to support organizations and their operations.
SV-1 also identifies the interfaces between systems and systems nodes. SV-2 documents the kinds of communications media that support the systems and implements their interfaces as described in SV Thus, SV-2 shows the communications details of SV-1 interfaces that automate aspects of the needlines represented in OV Although there is a correlation between OV-5 or business-process hierarchies and the system functional hierarchy of SV-4a, it need not be a one-to-one mapping, hence, the need for the Operational Activity to Systems Function Traceability Matrix SV-5a , which provides that mapping.
This product focuses on automated information exchanges from OV-3 that are implemented in systems. Non-automated information exchanges, such as verbal orders, are captured in the OV products only. It specifies the current performance parameters of each system, interface, or system function, and the expected or required performance parameters at specified times in the future.
Performance parameters include all technical performance characteristics of systems for which requirements can be developed and specification defined. Generally, the timeline milestones are critical for a successful understanding of the evolution timeline. Expected supporting technologies are those that can be reasonably forecast given the current state of technology and expected improvements.
New technologies should be tied to specific time periods, which can correlate against the time periods used in SV-8 milestones. The diagram basically represents the sets of events to which the systems in the architecture will respond by taking an action to move to a new state as a function of its current state. Each transition specifies an event and an action. Each event-trace diagram should have an accompanying description that defines the particular scenario or situation.
SVc in the Systems and Services View may reflect system-specific aspects or refinements of critical sequences of events described in the Operational View. SV Physical Schema One of the architecture products closest to actual system design in the Framework. The product defines the structure of the various kinds of system data that are utilized by the systems in the architecture. Technical standards view[ edit ] Technical standards view TV products define technical standards, implementation conventions, business rules and criteria that govern the architecture.
StdV-2 Technical Standards Forecast - Description of emerging standards that are expected to apply to the given architecture, within an appropriate set of timeframes. Version 2. All Viewpoint AV Describes the overarching aspects of architecture context that relate to all viewpoints. Articulates the capability requirements, the delivery timing, and the deployed capability.
Articulates the data relationships and alignment structures in the architecture content for the capability and operational requirements, system engineering processes, and systems and services.
Operational Viewpoint OV Includes the operational scenarios, activities, and requirements that support capabilities. Describes the relationships between operational and capability requirements and the various projects being implemented.
The Project Viewpoint also details dependencies among capability and operational requirements, system engineering processes, systems design, and services design within the Defense Acquisition System process. Presents the design for solutions articulating the Performers, Activities, Services, and their Exchanges, providing for or supporting operational and capability functions.
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 support , the design for solutions articulating the systems, their composition, interconnectivity, and context providing for or supporting operational and capability functions. 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. Note that Systems are made up of Materiel e. Node is a complex, logical concept that is represented with more concrete concepts. AV-2 Integrated Dictionary An architectural data repository with definitions of all terms used throughout Capability Viewpoint CV [ edit ] CV-1 Vision Addresses the enterprise concerns associated with the overall vision for transformational endeavours and thus defines the strategic context for a group of capabilities.
The purpose of the CV-1 is to provide a strategic context for the capabilities described in the Architecture Description. CV-2 Capability Taxonomy Captures capability taxonomies. The model presents a hierarchy of capabilities. These capabilities may be presented in the context of a timeline. The CV-2 specifies all the capabilities that are referenced throughout one or more architectures. CV-3 Capability Phasing The planned achievement of capability at different points in time or during specific periods of time.
The CV-3 shows the capability phasing in terms of the activities, conditions, desired effects, rules complied with, resource consumption and production, and measures, without regard to the performer and location solutions CV-4 Capability Dependencies The dependencies between planned capabilities and the definition of logical groupings of capabilities. CV-5 Capability to Organizational Development Mapping The fulfillment of capability requirements shows the planned capability deployment and interconnection for a particular Capability Phase.
The CV-5 shows the planned solution for the phase in terms of performers and locations and their associated concepts. CV-6 Capability to Operational Activities Mapping A mapping between the capabilities required and the operational activities that those capabilities support. CV-7 Capability to Services Mapping A mapping between the capabilities and the services that these capabilities enable.
OV-3 Operational Resource Flow Matrix A description of the resources exchanged and the relevant attributes of the exchanges. OV-4 Organizational Relationships Chart The organizational context, role or other relationships among organizations. OV-5a Operational Activity Decomposition Tree The capabilities and activities operational activities organized in a hierarchal structure. OV-5b Operational Activity Model The context of capabilities and activities operational activities and their relationships among activities, inputs, and outputs; Additional data can show cost, performers or other pertinent information.
It identifies business rules that constrain operations. OV-6b State Transition Description One of three models used to describe operational activity activity. It identifies business process activity responses to events usually, very short activities. It traces actions in a scenario or sequence of events. Project Viewpoint PV [ edit ] PV-1 Project Portfolio Relationships It describes the dependency relationships between the organizations and projects and the organizational structures needed to manage a portfolio of projects.
PV-2 Project Timelines A timeline perspective on programs or projects, with the key milestones and interdependencies. PV-3 Project to Capability Mapping A mapping of programs and projects to capabilities to show how the specific projects and program elements help to achieve a capability. Services Viewpoint SvcV [ edit ] The identification of services, service items, and their interconnections. It can be designed to show relationships of interest, e. SvcV-4 Services Functionality Description The functions performed by services and the service data flows among service functions activities.
SvcV-5 Operational Activity to Services Traceability Matrix A mapping of services activities back to operational activities activities. SvcV-6 Services Resource Flow Matrix It provides details of service Resource Flow elements being exchanged between services and the attributes of that exchange.
SvcV-8 Services Evolution Description The planned incremental steps toward migrating a suite of services to a more efficient suite or toward evolving current services to a future implementation. It identifies constraints that are imposed on systems functionality due to some aspect of system design or implementation.
It identifies responses of services to events.
Department of Defense Architecture Framework