Work Related Project Analysis

Topics: Implementation, Software testing, Concurrent Versions System Pages: 5 (1447 words) Published: January 10, 2011
Work-Related Project Analysis, Part III, Implementation
University of Phoenix
Systems Analysis and Design
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 including them in the testing of the system is not only desirable but also necessary. Coding

Coding includes the process of turning program logic into specific instructions that the computer system can execute. Since the project that Mastec is undertaking will use the Internet and the design is a server-client one the use of web-centric languages like Java could be used for coding purposes. Collaboration during this phase is important because many developers will be creating their own code, and ensuring that different parts of the code can interact without problems is necessary. “A revision control system such as CVS (Concurrent Versions System) is needed in this phase” (, 2009, para. 3). The reason is that a project of this magnitude can contain thousands of files, and providing a main storehouse is a necessity. Following a specific protocol during coding will prevent mistakes or errors that can compromise the whole project. People in charge of coding should include comments within the code so other developers that need to make changes to the code later on can understand what the original person intended. Testing

Testing is another important element of the implementation process because through testing programmers can verify if the software works properly. Programmers usually test programs individually, then by groups and then the system as a whole. This process can be divided into unit testing, integration testing and system testing.

Unit testing occurs when programmers test individual programs looking for syntax errors or any other errors that may prevent the application from running properly. “The primary goal of unit testing is to take the smallest piece of testable software in the application, isolate it from the remainder of the code, and determine whether it behaves exactly as you expect” (Microsoft, 2010, para. 1). Integration testing combines to individual units of the software to observe how they interact. Programmers need to develop test data...

References: 2009. Life cycle of a software development project. Retrieved on October 25, 2010 from 2010. Reliability tips. Retrieved on October 25, 2010 from Unit testing. Retrieved on October 25, 2010 from
Mochal, T. 2003. Project implementation: Eight steps to success. Retrieved on October 25, 2010 from
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • Work-Related Project Analysis Essay
  • Work-Related Project Analysis Essay
  • Work Related Project Analysis Essay
  • Essay on Work Related Project
  • Work Related Project Analysis Part I Essay
  • Work-Related Project Analysis, Part I Essay
  • Essay on Course Project Horizontal Analysis
  • BSA 376 Week 4 Work-Related Project Analysis Part 3 Essay

Become a StudyMode Member

Sign Up - It's Free