Documentation:    
·         Code listings of all in-house generated applications. These code listings can be either as hardcopy printouts (not the most efficient) or archived text files on removable media such as tape. Code listings should contain a header that describes each module, lists the author, lists inputs and outputs. Code listings should also contain comments that explain each section of the code and particularly describe any "special" code sections that are not obvious in function or content.
·         Runbooks that document each executable generated for the application. Runbooks contain installation instructions, operational instructions and troubleshooting guides.
·         Important project documents. Important documents consist of, but are not limited to, Design documents, Change logs, System Integration Test results, User Acceptance Test results and correspondence logs.
·         Skill Sets. Documentation does not end with pages of text describing application modules. Skill sets must also be documented, the management of the entire project will likely change by the time it is reactivated, documentation of required skill sets will ensure the proper re-staffing occurs.

SEE CODE DEPOT FOR FULL SCRIPTS

http://www.rampant-books.com/book_1002_oracle_tuning_definitive_reference_2nd_ed.htm