Work Related Project Analysis
Work-Related Project Analysis, Part III, Implementation
University of Phoenix
Systems Analysis and Design
BSA/376
October 25, 2010
Work-Related Project Analysis, Part III, Implementation
Mastec Incorporated has been working in the past month on a project designed to reduce time spent on the phone trying to activate receivers. The project is a necessity for the organization and that was reflected in the feasibility report. The design process was also successful and now the organization is ready for implementation. Implementation is a critical step in the system design process, because during this step all the planning comes to life. This paper will discuss the major activities that should be included in the implementation stage. These activities include coding, testing, installation, documentation, training, and support.
Implementation
Implementation involves creating the physical aspects of the system, installing software, hardware, and training employees to use the new system properly. Yet, some of the activities needed for implementation start actually ahead of time. This means that an organization can’t and should not start implementation without planning for it. One important step in a successful implementation planning includes coordination with third parties that may be involved in the implementation process. According to Tom Mochal from tech republic, in today’s market “few solutions can be implemented without involving a number of organizations. For IT solutions, there are usually one or more operations and infrastructure groups that need to be communicated to ahead of time” (2003, para. 5). Ensuring that all parties playing roles in the implementation process are on the same page is a recipe for success. Preparation of the infrastructure is another important step in the implementation process. Many projects are tested in an environment different from the real one, taking into account the real conditions of the organization and
University of Phoenix
Systems Analysis and Design
BSA/376
October 25, 2010
Work-Related Project Analysis, Part III, Implementation
Mastec Incorporated has been working in the past month on a project designed to reduce time spent on the phone trying to activate receivers. The project is a necessity for the organization and that was reflected in the feasibility report. The design process was also successful and now the organization is ready for implementation. Implementation is a critical step in the system design process, because during this step all the planning comes to life. This paper will discuss the major activities that should be included in the implementation stage. These activities include coding, testing, installation, documentation, training, and support.
Implementation
Implementation involves creating the physical aspects of the system, installing software, hardware, and training employees to use the new system properly. Yet, some of the activities needed for implementation start actually ahead of time. This means that an organization can’t and should not start implementation without planning for it. One important step in a successful implementation planning includes coordination with third parties that may be involved in the implementation process. According to Tom Mochal from tech republic, in today’s market “few solutions can be implemented without involving a number of organizations. For IT solutions, there are usually one or more operations and infrastructure groups that need to be communicated to ahead of time” (2003, para. 5). Ensuring that all parties playing roles in the implementation process are on the same page is a recipe for success. Preparation of the infrastructure is another important step in the implementation process. Many projects are tested in an environment different from the real one, taking into account the real conditions of the organization and
References: Faqs.com. 2009. Life cycle of a software development project. Retrieved on October 25, 2010 from http://www.faqs.org/docs/ldev/0130091154_28.htm Idcon.com. 2010. Reliability tips. Retrieved on October 25, 2010 from http://www.idcon.com/reliability-tips-76.htm Microsoft.com. Unit testing. Retrieved on October 25, 2010 from http://msdn.microsoft.com/en-us/library/aa292197(VS.71).aspx Mochal, T. 2003. Project implementation: Eight steps to success. Retrieved on October 25, 2010 from http://articles.techrepublic.com.com/5100-10878_11-1054399.html