2017
DOI: 10.1007/s10703-017-0273-z
|View full text |Cite
|
Sign up to set email alerts
|

Monitorability for the Hennessy–Milner logic with recursion

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
67
0

Year Published

2017
2017
2020
2020

Publication Types

Select...
6

Relationship

3
3

Authors

Journals

citations
Cited by 45 publications
(67 citation statements)
references
References 28 publications
0
67
0
Order By: Relevance
“…is shown not to be monitorable in the setting of [15,16]: to detect a violation, it requires at least two witness execution traces, one showing that action s can be performed at start-up, another showing that o can be performed at start-up. Monitorability in traditional RV settings typically assumes one execution trace.…”
Section: Examplementioning
confidence: 99%
See 4 more Smart Citations
“…is shown not to be monitorable in the setting of [15,16]: to detect a violation, it requires at least two witness execution traces, one showing that action s can be performed at start-up, another showing that o can be performed at start-up. Monitorability in traditional RV settings typically assumes one execution trace.…”
Section: Examplementioning
confidence: 99%
“…The monitor may also reach an inconclusive verdict whenever the trace exhibited by the system does not yield the necessary information for it to reach a definitive judgement. Following [15,16], this paper uses the safety fragment of the branching-time logic µHML [23,1], called sHML (Safety HML), which has been shown to be monitorable and maximally expressive w.r.t. the constraints of runtime monitoring.…”
Section: Monitors and Specificationmentioning
confidence: 99%
See 3 more Smart Citations