CSC/ECE 517 Fall 2011/ch18 6a sc

Programming by Contract

Common programming errors

It would not be wrong to say that no software in the world is bug free. A lot of bugs in software can be attributed to the programming errors that the programmers commonly make. The most common of them are:

• While considering possibilities, the programmer misses out on some
• Cut-and-paste programming
• Inflexible code that cannot adapt to changes that maybe needed of it in future
• Lack of error checking
• Software reuse
• Lack of mechanisms to recover from errors in a graceful manner

One of the several things essential to making bug free software a reality is "Programming by contract". It helps programmers develop robust software.

Programming by contract

Programming by Contract or Design by Contract (DbC) was first introduced by Bertrand Meyer, the creator of the Eiffel programming language. Although Eiffel has implemented assertions as built in DbC support, the concepts can be applied in any language. It uses pre-conditions and post-conditions to document or programmatically assert the change in state caused by a piece of a program. (1)

Background

Programming by Contract or Design by Contract (DbC) has its roots in work on formal verification, formal specification and Hoare logic. The original contributions includes:

• A clear metaphor to guide the design process.
• The application to inheritance, in particular a formalism for redefinition and dynamic binding.
• The application to exception handling.
• The connection with automatic software documentation.

Methodology

Programming by Contract creates a contract between the software developer and software user - in Meyer's terms the supplier (callee) and the consumer (caller/client).

Before entering a method or routine, a pre-condition must be satisfied by the consumer of the routine. Each routine ends with a post-conditions which the supplier guarantees to be true (if and only if the preconditions were met). Also, each class has an invariant which must be satisfied after any changes to an object are represented by the class. In other words, the invariant guarantees the object is in a valid state. (2)

If the consumer tries to call the method without meeting the preconditions, it can result in unexpected behavior. The program could crash or run in a loop forever. It may also deceptively generate garbage, while giving an impression that it is running correctly.

A Java Example

Here is a Java example that shows where the checks can be placed.

class Supplier{  //the supplier class
  public Supplier()
  {
      //some code that initializes the supplier constructor
      checkInvariant();  //verify class invariant
  }
  public supplier_method(Data data)
  {
     //some actions performed by supplier method
     postCondition(); //check if we have done what has been promised
     checkInvariant(); //verify class invariant
  }
}

class Client { // the client class
  public client_method (Data data){ //client method, calls supplier method
     Supplier s = new Supplier(); //initialize supplier constructor    
     preCondition(data);  //verify the preCondition before calling the supplier method
     s.supplier_method(data);
  }
}

Design by Contract Metaphor

DbC is a metaphor on how elements of a software system collaborate with each other, on the basis of mutual obligations and benefits. The metaphor comes from business life, where a "client" and a "supplier" agree on a "contract" which documents that:

• The supplier must provide a certain product (obligation) and is entitled to expect that the client has paid its fee (benefit).
• The client must pay the fee (obligation) and is entitled to get the product (benefit).
• Both parties must satisfy certain obligations, such as laws and regulations, applying to all contracts. (3)

We can use the previous Java example to show the relationship between obligation and benefit.

	Obligations	Benefit
Client	Satisfy preCondition()	Result from supplier_method
Supplier	Satisfy postCondition()	Know that preCondition() is satisfied by client_method

Apply Programming by Contract to Applications

Inheritance

When programming by contract is used with inheritance, a subcontract is added to the subclass. According to this subcontract and in accordance with the Liskov Substitution Principle, an overridden method in the subclass may have preconditions that are as weak as or weaker than the preconditions of the base class, and postconditions that are as strong as or stronger than the postconditions of the base class. We can see this in the following example:

class A
{
    public int foo(int x)
    {
         assert(1<x<3); // pre-condition
         ...
         assert(result<15); //post-condition
         return result;
    }
}

class B extends A 
{
    public int foo(int x)
    {
         assert(0<x<5); //weakened pre-condition
         ...
         assert(result<3); //strengthened post-condition
         return result;
    }	

}

References

1. Cunningham & Cunningham, Inc., Design by Contract
2. University of North Carolina
3. Eiffel Software, Design by Contract
http://www.cs.usfca.edu/~parrt/course/601/lectures/programming.by.contract.html