The testing system plan that should be conducted by Susan will include compilation of the program, desk checking, unit testing, integration testing, and system testing. The first step of the system testing plan is the compilation of the program; in this step, Susan (the programmer) should utilize the Computer-aided software engineering (CASE) tool. This will enable her to establish a strong basis for developing a system that maintainable, defect-free, and high quality. It will enable Susan to appropriately design and implement the system.
The second step in the testing system plan is desk checking. This is conducted by the individual who wrote the program (Susan). The main purpose of including this process in the testing system plan is to enable Susan (the programmer) to verify the algorithm coding and logic before she launches the program. This will enable her identify or rather spot any logical errors that could deter the smooth working of the program or prevent it from working.
Once the desk checking is completed, Susan (the programmer) should conduct unit testing. Here, the module or individual program is tested to identify any execution errors for elimination. In this phase, the programmer should individually test files and the programs that interact with other programs before they can integrate them into the system. To determine the potential causes and location of program errors, the programmer can use software tools. Additionally, the programmer can simulate the outcome and result of each program through stub testing and display a message to inform if the execution of the program was successful or not. This step will ensure that such errors do not recur and that the program is safe from a possible abnormal termination.
After the programmer has performed the unit testing, the step that follows is the integration testing; the procedure can be done by either the programmer or the system analysts. This phase involves testing two or more interdependent programs. To conduct an integration testing, the programmer or system analyst can simulate an operation problem or unusual event by passing between two or more programs,, typical records followed by blank records. This procedure is critical in order to understand how and determine whether the programs interact appropriately with other programs as well as files individually. It is essential in checking how the program fits with other programs and also the customer.
The final step is to test the system, otherwise known as ‘system testing.’ In this step, Susan can involve the users, and IT management can be involved or rather engaged in the process. Here, the entire information system is tested, including all the typical processing situations; in particular, data is entered by the users, and these include samples of live or actual data, performing queries, and producing reports simulation the actual conditions of operation. The main purpose of the system testing is to guarantee the IT managers, the developer, and the users that the program has taken into account all the necessary features and also has met all the required specifications.
Question 2
For the new billing system, my suggestion is the pilot changeover, which will involve its implementation at a particular Personal Trainer Inc.’s selected location. The main reason behind the choice of this method is because it will still allow the running of the old system, including the pilot sites, for the entire organization. Further, this changeover method combines both direct cutover and parallel operation methods. That is, the system is only implemented in the entire organization only if it is successful at the pilot site, and this is done through a direct cutover method. This ensures that the system failure risk is minimized, given that the implementation is restricted only to pilot sites before being effected to the entire organization.
Additionally, the pilot changeover method is more advantageous to the organization, given that it is safer and less expensive for the reasons that the system is run only in one section of the entire system and for a limited period of time. Therefore, it will save the organization money besides ensuring the smooth working of the system by keeping the data safe.
In order to be more effective, the pilot exercise should be conducted in one of the departments in the organization whose services are less critical and is able to handle any system failure. For instance, the IT department would be more appropriate compared to the billing department. Even though the pilot changeover method reduces the system failure risk and assures the working of the new system, the pilot site is still susceptible to the imminent risk of total failure.
Further, it should be conducted by individuals who did not take part nor were directly involved in the development of the system. This will ensure the completeness and accuracy of the system evaluation process. In particular, evaluation can be done by users, and IT staff or the organization can opt to seek the services of independent auditors or an internal audit group. Also, the individuals implementing the pilot changeover method should allow the system to be in operation for some period of time, with six months being the most appropriate, before evaluating it for effectiveness. This is for the reasons that if the evaluation of the pilot system is performed too early or soon after the implementation, they will be unable to appreciate or learn the weaknesses and strengths of the new system.