Aha! Another person who craves documentation. <img src="/images/icons/wink.gif" /> I'm in configuration management, so the things that come to me are "requirements documentation", "requirements traceability", "change control", and "change traceability". All three are vital. All requirements must be documented and traceable to the final product. Changes have to be controlled and must be traceable in each version of a product. The old saying is, "If it's not documented, it doesn't exist," and while that's obviously not literally true, if it's not documented there's no way of <i>proving</i> that it exists, that you know it exists, and that you understand what it is that exists. <div class="Discussion_UserSignature"> <p> </p><p><font color="#666699"><em>"People assume that time is a strict progression of cause to effect, but actually from a non-linear, non-subjective viewpoint it's more like a big ball of wibbly wobbly . . . timey wimey . . . stuff."</em> -- The Tenth Doctor, "Blink"</font></p> </div>