details for the publication
@techreport {El-SharkawyKrafczykSchmid16,
author={Sascha El-Sharkawy and Adam Krafczyk and Klaus Schmid},
title={Mismatched Configuration Information of Linux},
institution={Software Systems Engineering, Institut für Informatik, Universität Hildesheim},
number={1/2016, SSE 1/16/E},
year={2016},
url={https://sse.uni-hildesheim.de/media/fb4/informatik/AG_SSE/PDFs/publications/El-SharkawyKrafczykSchmid16.pdf},
abstract={Context. Software product line engineering has been established to minimize costs and efforts, while maximizing the quality of products in a family of software products. Software product lines typically contain a variability model, which supports the derivation of permissible variants. These variability models may contain expert/domain knowledge in the form of constraints. These constraints are used during the configuration process to avoid the selection of unsupported product variants. Problem. Developers must encode their knowledge about supported product variants and restrictions, otherwise the variability model becomes ineffective or even incorrect. The initial development of the variability model as well as the evolution of the product line implementation bear the risk that model and implementation drift apart. In this report, we introduce the notion of mismatched configuration information to describe the situation if the variability model does not react the dependencies of the implementation. This may indicate an incomplete variability model or undesired dependencies between code artifacts. Solution. We discuss the impact of mismatched configuration information and show how to detect this conceptually. Subsequently, we focus on mismatched hierarchical configuration information and present an effective heuristic for their detection. These results serve as an input to complete variability models or a code review to remove undesired implementation dependencies. We discuss the application of our approach on a Linux case study. The analysis of the x86 architecture of the Linux kernel takes only around 30 minutes and revealed mismatched configuration information, which was not treated by prior work.}
}
