Control Change Process

Control Change Process

When the current software package reaches its end life by either its limitations for what

the company needs to do, or by experiencing technical difficulties, the company has to start

planning the software change. Once the decision is made that software change is needed, a

formal evaluation of the extent of the projected transformation will have to be executed. To be

able to successfully implement the changes, all parties involved need to grasp the full extent of

doing those. The resources (human along with financial) need to be allocated and all the “side

effects” by the change need to be understood. “Side effects” simply mean the new relationship

between the suggested change and the related systems, protection of the integrity for all systems,

how any users might be affected, and the duration of the effects to those users.

After the evaluation, a formal change request will need to be produced. This form will

offer detailed description of the problem to the software developers, what modifications

are preferred, and what the company’s expectations are. The change request needs to be

precise because it will serve as the binding contract between the company and software

developers in regards to the expectations, and informed about the progress of their

efforts in form of version control sheets, design documents, and the source code. These serve as

a template for the company in their decision whether to pursue further changes.

After the new software is developed, implementation setting needs to be determined. The

company might opt to implement the changes in the live setting, which simply means that the

changes are going to be made while If the changes prove to be too much of the hindrance to the

company to the extent that the company might not be fully operational, changes might get

implemented and tested offline. A lot of times, companies would take down parts of their system

and implement the...