Why DoDAF Training? DoDAF 2.0 Certification: What is New? Current version is DoDAF 2.02
DoDAF 2.0 Certification (The Department of Defense Architecture Framework 2.02 is the evolution of DoDAF 1.5 and defines a new way to organize an enterprise architecture (EA) into complementary and consistent views, viewpoints and models.
Learn abut The DoDAF Architecture Framework Version 2.02
Department of Defense Architecture Framework Version 2.02, is the approved release of the DoDAF as of August 2010 including the DoDAF/DM2 2.01 to create DoDAF/DM2 2.02,
- DoDAF Conformance
- DoD Components
- Department. Conformance ensures that reuse of information, architecture artifacts, models, and viewpoints
- Meta Model
- Conformance in both the classified and unclassified communities
- DM2 concepts, associations, and attributes
- The architectural data transfer in accordance with the PES
- IDEAS Foundation Ontology
- DoDAF Viewpoints & Models
- DoDAF Models and Model Categories
- Levels of Architecture
- Architecture Interrogatives
- Architecture Modeling Primitives
- Details on Mapping to DM2
TONEX DoDAF Training Courses
|DoDAF 2.0 Training, Project-based Hands-on DoDAF Training Courses||3 Days|
|DoDAF 2.0 Workshop, DoDAF Training and Hands-on and Project Based (Advanced)||3 Days|
|DoDAF Training includes DoDAF 2.0 Certification Training covers the comprehensive framework and conceptual model enabling the development of architectures to facilitate the ability of Department of Defense (DoD) managers at all levels to make key decisions more effectively through organized information sharing across the Department, Joint Capability Areas (JCAs), Mission, Component, and Program boundaries.|
DoDAF Training: DoDAF 2.0 viewpoints including:
- All Viewpoint
- Capability Viewpoint
- Data and Information Viewpoint
- Operational Viewpoint
- Project Viewpoint
- Services Viewpoint
- Standards Viewpoint
- Systems Viewpoint
DoDAF 2 Background (Currently version 2.02)
DoDAF 2.0 also includes: DoDAF Meta-model (DM2), consisting of a Conceptual Data Model (CDM), Logical Data Model (LDM), and Physical Exchange Specification (PES) as an integral part of the architecture framework.
The DM2 replaces the Core Architecture Data Model (CADM) referenced in previous versions of DoDAF. Tonex also provide a comprehensive course in Joint Capabilities Integration and Development System (JCIDS).
DoDAF 2.0 serves as one of the principal pillars supporting the DoD Chief Information Officer (CIO) in his responsibilities for development and maintenance of architectures required under the Clinger-Cohen Act. DoDAF is prescribed for the use and development of Architectural Descriptions in the Department. It also provides extensive guidance on the development of architectures supporting the adoption and execution of Net-centric services within the Department.
DoD managers, as process owners, specify the requirements and control the development of architectures within their areas of authority and responsibility. They select an architect and an architecture development team to create the architecture in accordance with the requirements they define.
DoD Components are expected to conform to the DoDAF 2.0 developing architectures within the Department. DoDAF Conformance ensures reuse of information and that architecture artifacts, models, and viewpoints can be shared with common understanding.
DoDAF 2.0 focuses on architectural “data”, rather than on developing individual “products” as described in previous versions. In general, data can be collected, organized, and stored by a wide range of architecture tools developed by commercial sources. It is anticipated that these tools will adopt the DM2 PES for the exchange of architectural data.
DoDAF 2.0 provides a Data Capture Method for each data group of the DM2 to guide architects in collecting and organizing the necessary architectural data.
DoDAF 2.0 enables architectural content that is “Fit-for-Purpose” as an architectural description consistent with specific project or mission objectives. Because the techniques of architectural description can be applied at myriad levels of an enterprise, the purpose or use of an architectural description at each level will be different in content, structure, and level of detail. Tailoring the architectural description development to address specific, well-articulated, and understood purposes, will help ensure the necessary data is collected at the appropriate level of detail to support specific decisions or objectives.
DoDAF 2.0 Viewpoints and Models
DoDAF 2.0 has been designed to meet the specific business and operational needs of the DoD. It defines a way of representing an enterprise architecture that enables stakeholders to focus on specific areas of interests in the enterprise, while retaining sight of the big picture. To assist decision-makers, DoDAF provides the means of abstracting essential information from the underlying complexity and presenting it in a way that maintains coherence and consistency. One of the principal objectives is to present this information in a way that is understandable to the many stakeholder communities involved in developing, delivering, and sustaining capabilities in support of the stakeholder’s mission. It does so by dividing the problem space into manageable pieces, according to the stakeholder’s viewpoint, further defined as DoDAF-described Models.
Each viewpoint has a particular purpose, and usually presents one or combinations of the following:
- Broad summary information about the whole enterprise (e.g., high-level operational concepts).
- Narrowly focused information for a specialist purpose (e.g., system interface definitions).
- Information about how aspects of the enterprise are connected (e.g., how business or operational activities are supported by a system, or how program management brings together the different aspects of network enabled capability).
However, it should be emphasized that DoDAF is fundamentally about creating a coherent model of the enterprise to enable effective decision-making. The presentational aspects should not overemphasize the pictorial presentation at the expense of the underlying data.
DoDAF 2.0 organizes the DoDAF-described Models into the following viewpoints:
- The All Viewpoint describes the overarching aspects of architecture context that relate to all viewpoints.
- The Capability Viewpoint articulates the capability requirements, the delivery timing, and the deployed capability.
- The Data and Information Viewpoint articulates the data relationships and alignment structures in the architecture content for the capability and operational requirements, system engineering processes, and systems and services.
- The Operational Viewpoint includes the operational scenarios, activities, and requirements that support capabilities.
- The Project Viewpoint 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. An example is the Vcharts in Chapter 4 of the Defense Acquisition Guide.
- The Services Viewpoint is the design for solutions articulating the Performers, Activities, Services, and their Exchanges, providing for or supporting operational and capability functions.
- The Standards Viewpoint 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.
- The Systems Viewpoint, for Legacy support, is the design for solutions articulating the systems, their composition, interconnectivity, and context providing for or supporting operational and capability functions.