Svamp - An integrated approach for modeling functional and quality variability

Mikko Raatikainen, Eila Niemelä, Varvana Myllärniemi, Tomi Männistö

Research output: Chapter in Book/Report/Conference proceedingConference article in proceedingsScientificpeer-review

Abstract

Software variability modeling is a complex task. To manage this complexity, we introduce an approach called Svamp. The main contribution of Svamp is to model concepts through ontologies and offer tool support for capturing functional and quality variability in software product family architectures. Variability description languages are defined by different ontologies that provide meta-models. For structural and functional descriptions, the concepts, properties, and rules are defined by Kumbang ontology. Quality Attribute ontology defines the domain knowledge of a specific quality attribute, while Quality Variability ontology provides the concepts and rules related to quality variation. The approach is exemplified by our integrated tool suite, provided as a plug-in for the Eclipse platform.
Original languageEnglish
Title of host publicationSecond International Workshop on Variability Modelling of Software-intensive Systems (VaMoS'08)
EditorsPatrick Heymans, Kyo-Chul Kang, Andreas Metzger, Klaus Pohl
PublisherVeröffentlichungen der Universität Duisburg-Essen
Pages89-96
Publication statusPublished - 2008
MoE publication typeA4 Article in a conference publication
Event2nd International Workshop on Variability Modelling of Software-intensive Systems (VaMoS’08) - University of Duisburg-Essen, Duisburg-Essen, Germany
Duration: 16 Jan 200818 Jan 2008

Publication series

SeriesICB Research Report
Number22
ISSN1860-2770

Conference

Conference2nd International Workshop on Variability Modelling of Software-intensive Systems (VaMoS’08)
Country/TerritoryGermany
CityDuisburg-Essen
Period16/01/0818/01/08

Fingerprint

Dive into the research topics of 'Svamp - An integrated approach for modeling functional and quality variability'. Together they form a unique fingerprint.

Cite this