Management of Variability in Modular Ontology Development

Langermeier, Melanie; Rosina, Peter; Oberkampf, Heiner; Driessen, Thomas; Bauer, Bernhard

doi:10.1007/978-3-319-06859-6_20

Cited by 3 publications

(10 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…These are for example the relations owl:ontologyIRI, owl:imports or version information (see section 3) (Motik et al, 2012). In (Langermeier et al, 2013) we introduced an approach for the management of the dependencies between such ontological modules as well as their composition to one application ontology. We decided to use VMs to formalize and reason about the dependencies between modular ontologies.…”

Section: Variability Models For Modular Ontology Managementmentioning

confidence: 99%

“…An overview of this concept with the used models and their dependencies is given in Figure 1. Figure 2 is an example of V M I for the EA do-Figure 1: Overview of the models and their dependencies (Langermeier et al, 2013).…”

Section: Variability Models For Modular Ontology Managementmentioning

confidence: 99%

“…The four basic functions of persistent storage, create, read, update and delete, are called CRUD in the domain of computer science. (Langermeier et al, 2013) shows how to read from the OntRepo and VMs, in the following the create, update and delete (CUD) functions are shown. In the MOVO approach introduced in section 2 four results are established: (1) an ontology repository (OntRepo), containing the relevant ontological modules for the organization, ( 2) an ontological variability model V M O , formalizing the dependencies between the modules, ( 3) an integrated variability model V M I , formalizing additional dependencies according to a specific domain under consideration of V M O and (4) a specific configuration of modules, which is conform to V M I and serves as application ontology.…”

Section: Extending Movo For Version and Change Managementmentioning

confidence: 99%

“…A specific domain ontology is created through selection of different modules from an ontology repository. To manage the complexity of the different variants that exist for the composition of an application ontology, we proposed in (Langermeier et al, 2013) the use of variability management (MOVO). This is a technique from product line engineering, that focuses on a consequent and explicit documentation of the variability on software artifacts.…”

Section: Introductionmentioning

confidence: 99%

“…Figure 2: A variability model for modeling an enterprise architecture with a possible configuration (Langermeier et al, 2013).…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Change and Version Management in Variability Models for Modular Ontologies

Langermeier

Driessen

Oberkampf

et al. 2014

Proceedings of the 16th International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

Modular ontology management tries to overcome the disadvantages of large ontologies regarding reuse and performance. A possibility for the formalization of the various combinations are variability models, which originate from the software product line domain. Similar to that domain, knowledge models can then be individualized for a specific application through selection and exclusion of modules. However, the ontology repository as well as the requirements of the domain are not stable over time. A process is needed, that enables knowledge engineers and domain experts to adapt the principles of version and change management to the domain of modular ontology management. In this paper, we define the existing change scenarios and provide support for keeping the repository, the variability model and also the configurations consistent using Semantic Web technologies. The approach is presented with a use case from the enterprise architecture domain as running example.

show abstract

Section: Variability Models For Modular Ontology Managementmentioning

confidence: 99%

Section: Variability Models For Modular Ontology Managementmentioning

confidence: 99%

Section: Extending Movo For Version and Change Managementmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

“…Figure 2: A variability model for modeling an enterprise architecture with a possible configuration (Langermeier et al, 2013).…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Change and Version Management in Variability Models for Modular Ontologies

Langermeier

Driessen

Oberkampf

et al. 2014

Proceedings of the 16th International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

show abstract

Analysis of variability models: a systematic literature review

2020

View full text Add to dashboard Cite

Improving Variabilty Analysis through Scenario-Based Incompatibility Detection

2022

View full text Add to dashboard Cite

Software Product Line (SPL) developments include Variability Management (VA) as a core activity aiming at minimizing the inherent complexity in commonality and variability manipulation. Particularly, the (automated) analysis of variability models refers to the activities, methods and techniques involved in the definition, design, and instantiation of variabilities modeled during SPL development. Steps of this analysis are defined as a variability analysis process (VA process), which is focused on assisting variability model designers in avoiding anomalies and/or inconsistencies, and minimizing problems when products are implemented and derived. Previously, we have proposed an approach for analyzing variability models through a well-defined VA process (named SeVaTax). This process includes a comprehensive set of scenarios, which allows a designer to detect (and even correct in some cases) different incompatibilities. In this work, we extend SeVaTax by classifying the scenarios according to their dependencies, and by assessing the use of these scenarios. This assessment introduces two experiments to evaluate accuracy and coverage. The former addresses responses when variability models are analyzed, and the latter the completeness of our process with respect to other proposals. Findings show that a more extensive set of scenarios might improve the possibilities of current practices in variability analysis.

show abstract

Management of Variability in Modular Ontology Development

Cited by 3 publications

References 18 publications

Change and Version Management in Variability Models for Modular Ontologies

Change and Version Management in Variability Models for Modular Ontologies

Analysis of variability models: a systematic literature review

Improving Variabilty Analysis through Scenario-Based Incompatibility Detection

Contact Info

Product

Resources

About