Even when the installation process has begun, testing should continue. Installation is the process of actually replacing the current system or programs with the new system or programs. Thus, coding, testing, and installation processes create several deliverables that can be used as signoff points for management. The testing and implementation process should allow for back out points where new direction or error and bug elimination can occur. The deliverables are fail safes in a sense because a next task should not be started until a previous task has been given the okay by management. This process therefore puts a system of checks and balances in place.

Documentation and Training

Most people think that coding and testing are the only crucial aspects of implementation. Ironically, one of the more critical things to accomplish in the implementation phase is related to the understanding of the new system or program. Code documentation may be one of the most important steps in the entire process yet is often either overlooked, done poorly or worse, not done at all. The reason documentation is so crucial to a processes success is because it helps everyone get a grasp of exactly what is or was expected to happen in a system or program, develops blueprints for training and support and provides a diary like history, if done properly, which can be used to maintain the system. In addition, detailed documentation helps for future designs with expansions, upgrades or abolishment of some aspects of the system. Program and system testing results in conjunction with design blueprints or specifications that are well documented can be used to:

develop a user's guide develop a training plan develop an installation and conversion plans develop hardware or software installation schedules develop and alter data or database conversion plans develop a plans for facility remodeling

Training usually receives the needed attention during the implementation and operation phase. If the employees can not use the new system the system is a hindrance to organizational success. Training and documentation should focus on two audiences: information systems personnel maintaining the system and the end users of the system.

Maintenance...

Maintaining the system requires the organization to obtain maintenance requests from end users, transform these requests into coding programming or system and hardware changes, design the necessary changes and implementing those changes. Of course the same rigorous testing and documentation steps should be incorporated into the maintenance implementation changes.
Conclusion

In conclusion, this report was an add-on to the analysis of a work-related project using a systems analysis tool for the implementation of a specific business and information system. The focus was on the implementation stage of the development process. The typical implementation process is based on a project team installing applications and systems on a customer's or organization's production platform. This implementation was for International Lumberyards, Inc., who already completed the previous steps and financially justified the events based on the forecast return on investment. Insights into the six major activities of the implementation stage were described and each of the activities was broken down. In addition, a brief discussion about the benefits of using a well defined and repeatable process for meeting implementation objectives was provided.

References

Canberra. (n.d.). System Implementation. Retrieved on January 27, 2005, at http://www.ise.canberra.edu.au/u8310/l17.htm

Grabski, Severin V. (2002). International Lumberyards, Inc.: An Information System Consulting Case. Journal of Information Systems, 9/22.

Knight, Ph.D., Linda V. (2001, November 1). System Development Methodologies for Web Enabled E-Business: A Customization Paradigm. Retrieved January 16, 2005, at http://www.kellen.net/SysDev.htm

Peacock, Eileen (2004). Accounting for the development costs of internal-use software. Journal of Information Systems, 3/22.

Wikopedia. (n.d.). System Development Life Cycle. Retrieved January 16, 2005, at http://en.wikipedia.org/wiki/System_Development_Life_Cycle

Project Management