System Development Life Cycle
As a part-time intern, I have found myself trying out new systems that have been developed and deployed by the parent company. My job entails testing these new systems to determine if they have any bugs and if they will remain viable when rolled out on a large scale throughout a client’s company. My job is known as the testing phase and it occurs concurrently with the other phases of the system development life cycle.
Last April, I was asked to test a new accounting system to determine if it could handle the accounting workload for a small bakery. As usual, I tried to assess if it was capable of handling multiple requests at a time, giving the right results, and if the user interface was user-friendly. I had to involve some of the bakery employees to test if they were comfortable with using the new accounting system.
Overall, the experience was enlightening as it helped me discover what employees are looking for in a new system. They are looking for a system that is quick to compute calculations and output the relevant results in real time. They are also looking for a system that is easy to navigate and one that is not prone to jamming up or slowing down. The experience also re-emphasized the importance of my job in the testing phase. This phase allows the company to identify and assess the functionality of the proposed system as well as any risks that might undermine the system.
Generally, the system development life cycle is essential for the successful implementation of a new system. Even though most IS departments having a backlog of work and the SDLC might cause additional delays, the process is critical to the success of a system. The process helps to cut down costs that the company would have incurred if the system was developed and implemented haphazardly without a formidable plan to back it up (Rhodes, 2012).
Rhodes, D.L. (2012). The Systems Development Life Cycle as a standard: beyond the documentation. SAS Global Forum 2012. Retrieved on 26/11/2015 from http://support.sas.com/resources/papers/proceedings12/194-2012.pdf