Time-Aware Instrumentation of Embedded Software

Fischmeister, Sebastian; Lam, Patrick

doi:10.1109/tii.2010.2068304

Cited by 35 publications

(23 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A time-aware, software-based instrumentation methodology is presented in Fischmeister and Lam (2010). Similarly, a software-based monitoring approach discussed in Iyenghar et al (2010) is used for visualizing the behavior of targets in real time using UML diagrams.…”

Section: Trace Datamentioning

confidence: 99%

“…However, most of the aforementioned monitoring approaches, except Fischmeister and Lam (2010), concentrate on applications running on desktop computers. Further, none of the approaches presented in Fischmeister and Lam (2010), Graf et al (2007), Huang et al (2012), Iyenghar et al (2010), Watterson and Heffernan (2007) are time-and memory-aware.…”

Section: Trace Datamentioning

confidence: 99%

See 1 more Smart Citation

A model-based framework encompassing a complete workflow from specification until validation of timing requirements in embedded software systems

et al. 2016

View full text Add to dashboard Cite

Embedded software engineering very often involves development of complex, mission critical software; wherein it is imperative that the developed software fulfills its requirements to achieve high quality. In such cases, there are several advantages of using specialized Requirements Management (RM) tools for managing the requirements. Critical timing requirements are among the foremost non-functional (quality) requirements to be fulfilled by increasingly complex embedded software. Further, a correct and effective timing behavior is among the characteristics of high-quality software. On the other hand, Model-Driven Development (MDD) is considered as the next paradigm shift to address the increasing complexity in embedded software development and to achieve high-quality standards. Similarly, there are specialized tools for validating and analyzing the timing behavior of the embedded software. However, such tools are used very late in the development process, when the actual timing errors occur. Thus, it is intuitive to perceive that an integrated model-based framework encompassing a complete workflow from specification until validation of timing requirements in embedded software systems is very beneficial for high-quality software development, nevertheless is still missing. Addressing the aforementioned gap, this paper proposes an approach toward a complete workflow for managing timing requirements in RM tools, specifying timing behavior in MDD tools and their validation in specialized tools for timing analyses. A prototype implementation of the proposed framework and its experimental evaluation are discussed.

show abstract

Section: Trace Datamentioning

confidence: 99%

Section: Trace Datamentioning

confidence: 99%

A model-based framework encompassing a complete workflow from specification until validation of timing requirements in embedded software systems

et al. 2016

View full text Add to dashboard Cite

show abstract

“…Kim et al proposed a scalable data dependence profiling to reduce runtime and memory overhead [24] by storing memory references as compressed formats and using pipelining and data level parallelism for the data dependence profiling. Timeaware instrumentation approaches [27] [28] have been proposed to minimize violation of timing constraints due to instrumentation overhead. DIME [27] monitors instrumentation time and limits the program instrumentation to a given time budget in a time period.…”

Section: Related Workmentioning

confidence: 99%

“…DIME [27] monitors instrumentation time and limits the program instrumentation to a given time budget in a time period. A static approach [28] inserts instrumentation code only where the instrumentation can preserve the worst-case execution time.…”

Section: Related Workmentioning

confidence: 99%

On the existence of probe effect in multi-threaded embedded programs

Song

Lee

2014

Proceedings of the 14th International Conference on Embedded Software

View full text Add to dashboard Cite

Software instrumentation has been a convenient and portable approach for dynamic analysis, debugging, or profiling of program execution. Unfortunately, instrumentation may change the temporal behavior of multi-threaded program execution and result in different ordering of thread operations, which is called probe effect. While the approaches to reduce instrumentation overhead, to enable reproducible execution, and to enforce deterministic threading have been studied, no research has yet answered if an instrumented execution has the same behavior as the program execution without any instrumentation and how the execution gets changed if there were any. In this paper, we propose a simulation-based analysis to detect the changes of execution event ordering that are induced by instrumentation operations. The execution model of a program is constructed from the trace of instrumented program execution and is used in a simulation analysis where instrumentation overhead is removed. As a consequence, we can infer the ordering of events in the original program execution and verify the existence of probe effect resulted from instrumentation.

show abstract

“…Software Instrumentation. One can argue that round-robin hashing's markers can change the program behavior, however, it is usually acceptable that software-only instrumentation approaches bears the risk of changing the software behavior [37], as demonstrated by the widespread use of gprof, coverage-monitoring code compiled into the program, and valgrind [38]. Another example of the impact of software instrumentation would be in a controlling system, such as motor control signal.…”

Section: Tablementioning

confidence: 99%