2006
DOI: 10.1007/11922827_8
|View full text |Cite
|
Sign up to set email alerts
|

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

Abstract: 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 co… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
12
0

Year Published

2007
2007
2023
2023

Publication Types

Select...
5
1
1

Relationship

0
7

Authors

Journals

citations
Cited by 11 publications
(12 citation statements)
references
References 41 publications
(35 reference statements)
0
12
0
Order By: Relevance
“…al. [1] argue that the development of finegrained and resource-efficient system software product lines requires a means for separation of concerns [9] that does not lead to extra overhead in terms of memory and performance which they show using AspectC++. The FACET [2] project identifies the core functionality of a middleware framework and then codifies all additional functionality into separate aspects that represent domain concerns, which then can be woven into the core middleware.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…al. [1] argue that the development of finegrained and resource-efficient system software product lines requires a means for separation of concerns [9] that does not lead to extra overhead in terms of memory and performance which they show using AspectC++. The FACET [2] project identifies the core functionality of a middleware framework and then codifies all additional functionality into separate aspects that represent domain concerns, which then can be woven into the core middleware.…”
Section: Related Workmentioning
confidence: 99%
“…Most prior efforts at specializing middleware (and other system artifacts) [1]- [6] often require manual efforts in identifying opportunities for specialization and realizing them on the software artifacts. At first glance it may appear that these manual efforts are expended towards addressing problems that are purely accidental in nature.…”
Section: Introductionmentioning
confidence: 99%
“…Hence, feature modeling is specially important during domain engineering and also during product configuration. Several feature implementation techniques have also been proposed in order to facilitate the actual implementation of the software assets of a SPL [27], [20], [15]. Moreover, techniques for scoping [19], testing [30], managing variability [17], are also available, business aspects like risk management [31], management and financial controls [29] are also addressed.…”
Section: Introduction a Software Product Linesmentioning
confidence: 99%
“…al. [12] argue that fine-grained and resource-efficient embedded system software requires a means for separation of concerns that does not lead to extra overhead in terms of memory and performance. Aspect-oriented programming (AOP) [9] is shown to eliminate this overhead.…”
Section: Related Researchmentioning
confidence: 99%