2 research outputs found
An Unexpected Journey: Towards Runtime Verification of Multiagent Systems and Beyond
The Trace Expression formalism derives from works started in 2012 and is
mainly used to specify and verify interaction protocols at runtime, but other
applications have been devised. More specically, this thesis describes how
to extend and apply such formalism in the engineering process of distributed
articial intelligence systems (such as Multiagent systems).
This thesis extends the state of the art through four dierent contributions:
1. Theoretical: the thesis extends the original formalism in order to represent
also parametric and probabilistic specications (parametric trace
expressions and probabilistic trace expressions respectively).
2. Algorithmic: the thesis proposes algorithms for verifying trace expressions
at runtime in a decentralized way. The algorithms have been
designed to be as general as possible, but their implementation and
experimentation address scenarios where the modelled and observed
events are communicative events (interactions) inside a multiagent system.
3. Application: the thesis analyzes the relations between runtime and static
verication (e.g. model checking) proposing hybrid integrations in both
directions. First of all, the thesis proposes a trace expression model
checking approach where it shows how to statically verify LTL property
on a trace expression specication. After that, the thesis presents a
novel approach for supporting static verication through the addition
of monitors at runtime (post-process).
4. Implementation: the thesis presents RIVERtools, a tool supporting the
writing, the syntactic analysis and the decentralization of trace expressions
Managing bad AIPs with RIVERtools
We present the RIVERtools integrated development environment for specifying Agent Interaction Protocols (AIPs) modelled as trace expressions, and for statically verifying some of their properties. In particular, this demonstration paper aims at showing why a \u201cgood\u201d AIP can become a \u201cbad\u201d one because of unreliability of some communication channels, and how RIVERtools can cope with such bad AIPs, suggesting to the developer possible ways to dynamically verify them in a partially decentralized way