CHAPTER FOUR

SYSTEM IMPLEMENTATION

The study will aid in reducing queues at banking halls and reducing identity theft if successfully i

4.0 Introduction

This phase is called the System implementation phase, is the last and one of the important phases
in software development life cycle. The online school management system was implemented on
Windows operating systems. It also at this phase that the newly developed school system is
tested and ensure it is deliverable. System implementation encompasses series of stages and each
of these stages are concurrent and consist of essential activities to be carried out.

4.1 Testing

Testing in this system involves the executing the design code to ensure that they provide the
output desired and coded for. Testing is performed to ensure that it is working correctly and
efficiently. Testing is generally focused on two areas: internal efficiency and external
effectiveness (Taner et al., 2013).

The external testing in this system is done by debugging directly the design code to ensure that
the give the interface required, the rendering of the code to testing also allow detection of errors
which are corrected, the software was tested using Wamp Server for the Database and web
browsers (Chrome and Firefox) for testing the graphical User Interface. The goal of external
effectiveness testing is to verify that the software is functioning according to system design, and
that it is performing all necessary functions or sub-functions.

The goal of internal testing is to make sure that the design code is efficient, standardized, and
well document. Testing can be a labor-intensive process, due to iterative nature (Tochukwu et
al., 2015). For this project the testing was generally done together with the coding as codes are
tested by debugging in the development platform immediately after the code is written.

4.2 Program Languages

The system runs on a number of languages and tools which make it fully responsive and
dynamic. The application was built as web-based application that needs internet facilities to
function the application design was achieved using multiple languages which includes:

 PHP: It is used as the server scripting language on this application. It helps in making the
system be responsive.

 HTML: This language was basically used to position the components of the web version
of the system.

 JavaScript: the java script was used for the client scripting. It makes the system to be
interactive.

 CSS: is an acronym for cascading style sheet, it is mostly used together with HTML to
structure webpages.

 MySQL: It is a relational database system that is designed to work with multiple systems.
This tool is used to manage information in the database of both small and large systems.

4.3 Hardware Requirement

For this system to run effectively there must be a provision of the following hardware:

1. Hard disk capacity: 20 GB.

2. RAM size of 2GB

3. A Colored Monitor

4. Modem (Wireless Network)

4.4 Software Requirement

1. Operating system: Microsoft Windows 10.

2. JavaScript-enabled web browsers: Mozilla Firefox (most suitable), Internet Explorer,

Google Chrome were used.

3. Virtual Server: XAMPP server

4.5 Module Description

The implemented system is displayed as a module in this phase, various system functions are
highlighted using the module presentation after a successful system designed and
implementation in the case area, the module description is used to show the actual pictorial
description of the system, Module representation gives the actual pictorial presentation of the
designed system. The modules show the step-by-step procedure of using School Management
System. Below are the modules of the school management system screenshot from the actual
designed and implemented system. These modules are culled after the system was tested and put
in place.

4.5.1 CUSTOMER REGISTER PAGE

This is the page where customers signup in other to have an account with the system. The user
details are used for subsequent login to the customer dashboard.

Figure 4.5.1 Customer register page

4.5.2 THE CUSTOMER LOGIN PAGE

The login page allow the system to automatically authenticate the user, it is one of the cardinal
requirements of the system, before the student is allowed to the system he/she needs to provide
valid and correct and valid login details which are valid Login Username and Password, once all
the login details provided and are found to be in the system database, the user can be allowed to
get access into the complete system, but if the logins are incorrect the system will automatically
tell the user that the Logins are Incorrect and details has to be provided again.

Figure 4.5.2 Customer Login page

4.5.3 CUSTOMER DASHBOARD

The customer dashboard is the first page the customer sees after a successful login from the login
page. The customer dashboard is where the customers to have access to create ticket for
complaints and view previously created tickets.
 Figure 4.5.3 Customer Dashboard

4.5.4 CUSTOMER TICKET PAGE

This is the page where customers create a ticket for their complaints. The purpose of creating a
ticket in respect to a complaint is to be able to track each complaint status. After a successful
ticket been created, it appears on the admin dashboard for further processing.

Figure 4.5.4 Customer Ticket Page

4.5.5 CUSTOMER TICKET LIST

This is a page where customers check all previously created ticket.

Fig 4.5.5 Customer Ticket List

4.5.6 CUSTOMER PROFILE PAGE

Figure 4.5.6 shows the customer’s profile and give them the privilege to update their profile.

Fig 4.5.6 Customer Profile Page

4.5.7 ADMIN LOGIN

The admin login page is where the admin gain access to the admin dashboard. Only correct login
details would be grant access, while wrong details would be denied access.

Fig 4.5.7 Admin Login Page

4.5.8 ADMIN DASHBOARD

The admin dashboard is the page admin can perfume all the administration functions like to view
all registered customers and staff, view all and respond to tickets, etc.

Fig 4.5.8 Admin Dashboard Page

4.5.9 ADMIN PROFILE PAGE

Figure 4.5.9 shows the admin profile and give them the privilege to update their profile.

Fig 4.5.9 Admin Profile Page

4.5.10 SERVICE CATEGORY PAGE

This is the page where admin set the category of services they offer, and for which a customers
can have related issue or complain.

Fig 4.5.10 Service Category Page

4.5.11 TICKET LIST PAGE

This is the page where the admin can view all the tickets created by the customers. Each of this
ticket has a ticket id makes it easy to identify and track each ticket. The status of each ticket is
used to determine the state of the complaint.

Fig 4.5.11 Ticket List Page

4.5.12 CUSTOMER LIST PAGE

The Fig 4.5.12 shows all the registered customers on the system. The admin can chose to delete
or modify the customers account if he/she flout the rules of the system.

Fig 4.5.12 Customers List Page

4.6 MAINTENANCE
This phase is virtually never-ending phase. Generally, problems with the system developed
(which are not found during the development life cycle) come up after its practical uses starts, so
the issues related to the system are solved after deployment of the system. Not all the problems
come directly but they arise time to time and needs to be solved; hence this process is referred as
maintenance.