| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
5.9.3 Change Documentation Change documentation is a decision memorandum specifying the changes and justification with the accompanying IT spreadsheet reflecting the changes. The memorandum will also state that the changes to the program are approved and should be reflected in a control log. A quick sidebar for the real-world.. Documentation is a science. Scott W. Ambler, called Agile Documentation, found in the footnote, created the most successful model I have seen468. An example: The basic trade-off is the "security" of having the document against your trust in its accuracy. What would you rather have, 2000-page system document that is likely to have a significant number of errors in it but significant details or a 20-page, high-level overview? This type of documentation presents an audit trail of management approval of system changes before they were made. __________________ 468. http://www.agilemodeling.com/essays/agileDocumentation.htm
Home - Table Of Contents - Contact Us CertiGuide for Security+ (http://www.CertiGuide.com/secplus/) on CertiGuide.com Version 1.0 - Version Date: November 15, 2004 Adapted with permission from a work created by Tcat Houser et al. CertiGuide.com Version © Copyright 2004 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||