Verifying feature-based model templates against well-formedness OCL constraints
By Krzysztof Czarnecki, Krzysztof Pietroszek. International Conference on Generative Programming: Concepts and Experiences, 2006
307 citations recorded by the source corpus.
Feature-based model templates have been recently proposed as a approach for modeling software product lines. Unfortunately, templates are notoriously prone to errors that may go unnoticed for long time. This is because such an error is usually exhibited for some configurations only, and testing all configurations is typically not feasible in practice. In this paper, we present an automated verification procedure for ensuring that no ill-structured template instance will be generated from a correct configuration. We present the formal underpinnings of our proposed approach, analyze its complexity, and demonstrate its practical feasibility through a prototype implementation.
Subfields: Artificial Intelligence, Information Systems, Software
View Paper: https://www.semanticscholar.org/paper/8e27a464d8399ae342cc176177f82282318728d8
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Artificial Intelligence
- Christian Kästner
- Sven Apel
- Gunter Saake
- Thomas Thüm
- Krzysztof Czarnecki
- Ina Schaefer
- Andrzej Wasowski
- Don S. Batory
In Information Systems
- Christian Kästner
- Sven Apel
- Gunter Saake
- Thomas Thüm
- Krzysztof Czarnecki
- Ina Schaefer
- Andrzej Wasowski
- Don S. Batory
In Software
- Christian Kästner
- Sven Apel
- Krzysztof Czarnecki
- Thomas Thüm
- Gunter Saake
- Andrzej Wasowski
- Patrick Heymans
- Pierre-Yves Schobbens
Citations in the corpus
- Granularity in software product lines (2008, methodology): “These checks follow the concepts of Czarnecki and Pietroszek [11] and Thaker et al. [50] but their discussion exceeds the scope of this paper.”
- An Overview of Feature-Oriented Software Development (2009, background): “With regard to syntactic and type correctness of product lines, researchers made considerable progress in recent years [49, 120, 73, 13, 53, 78, 11].”
- Feature-Oriented Software Product Lines (2013, background): “2005) and checking model consistency (Czarnecki and Pietroszek 2006).”
- Cool features and tough decisions: a comparison of variability modeling approaches (2012, background): “, [20, 3, 27]) and 3) automated guidance during configuration.”
- Model checking lots of systems: efficient verification of temporal properties in software product lines (2010, background): “A natural generalisation of FTS would be to label each transition with a Boolean expression over the set of features, in the spirit of [12, 13 ].”
- A Classification and Survey of Analysis Strategies for Software Product Lines (2014, methodology): “…annotation-based implementation [Aversano et al. 2002; Kim et al. 2008; Kenner et al. 2010; Teixeira et al. 2011; Kästner et al. 2012a, 2012b; Liebig et al. 2013; Le et al. 2013; Chen et al. 2014], and annotation-based design [Czarnecki and Pietroszek 2006; Metzger et al. 2007; Heidenreich 2009].”