Introduction

System implementation refers to the whole process of putting the system in place to the time the systems starts working. System implementation process goes through six stages, they include:  application development, requirements documentation, system testing, data conversion, system users training and system changeover. In every stage of the system implementation process, a new task is introduced.

System implementation

This system should be developed with the knowledge that it will be used by all the customers of the bank throughout the country of the country, Gray and Schunn, (2009). It should therefore be in a position to process transaction of all customers when requested. The software should have a user friendly interface, Tutes. However, the following should be documented: activities during implementation of the system, which is to execute the activities, time frames for the specific duties to be accomplished, Ka.

System requirements include the necessary hardware and software in the implementation process which include servers, computers, and related equipment as well as the non computer equipment.  They should meet the specified requirement. The software specifications should include configuration and hardware compatibility, Anderson.

System testing will involve the process of installation experimenting to see it the system performing as expected. Once the system has been tested and confirmed that is working, data is converted conversion from the old system to the new system. Incase during the process of data conversion all the data is not converted as expected, a backup should be made for the data that has not been converted.

Prior to usage of the system, the people who will use the system should be trained, that is the staff should be given relevant training on the uses and interface navigation. Staff should be trained on the connection and uses of the hardware, how to get help from the system and how to maintain the system. The ICT technicians should be given extra training on repair and maintenance of the system. If a commercial trainee is to provide the training, make sure that they get the right schedule to follow. When the system and the staff are ready, the system should be changed over from the old to the newly implemented system. If everything is ready, direct changeover is recommended, Ian, (2010). If there are issues that need immediate attention in the system, they should be attended with the seriousness it deserves.

Source code

The source version control process will have a specific set of code commonly used in the internet.  There should be a main code line for every application created for the organization. These codelines will be used in managing software change and version control with each having unique purpose. There shall be main codeline and base codelines so that the main codeline controls the base codelines. A policy should be attached to each individual codeline. All the codelines shall not be stringently tested except the production codeline.

 Development environment shall be used by programmers in coming up with codes and testing. On the other hand, QA environment will always be used by the customer to confirm the well functionality of the business. In the production environment,   software facilitates the usage by the customer and therefore at this point, changes must be stringent the most. Braching will only be allowed when there is absolute demand from the system.

For this project to succeed, the following requirements should be met. To begin with, there should be enough human resources equipped with the skills it takes to accomplish the tasks. There should also be deliverables which should be are produced inform of outputs. There should be a monitoring and controlling plan to ensure that those problems that arise during the execution process are solved immediately, Jacobsen.

To provide software control, there should either be a Source Code Management (SCM) or Software Version Control (SVC) system for controlling versions and changes. To facilitate returning to the initial state in the code, there should be a control system for software change. To void issues like overwriting and avoid multiple changes in a file at the same time, the respective files should be locked when programmers are working on them. File relating to code must be brought under version control together with their files for specific requirements, Boaitey.

Developers should create personal folders in which they can place codes that they use of experimenting which they are not part of the main project. It can only be used for tools used in building but not those that are the requirements of the project. Project codes should not be placed here. Whenever there is a software request change, a unique tracking number should be created for it. Authority should be created which shall be responsible for approving all changes in the software, Boaitey. Bureaucracy and cost can be successfully managed here.

The system installation will require training for the staff who will be using the system and technicians who will be controlling the system. Technicians who will be responsible for controlling the system shall be trained to fully understand the system as well as solve problems that are likely to come up as the system goes live. Manuals should be supplied to these members of the organizations so that they can read more and understand the system in-depth, Boaitey.

arrow_upward