This document describes the process that is to be used for requesting and managing changes to work products created or maintained by the members of a project. Change control contains next: Proposed Changes, Basis of Proposed Changes, Approved / Disapproved.

Change Control Log is used to provide a record of all changes requested and decisions made. It contains such information as ModuleName, AssignedTo, DueDate Status and Comments.

Change Request Form is used to document details of the change, including the business case. It contains such information as Costs, Timeline, Change Request Assessment and Contractual Agreement.

Business Approval Form is used when team members need approve a requested activity from the Customer side. It contains such information as Customer Name, Project Name, Estimated Expenses, Proposal Submission Date.

Business Approval Checklist is a document used for defining a list of items you need to verify before getting an approval of a requested activity from the Customer side. It contains such information as Customer Name, Project Name, ProductValue, ServiceValue, SupportValue, StartDate and EndDate.

Data access control form is a document that can be used to regulate who or what can view or use resources in a computing environment. It contains such information as Person, Development, TestDept, PM, Finance, TestDate, Cases and Status.

A checklist helps to guide the testers that identify and plan software acceptance testing. Checklist deals with acceptance management testing that is performed throughout DLC. Its task is to check whether the application works in accordance with requirements, has no serious bugs and transfer responsibility to the owner.

Specifies the acceptance criteria, e.g. [System] is created by [Name of Company] and should be approved by [Name of Customer]. [Name of Company] confirms that the System fulfills all the requirements of the contract.

The Acceptance Test Plan verifies that the final product (i.e. the system that has been developed) meets the customer’s business requirements. This document outlines the steps required to prepare an Acceptance Test Plan. It also ensures that all components of the system are tested.

Contract Review Form is designed to assist in reviewing and negotiating proposed contractual provisions. It contains such information as Customer Name, Project Name, Date, Project Number, Contract Criteria, Documentation, Communications, Functional Specification, Quotation, Project Plan, ContractDocuments and Contractual Liabilities.