Demo Data from EDBT 2026 / reviewers in the wild / expert
Quentin Enard
dblp:59/8636
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2010
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1
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.
| Software engineering, system software, and programming languages
1 paper |
Requirements engineering and software design · 100% | |
| Human-computer interaction and pervasive computing
1 paper |
Ubiquitous computing and smart environments · 100% |
Topics — the 2 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design › design process
error handling design |
0.1 | 1 | 2010 | A domain-specific approach to architecturing error handling in pervasive computing · OOPSLA 2010 |
Requirements engineering and software design
software architecture |
0.1 | 1 | 2010 | A domain-specific approach to architecturing error handling in pervasive computing · OOPSLA 2010 |
Methods — techniques the papers use, named apart from their topics
domain-specific modeling · 0.2
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2010 | A domain-specific approach to architecturing error handling in pervasive computingabstractThe challenging nature of error handling constantly escalates as a growing number of environments consists of networked devices and software components. In these environments, errors cover a uniquely large spectrum of situations related to each layer ranging from hardware to distributed platforms, to software components. Handling errors becomes a daunting task for programmers, whose outcome is unpredictable. Scaling up error handling requires to raise the level of abstraction beyond the code level and the try-catch construct, approaching error handling at the software architecture level. Julien Mercadal, Quentin Enard, Charles Consel, Nicolas Loriant |
OOPSLA | 2 |