Implementation Case
Service Request SR-rm-022, Part 3
Implementation
Implementation begins with turning the ideas for the system into a physical working system. Writing the code for the software that will run the system, including the documentation for that code, is the first step. This code is written for any software the company will use, whether written in-house or purchased from a vendor. Purchased software will need tweaking to enable current system compatibility with the new. There will be fine tuning required for implementation of additions, corrections for errors, and new problems that surface after implementation.
Coding and Installation
For Riordan, this coding will require an upgrade to both the hardware systems and software. Writing an RFP to determine the best vendors for the project is the first step (Cliff Consulting, 1992-2007). Once the vendor is chosen, the servers will be the first hardware put into place. The software will need installation and testing next. This phase of the project needs to run parallel to the current system until testing is complete. At this point a beta test run with one or two employees trained with the new system will allow the analyst to finalize testing and make any corrections based on the problems that occur in the beta tests (Pataki, Dillon, & McCormack, 2001).
As the testing gets to the alpha phase the new client computers installation can begin giving these users an opportunity to learn the new hardware while continuing to run the current software systems. Once the beta testing is complete and the employees trained, the new systems will be released to the client computers and the current system disengaged.
Along with the client computer installation the team will put the remainder of the systems in place. The VOIP telephones, NAS, backup power, routers, printer’s switches, and gateways will be installed but not engaged until after beta testing is complete (Apollo Group, 2013).
Throughout this phase of the project documentation of the processes will be created. This documentation will give future analysts and maintenance the knowledge of how the system was developed and answer many questions about why it developed this way.
When the server installation is complete, they must be tested for compatibility with the current systems that will be reused. An example would be the satellite that connects the USA with China. This link must be stable and secure before going online for regular business.
Testing
Testing will take place from the beginning of the implementation phase to the end. The first series of tests to run will be inspections for known errors in language, walkthroughs to see what the code does, and desk checks with paper and pencil to make sure the code does what is expected.
The next test to run is unit tests at