Mothballing a Database Project Oracle Tips by Mike Ault

Documentation:
Documentation is the last part of mothballing a project. What must be documented? Essentially all of the thought and creative impulses that put the project together. If a CASE tool was used, much of this will already be present in the CASE tool's files. If a CASE tool isn't used this information must be extracted from the developers and designers. Unfortunately the first thing usually done in a project shutdown is the release of any and all contract personnel, in most cases these will be your expertise brought in for the project. Do not let anyone go until they have fully documented their sections of code. In addition you should capture their thoughts on additions, changes and improvements with the application modules for which they are responsible.

An example documentation set would consist of:
·         Executive Overview. This document explains the project, the project components and gives a brief explanation of the rest of the documentation set. It should contain the locations for all pertinent documents and archives.
·         Hardware overview. This document contains all of the specifications for the system hardware. The document should contain required CPU, IO, and Disk requirements as well as documenting networking needs.

---

For more information on this topic, I recommend Don Burleson's latest book "Oracle Tuning: The Definitive Reference".  You can buy it direct from the publisher for 50%-off and get instant access to the code depot of Oracle tuning scripts: