Software and Understanding

1.1. The problem

The problem should be completely understood before formulating the solution.

• If the problem is not understood,
  1. the solution will be wrong.
  2. bugs in the solution will be difficult to understand and correct.
• If the problem is understood
  1. the solution is likely to be more like the correct one
  2. errors can be understood and the correct bug fixes can be found.

1.2. understanding the problem

Understanding the problem requires

1. writing down the problem — sometimes the problem needs to be written down before trying to understand it.
2. understanding the functional domain which the problem is a part of.
3. understanding the definitions of the terms which have been used in writing the problem.

1.3. thinking up a solution

Trying to find a solution requires

1. good working knowledge of the technical tools that would be used
2. making sure the tools being considered are the right ones