Omnibus Verification Policies: A flexible, configurable approach to assertion-based software verification

Authors:
Thomas Wilson;Savi Maharaj;Robert G. Clark
Affiliations:
University of Stirling, Scotland;University of Stirling, Scotland;University of Stirling, Scotland
Venue:
SEFM '05 Proceedings of the Third IEEE International Conference on Software Engineering and Formal Methods
Year:
2005

Citing 7
Cited 2

Eiffel: the language

Eiffel: the language
Extended static checking for Java

PLDI '02 Proceedings of the ACM SIGPLAN 2002 Conference on Programming language design and implementation
On To Components

Computer
Extended Static Checking: A Ten-Year Perspective

Informatics - 10 Years Back. 10 Years Ahead.
PVS: Combining Specification, Proof Checking, and Model Checking

CAV '96 Proceedings of the 8th International Conference on Computer Aided Verification
Preliminary design of JML: a behavioral interface specification language for java

ACM SIGSOFT Software Engineering Notes
The spec# programming system: an overview

CASSIS'04 Proceedings of the 2004 international conference on Construction and Analysis of Safe, Secure, and Interoperable Smart Devices

Simplifying reasoning about objects with Tako

Proceedings of the 2006 conference on Specification and verification of component-based systems
Faster and More Complete Extended Static Checking for the Java Modeling Language

Journal of Automated Reasoning

Quantified Score

Hi-index	0.00

Visualization

Abstract

The three main assertion-based verification approaches are: Design by Contract (DBC), Extended Static Checking (ESC) and Verified Design by Contract (VDBC). Each approach offers a different balance between rigour and ease of use making them appropriate in different situations. Our goal is to explore the use of these approaches together in a flexible way, enabling an application to be broken down into sections with different reliability requirements and different verification approaches used in each section. We explain the benefits of using the approaches together, present a set of guidelines to avoid potential conflicts and give an overview of how the Omnibus IDE provides support for the full range of assertion-based verification approaches within a single tool.