exit button

CSC 630
GRAPHICS SYSTEMS
Format - Project Presentation

schedule | syllabus | format | style
project 0 |project 1a | project 1b | project 1c
 | project 2a | project 2b| project 2c
class projects

Format
Your projects reflect you. Make them professional.  Turn in all materials in a new pocket folder. Label your folder clearly with your name, course number, and section number printed on the outside. The folder can be reused for every project if kept clean.

Include the source files. They should begin with your name, the date, the course and section number, the name of the program, the compiler you are using, the path to your executable (verified that the world can run it), and the purpose of the program. See Basic Style and Documentation Guideline.

With every project type a one-half page informal discussion for the instructor that may include:

  • Specific programming & system problems (& solutions).
  • Modifications from problems with original design.
  • Unanswered questions that arose from the project.
  • General comments and conclusions.

Program test runs.  Turn in considerable test cases to demonstrate the correctness of each program. 

  • Internal comments in the program (//comment) should be clear enough to explain the operation of the program to anyone with some computer background

  • Descriptive identifier names should be used to make the program more readable.  Comment on the purpose of every variable that is not self-commenting. Separate every function with a commented header explaining what the function does.

  • Annotated comments (comments handwritten on the right side of the testing) can be made for the reader and highlighted with a yellow marker.  This is good for explaining program tests and pointing out extra credit.

  • File separation makes a program readable.
Header File
Separate the declaration of a function from its implementation with a header file. It must be well commented with constants (#defines), datatypes (typedef), global variables (minimize), & function prototypes.  The actual C++ code details are not put in the .h file, but are put in the .cc files. 
Main File
Separate the main function from the rest of the code by writing it first in your project calling the other functions.  It should be short, well commented, call the many utility functions in p1.cc, and contain the main event loop:

                for(;;)                      /*escape from loop when worm dies or fills the screen*/
                {
                      GetMove();
                     -----/*call functions as needed*/
                }
EVERY FILE, FUNCTION, PROCEDURE, AND PROGRAM WRITTEN IN THIS COURSE MUST BEGIN WITH A SHORT COMMENT ON ITS PURPOSE. IN THE PROJECTS AND THE EXAMINATIONS YOU WILL BE PENALIZED IF YOU OMIT COMMENTS.
top