Do #ifdef-based Variation Points Realize Feature Model Constraints?
Two mechanisms widely used in the Software Product Lines (SPL) Engineering are the feature model and the conditional compilation. The former models the variability in the problem space and the latter realizes it in the solution space. Even though the research community know that the feature model im...
| Autores: | , |
|---|---|
| Tipo de recurso: | artículo |
| Estado: | Versión publicada |
| Fecha de publicación: | 2015 |
| País: | Brasil |
| Institución: | Universidade Federal da Bahia (UFBA) |
| Repositorio: | Repositório Institucional da UFBA |
| Idioma: | inglés |
| OAI Identifier: | oai:repositorio.ufba.br:ri/19600 |
| Acceso en línea: | http://dl.acm.org/citation.cfm?doid=2830719.2830728 http://repositorio.ufba.br/ri/handle/ri/19600 |
| Access Level: | acceso abierto |
| Palabra clave: | SPL Feature Models Variantion Points Software Engineering |
| Sumario: | Two mechanisms widely used in the Software Product Lines (SPL) Engineering are the feature model and the conditional compilation. The former models the variability in the problem space and the latter realizes it in the solution space. Even though the research community know that the feature model imposes a number of constraints to the product line implementation, there is a lack of support to co-evolve problem space and solution space. In this paper, we present an exploratory study whether problem space constraints are considered at source code level of #ifdef-based SPL implementations. In order to accomplish our goal, we developed a preliminary approach to check problem and solution spaces in a prototype tool (fclcheck). The results show a lack of realization of feature model constraints while implementing variation points with that mechanism. We also evaluated the scalability of the approach and the recoverability of the tool. |
|---|