Variability management with feature models

Beuche, Danilo; Papajewski, Holger; Schröder-Preikschat, Wolfgang

doi:10.1016/j.scico.2003.04.005

Cited by 99 publications

(64 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…While there is a fairly large body of work in the literature on different facets of SPL, in the following we mention only those which address traceability as a primary aspect. Four important characteristics of a variability model, namely, consistency, visualization, scalability and traceability are defined in [9]. A variability management model that focuses on the traceability aspect of the notion of problem and solution spaces is presented in [2].…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Traceability Analyses between Features and Assets in Software Product Lines

Narwane

Galindo

Krishna

et al. 2016

Entropy

View full text Add to dashboard Cite

Abstract:In a Software Product Line (SPL), the central notion of implementability provides the requisite connection between specifications and their implementations, leading to the definition of products. While it appears to be a simple extension of the traceability relation between components and features, it involves several subtle issues that were overlooked in the existing literature. In this paper, we have introduced a precise and formal definition of implementability over a fairly expressive traceability relation. The consequent definition of products in the given SPL naturally entails a set of useful analysis problems that are either refinements of known problems or are completely novel. We also propose a new approach to solve these analysis problems by encoding them as Quantified Boolean Formulae (QBF) and solving them through Quantified Satisfiability (QSAT) solvers. QBF can represent more complex analysis operations, which cannot be represented by using propositional formulae. The methodology scales much better than the SAT-based solutions hinted in the literature and were demonstrated through a tool called SPLAnE (SPL Analysis Engine) on a large set of SPL models.

show abstract

Section: Related Workmentioning

confidence: 99%

“…The main idea behind all of these works is that the variability analysis can be reduced to constraints and variables modeling the feature level variability [2,[8][9][10][11][12][13][14][15]. While there are several recent works on traceability, most of them have confined themselves to an informal treatment [16][17][18][19].…”

Section: Introductionmentioning

confidence: 99%

Traceability Analyses between Features and Assets in Software Product Lines

Narwane

Galindo

Krishna

et al. 2016

Entropy

View full text Add to dashboard Cite

show abstract

“…The SMT target hardware consists of two MSP430 processors 3 clocked at 25 MHz. One variant of the system uses the MSP430F67791 with 256 KB Flash ROM and 32 KB RAM, the other variant uses the smaller MSP430F6736 with 128 KB Flash ROM and 8 KB RAM.…”

Section: Hardware Architecturementioning

confidence: 99%

Using C language extensions for developing embedded software: a case study

Voelter¹,

Deursen

Kolb³

et al. 2015

SIGPLAN Not.

View full text Add to dashboard Cite

We report on an industrial case study on developing the embedded software for a smart meter using the C programming language and domain-specific extensions of C such as components, physical units, state machines, registers and interrupts. We find that the extensions help significantly with managing the complexity of the software. They improve testability mainly by supporting hardware-independent testing, as illustrated by low integration efforts. The extensions also do not incur significant overhead regarding memory consumption and performance. Our case study relies on mbeddr, an extensible version of C. mbeddr, in turn, builds on the MPS language workbench which supports modular extension of languages and IDEs.

show abstract

“…In fact, thread switching bears a race condition in case of (full) preemptive scheduling, as necessary condition, and non-transitive (i. e. non-blocking, wait-free, or constructive) synchronization of task scheduling, as sufficient condition. 5 If task scheduling employs some kind of transitive synchronization, thread switching implicitly is indivisible and, thus, synchronized too. Otherwise one is spoilt for choice of the synchronization technique proper to make thread switching atomic.…”

Section: Thread Dispatchingmentioning

confidence: 99%

“…Basing on a tool which aids the construction process of a feature model and supports the mapping of features to implementations, automated generation of highly specialized software systems becomes possible [5].…”

Section: Feature Diagramsmentioning

confidence: 99%

Dimensions of variability in embedded operating systems

Schröder-Preikschat

Lohmann

Scheler

et al. 2007

Informatik Forsch. Entw.

Self Cite

View full text Add to dashboard Cite

Design, implementation, and re-engineering of operating systems are still an ambitious undertaking. Despite, or even because, of the long history of theory and practice in this field, adapting existing systems to environments of different conditions and requirements as originally specified or assumed, in terms of functional and/or non-functional respects, is anything but simple. Especially this is true for the embedded systems domain which, on the one hand, calls for highly specialized and application-aware system abstractions and, on the other hand, cares a great deal for easily reusable implementations of these abstractions. The latter aspect becomes more and more important as embedded systems technology is faced with an innovation cycle decreasing in length. Software for embedded systems needs to be designed for variability, and this is in particular true for the operating systems of this domain. The paper discusses dimensions of variability that need to be considered in the

show abstract

Variability management with feature models

Cited by 99 publications

References 5 publications

Traceability Analyses between Features and Assets in Software Product Lines

Traceability Analyses between Features and Assets in Software Product Lines

Using C language extensions for developing embedded software: a case study

Dimensions of variability in embedded operating systems

Contact Info

Product

Resources

About