Research on the Architecture of Shipborne UAV Target Indication Command and Control System based on DoDAF

The latest Department of Defense Architecture Framework (DoDAF) emphasizes the consistency of data, which requires to ensure that the models are related to each other and the data contained can be reused repeatedly. Therefore, a model relevance judgment principle is proposed. Based on DM2 related concepts, this principle determines whether there is an association relationship between models required for modeling according to the number of common data element types included and whether views can iterate with each other, so as to optimize modeling steps and find out the sequence of model generation. The relevance principle is applied to the development of shipborne UAV target command and control system architecture, and a visual description is made for organizational relations, resource interaction and combat activities.

I. Introduction

Department of Defense Architecture Framework (DoDAF) modeling is the most widely used architecture design method, which builds a complete architecture model through static description of target system attributes and dynamic description of system behavior [1]. The latest DoDAF2.02 version uses the "data as the center" development thought, replacing the original "product as the center" development thought [2]–[3]. For the new version, the US Army proposed the "six-step method", while domestic scholars also proposed the method for development of C⁴ISR system architecture designing method based on meta-model [4]. The existing modeling methods all propose that view models can iterate with each other, and the premise of iteration is that there is a certain correlation between the models. How to judge whether view models can be correlated with each other to achieve iteration is the defect of various methods. This paper presents existing DoDAF modeling principles while the model relevance judgment principle proposed [5], that is, the number of the same data element type is taken as the basis to judge whether the view-model can be associated. Based on this principle, it is possible to determine whether views can iterate over each other during modeling to figure out the sequence of view-model generation, and the development philosophy of "data-centric" can be used throughout the development process.