Documentation is vital in every circumstance. On the other hand, documentation in improving the framework is crucial. Often, an extremely significant, and many times overlooked, task is recording the internal programming configuration with the ultimate goal of future maintenance and upgrades. A project agreement could also distinguish the type and level of documentation that teachers must produce during each phase or period of the activity. Associations can also provide detailed documentation for each framework under management. Good documentation improves an association's ability to understand utility, security and control characteristics and can improve its ability to use and maintain the framework. Documentation may also incorporate point-by-point representations, documentation changes, and work directions (FFIEC 1996). There are two basic types of documentation, structure and customer documentation. Framework documentation incorporates the data needed for ongoing maintenance and operation of the PC framework. Examples of framework documentation include items such as specialized graphs, flow graphs, database management structures, and help records. Customer documentation should not be difficult to review and accompany. Support records are regularly composed in a regulated agreement and are made for clients of any level to accompany. Documentation is vital as it provides data that staff can accommodate into the new framework. It ensures the progression of framework improvement after the framework is passed on for use and the first programmers or designers proceed to different tasks. Customer documentation is necessary to reduce the amount of… half the paper… maintenance and improvements as dictated by occasional audits. For non-specialist outcomes, support can be the continuation of a helping process. Changes in nature, client and customer requirements, or design may prompt business process changes or reengineering activities to accept or review the business process. Support could also incorporate advances into the framework based on technical advances and could be addressed through framework updates or refresher activities. Constant change is a prerequisite of the sustainment phase and is inspected by distinguishing models and execution measures and archived in enterprise status audits. Change management and quality certification are also a necessity at this stage to ensure legitimate documentation of the framework set up comprehensively and correctly (House of Representatives 1999).