Service Request Sr Rm 004
Service Request SR-rm-004
Danny Floyd
BSA/375
June 17, 2011
Shirley Myers
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
Danny Floyd
BSA/375
June 17, 2011
Shirley Myers
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
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. .