CSC/ECE 517 Fall 2009/wiki 3 1 SJ: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 7: Line 7:
==The advantages of Contract Programming==
==The advantages of Contract Programming==


    * A better understanding of the object-oriented method and, more generally, of software construction.
* A better understanding of the object-oriented method and, more generally, of software construction.
    * A systematic approach to building bug-free object-oriented systems.
* A systematic approach to building bug-free object-oriented systems.
    * An effective framework for debugging, testing and, more generally, quality assurance.
* An effective framework for debugging, testing and, more generally, quality assurance.
    * A method for documenting software components.
* A method for documenting software components.
    * Better understanding and control of the inheritance mechanism.
* Better understanding and control of the inheritance mechanism.
    * A technique for dealing with abnormal cases, leading to a safe and effective language construct for exception handling.
* A technique for dealing with abnormal cases, leading to a safe and effective language construct for exception handling.





Revision as of 21:54, 18 November 2009

Advantages and Disadvantages of Programming by Contract

Introduction of Contract Programming

Contracts are a breakthrough technique to reduce the programming effort for large projects. Contracts are the concept of preconditions, postconditions, errors, and invariants.

The advantages of Contract Programming

  • A better understanding of the object-oriented method and, more generally, of software construction.
  • A systematic approach to building bug-free object-oriented systems.
  • An effective framework for debugging, testing and, more generally, quality assurance.
  • A method for documenting software components.
  • Better understanding and control of the inheritance mechanism.
  • A technique for dealing with abnormal cases, leading to a safe and effective language construct for exception handling.


Example of If statement

public class Operator
{
    string operation;

    public int Execute(int x, int y)
    {
         switch(operation)
         {
             case "Add":
                 return x + y;
             case "Subtract":
                 return x - y;
             case "Multiply":
                 return x * y;
             case "Divide":
                 return x / y;
             default:
                 throw new InvalidOperationException("Unsupported operation");
         }
    }
}

In such example of conditional statement on operator, we see that: if we want to reuse function "add" operator in the other code segment, we have to reuse whole Class operator with the value "Add". And if we want to add a new operation "Power", we need to code in the implementation of Class Operator.

Idea of Polymorphism

Facing the problem of the conditional statement, people[2] come up with refactoring method called 'Polymorphism'. The idea of Polymorphism is to replace the highly functional relationship with the subclass override procedure under abstract class. So subclass is created to encapsulate each function in the conditional statement and the conditional relation is replaced by override a common abstract class. The advantage of such idea is to separate the functionality.

Definition of Polymorphism

According to [1], Subtype polymorphism, almost universally called just polymorphism in the context of object-oriented programming, is the ability of one type, A, to appear as and be used like another type, B.

The primary usage of polymorphism in industry (object-oriented programming theory) is the ability of objects belonging to different types to respond to method, field, or property calls of the same name, each one according to an appropriate type-specific behavior. The programmer (and the program) does not have to know the exact type of the object in advance, and so the exact behavior is determined at run time.

Example of Refactoring Conditional Statement with Polymorphism

  • Before refactoring
public class Operator
{
    string operation;

    public int Execute(int x, int y)
    {
         switch(operation)
         {
             case "Add":
                 return x + y;
             case "Subtract":
                 return x - y;
             case "Multiply":
                 return x * y;
             case "Divide":
                 return x / y;
             default:
                 throw new InvalidOperationException("Unsupported operation");
         }
    }
}
  • After refactoring
public abstract class Operator
{
    public abstract int Execute(int x, int y)
}

public class Add : Operator
{
    public override int Execute(int x, int y)
    {
        return x + y;
    }
}
public class Subtract : Operator
{
    public override int Execute(int x, int y)
    {
        return x - y;
    }
}
public class Multiply: Operator
{
    public override int Execute(int x, int y)
    {
        return x * y;
    }
}
public class Divide: Operator
{
    public override int Execute(int x, int y)
    {
        return x / y;
    }
}

References

[1] wiki page of "Design by Contract", http://en.wikipedia.org/wiki/Design_by_contract

[2] Rene Santaolaya, Olivia G. Fragoso, Joaquín Pérez, Lorenzo Zambrano, Restructuring Conditional Code Structures Using Object Oriented Design Patterns, Lecture Notes in Computer Science.

[3] Refactoring conditional statement, http://sourcemaking.com/refactoring/replace-conditional-with-polymorphism

[4] Object Orientation Design, http://en.wikipedia.org/wiki/Object-oriented_design