Problem completion - constraints & criteria


The problem has been treated broadly up till this stage in order to derive as many candidate solutions as possible. It is now time to complete the problem, to focus on exactly what is required of solutions by way of constraints and criteria.

A constraint is more limiting than an equivalent criterion - the $10000 limit of constraint 'i' above leaves less scope for a solution than a criterion along the lines of 'cheap as possible' or 'minimum cost'. You should therefore try to increase the solution space wherever possible, by converting constraints into equivalent criteria. For example if Australia had adopted the criterion 'vi' above rather than the constraint 'iii' during the 1997 Kyoto talks then its stance would likely have attracted less criticism - ie. more folk might have been kept happy. Unfortunately many political decisions appear to be argued on the basis of constraints rather than criteria, thus antagonising whole sections of the community.

In this completion activity we are not interested in whether a candidate complies with a constraint or not, neither are we interested in how well a candidate satisfies a criterion - all we are doing is identifying and recording the constraints and criteria, so that they might be applied to candidates during later activities in the design process.

One of the most crucial tasks in the whole design process is to :

Ensure that ALL constraints and criteria are identified.

The constraints and criteria are determined by the wishlists of everyone who, and everything which will interact with the solution. A designer must therefore realistically visualise the solution as it progresses through its life stages, and anticipate these interactions together with the corresponding constraints and criteria. If other sources can assist with this task then clearly they should be consulted. A designer's incomplete knowledge of manufacturing processes for example is good reason for talking with a fitter and turner, for further reading, or for experimenting personally.

One of the reasons for mounting D&B competitions is that members of student design groups are involved with all life stages of their solution, and so must themselves establish the completion wishlist. Although other folks' agenda are not addressed, students still have to foresee the solution's future and to set constraints and criteria accordingly. These should not have to be inferred during later activities, but must be written down in black and white in the present completion activity.

One common criterion which is often overlooked is the need for simplicity. Here are a couple of cases where simplicity features :

Keep it as simple as possible
 
If you don't identify and write down all constraints  ( we must be able to make it) and criteria  ( it's got to be as simple as possible ) then you'll most probably overlook them when it comes to the next step, practicalisation, resulting in a less than optimum solution.


|   Notes contents   |   chapter index   |   previous   |   top of page   |   next   |

Valid HTML 4.0!     Copyright 1999-2005 Douglas Wright,   doug@mech.uwa.edu.au
      last updated May 2005