Streamlining Feature-Oriented Designs

Abstract

Abstract. Software development for embedded systems gains momentum but faces many challenges. Especially the constraints of deeply embedded systems, i.e., extreme resource and performance constraints, seem to prohibit the successful application of modern and approved programming and modularization techniques. In this paper we indicate that this objection is not necessarily justified. We propose to use refinement chain optimization to tailor and streamline feature-oriented designs to satisfy the resource constraints of (deeply) embedded systems. By means of a quantitative analysis of a case study we show that our proposal leads to a performance and footprint improvement significant for (deeply) embedded systems.

RobbyDBMS

“…The usage of FeatureC++ for developing SPLs has been evaluated before [13,17]. Our results coincide with these evaluations and exhibit further insights on the efficiency and variability.…”

“…Using the AVR HPL AVR 8-Bit Timer (1)(2)(3)(4)(5)(6)(7)(8) 16-Bit Timer (1)(2)(3)(4)(5)(6)(7)(8) Flash RAM (32B-32KB) DMA Channel (4) Event Channel (8) I/O Pins 10-Bit A/D (1)(2)(3)(4)(5)(6)(7)(8)(9)(10)(11)(12)(13)(14)(15)(16) 12-Bit A/D (5)(6)(7)(8)(9)(10)(11)(12)(13)(14)(15)(16) 12-Bit D/A (2)(3)(4) analog Comp. (1)(2)(3)…”

An orthogonal access modifier model for feature-oriented programming

“…The background is that the Jak compiler generates Java code in an intermediate step and it supports two options to do so [15]: in the first option, called Mixin, the compiler generates an inheritance hierarchy with one subclass per refinement; in the second option, called Jampack, the compiler generates a single class consisting of the elements of the base class and all of its refinements. Comparing the two options it becomes clear why they show different behaviors in our example, which we illustrate in Figure 5.…”

“…What we do not want is that internal implementation details of compilers or the use of compiler flags, which target at optimization [15], decide arbitrarily over the program semantics.…”