and manpower. There are many factors affecting feasibility, including budget and time constraints, as well as availability of manpower skilled enough to complete the task. It is only after feasibility has been determined that we finally begin to put things into the context of actual code. Now the developers must think about such issues such as what type of interface the program is to have with the user, which protocols the program will communicate with, etc. Another very important activity in this stage is defining classes, or categories under which your objects will be organized. Classes are key in separating different types of objects by attributes and behavior, which in turn allows the programmer to save time and effort redefining object attributes. Classes also help the programmer determine the restraints of the application, or if you will, how broadly the program can attack the problem. IMPLEMENTATION:The final step of the process is sitting down and actually writing some code. Of course, before the developer can start that, he/she must first decide which language to use. Although it all ends up 1s and 0s, the language in which a program is written has a lot to do with how effective the program is, how quickly it runs, and how easy (or difficult) it is to code. By this time there should be little guesswork left as to how to enter the code. The developer has in front of him/her all of the specifications, outlines, functions, variables, and classes to use, the whole program has been planned out. It is now simply a matter of translating that into code the computer can understand. Therein, then, lies the real reason to why all of this preparation is necessary before writing the first line: When authors write books, they cannot simply open up a manuscript and begin typing the first page they must already have planned out the elements of the story, plot and characters. In the same way, a programmer approaching a complex problem will ...
