TY - JOUR
T1 - An overview of the MOP runtime verification framework
AU - Meredith, Patrick O.Neil
AU - Jin, Dongyun
AU - Griffith, Dennis
AU - Chen, Feng
AU - Roşu, Grigore
N1 - Funding Information:
Supported in part by NSF grants CCF-0916893, CNS-0720512, and CCF-0448501, by NASA contract NNL08AA23C, and by a Samsung SAIT grant.
PY - 2012/6
Y1 - 2012/6
N2 - This article gives an overview of the, monitoring oriented programming framework (MOP). In MOP, runtime monitoring is supported and encouraged as a fundamental principle for building reliable systems. Monitors are automatically synthesized from specified properties and are used in conjunction with the original system to check its dynamic behaviors. When a specification is violated or validated at runtime, user-defined actions will be triggered, which can be any code, such as information logging or runtime recovery. Two instances of MOP are presented: JavaMOP (for Java programs) and BusMOP (for monitoring PCI bus traffic). The architecture of MOP is discussed, and an explanation of parametric trace monitoring and its implementation is given. A comprehensive evaluation of JavaMOP attests to its efficiency, especially in comparison with similar systems. The implementation of BusMOP is discussed in detail. In general, BusMOP imposes no runtime overhead on the system it is monitoring.
AB - This article gives an overview of the, monitoring oriented programming framework (MOP). In MOP, runtime monitoring is supported and encouraged as a fundamental principle for building reliable systems. Monitors are automatically synthesized from specified properties and are used in conjunction with the original system to check its dynamic behaviors. When a specification is violated or validated at runtime, user-defined actions will be triggered, which can be any code, such as information logging or runtime recovery. Two instances of MOP are presented: JavaMOP (for Java programs) and BusMOP (for monitoring PCI bus traffic). The architecture of MOP is discussed, and an explanation of parametric trace monitoring and its implementation is given. A comprehensive evaluation of JavaMOP attests to its efficiency, especially in comparison with similar systems. The implementation of BusMOP is discussed in detail. In general, BusMOP imposes no runtime overhead on the system it is monitoring.
KW - Monitoring
KW - Real time systems
KW - Runtime verification
KW - Testing
UR - http://www.scopus.com/inward/record.url?scp=84861233991&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=84861233991&partnerID=8YFLogxK
U2 - 10.1007/s10009-011-0198-6
DO - 10.1007/s10009-011-0198-6
M3 - Article
AN - SCOPUS:84861233991
SN - 1433-2779
VL - 14
SP - 249
EP - 289
JO - International Journal on Software Tools for Technology Transfer
JF - International Journal on Software Tools for Technology Transfer
IS - 3
ER -