Service Request SR-rm-004
June 17, 2011
Service Request SR-rm-004
The purpose of this paper is to incorporate the transition from the design to the implementation phase. The implementation phase is the fourth phase of the system development life cycle. This phase is refers to as the decisive moment. All the work that has been done up to this point to bring an idea to realty is coming to life. This phase is most expensive and time-consuming of the previous three phases. The work done in this phase is tedious, and requires the strictest focus to the attention of detail. The major activities involved in this area are coding, testing, installation, documentation, training, and support. The purpose for this these activities are to transform the work from the previous phase into a physical working system that can process the specific task for the information management office for which it was created.
This phase requires the coordination and cooperation of many people. The system analyst cannot conduct all the work alone. The first step involves coding. Coding is process of converting writing computer language that tells the system the commands to perform when certain commands are given. As the coding process being, the process of testing is also taking place as well. When coding is written, it must pass validation or the computer will not understand the language and the expect program will not perform to standard. Many strategies are available for testing validation; the size of the system dictates which is best. Throughout the system development life cycle, software testing was taking place after certain events to ensure the preliminary creation was on track. During analysis the overall test plan was developed. In the design phase, the unit test, integration test plan, and a system test plan was developed. Inspections are formal group activities that perform manually to find obvious errors such as syntax and grammar. The participants used a checklist of well-known errors for the specific language that written in the program. Using this type code inspection, a participant usually find from 60 to 90 percent of software errors. Other checks and balances that take place throughout the system development life cycle is a code walk through, desk checking, unit testing, and integration testing. . A walk through is a process conducted similar to purchasing home, before you actual close on the house, you walk through it with the project manager to identify deficiencies that need to be corrected. In this case, a walk through is conducted at a review meeting chaired by the project manager or chief programmer. The programmer presents his work for review; he walks through the code in details with a focus on the logic of the code not specific test cases. The reviewers can ask the programmer to walk through specific test cases. The chairperson will resolve disagreements that cannot reach among the participants. A second walk through will then be schedule to follow up correction if needed. Desk checking is an informal process where the program code is check for sequential order. Unit testing, which is also know as module or functional testing is when each module is tested to find errors in the code. Integration testing is the process of combining modules and testing in a top down incremental fashion. Some other tests are important to mention is the system testing, stub testing, acceptance testing, alpha, and beta testing. System testing is similar to integration testing, but you do not integrate modules into the program for testing, you integrate programs into systems. Programs are typically integration in a top down incremental fashion. Stub testing is technique used in testing modules, especially where those modules written, test in a top down fashion, where a few lines of code are used to substitute for subordinate modules. The purpose of system test is more important...
References: Edwards, C. (1984). Information Systems Maintenance: An Integrated Perspective. MIS Quarterly, 8(4), 237-256. Retrieved from EBSCOhost
Fry, Z. P., Shepherd, D. D., Hill, E. E., Pollock, L. L., & Vijay-Shanker, K. K. (2008). Analysing source code: looking for useful verb–direct object pairs in all the right places. IET Software, 2(1), 27-36. doi:10.1049/iet-sen:20070112
Sharma, R., & Yetton, P. (2007). THE CONTINGENT EFFECTS OF TRAINING, TECHNICAL COMPLEXITY, AND TASK INTERDEPENDENCE ON SUCCESSFUL INFORMATION SYSTEMS IMPLEMENTATION. MIS Quarterly, 31(2), 219-238. Retrieved from EBSCOhost.
Valacich, J., George, J., & Roth, R. (2009). Essentials of systems analysis and design (4th ed.). Upper Saddle River, NJ: Prentice Hall.
Please join StudyMode to read the full document