A framework for the semantics of behavioral contracts

Abstract

Abstract. Contracts have proved a powerful concept in software engineering, to the point where we have a well regarded software development approach centered on their use, and native support in programming languages. However, it is not clear that there is a uniform concept of contract that can be applied to both algorithmic and interactive software. We propose a framework for thinking about software contracts based on the idea that a contract aims to preserve a formal proposition about the software system being built, and the form of the contract must reflect both the proposition whose truth is to be preserved and the formal reasoning system used for verification. In particular, we believe that very different forms of contract are needed for algorithmic and interactive software and illustrate this with examples.

Modelling session types using contracts

“…Throughout the paper we follow the approach of Castagna et al (2009) and Padovani (2010), and think of 'contracts' only as terms of (some dialect of) ccs without τ's (Nicola and Hennessy 1987); in particular, our notion of contract is completely independent of that discussed in McNeile (2010) and Meyer (1997).…”