Implementation Plan

Project Implementation

Once the human resource information system (HRIS) is complete, it will go through the implementation process to ensure that it is a fit for the Riordan Manufacturing environment and that the users are oriented on how it works. There are several core activities that take place during system implementation that includes coding, testing installation, documentation, training, support, and maintenance. All this activities are imperative to the successful implementation of the system and are meant to support each other (Valacich, George, & Hoffer, 2009) .

The coding process is when programmers will turn the design specification in to a language that the computer can understand and interpret. Once coding commences, the testing process can begin and continue correspondingly. Software testing will be both manual and automated. Manual testing involves the examining of codes checking for occurrence of well-known bugs while automated testing checks for syntax, grammar and other routine errors. Most of the manual testing done is to help identify subtle errors. Other ways that manual testing checks for errors is through manual walkthroughs where the system will be reviewed for deliverables including codes and design specification. Walkthroughs will be done frequently and on a relatively smaller scope with the aim of identifying errors but not correcting them (Valacich, George, & Hoffer, 2009) .

Unit or modular testing is one of the automated ways that will be used to perform testing on the system. The unit testing will involve testing lone modules of codes using a compiler to check for any errors that may exist in the module; the modules will then be combined for integration testing. Once the HRIS system has gone through the testing phases above it will go through user acceptance testing where the users will typically verify and accept that they are satisfied with the application. Most of the user acceptance testing will be done on a beta version in which live data will be used in the Riordan users' real working environment. A system audit will be done by the internal auditors and members of the quality assurance group (Valacich, George, & Hoffer, 2009) .

During beta testing, recovery, security, stress, and performance will be checked on the system. This will help ensure that the system will protect from improper penetration, recover accordingly where needed, and perform optimally when under extreme pressure.

The system installation will take place in phases with staged and incremental model based on functional components and business needs. This will mitigate the impact of potential downtime and costs from system failure. The installation in phases will also help the project team identify any potential problems and address them before continuing with the next phases. Since the old and new processes will be running parallel during installation the two processes will be bridged to work in harmony. The installation in phases is expected to take five to six months before all of the human resources and the employees are on the new platform.

While the new HRIS is being tested and installed, system documentation as well as user documentation should be written. When the new system was being written, documentation on each module should have been created by the programmer detailing the code he was writing. These documents from all the modules can be used to form the system documentation. In addition to the programmer's documents, system design specifications, data flow charts, and any other diagrams that were used in the project should be compiled into the system documentation. These system documents will help future programmer and analysts pick up where the project left off if there are any changes or modifications that need to be made to the program. Without these documents, programmers would have to go through all the code to understand what was created before. Likewise, analysts will have to start the investigative process all over again.

User documentation will be created from the notes of programmers,