DVDaniele Varacca
Daniele Varacca
*This is an algorithmically generated author record based on publicly available information.
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Previous Organizations / Institutes
The organizations / institutes from the scholar's other articles in the past ten years
Research Subjects
Daniele Varacca has a total of 4 co-authors. Here are the top co-authors by number of shared publications:
- Cătălin Dima
LACL, Université Paris-Est Créteil
2 shared publications - Clément Aubert
Augusta University Augusta GA USA
1 shared publication - Dumitru-Bogdan Prelipcean
LACL, Université Paris-Est Créteil
1 shared publication - Romain Demangeon
LIP6, Sorbonne University Paris
1 shared publication
Latest Publications
- 11 November 2025
- Published by Springer Nature
- p. 172-188
Formal Construction of Threat Detections from Attack Trees
- 11 November 2025
- Published by Springer Nature
- p. 172-188
Formal Construction of Threat Detections from Attack Trees
- 7 September 2023
- Published by Springer Nature
- p. 312-327
Observational Preorders for Alternating Transition Systems
- 7 September 2023
- Published by Springer Nature
- p. 312-327
Observational Preorders for Alternating Transition Systems
- Open Access
Processes Against Tests: Defining Contextual Equivalences
In this position paper, we would like to offer and defend a template to study equivalences between programs---in the particular framework of process algebras for concurrent computation.We believe that our layered model of development will clarify the distinction that is too often left implicit between the tasks and duties of the programmer and of the tester.It will also enlighten pre-existing issues that have been running across process algebras such as the calculus of communicating systems, the \(\pi\)-calculus---also in its distributed version---or mobile ambients.Our distinction starts by subdividing the notion of process in three conceptually separated entities, that we call \emph{process terms}, (completed) \emph{processes} and \emph{tests}, and by stressing the importance of formalizing the \emph{completion} of process terms and the \emph{instrumentation} that results from placing a (completed) processes into a test.While the role of what can be observed and the subtleties in the definitions of congruences have been intensively studied, the fact that \emph{not every term can be tested}, and that \emph{the tester should have access to a different set of tools than the programmer} is curiously left out, or at least not often formally discussed--in this respect, the theory of monitor is a counter-examples that we discuss and compare to our approach.We argue that this blind spot comes from the under-specification of contexts---environments in which comparisons occur---that play multiple distinct roles but are generally---at least, on the surface of it---given only one definition that fails to capture all of their aspects.Open AccessProcesses Against Tests: Defining Contextual Equivalences
In this position paper, we would like to offer and defend a template to study equivalences between programs---in the particular framework of process algebras for concurrent computation.We believe that our layered model of development will clarify the distinction that is too often left implicit between the tasks and duties of the programmer and of the tester.It will also enlighten pre-existing issues that have been running across process algebras such as the calculus of communicating systems, the \(\pi\)-calculus---also in its distributed version---or mobile ambients.Our distinction starts by subdividing the notion of process in three conceptually separated entities, that we call \emph{process terms}, (completed) \emph{processes} and \emph{tests}, and by stressing the importance of formalizing the \emph{completion} of process terms and the \emph{instrumentation} that results from placing a (completed) processes into a test.While the role of what can be observed and the subtleties in the definitions of congruences have been intensively studied, the fact that \emph{not every term can be tested}, and that \emph{the tester should have access to a different set of tools than the programmer} is curiously left out, or at least not often formally discussed--in this respect, the theory of monitor is a counter-examples that we discuss and compare to our approach.We argue that this blind spot comes from the under-specification of contexts---environments in which comparisons occur---that play multiple distinct roles but are generally---at least, on the surface of it---given only one definition that fails to capture all of their aspects.