brentwoodhigh.com

cplusplus.com | Java Documentation | Site Stats
APCS schedule | APCS LogIn | APCS Forms | APCS Resources | APCS Archive | APCS Stuff
C++ schedule | C++ LogIn | C++ Forms | C++ Resources | C++ Archive | C++ Stuff
Adven schedule | Adven LogIn | Adven Forms | Adven Resources | Adven Archive | Adven Stuff
Stats schedule | Stats LogIn | Stats Forms | Stats Resources | Stats Archive | Stats Stuff

IDOC Requirements

The top of each source file should contain:

1. First and Last Name
2. Description of the Program
3. Starting Date
4. Location of the completed program - user drive, local computer, external drive, home computer)
5. Contributors to the Program - List the name of those who have assisted with a general statement of where help was received. INCLUDE all that assist. What is a Contributor?

Source Code Documentation

1. comment following each brace } indication which block is closed. Examples :

} //end while
} // end for i
} // end main
} // end calcAvg

2. functions in C++

Short description of the function is intended to accomplish.
Any preconditions - we will assume the precondition - arguments are not uninitialized variables.
Post conditions - Changes in the calling function other than what is returned by the function.
Expected framework for a function's IDOC

//Desc -
//Pre -
//Post -


3. Sample Output

Sample output is required most programs. Sample output should be copied and pasted as a comment after the closing brace of the main function.
If the program outputs to a file containing more than 15 lines a path to the output file is required.

 

 

 

 

 

Updated: Friday, November 23, 2007 7:53 PM

About Us | Site Map | Contact Us | ©2005 brentwoodhigh.com