(Tell the readers: if you need to forward it, please private message bloggers. Please don't change the content and pictures yourself!)
1. Definition of DODAF
DoDAF adopts a standard method to describe the guidelines of "EA's data and relationship types", is a guide to express "the format and content of the standard set of EA models", and is a solution to complex systems (including human factors, such as actions). (Or [institution or personnel] type) guidance on structured issues;
DoDAF V2.02 is based on the transformation of entities (such as agencies) with the times, focusing on 6 types of stakeholders, 6 standard questions, 8 selectable viewpoints and 52 models, providing solutions for personnel, processes and technology integration It is a collection of (modeling) methods for integrated, structured, and deep-level problems.
The EA based on the DoDAF structure can reveal the current status of the team, outline the future blueprint of the team, and determine the development plan of the team, thereby laying the foundation for the team's visibility, control, harmony, rolling and continuous development. The ultimate goal of EA is to consolidate the foundation of team informatization and even modernization.
The EA based on the DoDAF architecture supports operational (or business) decision-making, joint capability integration and development decision-making, unified acquisition decision-making, portfolio investment (financing) management decision-making, system engineering decision-making, network-centric integration decision-making; supporting institutional reform (transformation), Planning and demonstration research, development roadmap development, business process reengineering, complex system design and development, and service-oriented solutions. 
Figure
12. The DoDAF concept
provides a top-level collection of concepts, guidelines, best practices and methods that promote the development of team architecture (EA), and supports the decision-making process of command, management, and competence domains.
Support the development of the team in the direction of network centralization (such as supporting networked operations), and support the development of service-oriented architecture (SOA).
Focusing on the architectural data that generates key decisions can ensure that architects provide decision makers with visual source information through views and models; it can promote the flexible development of views that conform to team culture and characteristics.
Create an EA that supports team management for architects, provide methods and recommend techniques.
3. The purpose and scope of DoDFA
rely on a set of common vocabulary similar to "common methods and language" to provide guidance for team structure (EA) development, EA information exchange and promotion of interoperability between EAs.
Large and complex entities require sophisticated information, systems, services and technologies to complete complex and joint missions. To this end, structured and repeatable evaluation and selection of investment methods are required, and new systems, deployment of new technologies, and the ability to provide new services are required to improve decision-making and management value and carry out effective transformation.
The DoDAF guidelines apply to the development, maintenance and use of EA; the basic structure of DoDAF supports unified splicing of EAs at the same level and unified linking of EAs at each level.
DoDAF can provide guidance for all aspects of the EA life cycle and is
the basis for continuous management and management of EA capabilities .
DoDAF supports the development of "Service Oriented Architecture (SOA)". 
Figure 2
Four. The core
8 viewpoints of DoDAF : panorama, capabilities, operations, systems, services, data and information, standards, and projects.
Figure 3 
Figure 4
5. The DoDAF framework
DoDAF, version 1.0 in 2003 rewrites the original C4ISR framework specification version 2.0, and divides the guidance, product description and supplementary information into 2 volumes and a manual (Desk Book). This version Extend the applicability of architecture principles and business to all mission areas, not limited to the scope of C4ISR. Version 1.5 in 2007 is a transitional version that reflects the state: & the Ministry of Defense towards network-centric warfare.
In 2009, version 2.0 emphasizes the data-centric architecture specification, which is relatively high in completeness. It is divided into three volumes: Manager's Guide, Architect's Guide and Developer's Guide. How are the contents of the eight viewpoints connected? Its practicality is also relatively high. It is used by the Ministry of National Defense and has steps to tell you how to do it. Although it is used for national defense, many companies in the United States are also using it. For the department: & team is the ability to work together, and for the enterprise, it is the ability to work together. For example, in the supply chain of an enterprise, how to coordinate and communicate externally is essentially the same. 
Figure 5 The
data-centric architecture results can be aggregated into an integrated country: & defense system data assets. Different users can filter the corresponding data range according to their specific needs, and use appropriate performance technology to display the data results. For example, through dashboards, statistical reports, and graphs, we can display national analysis data and development trends, and can use AI technology to analyze national defense architecture big data to identify new innovation needs. Design a reference architecture for certain types of scenarios for unified reference for decision makers, managers, architects, combatants, developers, etc. Provide basic data for equipment capability analysis and equipment portfolio planning for new capabilities and equipment demonstration personnel. 
Figure 6