Software Configuration Management Plan

Software Configuration Management Plan

1 Introduction

1.1 Purpose

Development of a Software Configuration Management Plan is the main purpose of this document. This document will be used through out the software development life cycle. The management of changes can be furnished by this document. This will also help us to maintain quality of the project by keeping track of changes.

1.2 Skill Level and Qualification

This software is not developed for any firm. This is final project of Maser degree. This project is requirement of Degree. This software will be developed in VB 6.0 technology will be used to develop it. Books and lot of related material is required for this project.

1.3 Resources

This project will be developed by Wajid Ali Hadri who are responsible for managing all activities.

2 Standards

Refer to SQA plan, section 4.2

3 Configuration and Identification Following configuration item has been identified for the project:

Software Required Specification

Data Flow Diagram

Class Diagram

Software Design Documents

Architecture Design

Database Design

Implementation

Cane Procurement Planning Module

Login Module

Cane Procurement Module

Cane Weighting Module

Cane Accounting Module

Software Testing

Unit testing

Manual testing

Integration testing

4 Change Control

4.1 Change Control Procedure

If any firm desires to buy this software, meeting will arrange with client to verify any procedure chang in software. The requirement will be discussed with client and verified .if any change is desired a report will be generated against that module.

4.2 Reporting Documents

If client desired to make any change, a document will be produced. A change will be noted and verified in that document. The document template is as:

Software change RequestS-NoPage:

Name of Originator:Phone#Date:

Project :Version:

Reason for change

Change Description

Reviewed bySignatureDate

Change Approved (Y/N)Name:SignatureDate

5 Storage /Handling

All change documents are stored on local hard drive. Any change made to these documents will be assign new version.

6 Tools

No any special Tool for SCM will be used.