My favorites | Sign in
Project Logo
                
Search
for
Updated Oct 29, 2008 by siev...@wells.edu
ProceduresCoverPage  

Copy & paste this, one per procedure; Name your page with your procedure name.

Procedure/routine documentation: Name of Routine:

Writer's name:

Most recent update Date:

Credits: Who helped with what.

Brief description:

Inputs: and Preconditions:

I use:

Outputs and Postconditions:

I Change in computer:

Procedure(s) I call:

Routine(s) that call me:

Add to Memory Globals sheet if necessary

Status: (Top level, written but not tested, buggy, CLEAN AND DONE)

Internal documentation: top level description + Code, with "test driver" and results of test runs, and should follow this:

Sign your code; comments top and bottom

;--- --- E.D. Student begin--- --- , etc.


Sign in to add a comment
Hosted by Google Code