2013
DOI: 10.1002/j.2334-5837.2013.tb03083.x
|View full text |Cite
|
Sign up to set email alerts
|

6.5.1 I5: A Model‐Based Framework for Architecting System‐of‐Systems Interoperability, Interconnectivity, Interfacing, Integration, and Interaction

Abstract: We present I 5 -Interoperability, Interconnectivity, Interfacing, Integration, and Interactiona Model-Based Framework for Architecting Systems-of-Systems. Interoperability programs deliver end-to-end cooperation and collaboration capabilities and services among organizations, users, systems, and infrastructures, on top of a set of existing systems. Each system has its own programmatic and technical constraints and issues. System-level stakeholders usually prefer core functionality over integration, and expect … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
15
0

Year Published

2013
2013
2024
2024

Publication Types

Select...
7
1

Relationship

2
6

Authors

Journals

citations
Cited by 19 publications
(15 citation statements)
references
References 18 publications
0
15
0
Order By: Relevance
“…A majority of the literature focuses on this aspect of interoperability and the ability to model information flows between systems or components of systems . Mordecai and Dori expand beyond this definition slightly as they discuss information exchanges and payloads but they focus on model‐based architecture for information flows . Fry and DeLaurentis discuss interoperability in terms of openness and accessibility to information flows and methods for modeling these interactions .…”
Section: Literature Reviewmentioning
confidence: 99%
“…A majority of the literature focuses on this aspect of interoperability and the ability to model information flows between systems or components of systems . Mordecai and Dori expand beyond this definition slightly as they discuss information exchanges and payloads but they focus on model‐based architecture for information flows . Fry and DeLaurentis discuss interoperability in terms of openness and accessibility to information flows and methods for modeling these interactions .…”
Section: Literature Reviewmentioning
confidence: 99%
“…Integrating independent systems into an interoperable SoS is challenging . SoS integration “involves interfacing and enabling the interactions of component systems to create the needed SoS capability to accomplish a mission or business goals.” Interoperability in SoS is defined as “the ability of distinct systems to share semantically compatible information and then process and manage the information in semantically compatible ways, enabling users to perform desired tasks.” According to the literature in interface management, “ensuring interface compatibility is the process of identifying all functional and physical characteristics of interacting entities from different organizations, and ensuring that proposed changes to these characteristics are assessed and approved before implementation.” A “multidisciplinary interface represents the logical or physical relationship integrating the components” of the system …”
Section: Theoretical Backgroundmentioning
confidence: 99%
“…Related work in this area including service-oriented computing and component-based software techniques such as system integration, is surveyed more comprehensively in (Bryans, Payne et al 2013). (Mordecai and Dori 2013) also aim to develop a model-based approach to the design of interfaces and interactions among disparate systems. They seek to ensure interoperability of the SoS by developing a framework for integration in which the integration domain is a treated as a system in its own right.…”
Section: Related Workmentioning
confidence: 99%
“…The task of the SoS integrator is formidable, and "SoS integration can be a complex, risky, long, and frustrating effort" (Mordecai and Dori 2013). In developing a new SoS, an integrator must have the ability to determine that the combination of proposed contracts and interfaces leads to the desired emergent behavior.…”
Section: Interface and Contract Modelingmentioning
confidence: 99%