Streamlining object-oriented software for deeply embedded applications

Beuche, Danilo; Schröder-Preikschat, Wolfgang; Spinczyk, Olaf; Spinczyk, Ute

doi:10.1109/tools.2000.848749

Cited by 2 publications

(2 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As a matter of fact, it is impossible to proof that the design and implementation of some software is optimal with respect to runtime resource requirements. The authors have, however, profound experience in developing resource-minimal object-oriented product lines [11,10,34]. There is, furthermore, quite some evidence that any OO version would lead to higher memory requirements than the AO version: As pointed out in the previous sections, runtime mechanisms have to be used with OO to reach the required flexibility which, as described in sections 3.5 and 4, induce overhead.…”

Section: Design Issuesmentioning

confidence: 99%

Lean and Efficient System Software Product Lines: Where Aspects Beat Objects

Lohmann

Spinczyk

Schröder-Preikschat

2006

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Software development in the domain of embedded and deeply embedded systems is dominated by cost pressure and extremely limited hardware resources. As a result, modern concepts for separation of concerns and software reuse are widely ignored, as developers worry about the thereby induced memory and performance overhead. Especially object-oriented programming (OOP) is still little in demand. For the development of highly configurable fine-grained system software product lines, however, separation of concerns (SoC) is a crucial property. As the overhead of object-orientation is not acceptable in this domain, we propose aspect-oriented programming (AOP) as an alternative. Compared to OOP, AOP makes it possible to reach similar or even better separation of concerns with significantly smaller memory footprints. In a case study for an embedded system product line the memory costs for SoC could be reduced from 148-236% to 2-10% by using AOP instead of OOP.

show abstract

Section: Design Issuesmentioning

confidence: 99%

Lean and Efficient System Software Product Lines: Where Aspects Beat Objects

Lohmann

Spinczyk

Schröder-Preikschat

2006

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…The feature modeling and aspect-oriented programming techniques described in the previous sections have been implemented in our group in prototypical form [3], [2]. The resulting tools have been used to build an interactive configuration enviroment for the PURE operating system family.…”

Section: Current State and Future Developmentmentioning

confidence: 99%