|
|
|
|
| Programming Time | A few minutes to several hours | Months to years - usually an ongoing process |
| Complexity | Relatively simple | Complexity at the level of large building architecture, aircraft design, the tax code, etc. |
| Reliability | Can be made almost error free | Will contain quite a few errors (bugs), some of them serious; but still very reliable |
| Users | Few, often the programmer | Many different users with varing levels of skill and a wide range of problems to be solved |
| Planning and Design | Not absolutely needed | Accounts for 75 to 80% of the total cost of producing the program |
| Documentation | Usually not required | An absolute necessity so the users can use the program and so that the program can be changed in the future |

Understand (define) the problem and what the solution must do. Develop a logical sequence of steps to be used to solve the problem. Follow the steps exactly to see if the solution really does solve the problem |
|
Translate the algorithm into a programming language. Have the computer follow the instructions, manually checking the results. If errors are found, analyze the program and the algorithm to determine the source of the errors, then make corrections. |
|
The program is distributed and used by one or more individuals. Modify the program to meet changing requirements or to correct any errors that show up in using it. |
![]() |

|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|

|
|
|
|
|
|

