Best practices of interoperability among heterogeneous software systems: a Semat-based representation

Main Article Content


Diana María Torres-Ricaurte
Carlos Mario Zapata-Jaramillo


Interoperability among heterogeneous software systems is a software quality sub-characteristic. Some methods for dealing with interoperability exhibit differences in aspects like generality, development method, and work products, among others. However, some authors understand interoperability as a non-functional requirement with general-purpose practices for identifying and specifying such requirement. Other authors assess and achieve interoperability by using work products falling beyond defined practices. Consequently, in this paper we propose four best practices in order to accomplish interoperability among heterogeneous software systems. Our best practices are represented with the Semat (Software Engineering Method and Theory) kernel, since it includes a language with simple and precise elements. Definition of interoperability best practices enables unification of the effort focused on software systems interoperability.


Article Details


All articles included in the Revista Facultad de Ingeniería are published under the Creative Commons (BY) license.

Authors must complete, sign, and submit the Review and Publication Authorization Form of the manuscript provided by the Journal; this form should contain all the originality and copyright information of the manuscript.

The authors who publish in this Journal accept the following conditions:

a. The authors retain the copyright and transfer the right of the first publication to the journal, with the work registered under the Creative Commons attribution license, which allows third parties to use what is published as long as they mention the authorship of the work and the first publication in this Journal.

b. Authors can make other independent and additional contractual agreements for the non-exclusive distribution of the version of the article published in this journal (eg, include it in an institutional repository or publish it in a book) provided they clearly indicate that the work It was first published in this Journal.

c. Authors are allowed and recommended to publish their work on the Internet (for example on institutional or personal pages) before and during the process.
review and publication, as it can lead to productive exchanges and a greater and faster dissemination of published work.

d. The Journal authorizes the total or partial reproduction of the content of the publication, as long as the source is cited, that is, the name of the Journal, name of the author (s), year, volume, publication number and pages of the article.

e. The ideas and statements issued by the authors are their responsibility and in no case bind the Journal.


[1] Systems and software Engineering-Systems and software Quality Requirements and Evaluation, ISO/ IEC 25000: 2014.

[2] C4ISR Interoperability Working Group, Levels of information systems interoperability (LISI). Washington, DC, 1998.

[3] L. Chung, B. A. Nixon, E. Yu, and J. Mylopoulos, Non-functional requirements in software engineering. Boston, MA: Springer US, 2000. DOI:

[4] B. Paech and D. Kerkow, “Non-functional requirements engineering-quality is essential,” in Proc. 10th International Workshop on Requirements Engineering Foundation for Software Quality, Riga, Latvia, 2004, pp. 237-250.

[5] W. M. Farid, “The NORMAP Methodology: Lightweight Engineering of Non-functional Requirements for Agile Processes,” in Proc. 2012 19th Asia-Pacific Software Engineering Conference, Hong Kong, China, Dec. 2012, pp. 322-325. DOI:

[6] S. Supakkul, E. Oladimeji, and L. Chung, “Toward component non-functional interoperability analysis: A uml-based and goal-oriented approach,” in Proc. IEEE International Conference on Information Reuse and Integration, Waikoloa, USA, 2006, pp. 351-358.

[7] I. Brito, A. Moreira, and J. Araújo, “A requirements model for quality attributes,” in Proc. Aspect-Oriented Requirements Engineering and Architecture Design, Enschede, Netherlands, 2002, pp. 1-7.

[8] C. M. Zapata (Traductor), I. Jacobson, P. P. W. Ng, P. E. McMahon, I. Spence, and S. Lidman, “La Esencia de la Ingeniería de Software: El Núcleo de Semat,” Revista Latinoamericana de Ingeniería de Software, vol. 1(3), pp. 71-78, Jun. 2013.

[9] I. Jacobson, P. Ng, P. McMahon, I. Spence, and S. Lidman, Kernel and Language for Software Engineering Methods (Essence), Needham, MA: OMG, 2014.


Download data is not yet available.