CHAPTER FOUR

DESIGN IMPLEMENTATION

INTRODUCTION

This chapter includes models or programs showing what they accomplish, how the system

can be developed, the programming language used and why it is used. Essentially, the

following items would be discussed:

i. Hardware Requirements

ii. Software Requirements

iii. Program modules and interfaces

4.0 HARDWARE REQUIREMENTS

Minimum Requirements

I. An Intel Pentium IV with a minimum processor speed of 1.6 GHz.

II. Minimum of 1GB of RAM

III. Hard Drive with capacity of 10GB and above

4.1 SOFTWARE REQUIREMENTS

Table 4.1: Software Requirements

Requirements Software

Operating System Microsoft Windows Xp, Windows Vista, Windows 7 and

also compatible with Windows 8. All operating systems

highlighted can also be 32-bit or 64-bit architectures.

Database Management System MySQL Server 5.5.16

Scripting and Development Tool PHP 5.3.8

Web Server Apache 2.2.21

Table 4.1: The Web Client/Application Software Requirements

Requirements Software

Operating System Microsoft Windows XP, Vista, Windows 7

Internet Browser Optimized for: Mozilla Firefox, Google Chrome,

Opera, Safari and Internet Explorer

4.2 DOCUMENTATION

In order to be able to make a practical demonstration, the developed application has been

populated with test data and the process through which this was done would be explained

briefly. Setting up the application environment requires first that the database is created on

the server, all database tables are created and the application files are published to the

webserver. Then, the system administrators account is added to the system so that all other

configuration can be done from within the web application.

The system administrator then logs in and adds operators, students and other users in the

system. In order to allow other users (students and operators) to have access into the

application, the administrator need to activate the accounts for them. While setting up, we

logged in as an administrator to create users as students and operators.

Logging in as a student, the student can update his/her personal information, writes his/her

complains, edits his/her complains and then registers or submits the complains to the

appropriate department.

Finally, we later logged in as the system administrator to view, edit users, check complains

and forward complaints to the constituted authority.

While testing the application, we also logged in as operators whose major functions is to

check for new complaints coming in, direct the complaints to the necessary division and

review obsolete complaints and information with the system administrator.

4.3 SAMPLE IMPLEMENTATION

The web application in this project comprises of several modules, each with its own specific

tasks and functions. Some of the modules are co-dependent while some are independent of

the others. The modules are as follows:

4.4.1 LOGIN PAGE

The login page is the landing page where a user will have to enter his/her username and

password to be able to login to the system

FIG. 4.4.1 OPERATOR LOGIN PAGE

ADMINISTRATORS PROFILE PAGES

4.4.2 USERS PAGE:

This is the page where the administrator will register students and operators, update their

personal information e.g. Department, College, Name and Matric Number.

FIG. 4.4.2 USERS REGISTRATION PAGE

4.4.3 REGISTERED OPERATORS PAGE:

This page shows the list of registered operators with their staff ID, full name, user name, date

created, last login, login counts and the edit buttons/tabs.

The administrator can also add new operator on this page.

 FIG. 4.4.3 OPERATORS PAGE

4.4.4 COURSE MANAGEMENT PAGE:

This page shows the list of registered colleges in the university with their respective

departments and the edit button. New Colleges can also be registered in this page.

FIG 4.4.4 REGISTERED COLLEGES PAGE

4.4.5 COURSE MANAGEMENT (Roles Column) PAGE:

This page displays the individual and independent divisions/roles in the university whereby

complaints are forwarded to for further processing. New roles can be added from this page

and existing roles can be edited.

FIG 4.4.5 REGISTERED ROLES PAGE

4.4.6 COMPLAIN PAGE:

This is the user interface where the administrator can access all complaints made by students,

staff, lecturers and other users in the system. This page comprises of full name, status,

incident date, complain date, view complain and the complaint status (whether resolved or

not).

FIG 4.4.6 PENDING COMPLAIN PAGE