(Notice to readers: This article has also been published to other blogs. The owner of this blog is the guide of the author and owns the copyright of this article.
If you need to repost, please private message the blogger. Please do not change the content and pictures yourself)
1 Summary of the full text
This article aims to provide users with a suggested document based on DoDAF's defense architecture demonstration method. The full text provides users with some basic introductions to DoDAF, as well as the comprehensive background needed to understand the DoDAF method, and focus on A comprehensive introduction was given to the pilot project.
This article is divided into 7 chapters. The first chapter is a summary of the full text. Introduce the overall situation of this article.
Chapter Two, What is DoDAF. In addition to introducing the basic concepts of DoDAF, it also provides some key knowledge points of DoDAF. Readers who have a certain understanding of DoDAF do not need to care about this chapter.
Chapter Three, what can we get. Focusing on the general value that DoDAF can provide to users, here is an introduction to some key background knowledge of DoDAF.
Chapter 4, how to use DodAF. Mainly introduce the reference process of using DoDAF for project modeling.
The fifth chapter is the implementation suggestions of the pilot project. Introducing the general suggestion process for the implementation of the pilot project is one of the focus of this article.
Chapter VI, case reference and interpretation. Introduce a DoDAF case project based on anti-submarine operations to help readers more intuitively understand what the pilot project might look like.
Chapter Seven, this article summarizes. A full-text summary of the content of this document.
This article tries to make some key content involved in DoDAF as much as possible , I hope that reading through this article can provide you with some useful value.
Demonstration case statement:
The relevant "scene" case demonstrations used in this document are based on the collection and sorting of public information on the Internet, combined with DoDAF Related methods and processes, models developed only for public demonstration purposes. However, the methods and processes referenced in this model are a summary of experience verified by actual projects.
2 What is DoDAF
The main points of this chapter
DoDAF is based on the top-level system of the Ministry of Defense. Structure, a defined set of architectural frameworks, used to standardize the design and use of national defense systems, and provide basic framework basis for structures, methods, tools, etc.
However, DoDAF is not just a framework for describing the national defense system structure, it actually carries more concepts, methodology, and technical content behind it-without this background knowledge, DoDAF is just a set of dry charts.
Therefore, when conducting DoDAF research, it is necessary to go beyond the conventions of the DoDAF framework itself, and explore more extensively the national defense system structure, national defense strategic concepts, operations (warfare, capabilities, equipment system demonstration methods, and related In order to truly grasp the essence of DoDAF and find the value of using DoDAF.
2.1 The definition of DoDAF and its development context
define a set of development, display and integration operations for the description, development, display, and integration of national defense architecture (war, business operation) The purpose is to ensure that the architecture description can be compared and correlated within the organization, including joint and multi-country. It is
developed by the US Undersecretary of Defense for Business Transformation working group of the Ministry of Defense. DoDAF defines a common approach for the description, representation, and integration of DoD system architecture and commercial operations and processes. The purpose of DoDAF is to ensure that the organization-wide architecture descriptions can be compared and correlated, including Different military %## areas. DoDAF explains this requirement by guiding how to describe the system architecture (to enable it to be evaluated and understood) and other architecture descriptions developed in accordance with the same guidelines. Operation (and decision makers can use DoDAF compliance The report compares alternative system architectures and manages the evolution of the existing system.
The creation and development of DoDAF is to support national defense strategy and capacity building. To be proficient in DoDAF requires a deep understanding of US military work* (war thinking Reform, and clarify the positioning, role and value of DoDAF in the construction of national defense, especially its relationship with other engineering methods, and proceed from the reality of China’s national defense, to gradually carry out practice and development in an organized and orderly manner. optimization.
The core positioning of DoDAF is to provide a standard framework definition for the core process and structure of the Ministry of Defense, promote the integration of the organization, process, and structure of the Ministry of Defense, and promote the reform and development of the Ministry of Defense.
Provide an integrated basic standard framework for the organization, process, and structure of the Ministry of Defense system.
Traditional decision-making and design methods form a chimney, lacking integrity and foresight, and determining and approving requirements are often used as response to specific threats or operations (war use). The conceived independent plan is not regarded as part of the cross-system top-level architecture, so there is a lack of coordination among various departments, and the decision-making lacks integrity and vision.
DODAF is based on the concept of top-level design from the beginning of the design. The top-level structure of the Ministry of Defense provides a standard framework and is committed to providing basic standards that integrate various organizations, processes and structures in the Ministry of Defense system.
Provides a standard framework for the core processes of the Ministry of Defense and supports unified The format description framework
manages the process and structure of the Ministry of Defense from the perspective of the top-level architecture, which can more effectively connect all the elements of the national defense process. DODAF aims to provide a standard framework for the core process of the Ministry of Defense to meet the requirements of the national defense department. …Description of the core process and architecture of the Ministry of Defense, providing concepts, guidelines and reference suggestions for development based on DoDAF. Participants in the core process of the Ministry of Defense first need to be guided by the process specification, and then use DoDAF as the framework standard Guide to develop corresponding architecture data, such as performing operations (scenario analysis, business process design, system architecture development, etc.). DoDAF cannot be used as the only guide for architecture development. Its core value is to provide standard or available data for all processes and architectures. The definition and relationship of the docking, ignoring this point, can easily lead to confusion about what DoDAF can do.
Supporting the componentization, servicing requirements and network-centric operations of the Ministry of Defense (the development of warfare architecture
faces limited resources Responding to the challenges of unpredictable multiple threats, after the Cold War, China
In joint cooperation (during war, forward-looking, flexible and rapid integration of various national defense resources to respond to various threats. More fine-grained operations (war organization division and more closely connected operations (war network, which provides The basis of the joint, in the development of operations (wartime, operations (war units can be flexibly deployed, so as to form various scales and levels of operations (war organization, and use network-centric warfare to achieve a wide range of operations (war unit connection, in order to finally achieve the operation)). (war purposes. country & ... component-based defense system, is a service of the country & ... anti-unit split up, an important way to flexible deployment, and network center for (combat system is connected as a basis (war unit, as ( The battle network’s information transmission capabilities, command and control capabilities, network security capabilities, equipment & system interoperability, damage recovery and redundancy capabilities form the key to the joint.
Support "capability-based" strategic decision-making and joint concepts, convergence capability and the ability to achieve
* Department of Defense from traditional to "threat-based" decision-making decision-making "ability", "threat-based" decision in determining and approval requirements are often as corresponds to a specific threat or as an independent (war using conceived The plan is not included in the cross-system top-level architecture consideration, so there is a lack of coordination between various departments, and the decision-making lacks foresight.
In the "capability-based" decision-making, the Ministry of Defense uses JCIDS as the core process. Strategy and action* (competence-based assessment (CBA) for combat tasks, comprehensively consider the support effects and gaps of various elements such as organization, process, architecture, and systems to achieve capabilities, form DOTMLPF change recommendations, and use them to guide the development of actual capabilities Improvement solutions. Among them, the equipment and system capacity improvement solutions are handled by the DAS process, which undertakes the full life cycle management from equipment selection, research and development, production to deployment, and the system engineering (SE) closely cooperates with the DAS process. The fundamental goal is to achieve capacity improvement.
2.2 DoDAF is a framework description of the architecture
DoDAF is a set of standardized framework definitions used to describe the national defense top-level architecture, and it actually reflects the structure of the national defense top-level architecture. From the perspective of the top-level structure, it supports the realization of the national defense strategy upwards and transforms it downward into a series of implementable projects to specifically promote the construction and development of the national defense system.
The role of DoDAF is to specifically describe the top-level architecture. The latest DoDAF 2.0 defines all aspects of the national defense architecture through a 7+1 perspective, and focuses on adding a capability perspective to support the JCIDS process in the national defense architecture.
Therefore, if you need to study DoDAF in depth, you must further comprehensively study the top-level architecture of the country and its related processes, technologies, systems, tools, etc. to truly gain insight into the connotation of DoDAF.
2.3 Introduction to the main points of
DoDAF 2.0 In order to support the new changes in the process and architecture of the Ministry of Defense, DoDAF 2.0 has expanded from the 4 perspectives of DoDAF 1.5 to 8 perspectives, forming new perspectives on capabilities, services and data, increasing project perspectives, and expanding technical standards perspectives. Standard perspective
DoDAF 2.0 focuses on the top-level architecture, serves the core decision-making process of the Ministry of Defense, and uses the Metamodel of the Ministry of Defense as the data organization form, changing from "architected product-centric" to "data-based "Center" emphasizes the collection, storage and use of data required for efficient decision-making. Architects and stakeholders can choose an architecture description form that "fits the goal" as needed to provide a visual architecture description.
Support the six core processes of the Ministry of Defense:
- Joint Capability Integration and Development System(JCIDS)
- Defense Acquisition System(DAS)
- Systems Engineering(SE)
- Planning, Programming, Budgeting, and Execution(PPBE)
- (Capabilities) Portfolio Management(PfM)
- Operations Planning
DoDAF 2.0 combines the new needs and practical experience of the Ministry of Defense, from a 3+1 perspective to a 7+1 perspective, resulting in a series of major changes, and perfecting the description of the top-level structure of the Ministry of Defense and its relationship with the federal government. The relationship between the top-level architecture. From the perspective of the key impact on the development of national defense architecture, the addition of an independent capability perspective is the biggest change in DoDAF 2.0, which supports JCIDS. Another more important change is to increase the service perspective, add a service layer between capabilities and the realization of capabilities, and regard various national and defense resources (organizations, equipment) as components, and realize each The rapid combination of class components to realize the ability.
To be continued...