Organizations and businesses utilize different forms of information systems in order to support the abundance of processes needed to fulfill their business functions. Every type of information systems consists of a particular focus or purpose, and each part has a life of its own1. The “life of its own” theory is formally known as a systems development lifecycle and it contains the integrated method of planning, building, deploying, using, updating, and maintaining an information system1. When looking at developing a new information system, the system itself involves various different, but relevant activities. Such phases, or activities, typically included planning, analysis, design, and implementation. The purpose of this paper is to break the implementation phase down into the before and the after.
Implementation of an information system consists of the development, installation and testing of the system’s components as well as the delivery of the system into production. The objective of system implementation is to construct a system, install it, replace the old system, prepare the new system, and create user documentation, train users, and post implementation evaluation of results. During this phase, it’s also involves a closedown the entire project. Before the closedown and changeover occurs, the system must be tested, documented, users trained, and the existing data should be converted. The five major tasks during the implementation phase are coding, testing, installation, documentation and training. The purpose of this phase is to convert the physical system specifications into working and reliable software and hardware, document the work that has been done and provide assistance for current and future users.
Coding is the process by which the physical specifications created in the preceding phases are converted into working computer codes by the team of programmer’s. Coding is a task where all of the designs during the previous phases will be programmed using a software that had been defined before. During the coding phase, each program module will be tested individually, then as part of a larger program, and then as the complete system. At the same time, the team should come out with a system and user documentation to help users in using the system. There are several sub activities involved during coding activity. The sub activities involve system analysts, programmers, system designers and database administrators. Such activities are planned simultaneously with other activities; network building and testing, database building and testing, install and test new software, write and test new programs.
After the coding process, programmers must test each associated program to ensure it functions appropriately. Subsequently, programs are then tested collectively, and lastly the development team tests the entire system. The first act in testing is unit testing. By definition, unit testing is the testing of an individual program or module1....