scholarly journals The LIME Interface Specification Language and Runtime Monitoring Tool

Author(s):  
Kari Kähkönen ◽  
Jani Lampinen ◽  
Keijo Heljanko ◽  
Ilkka Niemelä
Author(s):  
Fernando Alonso ◽  
José L. Fuertes ◽  
Ángel L. González ◽  
Loïc Martínez

1994 ◽  
Vol 3 (3) ◽  
pp. 221-153 ◽  
Author(s):  
Yoonsik Cheon ◽  
Gary T. Leavens

2015 ◽  
Vol 25 (09n10) ◽  
pp. 1515-1530
Author(s):  
Joilson Abrantes ◽  
Roberta Coelho ◽  
Rodrigo Bonifácio

The exception handling policy of a system comprises the set of design rules that specify its exception handling behavior (how exceptions should be handled and thrown). Such policy is usually undocumented and implicitly defined by the system architect. For this reason, developers often consider that by just including catch-blocks in the code they are dealing with exceptional conditions. This lack of information may turn the exception handling into a generalized “goto” mechanism making the program more complex and less reliable. This work presents a domain-specific language called ECL (Exception Contract Language) to specify the exception handling policy and a runtime monitoring tool which dynamically checks this policy. The monitoring tool is implemented in the form of an aspect library, which can be added to any Java system without the need to change the application source code. We applied this approach to two large-scale web-based systems and to a set of versions of the well-known JUnit framework. The results indicate that this approach can be used to express and to automatically check the exception handling policy of a system, and consequently support the development of more robust Java systems.


Author(s):  
Fuyuan Zhang ◽  
Zhengwei Qi ◽  
Haibing Guan ◽  
Xuezheng Liu ◽  
Mao Yang ◽  
...  

1988 ◽  
Vol 7 (2) ◽  
pp. 117-127 ◽  
Author(s):  
C.A. Wood ◽  
P.D. Gray ◽  
A.C. Kilgour

10.29007/jnj2 ◽  
2018 ◽  
Author(s):  
David Cerna ◽  
Wolfgang Schreiner ◽  
Temur Kutsia

We analyze the space complexity of monitoring streams of messages whose expected behavior is specified in a fragment of predicate logic; this fragment is the core of the LogicGuard specification language that has been developed in industrial context for the runtime monitoring of network traffic. The execution of the monitors is defined by an operational semantics for the step-wise evaluation of formulas, of which require the preservation of instances of the formulas in memory until their truth value can be determined. In the presented work, we analyze the number of instances that have to be preserved over time for a significant fragment of the core language that involves only “future looking quantifiers” which lays the foundations for the space analysis of the entire core language.


Sign in / Sign up

Export Citation Format

Share Document