Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Alwin Berger

dblp:426/1172 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
1since 2021 · last 2025
0009-0005-1507-3995ORCID · reported

Domains — the database's venue-derived domains; a paper can count in several

Applied, interdisciplinary, general and emerging computing · 1 · 1 first-author · 1 since 2021

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Computer architecture, parallel and distributed computing, and storage systems
1 paper
Embedded and real-time systems · 100%
Software engineering, system software, and programming languages
1 paper
Software testing · 100%

Topics — the 5 heaviest of 5, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Software testing › fuzzing
feedback-guided fuzzing
0.912025
Dynamic Fuzzing-Based Whole-System Timing Analysis · RTSS 2025
Software testing
fuzzing
0.912025
Dynamic Fuzzing-Based Whole-System Timing Analysis · RTSS 2025
Embedded and real-time systems
real-time scheduling
0.912025
Dynamic Fuzzing-Based Whole-System Timing Analysis · RTSS 2025
Embedded and real-time systems › real-time scheduling › schedulability analysis
response time analysis
0.912025
Dynamic Fuzzing-Based Whole-System Timing Analysis · RTSS 2025
Embedded and real-time systems
real-time operating systems
0.312025
Dynamic Fuzzing-Based Whole-System Timing Analysis · RTSS 2025

Methods — techniques the papers use, named apart from their topics

feedback-guided fuzzing · 1.7dynamic analysis · 1.7
YearPublicationVenuePosition
2025 Dynamic Fuzzing-Based Whole-System Timing Analysis
abstract
Worst-case timing analysis traditionally begins with estimating the worst-case execution time (WCET) of individual tasks using either static analysis or measurement-based techniques. To derive worst-case response times (WCRTs), engineers typically compose these WCETs with bounds on preemption and operating system overheads. However, WCRTs depend on complex system-level interactions, including task communication, OS behavior, and asynchronous events. Compositional analysis often overestimates, assuming that worst-case conditions across components coincide, admitting infeasible global control-flow paths. whole-system Static techniques refine this by modeling the system holistically but require platform-specific tailoring or extensive annotations. A dynamic equivalent has been missing. We present Fret, the first dynamic whole-system approach for estimating WCRTs. Fret employs feedback-guided fuzzing to uncover timing-critical dependencies, including inter-task communication, task/OS interactions, and interrupt effects, without requiring prior knowledge of inputs or states. Implemented using LibAFL and evaluated on FreeRTOS with realistic benchmarks, FRET consistently outperforms state-of-the-art fuzzing strategies in estimating accurate response times. Although not sound, Fret delivers more than timing estimates: it produces actionable artifacts-worst-case inputs, interrupt schedules, and intertask program-flow information-that complement static analyses and support system validation, runtime monitoring, and robust mixed-criticality scheduling.
Alwin Berger, Simon Schuster, Peter Wägemann, Peter Ulbrich
RTSS1