Software Maintenance & Change Control Plan

Table of Contents 1.<Tab/>Purpose<Tab/>3 1.1.<Tab/>Maintenance<Tab/>3 1.2.<Tab/>Change Control<Tab/>3 2.<Tab/>Scope<Tab/>4 3.<Tab/>Reference Documentation<Tab/>4 4.<Tab/>Change Management Process<Tab/>5 4.1.<…showed first 75 words of 1112 total…

…showed last 75 words of 1112 total…Location A database will be maintained of Software Change Requests and their corresponding documentation, including (but not limited to) version control information, libraries and references, project meeting minutes, test data, etc. 7.<Tab/>Signoffs The Software Development Team manager or program lead will have the final signoff authority to mark a change project as 'closed.' A project is generally considered closed when the Software Change Request is rejected or implemented successfully.