FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W2397928607> ?p ?o ?g. }

• W2397928607 endingPage "10" @default.
• W2397928607 startingPage "3" @default.
• W2397928607 abstract "Use of models and modelling languages in software engineering is very common nowadays. To formalize these modelling languages, many metamodels have been proposed in the software engineering literature as well as by standard organizations. Interoperability of these metamodels has emerged as a key concern for their practical usage. We have developed a framework for facilitating metamodel interoperability based on schema matching and ontology matching techniques. In this paper we discuss not the techniques used but rather we focus on the lessons we have learned by applying the framework on several pairs of metamodels for finding similarities between them. We have highlighted some areas where these techniques can be beneficial and also pointed out some limitations of these techniques in this domain. 1 Problem Description and Motivation Many metamodels have been proposed in different domains of software engineering such as process [1], product [2], metrics [3] and programming [4]. Most of these metamodels have been developed independently of each other with shared concepts being only accidental. These metamodels are evolving continuously and many versions of these metamodels have been introduced over the years. This evolution has extended not only the scope but their size [5] and complexity as well. The need to formulate a way in which these metamodels can be used in an interoperable fashion has emerged as a key issue in the practical usage of these metamodels. There are several benefits of such interoperability including: reduced joint complexity, ease of understanding and use for newcomers, portability of models across modelling tools and better communication between researchers [6]. This overall need is also emphasized by the software engineering community [7] and further endorsed by the rise of industry interest as well as various conferences and workshops on the topic [8]. To have interoperability between any pair of metamodels, similarities between the elements of metamodels need to be identified. This is undertaken by a matching technique as yet little utilized for metamodels although widely used in ontology engineering. Close similarity between metamodels and ontologies [7],[9],[10] suggests that it should be efficacious to adopt ontology matching techniques for facilitating meta-model interoperability with a first step of linguistic matching. Indeed, ontologies are also helpful in reducing semantic ambiguity [9], helping not only to improve the semantics of a metamodel [10] but also providing a potential way in which these meta-models can be bridged with each other to be interoperable. A framework [11] for facilitating interoperability of metamodels has been developed based on the ontology merging and schema matching techniques. The frame-work was applied to several pairs of metamodels including OSM [12], BPMN [13], SPEM [1] and some multi agent systems (MAS) metamodels. In this paper we discuss the lessons learned by applying the framework on these metamodels. We have highlighted the areas of metamodel interoperability that can be assisted by using these techniques as well as discussing some of their limitations. In Section 2 we briefly present our framework for metamodel interoperability. Section 3 presents the lessons learned during the application of this framework to several metamodels, followed by a conclusion and summary of likely future work (Section 4)." @default.
• W2397928607 created "2016-06-24" @default.
• W2397928607 creator A5070809975 @default.
• W2397928607 date "2012-01-01" @default.
• W2397928607 modified "2023-09-23" @default.
• W2397928607 title "Interoperability of software Engineering Metamodels: Lessons Learned." @default.
• W2397928607 cites W1415855017 @default.
• W2397928607 cites W1494058686 @default.
• W2397928607 cites W1530861867 @default.
• W2397928607 cites W1562095323 @default.
• W2397928607 cites W1807218968 @default.
• W2397928607 cites W1845712655 @default.
• W2397928607 cites W1931408162 @default.
• W2397928607 cites W1999962878 @default.
• W2397928607 cites W2019192014 @default.
• W2397928607 cites W2028368146 @default.
• W2397928607 cites W2044463389 @default.
• W2397928607 cites W2081401189 @default.
• W2397928607 cites W2081580037 @default.
• W2397928607 cites W2115868996 @default.
• W2397928607 cites W2125822162 @default.
• W2397928607 cites W2138961726 @default.
• W2397928607 cites W2154891096 @default.
• W2397928607 cites W2156543375 @default.
• W2397928607 cites W2190746580 @default.
• W2397928607 cites W38032089 @default.
• W2397928607 cites W5067071 @default.
• W2397928607 cites W81368115 @default.
• W2397928607 hasPublicationYear "2012" @default.
• W2397928607 type Work @default.
• W2397928607 sameAs 2397928607 @default.
• W2397928607 citedByCount "0" @default.
• W2397928607 crossrefType "journal-article" @default.
• W2397928607 hasAuthorship W2397928607A5070809975 @default.
• W2397928607 hasConcept C115903868 @default.
• W2397928607 hasConcept C127413603 @default.
• W2397928607 hasConcept C136764020 @default.
• W2397928607 hasConcept C199360897 @default.
• W2397928607 hasConcept C20136886 @default.
• W2397928607 hasConcept C201995342 @default.
• W2397928607 hasConcept C2777904410 @default.
• W2397928607 hasConcept C2778177629 @default.
• W2397928607 hasConcept C41008148 @default.
• W2397928607 hasConcept C529173508 @default.
• W2397928607 hasConcept C63000827 @default.
• W2397928607 hasConcept C86610423 @default.
• W2397928607 hasConceptScore W2397928607C115903868 @default.
• W2397928607 hasConceptScore W2397928607C127413603 @default.
• W2397928607 hasConceptScore W2397928607C136764020 @default.
• W2397928607 hasConceptScore W2397928607C199360897 @default.
• W2397928607 hasConceptScore W2397928607C20136886 @default.
• W2397928607 hasConceptScore W2397928607C201995342 @default.
• W2397928607 hasConceptScore W2397928607C2777904410 @default.
• W2397928607 hasConceptScore W2397928607C2778177629 @default.
• W2397928607 hasConceptScore W2397928607C41008148 @default.
• W2397928607 hasConceptScore W2397928607C529173508 @default.
• W2397928607 hasConceptScore W2397928607C63000827 @default.
• W2397928607 hasConceptScore W2397928607C86610423 @default.
• W2397928607 hasLocation W23979286071 @default.
• W2397928607 hasOpenAccess W2397928607 @default.
• W2397928607 hasPrimaryLocation W23979286071 @default.
• W2397928607 hasRelatedWork W1602613331 @default.
• W2397928607 hasRelatedWork W1603685546 @default.
• W2397928607 hasRelatedWork W163864919 @default.
• W2397928607 hasRelatedWork W1968056213 @default.
• W2397928607 hasRelatedWork W1985584087 @default.
• W2397928607 hasRelatedWork W2000432130 @default.
• W2397928607 hasRelatedWork W2057478091 @default.
• W2397928607 hasRelatedWork W2088637672 @default.
• W2397928607 hasRelatedWork W2103311462 @default.
• W2397928607 hasRelatedWork W2169774668 @default.
• W2397928607 hasRelatedWork W2184781191 @default.
• W2397928607 hasRelatedWork W2755868726 @default.
• W2397928607 hasRelatedWork W2794608298 @default.
• W2397928607 hasRelatedWork W2885758397 @default.
• W2397928607 hasRelatedWork W3103086489 @default.
• W2397928607 hasRelatedWork W310460277 @default.
• W2397928607 hasRelatedWork W3161403168 @default.
• W2397928607 hasRelatedWork W3197846314 @default.
• W2397928607 hasRelatedWork W154820431 @default.
• W2397928607 hasRelatedWork W2288672901 @default.
• W2397928607 isParatext "false" @default.
• W2397928607 isRetracted "false" @default.
• W2397928607 magId "2397928607" @default.
• W2397928607 workType "article" @default.