Models of Interoperability

Abstract models of critical features of a problem domain or technology have proven valuable in almost every engineering domain. Within software engineering, abstract architectural models are currently being extensively exploited (e.g., the standard model for networking protocols and distributed applications is the International Standard Organization's Open System Interconnect model). Other forms of models are used to assist in capturing and analyzing requirements, and predicting performance and costs.

Note that, in addition to abstract models, there is another form of interoperability model that is often closely tied to a particular technology. For example, the J2EE implements a particular model for establishing connections between enterprise information systems and application. This section does not directly address these more concrete models that are tied to specific technologies.

Within the problem domain of interoperability among systems, there are many potential benefits of clear, concise abstract models. Such models could:

define a common vocabulary that allows meaningful discussion and analysis
provide hints regarding the structure of solutions
serve as a basis to evaluate new ideas and assess different options

This section describes several abstract models of interoperability.

Basic Issues

Abstract interoperability models fall into one of two basic categories:

models focusing on technical aspects of achieving interoperability
models that, in addition to addressing technical aspects, also address organizational and operational aspects of interoperability.

These categories of models differ in the range of interoperability issues that they address, as well as in their intent. Technical models are often created as a way of categorizing systems in terms of interoperability characteristics, while the more wide ranging models are often intended to facilitate discussion about a variety of activities that contribute to interoperability success and failure.

Focus Areas

Four different abstract interoperability models are presented:

LISI is a technical model intended to categorize systems. LCIM is intended to bridge the gap between conceptual design and technical design for interoperability. LCI addresses the wide range of technical and organizational characteristics that must align in order for coalitions to interoperate. Finally, SOSI represents a simple model that focuses on the activities of organizations constructing and operating systems that must interoperate, as well as technical factors.

References

[C4ISR 98] C4ISR Interoperability Working Group, Department of Defense. Levels of Information Systems Interoperability (LISI). Washington, D.C., 1998

[Morris 04] Morris, E.; Levine, L.; Meyers, C.; Plakosh, D.; and Place, P. Systems of Systems Interoperability. CMU/SEI-2004-TR-004 (ESC-TR-2004-004). Software Engineering Institute, Carnegie Mellon University. April 2004

[Tolk 03a] Tolk, Andreas & Muguira, James A. The Levels of Conceptual Interoperability Model, 2003 Fall Simulation Interoperability Workshop Orlando, Florida, September 2003

[Tolk 03b] Tolk, Andreas, Beyond Technical Interoperability; Introducing a Reference Model for Measures of Merit for Coalition Interoperability, 8th International Command and Control Research and Technology Symposium (ICCRTS), Washington, D.C., June 17-19, 2003. Washington D.C., Command and Control Research Program (CCRP), 2003

	ISIS Main Page
	Conferences, Workshops, and Other Events
	Presentations
	Publications
	References
	ISIS Staff
	Working with Us
	Performance-Critical Systems
	COTS-Based Systems
	Dynamic Systems Program