2017
DOI: 10.1109/access.2017.2739922
|View full text |Cite
|
Sign up to set email alerts
|

Achieving Data Interoperability of Communication Interfaces for Combat System Engineering

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

1
17
0

Year Published

2018
2018
2022
2022

Publication Types

Select...
7

Relationship

3
4

Authors

Journals

citations
Cited by 11 publications
(18 citation statements)
references
References 25 publications
1
17
0
Order By: Relevance
“…However, all of these models focus on the exchange of information between systems and potential factors that could impact this exchange. Seo, Park, and Lee propose an interoperability verification and validation tool set for combat systems; however, this tool set focuses on information exchanges between systems . They go as far as to limit the definition of interoperability for their work to: “the ability of two or more system components to exchange information via the communication interfaces.” The manual for the Joint Capability Integration and Development System (JCIDS) narrowly focuses interoperability on the Net‐Centric KPP that describes a system's ability to enter and operate within the DoD networks .…”
Section: Literature Reviewmentioning
confidence: 99%
See 1 more Smart Citation
“…However, all of these models focus on the exchange of information between systems and potential factors that could impact this exchange. Seo, Park, and Lee propose an interoperability verification and validation tool set for combat systems; however, this tool set focuses on information exchanges between systems . They go as far as to limit the definition of interoperability for their work to: “the ability of two or more system components to exchange information via the communication interfaces.” The manual for the Joint Capability Integration and Development System (JCIDS) narrowly focuses interoperability on the Net‐Centric KPP that describes a system's ability to enter and operate within the DoD networks .…”
Section: Literature Reviewmentioning
confidence: 99%
“…Seo, Park, and Lee propose an interoperability verification and validation tool set for combat systems; however, this tool set focuses on information exchanges between systems . They go as far as to limit the definition of interoperability for their work to: “the ability of two or more system components to exchange information via the communication interfaces.” The manual for the Joint Capability Integration and Development System (JCIDS) narrowly focuses interoperability on the Net‐Centric KPP that describes a system's ability to enter and operate within the DoD networks . It is sufficient to say that the DoD's focus on information flows to define interoperability neglects to consider other aspects of interoperability like physical connections or shared resources.…”
Section: Literature Reviewmentioning
confidence: 99%
“…In this respect, the DSME has carried out several tests to resolve interface faults using the proposed method and software at the design phase as well as the integration phase. More detailed descriptions for this PIP were informed in our previous work [12]. Table 5, the proposed modeling and software have been utilized for nine shipboard tests over the last three years.…”
Section: Applicationmentioning
confidence: 99%
“…In order to transfer sensitive information, a sending system encodes interface data (i.e., messages) so only authorized receivers can understand [11]. The encoding rules contain what payloads (i.e., fields in this study) are structured in a message or how each field is logically converted, which are described in the interface protocols [12]. Because the protocols including the structural and logical rules are diverse and complicated, they should be preferentially explored for overcoming the interface faults.…”
Section: Introductionmentioning
confidence: 99%
“…Then, the engineer interacts with the two systems under standardized architectures such as high-level architecture (HLA) or test and training enabling architecture [9,10]. This is a typical approach for system of systems (SoS) development, which supports the high reality of component systems and flexibility in changing them [11,12].…”
Section: Introductionmentioning
confidence: 99%