An overview of the MOP runtime verification framework

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 t...

Full description

Saved in:
Bibliographic Details
Published in:International journal on software tools for technology transfer Vol. 14; no. 3; pp. 249 - 289
Main Authors: Meredith, Patrick O’Neil, Jin, Dongyun, Griffith, Dennis, Chen, Feng, Roşu, Grigore
Format: Journal Article
Language:English
Published: Berlin/Heidelberg Springer-Verlag 01.06.2012
Springer Nature B.V
Subjects:
Architecture
Buses (vehicles)
Computer programming
Computer programs
Computer Science
Dynamical systems
Dynamics
Java (programming language)
Monitoring
Monitors
Runtime Verification
Software
Software Engineering
Software Engineering/Programming and Operating Systems
Systems management
Technology transfer
Theory of Computation
Real time systems
Monitoring
Runtime verification
Testing
ISSN:1433-2779, 1433-2787
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary: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.
Bibliography:SourceType-Scholarly Journals-1
ObjectType-Feature-1
content type line 14
ObjectType-Article-2
content type line 23
ISSN:1433-2779
1433-2787
DOI:10.1007/s10009-011-0198-6