Quentin Boucher

Learn More
In the scientific community, feature models are the de-facto standard for representing variability in software product line engineering. This is different from industrial settings where they appear to be used much less frequently. We and other authors found that in a number of cases, they lack concision, naturalness and expressiveness. This is confirmed by(More)
Feature models are a common way to represent variability in software product line engineering. For this purpose, most authors use a graphical notation based on FODA. The main drawback of those approaches is their lack of scalability: they generally do not fit real-size problems. Indeed, their graphical syntax does not account for attributes or complex(More)
A feature model captures various possible configurations of products within a product family. When configuring a product, several features are selected and composed. Selecting features at the program level has a general limitation of not being able to relate the resulting configuration to its requirements. As a result, it is difficult to decide whether a(More)
Feature cardinalities in feature diagrams determine the number of times a feature and its subtree can be duplicated during configuration by an operation named "cloning". Other authors already investigated the problem and published different proposals of semantics for this construct. However, this previous work is not easily amenable to the formal study of(More)
Nowadays, mass customization has been embraced by a large portion of the industry. As a result, the web abounds with sales configurators that help customers tailor all kinds of goods and services to their specific needs. In many cases, configurators have become the single entry point for placing customer orders. As such, they are strategic components of(More)
Using ISO/IEC 29110, very small entities (VSEs) can perform a stepwise increment of their software process by switching between the different ISO/ IEC profiles. However, ISO/IEC 29110 provides no guidance on how to switch between profiles incrementally, other than resorting to costly software development process experts unaffordable for VSEs. To address(More)
To realise variability at the code level, product line methods classically advocate usage of inheritance, components, frameworks, aspects or generative techniques. However, these might require unaffordable paradigm shifts for the developers if the software was not thought at the outset as a product line. Furthermore, these techniques can be conflicting with(More)
In software product lines, feature models are the <i>de-facto</i> standard for representing variability as well as for configuring products. Yet, configuration relying on feature models faces two issues: <i>i)</i> it assumes knowledge of the underlying formalism, which may not be true for end users and <i>ii)</i> it does not take advantage of advanced(More)
Delivering configurable solutions, that is products tailored to the requirements of a particular customer, is a priority of most B2B and B2C markets. These markets now heavily rely on interactive configurators that help customers build complete and correct products. Reliability is thus a critical requirement for configurators. Yet, our experience in(More)