PROGRAM GUIDELINES
1. All program files should begin with comment lines that identify the following information:
2. All modules should begin with comment lines that identify the following information:
3. Variable names should be meaningful & a comment should be included with each declaration.
4. Use blank lines to make the program easier to read.
5. Each statement should be on a separate line.
6. All input statements should be preceded by a user friendly prompt.
7. Proper indention of program structures must be used.
8. Only one entrance and one exit are permitted in the main program, modules, and loops. No GOTO branch statements may be used in the program unless explicitly instructed to do so.
9. The main program and modules should be a maximum of one page in length. Little or no detail code should exist in the main program.
10. All programs must be accompanied by the documentation specified in the assignment - algorithm, structure chart, testing, and/or output.
11. All hand written work that is turned in should be on 8.5 X 11 inch paper, use one side only.
12. All work should be turned in using the lab folder. All printouts should be readable, dark ink. Be as neat as possible - YOU WILL BE GRADED ON THIS, TAKE PRIDE IN YOUR WORK!!
13. You may seek help on your assignments from classmates, peers, teachers, tutors, and me. You must be aware of the difference between helping and cheating. Please indicate on your assignment if you received help or gave help and the person's name. (This keeps everybody honest) If you are unclear about what is considered cheating, please see me!
14. Program specifications will be provided for each program. The specifications may not include all the details about the program. As programmers it is your responsibility to fill in the gaps by asking questions. Do not assume anything! We will discuss program details in class. It is your responsibility to make note of these details and implement your program accordingly.
15. Programs will be graded on the following: