A tool for analyzing variability based on functional requirements and testing artifacts

Michal Steinberger, Iris Reinhartz-Berger, Amir Tomer

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

Abstract

Analyzing differences among software artifacts is beneficial in a variety of scenarios, such as feasibility study, configuration management, and software product line engineering. Currently variability analysis is mainly done based on artifacts developed in a certain development phase (most notably, requirements engineering). We will demonstrate a tool that utilizes both functional requirements and test cases in order to analyze variability more comprehensively. The tool implements the ideas of SOVA R-TC method.

Original languageAmerican English
Title of host publicationAdvances in Conceptual Modeling - ER 2016 Workshops, AHA, MoBiD, MORE-BI, MReBA, QMMQ, SCME, and WM2SP, Proceedings
EditorsSebastian Link, Juan C. Trujillo
PublisherSpringer Verlag
Pages243-250
Number of pages8
ISBN (Print)9783319477169
DOIs
StatePublished - 2016
Event35th International Conference on Conceptual Modelling, ER 2016 held in conjunction with Workshops on AHA, MoBiD, MORE-BI, MReBA, QMMQ, SCME and WM2SP, 2016 - Gifu, Japan
Duration: 14 Nov 201617 Nov 2016

Publication series

NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
Volume9975 LNCS

Conference

Conference35th International Conference on Conceptual Modelling, ER 2016 held in conjunction with Workshops on AHA, MoBiD, MORE-BI, MReBA, QMMQ, SCME and WM2SP, 2016
Country/TerritoryJapan
CityGifu
Period14/11/1617/11/16

Keywords

  • Feature diagrams
  • Natural language processing
  • Ontology
  • Software product line engineering
  • Variability analysis

All Science Journal Classification (ASJC) codes

  • Theoretical Computer Science
  • General Computer Science

Fingerprint

Dive into the research topics of 'A tool for analyzing variability based on functional requirements and testing artifacts'. Together they form a unique fingerprint.

Cite this