Business Information System Implementation for a Lumberyard
This report examines the implementation stage of a business information system development project for International Lumberyards, Inc. Building on a completed needs assessment and reengineering analysis, the paper walks through the six major activities of the implementation phase: coding, testing, installation, documentation, training, and support. It details how four simultaneous system upgrades—web development, local area networking, new hardware, and computerized business functions—were managed in parallel. The report also discusses the value of well-defined, repeatable processes for quality control, documentation practices, and ongoing system maintenance within the System Development Life Cycle framework.
- Introduction: Scope and overview of the implementation project
- Coding the New System: Four simultaneous coding tasks and network complexity
- Testing and Installation: Parallel testing, deliverables, and management sign-off
- Documentation and Training: Why documentation and user training are critical
- Maintenance and Support: Ongoing SDLC cycles and maintenance requests
- Conclusion: Summary of implementation stages and key findings
✍️ How to write this paper — guide, tools & examples ▾
What makes this paper effective
- The paper applies a clear, stage-by-stage framework to a concrete real-world scenario, making abstract implementation concepts tangible through the International Lumberyards case.
- Technical specificity — naming protocols such as ATM, CISCO routers, DNS servers, and IP addressing schemes — demonstrates domain knowledge and strengthens credibility.
- The paper consistently connects each implementation activity back to organizational impact (e.g., why documentation matters for future upgrades, why training determines system success).
Key academic technique demonstrated
The paper demonstrates applied case analysis: it takes a theoretical framework (the six stages of system implementation from the SDLC literature) and systematically maps each stage onto the operational reality of a specific company. This technique shows readers how to bridge textbook models and real-world project constraints.
Structure breakdown
The report opens with a contextual introduction that establishes scope and the client organization. It then proceeds through four body sections — coding, testing/installation, documentation/training, and maintenance/support — each addressing a discrete phase of the implementation lifecycle. A brief conclusion restates the report's purpose and findings. The structure mirrors the chronological order of an actual implementation project, reinforcing the paper's practical orientation.
Introduction
This report is 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 is on the actual implementation stage of the development process. The typical implementation process entails a project team installing applications and systems on a customer's or organization's production platform, which is usually followed by whatever training and acceptance testing is needed, ultimately leading to customer sign-off on the application or system.
This implementation is for International Lumberyards, Inc., which first conducted a detailed needs assessment that verified the need for a new, more modern software and hardware approach — one that could be financially justified in regard to the organization's overall return on investment. The company had successfully completed the necessary information-gathering and utilized various other techniques in the reengineering project, and was prepared to implement the new code and equipment.
Insights into the six major activities of the System Development Life Cycle (SDLC) implementation stage are described throughout this report: coding, testing, installation, documentation, training, and support. Each of these six activities is examined to explain specifically how each was planned for and how the various aspects of the software and hardware upgrades were affected. In addition, a brief discussion about the benefits of using a well-defined and repeatable process for meeting implementation objectives is provided.
References
Canberra. (n.d.). System implementation. Retrieved January 27, 2005, from
Grabski, S. V. (2002). International Lumberyards, Inc.: An information system consulting case. Journal of Information Systems, 9(22).
Knight, L. V. (2001, November 1). System development methodologies for web-enabled e-business: A customization paradigm. Retrieved January 16, 2005, from
Peacock, E. (2004). Accounting for the development costs of internal-use software. Journal of Information Systems, 3(22).
Wikipedia. (n.d.). System development life cycle. Retrieved January 16, 2005, from http://en.wikipedia.org/wiki/System_Development_Life_Cycle
Create your account
Always verify citation format against your institution’s current style guide requirements.