To Describe the Implementation Stage for This Project

The objective of this paper is to describe the implementation stage for this project.

There are 6 major activities and will be covered as follows:

* Coding

* Testing

* Installation

* Training

* Support

Coding is the process through which the agreed upon requirements created by the stakeholders are turned into functional code. Depending on the requirements this process can be quite rigorous and involved. The obvious outcome of this process is the actual code; however another important result is program documentation. System documentation is most important for the IT group. The first group is operational support or otherwise known as the company's helpdesk. This will help them support the very end users who are going to be using this software. Documentation is most important for the System Administrators and other members in the programming group which will aid them in troubleshooting especially for newer members not involved in the project's inception.

Once coding is complete the next phase is testing. As each module is completed, they can be tested individually then once multiple modules are complete, they can be tested together as one large system.

IT and select end users will be a part of this process. IT can test the software on the infrastructure to ensure proper throughput. This helps identify if the bandwidth requirements are sufficient for the network and does not contribute to such things as network lags. It can also ensure proper response time and can make the proper adjustments to hardware or OS configurations to achieve the desired result.

The select end users will 'script' what daily routines would run on this system. This helps identify if the system can deliver what was originally agreed upon. This also simulates workload; it will monitor the system as the testing group runs simulations. Documentation is another outcome of this process just as it was in coding. At this phase, since end users are involved, a standard operating procedures manual and/or user guide can start to be formulated. This 'SOP' will give end users a reference while they are still learning the software. This same documentation will also help operational support or otherwise known as the helpdesk and maintenance programmers to support these very end users.

The next is installation. This involves should only involve the IT group. In this process, the client machines are staged and pre configured to be able to handle the system. Once staging and pre configuration is complete, the actual software is installed and configured. Configuration examples would be setting the proper hostnames and ip addresses to tell the software where the server is. This is assuming that client/server architecture is being used. Again documentation is important and should be done as you go. The key components to document are those very configurations. This will greatly help the helpdesk as going forward, they will be probably be