CSC/ECE 517 Fall 2009/wiki3 9 lkf

This is currently work in progress, please do not review yet

---

Non-Redundancy Principle

---

Topic: Non-Redundancy Principle

Topic Description: Programming by contract, and design by contract, are well covered in Wikipedia and across the Web. But the Non-Redundancy Principle, an important part of programming by contract, is not. Explore the applications and implications of the principle that says that the body of a routine should never test for the routine's precondition.

---

Introduction

The Non-Redundancy principle indicates that subroutines must never test for the validity of that which is stated as a precondition for the subroutine's execution. A precondition is a property that must be true for a subroutine to execute successfully [3]. The subroutine itself should not include code to verify that the preconditions for its execution are met by the given input. According to the non-redundancy principle, checking for preconditions is the responsibility of the client code. The most widely used definition of the principle is given by Meyer, who states, "under no circumstances shall the body of a routine ever test for its precondition." [3]

For example, a routine that calculates the square root of a number would violate the Non-Redundancy principle if its code tests to make sure that the input given is not a negative number [8].

Example

A common way to implement preconditions is to use the assert command, for instance in C#...., in Java...., in Ruby ...

According to the Non-Redundancy principle, testing for the same precondition should not occur more than once in the code-base, hence eliminating redundant code. The Non-Redundancy principle is part of the [Design by Contract] methodology, which proposes that the relationship between a class and its clients must be defined in terms of a formal agreement that clearly states the responsibilities and duties of each party [5]. The agreement may be enforced or guaranteed with the use of preconditions.

Proper application of the non-redundancy principle results in the code shown in the next example:

• • • • insert good code here

Preconditions may be of two types demanding and tolerant. Demanding preconditions place the burden on the client routine to ensure that the precondition for correct execution of the subroutine is met, i.e. the validation code is in the calling routine. Tolerant preconditions place the burden on the subroutine to ensure that the precondition for correct execution of the subroutine is met, i.e. the validation code is inside the subroutine [10]. Adherence to the non-redundancy principle stipulates that the same condition should only be tested by either demanding or tolerant preconditions but not by both.

Here I may give an example of tolerant preconditions and demanding preconditions using the same Square root example.

Applications of the Non-Redundancy Principle

Among the reasons for adhering to the non-redundancy principle we can count the following:

• Ease of maintenance due to simplified code.
• Less complexity because a particular condition is only checked once rather than in multiple places throughout the code. * The expectation is that by having components adhere to contracts that clearly define each component's responsibilities the code will be less complex.
• More reliable code because there are less places where the same validation can be incorrect.
• More reliability is expected because the number of points where failures can occur, i.e. incorrect code, is reduced.

Implications of the Non-Redundancy Principle

Although the use of the non-redundancy principle on software design has definite advantages, its application has are certain implications which must be considered. Possible consequences or implications that result from the application of the Non-Redundancy principle in a software development effort include the following:

The application of the principle may result in the introduction of vulnerabilities.

The resulting software may me more prone to having faults.

The principle is in opposition to the recommendations provided by the [Defensive Programming] techniques that are part of traditional software engineering methodologies. Defensive programming states that code should be written to include the necessary validations and preventive code to ensure its correct operation.

Supporters of the non-redundancy principle argue that the use of defensive programming techniques could possibly result in too much code that checks for errors; however, the expectation is that such additional code makes the code more robust and that it will not introduce additional faults [9].

Summary

The non-redundancy principle is used in software design to propose software where preconditions are not checked at the subroutine level but rather at the calling routine. The advantage of such design is code that is simpler and easier to maintain. The non-redundancy principle diverges from the defensive programming techniques that are proposed by traditional software engineering methodologies. One could argue that the former approach results in code that is simpler and easier to maintain while the latter results in code that is more robust and free of faults.

References

[1] http://fox.wikis.com/wc.dll?Wiki~NonRedundancyPrinciple

[2] http://fox.wikis.com/wc.dll?Wiki~PreCondition

[3] Meyer, Bertrand (1997), Object - Oriented Software Construction, Prentice Hall, Englewood Cliffs, NJ, ISBN 0136291554

[4] http://www.actapress.com/Abstract.aspx?paperId=17535

[5] http://fox.wikis.com/wc.dll?Wiki~DesignByContract

[6] http://fox.wikis.com/wc.dll?Wiki~DefensiveProgramming

[7] http://synesis.com.au/publishing/monolith/glossary.html

[8] www.cs.caltech.edu/~cs141/2003/lectures/lecture5.pdf

[9] http://movingreally.blogspot.com/2007/05/non-redundancy-principle.html

[10] Lecture slides from the Software Design course in the Department of Computer Science at the Technion---Israel institute of Technology, available at: http://www.cs.technion.ac.il/Courses/OOP/slides/export/236700/yoav/eiffel_programming_by_contract_new.ppt

---

CSC 517 Fall 2009

Wiki 3 Assignment

Author: Newwolf