System Implementation document
Supervisor: Griffin Kenga
Email: kenga@[Link]
Tel: +254-724584694
• This chapter contains the sixth, seventh and eighth milestones of your project.
• This document describes how the blue print of the product has been realized.
• From this document one can look back at the objectives set out in the proposal and see if they have all been
achieved.
• The document should provide major implementation tasks, user manual, screen shots of the running system
and how the system was tested.
• The key sections include:-
• The cover page
• The table of contents
• [Link]
• 6.2. System description
• 6.3. Assumptions and constraints
• 6.4. System organization
• 6.5. Description of the implementation
• 6.6. Major implementation tasks
• 6.7. Implementation support
• 6.8. User manual
• 6.9. The test plan
3/3/2023 • 6.10. Appendices Griffin Kenga
Chapter 6: System Implementation
Chapter 6: System implementation
6.1. Introduction
The system implementation document’s goal is explained in this subsection, which also outlines
the system that will be used. Describe the organization of the system being implemented.
6.2. System description
An overview of the procedures the system is meant to support is given in this section of the
chapter. Describe the types of data maintained, their sources, and purposes if the system is a has
a data store (database). To characterize the system, provide any identifiers, names, acronyms,
version numbers, and release numbers.
6.3. Assumptions and constraints
This section outlines the limitations that were relevant to the creation and implementation of
this chapter of the report. When identifying the assumptions and restrictions, some things to
keep in mind are: Project schedule, budget, resource availability, skill types, software and
hardware to be purchased or utilized, restrictions
Griffin Kenga on product interfaces etc.
Chapter 6: System Implementation
6.4. System organization
The primary system components necessary for the system implementation are described in this section of
the chapter. Describe both software and hardware. If necessary a screenshot of the system and block
diagram of the system can be used to paint a clear image of the system.
6.5. Description of implementation
This subsection provides a description of the planned installation and changeover plans. Describe how the
new system will replace the old system (changeover) without interrupting business operations: phased,
parallel and direct changeover are some of the strategies that can be used.
6.6. Major implementation tasks
In this section, describe the major tasks involved in the implementation. For each task include:
• The task to be undertaken
• The person(s) (no need to mention names) who will be involved :
• Resources that will be required to accomplish the task.
• Criteria for successful completion of the task e.g. user acceptance.
Examples of tasks include:-
• Planning and coordination for the implementation
• Training the personnel
• Performing site survey before implementation
• Acquisition of software and hardware for the implementation
• Developing the front end and backend
• Performing data conversion
3/3/2023 Griffin Kenga
Chapter 6: System Implementation
6.7. Implementation support
In this section, describe the hardware, software, and other materials that will support implementation:
Hardware: Hardware for installation and testing e.g. computers, servers, peripherals.
Software: Any non hardware components e.g software, databases, and compilers, operating systems,
utilities required to support implementation.
Facilities: Physical workspace for assembling and testing, floor space for training users.
6.8. User manual
In this section describe the steps for installation and configuration of the system. Include steps involved
operating the system e.g.
• running various tasks within the system
• report print
• recovering data
• creating backups
• basic troubleshooting steps
3/3/2023 Griffin Kenga
Chapter 6: System Implementation
6.9. Test plan
• Describe the goal(s) for testing the system.
• Describe the type(s) of the testing that were undertaken.
• Describe the components of the system that were tested, what were the expected and actual results after the test and actions
that were taken after the test(s).
6.10 Appendices
• Screenshots for the running system
• Sample code of the running system
References
3/3/2023 Griffin Kenga