CLC number: TP301
On-line Access: 2013-09-05
Received: 2013-01-10
Revision Accepted: 2013-05-30
Crosschecked: 2013-08-21
Cited: 3
Clicked: 6054
Reza Rezaei, Thiam-kian Chiew, Sai-peck Lee. A review of interoperability assessment models[J]. Journal of Zhejiang University Science C, 2013, 14(9): 663-681.
@article{title="A review of interoperability assessment models",
author="Reza Rezaei, Thiam-kian Chiew, Sai-peck Lee",
journal="Journal of Zhejiang University Science C",
volume="14",
number="9",
pages="663-681",
year="2013",
publisher="Zhejiang University Press & Springer",
doi="10.1631/jzus.C1300013"
}
%0 Journal Article
%T A review of interoperability assessment models
%A Reza Rezaei
%A Thiam-kian Chiew
%A Sai-peck Lee
%J Journal of Zhejiang University SCIENCE C
%V 14
%N 9
%P 663-681
%@ 1869-1951
%D 2013
%I Zhejiang University Press & Springer
%DOI 10.1631/jzus.C1300013
TY - JOUR
T1 - A review of interoperability assessment models
A1 - Reza Rezaei
A1 - Thiam-kian Chiew
A1 - Sai-peck Lee
J0 - Journal of Zhejiang University Science C
VL - 14
IS - 9
SP - 663
EP - 681
%@ 1869-1951
Y1 - 2013
PB - Zhejiang University Press & Springer
ER -
DOI - 10.1631/jzus.C1300013
Abstract: interoperability is the ability of systems to provide services to and accept services from other systems, and to use the services exchanged so as to operate together in a more effective manner. The fact that interoperability can be improved means that the metrics for measuring interoperability can be defined. For the purpose of measuring the interoperability between systems, an interoperability assessment model is required. This paper deals with the existing interoperability assessment models. A comparative analysis among these models is provided to evaluate the similarities and differences in their philosophy and implementation. The analysis yields a set of recommendations for any party that is open to the idea of creating or improving an interoperability assessment model.
[1]Amanowicz, M., Gajewski, P., 1996. Military Communications and Information Systems Interoperability. Proc. IEEE Military Communications Conf., p.280-283.
[2]Berre, A.J., Elvesaeter, B., Figay, N., Guglielmina, C., Johnsen, S.G., Karlsen, D., Knothe, T., Lippe, S., 2007. The ATHENA Interoperability Framework. In: Gonçalves, R.J., Müller, J.P., Mertins, K., et al. (Eds.), Enterprise Interoperability II: New Challenges and Approaches, p.569-580.
[3]Breitfelder, K., Messina, D., 2000. IEEE 100: the Authoritative Dictionary of IEEE Standards Terms (7th Ed.). IEEE Press.
[4]Carney, D., Oberndorf, P., 2004. Integration and Interoperability Models for Systems of Systems. Proc. System and Software Technology Conf., p.1-35.
[5]Chairman Joint Chiefs of Staff, 2004. Department of Defense Dictionary of Military and Associated Terms, Joint Publication 1-02. Washington, D.C., USA.
[6]Chairman Joint Chiefs of Staff, 2008. DoD Dictionary of Military and Associated Terms, Joint Publication 1-02. Washington, D.C., USA.
[7]Chen, D., 2006. Enterprise Interoperability Framework. Proc. Enterprise Modelling and Ontologies for Interoperability, EMOI-Interop.
[8]Chen, D., Vallespir, B., Daclin, N., 2008. An Approach for Enterprise Interoperability Measurement. Proc. MoDISE-EUS, p.1-12.
[9]Clark, T., Jones, R., 1999. Organisational Interoperability Maturity Model for C2. Proc. Command and Control Research and Technology Symp.
[10]Clark, T., Moon, T., 2001. Interoperability for joint and coalition operations. Austr. Defence Force J., (151):23-36.
[11]Department of Defense (DoD), 1998. Levels of Information Systems Interoperability (LISI).
[12]Department of Defense (DoD), 1999. Realizing the Potential of C4I. Technical Report, National Academy Press, Washington, D.C., USA.
[13]Department of Defense (DoD), 2001a. Chairman of the Joint Chiefs of Staff Instruction. CJCSI 2800.01C.
[14]Department of Defense (DoD), 2001b. DoD Dictionary of Military and Associated Terms, Joint Publication JP1-02. Washington, D.C., USA.
[15]Dimario, M.J., 2006. System of Systems Interoperability Types and Characteristics in Joint Command and Control. Proc. IEEE/SMC Int. Conf. on System of Systems Engineering, p.236-241.
[16]DoD Directive, 1980. Standardization and Interoperability of Weapons Systems and Equipment within the North Atlantic Treaty Organization. DoD, Washington D.C., USA.
[17]Ford, T., Colombi, J., Graham, S., Jacques, D., 2007a. The Interoperability Score. Proc. 5th Annual Conf. on Systems Engineering Research, p.1-10.
[18]Ford, T., Colombi, J., Graham, S., Jacques, D., 2007b. Survey on Interoperability Measurement. Technical Report, DTIC Document.
[19]Ford, T., Colombi, J., Graham, S., Jacques, D., 2008. Measuring System Interoperability (An i-Score Improvement). CSER.
[20]Geraci, A., Katki, F., Mcmonegal, L., Meyer, B., Lane, J., Wilson, P., Radatz, J., Yee, M., Porteous, H., Springsteel, F., 1991. IEEE Standard Computer Dictionary: a Compilation of IEEE Standard Computer Glossaries. IEEE Press.
[21]Guijarro, L., 2009. Semantic interoperability in egovernment initiatives. Comput. Stand. Inter., 31(1):174-180.
[22]Hall, J., Koukoulas, S., 2008. Semantic Interoperability for E-Business in the ISP Service Domain. ICE-B, p.390-396.
[23]Hamilton, J.A.Jr, Rosen, J.D., Summers, P.A., 2002. An Interoperability Road Map for C4ISR Legacy Systems. Technical Report, DTIC Document.
[24]Heiler, S., 1995. Semantic interoperability. ACM Comput. Surv., 27(2):271-273.
[25]Jochem, R., 2010. Enterprise Interoperability Assessment. 8th Int. Conf. of Modeling and Simulation, p.1-9.
[26]Kasunic, M., 2001. Measuring Systems Interoperability: Challenges and Opportunities. Version 1.0. Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA.
[27]Kasunic, M., 2003. Measuring Systems Interoperability. Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, p.1-18.
[28]Kasunic, M., Anderson, W., 2004. Measuring Systems Interoperability: Challenges and Opportunities. Technical Report CMU/SEI-2004-TN-003, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA.
[29]Kinder, T., 2003. Mrs Miller moves house: the interoperability of local public services in Europe. J. Eur. Soc. Policy, 13(2):141-157.
[30]Kingston, G., 2005. An Organisational Interoperability Agility Model. Technical Report, Defence Science and Technology Organisation Canberra (Australia).
[31]Kosanke, K., 2006. ISO Standards for Interoperability: a Comparison. Interperability of Enterprise Software and Applications. Springer, p.55-64.
[32]LaVean, G.E., 1980. Interoperability in defense communications. IEEE Trans. Commun., 28(9):1445-1455.
[33]Leite, M.J., 1998. Interoperability Assessment. Technical Report, PRC Inc., Arlington, VA.
[34]Levine, L., Meyers, B.C., Morris, E.J., 2003. Technical Note CMU/SEI-2003-TN-016. Proc. System of Systems Interoperability Workshop.
[35]Lewis, G.A., Wrage, L., 2006. Model Problems in Technologies for Interoperability: Web Services. Technical Report CMU/SEI-2006-TN-021.
[36]Mensh, D., Kite, R., Darby, P., 1989. A methodology for quantifying interoperability. Nav. Eng. J., 101.3:251.
[37]Meyers, B.C., Smith, J.D., 2007. Programmatic Interoperability. Technical Report CMU/SEI-2008-TN-012, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA.
[38]Meyers, B.C., Monarch, I., Levine, L., Smith, J.I.I., 2005. Including Interoperability in the Acquisition Process. CMU/SEI-2005-TR-004, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA.
[39]Morris, E., Levine, L., Meyers, C., Place, P., Plakosh, D., 2004a. System of Systems Interoperability (SOSI): Final Report. Citeseer, ESC-TR-2004-004.
[40]Morris, E., Levine, L., Meyers, C., Plakosh, D., 2004b. System of Systems Interoperability (SOSI): Final Report. CMU/SEI-2004-TR-004, Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA.
[41]Munk, S., 2002. An analysis of basic interoperability related terms, system of interoperability types. Acad. Appl. Res. Mil. Sci., 1:117-131.
[42]Novakouski, M., Lewis, G.A., 2012. Interoperability in the E-Government. CMU/SEI-2011-TN-014, Carnegie Mellon University, Pittsburgh, PA.
[43]Presson, P.E., 1983. Software Metrics and Interoperability. Proc. AIAA Computers in Aerospace IV Conf.
[44]Radatz, J., Geraci, A., Katki, F., 1990. IEEE Standard Glossary of Software Engineering Terminology. IEEE Standard, p.1-84.
[45]Ruggaber, R., 2005. ATHENA - Advanced Technologies for Interoperability of Heterogeneous Enterprise Networks and Their Applications. In: Konstantas, D., Bourrières, J.P., Léonard, M., et al. (Eds.), Interoperability of Enterprise Software and Applications. Springer London, p.459-460.
[46]Schade, U., 2005. Towards the Edge and Beyond: the Role of Interoperability. 10th Int. Command and Control Research and Technology Symp.
[47]Stewart, K., 2004. Non-technical Interoperability: the Challenge of Command Leadership in Multinational Operations. ADA465749, QinetiQ Ltd., Centre for Human Sciences, Farnborough, United Kingdom.
[48]Stewart, K., Clarke, H., Goillau, P., Verrall, N., Widdowson, M., 2004. Non-technical Interoperability in Multinational Forces. QinetiQ Ltd., Centre for Human Sciences, Farnborough, United Kingdom.
[49]United States Joint Forces Command, 2001. Capstone Requirements Document: Global Information Grid (GIG). JROCM 134-01.
[50]USA and Australia, 2004. Review of Operational Level Interoperability Between the Military Forces of Australia and the United States of America.
[51]van der Veer, H., Wiles, A., 2008. Achieving Technical Interoperability—the ETSI Approach. ETSI White Paper.
Open peer comments: Debate/Discuss/Question/Opinion
<1>