According to a study in 2002 commissioned by a US Department, software bugs annually costs the US economy an estimated $59 billion. A more recent study in 2013 by Cambridge University estimated that the global cost has risen to $312 billion globally. There exists various ways to prevent, isolate and fix software bugs, ranging from lightweight methods that are (semi)-automatic, to heavyweight methods that require significant user interaction. Our own method described in this tutorial is based on automated run-time checking of a combination of protocol- and data-oriented properties of object-oriented programs.
Additional Metadata
Keywords Run-Time Assertion Checking, Monitoring, Run-Time Verification, Attribute Grammars
THEME Software (theme 1)
Publisher Springer
Editor M. Bernardo , F. Damiani , R. Hähnle (Reiner) , E.B. Johnsen (Einar Broch) , I. Schaefer
Persistent URL dx.doi.org/10.1007/978-3-319-07317-0_6
Conference International School on Formal Methods for the Design of Computer, Communication, and Software Systems
Citation
de Boer, F.S, & de Gouw, C.P.T. (2014). Combining Monitoring with Run-Time Assertion Checking. In M Bernardo, F Damiani, R Hähnle, E.B Johnsen, & I Schaefer (Eds.), Proceedings of International School on Formal Methods for the Design of Computer, Communication, and Software Systems 2014 (SFM 14) (pp. 217–262). Springer. doi:10.1007/978-3-319-07317-0_6