How to Complete an Interactive Configuration Process?

Janota, Mikoláš; Botterweck, Goetz; Grigore, Radu; Marques-Silva, João

doi:10.1007/978-3-642-11266-9_44

Cited by 15 publications

(18 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It also allows users to remove unnecessary features of the original firmware by selecting individual patches. 4. http://os.inf.tu-dresden.de/drops/overview.html 3.1.9 ToyBox ToyBox is our smallest subject.…”

Section: Freetzmentioning

confidence: 99%

“…Fig. 7 shows the eCos-i386 model with links from the groups to the architectural concern for whose configuration Math library (19) POSIX file I/O compatibility layer (18) uITRON compatibility layer (65) Watchdog IO device (12) Wallclock device (20) Basic networking framework (175) DNS client (13) Flash device drivers (44) RAM filesystem (15) Simple Network Time Protocol (6) ROM filesystem (4) JFFS2 filesystem (17) FAT filesystem (10) Linux compatibility layer (1) VNC server (25) Zlib compress and decompress (10) Disk device drivers (5) Hardware Abstraction Layer (99) Exceptions Virtual Vectors Interrupts (6) Kernel (107) Libraries (143) Math (19) C (124) Compatibility (135) POSIX (49) uTron ( Ethernet (32) Serial (84) Flash (44) File System (46) Web Server (25) Fig. 7.…”

Section: Ecos-i386mentioning

confidence: 99%

“…Product line users derive concrete products from variability models. A range of automated tools supports these activities: analyzers verify model consistency or detect dead features [1]; graphical configuration tools (configurators for short) support intelligent choice propagation and model completion [2], [3], [4]. These tools are usually optimized for models with certain properties, such as size and density of constraints, due to the computational hardness of configuration problems.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A Study of Variability Models and Languages in the Systems Software Domain

Berger

She

Lotufo

et al. 2013

IIEEE Trans. Software Eng.

156

183

View full text Add to dashboard Cite

Abstract-Variability models represent the common and variable features of products in a product line. Since the introduction of FODA in 1990, several variability modeling languages have been proposed in academia and industry, followed by hundreds of research papers on variability models and modeling. However, little is known about the practical use of such languages. We study the constructs, semantics, usage, and associated tools of two variability modeling languages, Kconfig and CDL, which are independently developed outside academia and used in large and significant software projects. We analyze 128 variability models found in twelve open source projects using these languages. Our study (1) supports variability modeling research with empirical data on the real-world use of its flagship concepts. However, we (2) also provide requirements for concepts and mechanisms that are not commonly considered in academic techniques, and (3) challenge assumptions about size and complexity of variability models made in academic papers. These results are of interest to researchers working on variability modeling and analysis techniques and to designers of tools, such as feature dependency checkers and interactive product configurators.

show abstract

Section: Freetzmentioning

confidence: 99%

Section: Ecos-i386mentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A Study of Variability Models and Languages in the Systems Software Domain

Berger

She

Lotufo

et al. 2013

IIEEE Trans. Software Eng.

156

183

View full text Add to dashboard Cite

show abstract

“…In this way, no error can be introduced. Janota et al [23] propose an approach to complete a partial configuration by automatically setting the unknown options in a safe way. However, both approaches require that the configuration starts with variables in the unknown state.…”

Section: Related Workmentioning

confidence: 99%

Generating range fixes for software configuration

Xiong¹,

Hubaux²,

Czarnecki³

2012

2012 34th International Conference on Software Engineering (ICSE)

View full text Add to dashboard Cite

Abstract-To prevent ill-formed configurations, highly configurable software often allows defining constraints over the available options. As these constraints can be complex, fixing a configuration that violates one or more constraints can be challenging. Although several fix-generation approaches exist, their applicability is limited because (1) they typically generate only one fix, failing to cover the solution that the user wants; and (2) they do not fully support non-Boolean constraints, which contain arithmetic, inequality, and string operators. This paper proposes a novel concept, range fix, for software configuration. A range fix specifies the options to change and the ranges of values for these options. We also design an algorithm that automatically generates range fixes for a violated constraint. We have evaluated our approach with three different strategies for handling constraint interactions, on data from five open source projects. Our evaluation shows that, even with the most complex strategy, our approach generates complete fix lists that are mostly short and concise, in a fraction of a second.

show abstract

“…Benavides et al [89] presented a structured literature review of the existing proposals for the automated analysis of feature models. Example analyses include consistency check or dead feature detections [90], interactive guidance during configuration [91,92], or fixing models and configurations [93][94][95]. It should be noted that most of the reasoning operations (e.g., satisfiability) are difficult computational problem and are NP-complete [36].…”

Section: Automated Analysis Of Feature Modelsmentioning

confidence: 99%

Model-Driven Engineering for Software Product Lines

Jézéquel

2012

ISRN Software Engineering

View full text Add to dashboard Cite

Modeling variability in the context of software product-lines has been around for about 25 years in the research community. It started with Feature Modeling and soon enough was extended to handle many different concerns. Beyond being used for a mere description and documentation of variability, variability models are more and more leveraged to produce other artifacts, such as configurators, code, or test cases. This paper overviews several classification dimensions of variability modeling and explores how do they fit with such artifact production purposes.

show abstract

How to Complete an Interactive Configuration Process?

Cited by 15 publications

References 21 publications

A Study of Variability Models and Languages in the Systems Software Domain

A Study of Variability Models and Languages in the Systems Software Domain

Generating range fixes for software configuration

Model-Driven Engineering for Software Product Lines

Contact Info

Product

Resources

About