The best way to approach a C language problem is to consider it in three major stages:
1. Problem analysis and program design - about one-half the total time;
2. Writing the program itself - about one-quarter of the total time;
3. Testing and debugging - the time remaining, about one-quarter of the total.
Most students tend to skimp on the first part and merge the other two into an unending sequence of "try this" and "try that", until something happens to work. Sometimes it’s not really understood why it finally works (if it really does)!
The solution is to use tools like pseudocode to sort out how to actually write the program.
Analyze the problem
This may sound easy, but it’s the part most often neglected. Read over the lab carefully. Now read it again. Read it a third time, and try to write out (on a separate piece of paper, or using a tool like Word) an outline of what you believe is required. From that, list items you are unclear on, or parts that appear......
Join Now or Login to view the rest of this paper.
Approximate Word Count: 336
Approximate Pages: 2 (260 words per double-spaced page) |