Applying aspects to a real-time embedded operating system

Afonso, Francisco; Montenegro, Sérgio; Tavares, Adriano

doi:10.1145/1233901.1233902

Cited by 14 publications

(13 citation statements)

References 13 publications

(10 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We expect that common recovery advice will involve an exception-like mechanism for unwinding to an appropriate program point. 1 Other strategies such as stack compression are possible in some cases; exploring these is part of our current research.…”

Section: Aspects For Resource Managementmentioning

confidence: 99%

Resource management aspects for sensor network software

Walton

Eide

2007

Proceedings of the 4th Workshop on Programming Languages and Operating Systems

View full text Add to dashboard Cite

The software that runs on a typical wireless sensor network node must address a variety of constraints that are imposed by its purpose and implementation platform. Examples of such constraints include real-time behavior, highly limited RAM and ROM, and other scarce resources. These constraints lead to crosscutting concerns for the implementations of sensor network software: that is, all parts of the software must be carefully written to respect its resource constraints. Neither traditional languages (such as C) nor component-based languages (such as nesC) for implementing sensor network software allow programmers to deal with crosscutting resource constraints in a modular fashion.In this paper we describe Aspect nesC (ANesC), a language we are now implementing to help programmers modularize the implementations of crosscutting concerns within sensor network software. Aspect nesC extends nesC, a component-based dialect of C, with constructs for aspect-oriented programming. In addition to combining the ideas of components and aspects in a single language, ANesC will provide specific and novel constructs for resource-management concerns. For instance, pointcuts can identify program points at which the run-time stack is about to be exhausted or a real-time deadline has been missed. Corrective actions can be associated with these points via "advice." A primary task of the Aspect nesC compiler is to implement such resource-focused aspects in an efficient manner.

show abstract

Section: Aspects For Resource Managementmentioning

confidence: 99%

Resource management aspects for sensor network software

Walton

Eide

2007

Proceedings of the 4th Workshop on Programming Languages and Operating Systems

View full text Add to dashboard Cite

show abstract

“…However, we are convinced that the fault-tolerance concerns should be separated from the "business logic" of the application to reduce complexity. Several researchers attacked this modularity problem by exercising aspect-oriented programming, in particular AspectC++ [37], [38]. For example, Alexandersson et al [38] implemented triple-time-redundant execution and control-flow checking as a proof of concept, which led to 300 % runtime overhead.…”

Section: Software-based Memory Protectionmentioning

confidence: 99%

Generative software-based memory error detection and correction for operating system data structures

Borchert¹,

Schirmeier²,

Spinczyk³

2013

2013 43rd Annual IEEE/IFIP International Conference on Dependable Systems and Networks (DSN)

View full text Add to dashboard Cite

Abstract-Recent studies indicate that the number of system failures caused by main memory errors is much higher than expected. In contrast to the commonly used hardware-based countermeasures, for example using ECC memory, softwarebased fault-tolerance measures are much more flexible and can exploit application knowledge, such as the criticality of specific data structures. This paper presents a software-based memory error protection approach, which we used to harden the eCos operating system in a case study. The main benefits of our approach are the flexibility to choose from an extensible toolbox of easily pluggable error detection and correction schemes as well as its very low runtime overhead, which totals in a range of 0.09-1.7 %. The implementation is based on aspect-oriented programming and exploits the object-oriented program structure of eCos to identify well-suited code locations for the insertion of generative fault-tolerance measures.

show abstract

“…Lee (2006) applies aspect-oriented tracing to modify Reflexion Model-an existing software system for drawing conceptual model. Afonso et al (2007) apply aspects to synchronization and logging a real-time embedded Briand et al (2005) report on how AspectJ can be used efficiently for instrumentation of contracts and invariants in Java to help testing and debugging. Cheon and Avila (2010) use AspectJ for automated random testing for Java program on executable assertions.…”

Section: Related Workmentioning

confidence: 99%

“…Several techniques exist (Moa 2007;Xie and Zhao 2006;Sokenou and Vösgen 2005;Afonso et al 2007;Bruel et al 2003) that use AOP to improve testing of software. Also, researchers (Störzer et al 2003;Briand et al 2005;Harrold et al 2001) have used AOP for tracing the internal execution details of software.…”

Section: Introductionmentioning

confidence: 99%

Observability using aspect-oriented programming for OO software testing

Meetei

Goel

Wasan

2011

Int J Syst Assur Eng Manag

View full text Add to dashboard Cite

Software testing is a process of executing software with the goal of finding errors. It is an important phase in the software development process. It still remains an art due to limitations in understanding of the principles of software. In this paper, we present a new approach to testing object-oriented software using aspect-oriented programming. We propose an aspect-based testing technique that facilitates observing internal details of execution at unit, integration and system levels, during testing of objectoriented software. Our technique adapts logging aspect, to suit the testing needs of object-oriented software. The logging aspect is introduced externally to the software under test, for observing the system's internal and external behavior. The internal execution details are stored in a log file for use during post-analysis. Test coverage reports are generated from the information gathered from the log file. It includes coverage at method, class, inheritance and dynamic binding levels.

show abstract

Applying aspects to a real-time embedded operating system

Cited by 14 publications

References 13 publications

Resource management aspects for sensor network software

Resource management aspects for sensor network software

Generative software-based memory error detection and correction for operating system data structures

Observability using aspect-oriented programming for OO software testing

Contact Info

Product

Resources

About