A COMPUTERISED LOAN SCHEME INFORMATION MANAGEMENT

SYSTEM

FOR HIGHER EDUCATION STUDENTS FINANCING BOARD (HESFB)

BY

LUBEGA PETER

216006032

16/U/6610/PS

BACHELOR OF STATISTICS ш

A PROJECT REPORT SUBMITTED TO THE SCHOOL OF STATISTICS AND

PLANNING, MAKERERE UNIVERSITY IN PARTIAL FULFILLMENT
OF THE REQUIREMENTS FOR THE AWARD OF BACHELOR
OF STATISTICS DEGREE

JULY 2019
DECLARATION

i
APPROVAL

ii
 DEDICATION

I dedicate this report to my beloved mother Mrs. Nakabugo Josephine for her continued
support towards my education, the love, care and cooperation. May the almighty God
richly reward her.

It's on this note that I still come extending my sincere gratitude to my only one beloved
sister Nakibuule Esther. Thanks for the care and encouragement towards me.

iii
 ACKNOWLEDGEMENT

I acknowledge the Almighty God who granted me good health life and knowledge to
successfully finish my project.

In the same breath, I would like to extend my sincere thanks to my host supervisor Mr.
Serunjogi Ambrose upon whose guidance I could follow always throughout the entire
project period.

Further appreciation goes to the Higher Education Students Financing Board (HESFB)
for availing me with all the system information and guidance.

In the same regards, I must pay humble gratitude to all my friends for the great
cooperation, particularly Kibande Micheal, Mulapada Seth, Tumuhe Hildah and the
entire Bachelor of statistics computing class.

My acknowledgements would be short and inconclusive without mentioning my kindest

and most loving mother Nakabuga Josephine for the ending-less support she accorded me
with thought my internship period.

Lastly but not least, can‟t forgetting the school of statistics library for availing me with
the necessary materials and data to complete my project.

iv
 TABLE OF CONTENTS

DECLARATION ............................................................................................................................. i
APPROVAL ................................................................................................................................... ii
DEDICATION ............................................................................................................................... iii
ACKNOWLEDGEMENT ..............................................................................................................iv
LIST OF TABLES .........................................................................................................................vii
LIST OF FIGURES/ PICTURES .................................................................................................viii
LIST OF ABBREVIATIONS .........................................................................................................ix
ABSTRACT.....................................................................................................................................x
CHAPTER ONE ........................................................................................................................... 1
1.0 Introduction ............................................................................................................................... 1
1.1Background to the problem and the HESFB.............................................................................. 1
1.2 Problem Statement .................................................................................................................... 2
1.3 Objectives of the Project ........................................................................................................... 2
1.3.1 Specific Objectives ................................................................................................................ 2
1.4 Purpose of the study .................................................................................................................. 2
1.5 Scope of the Project .................................................................................................................. 2
CHAPTER TWO: LITERATURE REVIEW ............................................................................ 3
2.0 Introduction ............................................................................................................................... 3
2.1 Development of the information Management System ............................................................ 4
2.3 Advantages and Disadvantages of the Loan Management System .......................................... 5
2.4 Design of the Loan Management System ................................................................................. 5
CHAPTER THREE: METHODOLOGY................................................................................... 6
3.0 Introduction ............................................................................................................................... 6
3.1 Statistical hypothesis................................................................................................................. 6
3.2 System Analysis and Design..................................................................................................... 6
3.2.1 Current System Investigation................................................................................................. 6
3.2.2 Analysis of Existing system ................................................................................................... 6
3.2.3 Problems of Existing system.................................................................................................. 7

v
3.2.4 Advantages of Proposed system ............................................................................................ 7
3.2.5 Design and implementation Methodology ............................................................................. 8
3.2.6 Software Requirements .......................................................................................................... 8
3.2.7 Software tools used ................................................................................................................ 8
3.2.8 System Testing and Validation .............................................................................................. 9
3.2.8.1 System Testing .................................................................................................................... 9
3.2.8.2 System validation ................................................................................................................ 9
3.2.9 System Development Approach ............................................................................................ 9
CHAPTER FOUR: PRESENTATION OF THE PROPOSED SYSTEM ............................. 10
4.0 Introduction ............................................................................................................................. 10
4.1 System requirements ............................................................................................................... 10
4.1.1 Functional requirements....................................................................................................... 10
4.1.2 Non-Functional requirements .............................................................................................. 10
4.2 System Operation Description ................................................................................................ 10
4.2.1 Features of the administration panel .................................................................................... 10
4.2.2 Features of the user panel..................................................................................................... 11
4.3 Data flow diagrams ................................................................................................................. 11
4.3.1 The system context diagram ................................................................................................ 11
4.3.2 Level 1 Dataflow diagram.................................................................................................... 12
4.4 Data modeling and design....................................................................................................... 13
4.4.1 The Entity Relations Diagram ............................................................................................. 13
4.5 Data dictionary ........................................................................................................................ 14
4.6 Project Screenshots ................................................................................................................. 15
CHAPTER FIVE: SUMMARY, CONCLUSION AND RECOMMENDATIONS .............. 25
5.0 Introduction ............................................................................................................................. 25
5.1 Summary ................................................................................................................................. 25
5.2 Conclusion .............................................................................................................................. 25
5.3 Recommendations ................................................................................................................... 25
REFERENCES............................................................................................................................ 26
APPENDICES ............................................................................................................................. 28

vi
 LIST OF TABLES

Table 1: Data Dictionary ....................................................................................................... 14

vii
 LIST OF FIGURES/ PICTURES

Figure 1.Context (Level 0) Diagram..................................................................................11

Figure 2.LEVEL 1 SYSTEM DATA FLOW DIAGRAM ................................................12
Figure 3.Entity Relation Diagram developed by Visual Paradigm....................................13
Figure 4.Screen shot of the WAMP Server IDE ................................................................15
Figure 5.Screen shot of the Login Panel ............................................................................16
Figure 6. Screen shot of the user/student's Home page .....................................................17
Figure 7.Screenshot of the File uploading Panel ...............................................................18
Figure 8.Screenshot of the Disbursement Form ................................................................19
Figure 9.Screen shot of the chatroom panel.......................................................................20
Figure 10.Screen shot of the online application panel .......................................................21
Figure 11.Screen shot after the Administration panel is accessed successfully ................22
Figure 12.Screen short of the administrator's panel ...........................................................23
Figure 13.Screenshot of the add new user by the Administrator .......................................24

viii
 LIST OF ABBREVIATIONS

ADMIN Administrator

ERD Entity Relationship Diagram

HESFB Higher Education Students Financing Board

PHP Hypertext Preprocessor

PK Primary Key

SQL Structured Query Language

WAMP Windows, Apache, MySQL, and PHP

ix
 ABSTRACT

The Computerized Loan Scheme Information Management System Project was designed
and implemented in order to study the existing system, identifying the problem, and
improving it for more proficiency. With much data but without experience in managing
this loan, the system information is confusing and unorganized.

The existing system is still operating in manual system; therefore, the computerized
system should be implemented to enhance the efficiency to become a more the systematic
system.

The project covers the system analysis and design of getting loan detail process, settling
process, and receiving payment process. The existing system presents the problems
occurring from manual operations. This project is arranged to overcome many problems
such as data redundancy, data incorrectness, time consuming, miscommunications and
very many others. The new computerized system will reduce errors while providing a
better control over the process and better management information in a timely manner for
implementation strategies.

The study of this project begins with the requirement definitions and analysis of the
existing system. After studying, it shows the inefficiency in loan document collection;
therefore, the management agrees that Loan Scheme Information Management System
should be changed from manual to the computerized system.
The results of the system study are proposed in various forms such as data flow diagrams,
relational tables among others, which are demonstrated in the process of the existing
system.
The new system is implemented in a user interface technology and well checked to
ensure that there is no error in the programs.
Its outputs are met with the target of the Higher Education Students Financing Board
(HESFB). To enhance the effective management of customers, the system should be
further developed so that it supports other bidding loan information like bank statements.

x
 CHAPTER ONE
1.0 Introduction
This is an introductory chapter that entails the project background, problem statement,
objectives of the study, scope of the study as well as its significance

1.1Background to the problem and the HESFB

Social Loans have played a very vital role in fairing the distribution of higher education
financial support and they are believed to replace the government sponsorship program in
the near future among countries like Uganda, Kenya and Rwanda although Tanzania
according to (Mussa, 2015) has already fully initiated it as its only government
sponsorship program towards students enrolling for higher education.

These Loans are given to the intelligent but needy students joining higher institutions of
learning and are to be paid back at either zero or very low interest rates. In this, a clear
and authentic information flow channel is required which at the same time can keep truck
of the entire transaction process in terms of loan disbursement and repayment.

According to (Aaron_Hill, 2003), loans are either secure or unsecure basically there are
six types of loan as mentioned below; Personal loans, Cash advances, Student loans,
Mortgage loans, Home-equity loans and lines of credit, Small business loans.

However, this project focuses on the student loans in Uganda and how their management
can be improved efficiently in cooperation with the HESFB through the Loan Scheme
Management System.

The Loan Scheme Management System can be modified into different aspects say an
android application, Desktop Application but for a mean time, it is to be employed as an
online system unless if there happens to be a specific demand for such a modification.

This system has numerous features such as passwords at various levels, interlinked to
other sites like the secure jobs and internship sites among other features.

1
1.2 Problem Statement
The existing system only interacts with administrators and basically spreadsheet
interfaced, where students‟ tuition invoices are submitted in form of hard copies and rear
communications are made upon payment deadlines. In this manual driven system,
students are never given a chance to know how much funds have been allocated to their
institution accounts in respect to the requested variances usually occur. The only mode of
communication across the students and administrators is through phone text massages
which are expensive yet inefficient.

The Loans Information Management System for the above issues is to strictly put much
emphasis on availing a central portal from which all inter-communications will be made
in relation to disbursements among other document management and will be over sighted
by the Board Secretarial department.

1.3 Objectives of the Project

The main objective of this project is to design a Loan Information Management System
that can that will foster the secretarial day to day operations efficiently through
promoting communication and document processing.

1.3.1 Specific Objectives

a. To understand the pressing loopholes in the present system (manual system).
b. To correlate the relevancy of the system among students on the scheme and the
scheme administrators.
c. To learn more about the HESFB operations and analyze the supplementary add-
ins into the design

1.4 Purpose of the study

This study is undertaken to develop a computerized system that will centralize all the
student-administration communications and will provide an automated data base to store
all recent disbursements of then hence easy to track, access more information about the
HESFB.

1.5 Scope of the Project

The study focuses on the Higher Education Students Financing Board though
concentration was embarked much on interaction among the key entities (students,
Universities, higher learning institutions and other parties of the general public).

The system trucks the entire loans disbursement process and centralizes communication
in all the 20 universities and the proceeding 34 tertiary institutions.

2
 CHAPTER TWO: LITERATURE REVIEW
2.0 Introduction
Generally, the pattern of scholarships (social loans) was well established before the
United States of America even existed, and, as in England, was usually a matter of gifting
between elite families (Thelin_J.R&Wilkinson, 2011). In 1639, the American system of
higher education was established to continue the tradition of sponsorship, charity, as per
the patronage was established by European universities (Fuller, 2014)
He argues that financial support were generally from three sources namely:
a) The student-paid
b) Church-paid
c) Crown- or state-paid
By 1643, Harvard had received funds for its first endowed scholarship from Lady Anne
Radcliffe Mowlson, who stipulated that interest on her donation of £100 be used to aid
poor students‟ pursuit of education (Mowlson, 1643).
In 1838, Harvard established a private student lending agency responsible for making
zero-interest loans to students who could otherwise not afford to attend. The program,
known commonly as the Harvard Loan
Program, was a part of Harvard‟s General Beneficiary Fund raised by wealthy alumni and
benefactors (Harvard_University, 1874).
It‟s in that age of then that student loan scheme management systems were given
thoughts and built to track the funds and communication flows among the scheme
boundaries.
All systems were to be built under the guidance by the Higher Education Act of 1965
which was a highlight in President Lyndon Johnson‟s legislative accomplishments and
stands out as one of the seminal moments in American higher education history (Cohen_
AM:& Kisker, 2009).
In regards to this report, the Loan management systems are mainly used to store
transactional data for given loans and bridge out customer institution communications.
They record data for given sums, returned sums for principal, taxes and rates. Some
authors (Niţescu, 2012, pp. 53-62) focus on customer factors influencing a customer

3
(student) behavior and their impact on early repayment of loans. Niţescu also analyzes
the period of loan payment.
Others (Kohler et al.2012, pp. 8-20) connect the term “loan management systems” with
libraries.
Usually loan management systems operate with confidential databases. Thus they are
usually not used in scientific research.
Researchers prefer to use other forms of collecting data – for instance focus group
discussions.

2.1 Development of the information Management System

Different scholars have defined information management system in different ways but all
merging to the same point.

According to (MUSUMBA, 2006) an information system is a set of interrelated

components that collectively retrieve process, store and distribute information to support
decision making and control in an organization.

In the same vein, (Akram, 2011) defines an Information System as the arrangement of
groups, data, processes and Technology that accumulates together to process, store and
output information as per needed to enhance and speed up the process of decision
making.

(Dhungana, 2002) explains that an information system lays a clear flow of information in
an organization following four strategic levels from the strategic to the operational level.

In his words, (Keneth L. , 2007) “Information systems (IS) encompasses an

understanding of the management and organizational dimensions as well as technical
dimensions of the systems as information systems literacy”, thus information systems are
a baseline for organization‟s growth in supplement to its survival.
However, (Yogesh.D., 2017) explains that Information management expands a step ahead
to focus more on managing activities that make changes in patterns of behavior of the
management, customers and the globe in general through empowering them with
information that enables to identify the most optimal decision to take.

4
2.3 Advantages and Disadvantages of the Loan Management System
There are many advantages as per attached to the loan management system and these
include: reduction in supervision costs, eased follow up process on the repayment
process, automated analysis among the enrolled patterns most so in terms of gender as
pointed out by (Hua.Shen, 2010).

Furthermore, (Dimple, 2017) states the other advantages as normalization in documents

submitted by the students, multiple accesses to information and many others.

To a smaller extent, the loan information management system has some disadvantages
and these include higher risk to hackers accessing the restricted information, increased
costs in terms of payments made to the system administrators, developers and all in all,
loss of jobs to some of the data workers.

With all the above, the merits of the loan management system outweigh the demerits and
hence I was given a way forward to develop the system.

2.4 Design of the Loan Management System

The system operates in respect of the organizational strategic levels and it employs a top
down model. This is done to ensure a clearly defined information flow from the strategic
managers to the operational managers (scheme secretaries) and finally to the users who
are the students.

(K.Dagba, 2014) developed a loan management system whose architecture comprised of

three tier layers: The Client-side interface layer, Server-side application layer and
Database layer which were built using html, java and bootstraps, however it was very
possible to use php instead of java as expressed in this system.

All these languages are mothered by C language which then upgraded to C++ and php
inherits its basics from html.

(Benita, 2006) expresses seven main reasons for the use of php in such a system and
these are; Php is speed and robust, superior on Memory Management, has no hidden costs
with PHP, integration with MySQL database, it is closer to Java/C++ Style of
Programming, it never shows Stopper Bugs and on to that, it employs the cross-Platform
Migration Strategy.

5
 CHAPTER THREE: METHODOLOGY
3.0 Introduction
Generally, the New system takes up four main stages in its development. These are;
i. Software and information analysis
ii. Design
iii. Coding and implementation
iv. Testing and maintenance
Within these stages, particular concepts are looked up for and these are preceded as
below.

3.1 Statistical hypothesis

Ho: The use of the manual system is more efficient than the use of a computerized Loans
Management system.

Ha: The use of the manual system is less efficient than the use of the computerized Loans
Management System.

3.2 System Analysis and Design

3.2.1 Current System Investigation
In the development of this system, I first gathered information from both the students
financed by the loan scheme and the loan scheme administrators.
Information was focusing on need for this new system and I with the assistance from
student coordinators used oral interviews as a data collection method.

On the administrator side, I collected primary data that contained of the actual number of
institutions financed, the type of documents required in the disbursement process towards
the students, anticipated number of students to be supported by the system among other
attributes.

3.2.2 Analysis of Existing system

The existing Loan system at Hesfb is less computerized of which most modules are
manual involving a lot of paper work.

6
Besides texting, the other communication mode between the students and administrators
is transitive where information is conveyed to student coordinators by calls and these
later pass on the information to the students.
In the same line, students submit any of the required documents in hard copy form.

3.2.3 Problems of Existing system

The following problems were identified from the overview of the existing system:
 Prone to Miscommunications. As information is passed on through many people,
it gains attenuation and hence wrongly got by the target people.
 Document submission delays. Since coordinators submit documents in lots, they
tend to delay as for some lots, students delay to submit and this inconveniences
the ones who submit in time as transactions in result are also delayed most so for
Makerere students.
 Risk of data loss. These records are at a very high risk among which is a fire
outbreak and intended theft.
 Tiresome to the scheme secretaries. During the time of exam commencement,
students happen to have pending balances on their institutional accounts. These
get means to reach the secretariat section and immediate effect has to be acted.
 As record volumes increase, it becomes a burden for physical storage space.
 The existing system is very much prone to errors.
 There is low output due to low processing speed.

3.2.4 Advantages of Proposed system

The following some of the advantages of the proposed system:
It provides an immediate access and response since it is an online application system.
It is a central communication portal between loan scheme financed students and their
administrators. It requires less physical storage space and allows for back up of data from
the database.
It eases the work flow for the scheme secretaries.
It is more secure than the previous system by authenticating users through passwords.

7
3.2.5 Design and implementation Methodology
At the design level, I developed a context diagram, dataflow diagrams and the entity
relation diagram.
We are to then use the prototype model for implementation where at first, the proposed
system will be used alongside the existing manual system.
Keen analysis shall be made on the prototype efficiency, fix the will be available
problems and officially be finalized.

3.2.6 Software Requirements

The system is an online based application composed of bootstrap features hence can be
accessed by most gadgets like phones, laptops, desktops and tablets using most of the
popular search engines.

3.2.7 Software tools used

The Loan Scheme management system was developed by use of some of the tools below:
 I used wampserver3.1.4 as my Integrated Development Environment (IDE).

WAMP is the abbreviation of the package: Apache, MySQL, and one of Perl,
PHP, or Python in the Microsoft Windows operating system.

 The database used will be MySQL because it is easy to retrieve and maintain
records using simple queries. I further used SQLite as the Database Management
System because it makes working with MySQL databases easier.

 Visual_Paradigm_15.2 to draw the data flow diagrams (DFDs) and the Entity
Relation Diagrams (ERD).
 Php was the main language used and I adapted to it because with a prior
knowledge on HTML, php was easy to learn than any other language.

8
3.2.8 System Testing and Validation
3.2.8.1 System Testing
Generally, we test the system by failing it, we tested it in line with user requirements
(system testing) and the system was secure and further met other expected requirements
like consistence in accessibility.

3.2.8.2 System validation

Here, the aim is to determine whether the system exactly meets what it was designed for.

The Loan Scheme Management system has been interacted with some few students and
administrators who have reviewed whether it fulfills all their requirements and perform
the activities to their expectations.

3.2.9 System Development Approach

I used the waterfall model for system development and this is because it is simple and
easy to understand and use, it is easy to manage due to the rigidity of the model-each
phase has specific deliverables and a review process among other advantages.

9
 CHAPTER FOUR: PRESENTATION OF THE PROPOSED SYSTEM
4.0 Introduction
This chapter full comprehends the functioning system that was designed for the Higher
Education Financing Board with illustrations.

4.1 System requirements

4.1.1 Functional requirements
 The System allows uploading and storing of all required documents in the loan
disbursement processes for example the financial card soft copy among others.

 This system provides group chats across institutions, store the chats and a general
chat from which all administrative communications shall be passed.
 The system also accesses students with all required information about the HESFB.
 The system provides an On-line registration option to all those who would wish to
apply on to the scheme through already benefiting students.

4.1.2 Non-Functional requirements

 The system is to have to panels; administrator‟s panel and user panel which are
well protected by passwords and automated redirection respectively.
 The system is online hosted hence is accessible by any user regardless of the
location.
 The system allows printing of documents required by the user.

4.2 System Operation Description

This system is online based and among others, it has two main users: the sponsored
students and the scheme administrators.

These have different roles, and view different dash boards however data and information
from both panels is communicative.

4.2.1 Features of the administration panel

i. Register new students on to the system.
ii. Update information on the entire system
iii. Receive or view all uploaded documents by students.
iv. Reply to students‟ questions via the chat rooms.

10
4.2.2 Features of the user panel
i. A responsive chat room connecting all institutions but with sub chat room options
which are to be used for scheme matters communication at any level.
ii. The user panel provides a disbursements section where users can upload all their
documents concerned with the disbursement process, and be able to view recent
disbursements.
iii. User panel provides downloadable documents on all information about the
HESFB.
iv. It opts to have a career class from which users are recommended with available
internship, volunteer and job opportunities.

4.3 Data flow diagrams

According to (visual-paradigm, 2012), A Data Flow Diagram (DFD) is traditional visual
representation of the information flows within a system.

4.3.1 The system context diagram

Figure 1: Context (Level 0) Diagram

11
A “REQUEST” covers all instructions from the user to the system and may include
username verification among others, on the other side, information entails all sorts of
system responses including those of authentication.

4.3.2 Level 1 Dataflow diagram

Figure 2: Level 1 System Data Flow Diagram

KEY
D1- User database with login details
D2- Chats Database with all the messages and comments posted plus the user‟s profile
D3- Disbursements Database (this one stores all students‟ documents uploaded)

12
4.4 Data modeling and design
The system database was first modeled using Visual paradigm 15.2 (Desktop
Application) as shown in the figure below and then designed using SQL Desktop
Application under the Wamp as the development environment.

The tables used are;

 USER
 CHAT
 DISBUSMENT
 CHAT MEMBER

4.4.1 The Entity Relations Diagram

This diagram shows a relationship between the system tables also known as tables.

Figure 3: Entity Relation Diagram developed by Visual Paradigm

13
4.5 Data dictionary
Attribute Name Notes Data Type Field Length Description
Name Full Names VARCHAR NOT NULL

User Name System Name VARCHAR NOT NULL

Password VARCHAR NOT NULL

Gender VARCHAR NOT NULL

DOB Date of Birth DATE NOT NULL

Image Profile Image BLOB

M.Status Marital Status VARCHAR

NIN National VARCHAR NOT NULL

Identification
Number

Phone_No Student‟s Phone INTEGER NOT NULL

Number

Email Student‟s Email VARCHAR NOT NULL

Address

W_NO WhatsApp Number INTEGER

F-Address VARCHAR

Un.Name University Name VARCHAR NOT NULL

Un.Reg-No University INTEGER NOT NULL

Registration Number

FCNo Financial Card INTEGER Primary Key

Number

Table 1: Data Dictionary

14
4.6 Project Screenshots
WAMP Server IDE

Figure 4: Screen shot of the WAMP Server IDE

15
The Login Panel
The User is prompted for Username and password for authentication into the system, sign
up in case he or she is new.

Figure 5: Screen shot of the Login Panel

16
THE HOME PAGE

This is the user dashboard or Home page for the user „s panel and not the administrator‟s
panel

Figure 6: Screen shot of the user/student's Home page

17
File Uploading Panel

This browses your device to access and upload any light file on it to the system.

Figure 7: Screenshot of the File uploading Panel

18
Disbursement Form
This form captures full details of the students Bio Data

Figure 8: Screenshot of the Disbursement Form

19
Chat Room Panel

Here students‟ coordinators can create chatrooms and add in all students from their
collages which groups are authenticated with group passwords except the general
chatroom created by the administrators.

Figure 9: Screen shot of the chatroom panel

20
The New Student application on to the scheme panel

On this panel, students enrolled for higher education can apply to join the scheme.

Figure 10: Screen shot of the online application panel

21
Administration Panel Access
The same login panel diverts access to two different home pages/ dashboards and this is
through the system authentication code upon which students are given a 1 and 2 for the
Administrators. It is only the administrators who can change the access code of any user.

Figure 11: .Screen shot after the Administration panel is accessed successfully

22
Administrators’ Panel
The administrator can add a new user, delete or edit any user information except the
password and he can navigate through the entire user panel.

Figure 12: Screen short of the administrator's panel

23
Add New User Panel
The administrator can add a new user and then it is the user to complete the registration
as he/she fills in the Bio data.

Figure 13: Screenshot of the add new user by the Administrator

24
 CHAPTER FIVE: SUMMARY, CONCLUSION AND RECOMMENDATIONS
5.0 Introduction
This chapter gives an overview of the loan management system aspects built, the
proposes and future prospects raised.

5.1 Summary
There are resources wasted in in terms of time, paper, money among others in the
secretarial section of the loan scheme most so in the disbursement and record keeping
processes. This is because the section hasn‟t yet incorporated technology sufficiently.

In the pursuit to lower the costs and facilitate efficient communication, technology was
the only way to go and hence the development of the loan scheme management system
that is to center all operations between the students and the administrators in the
secretarial section.

5.2 Conclusion
In conclusion, the designed loan Scheme Management System is efficient, user friendly
and adequately meets the minimum expectations that it was designed for.

The old system will be abandoned due to inefficiency and take up the new system though
mobilization will be done first to inform the student users upon its existence and main
objectives.

5.3 Recommendations
I recommend other researchers who might want to take up further development of the
same system to include transaction modules between the scheme and other institutions
such as banks, universities among others.

I also recommend HESFB to implement this system as it will ease information flow
between them and the students, provide a 24-hour documentation access among other
which in the long run will improve the scheme efficiency and reputation significantly.

The researcher further recommends all students on the scheme to make use of this system
but first understand its major aims.

25
 REFERENCES
Lndex.php. (2018, December 2nd). Retrieved from hesfb:
https://www.hesfb.go.tz/index.php/option?option=content&view=artical&id=32&
itemid=66

Aaron_Hill. (2003). Types of Loans. INTRODUCTION TO BUSINESS.

Akram, J. (2011). ENHANCING STRATEGIC AND TACTICAL PLANNING. THE

SIGNIFICANCE OF MANAGEMENT INFORMATION SYSTEMS, 459-470.

al, G. e. (1995). DATA BASE SYSTEMS.

al, G. e. (1995). Databases. DATABASE SYSTEMS.

Benita, Y. (2006). Reasons for using php. PHP-HYPERTEXT PROCESSOR, 18-20.

BOARD, T. H. (2018, December 2nd). index. Retrieved from hesfb:

https://www.hesfb.go.tz/index.php?option=content&view=article&id=32&itemid
=66

Cohen_ AM:& Kisker, C. B. (2009). The shaping of American higher education:. San
Francisco: Jossey-Bass.

Dhungana, S. (2002). MIS, 10-13.

Dimple, P. M. (2017). Benefits and disadvantage of library automation. International

Journal of All Research Education and Scientific Methods.

Fuller, M. B. (2014). A History of Financial Aid to Students. Student Financial Aid , 1-

29.

Grammatikou.et.al. (1995). Databases. DATABASE SYSTEMS.

Harvard_University. (1874). private student lending.

HESFB-Tanzania. (2018, December 2nd). Retrieved from

https://www.hesfb.go.tz/index.php?option=content&view=artical&id=32&itemid
=66

26
Hua.Shen. (2010). Advantages and disadvantages of students loan systems. International
education studies, 45-47.

K.Dagba, T. &. (2014). A loan management system as web services.

Keneth, L. &. (2007). Managing the digital firm. Management Information Systems, 103 -
124.

Keneth, L. (2007). Managing a digital firm. Management information Systems, 103 -125.

Mitchell, J. (2019). WALL STREET JOURNAL.

Mowlson, A. R. (1643, May 9). Bequest of Lady Mowlson. Retrieved JUNE 5, 2019,
from Bequest of Lady Mowlson Cambridge,MA, United States of American:
http://ids.lib.harvard.edu/ids/view/24938613?buttons=y

Mussa, A. (2015, March 16). International Journal of Management Sciences and Business
Research. pp. 45-47.

MUSUMBA. (2006). Academia. Retrieved from http://www.academia.edu/3239904

Stoner, J. (1995). MANAGEMENT 6th EDITION LONDON, 21-25.

TEBAJUKIRA, M. (2010, APRIL 13). STUDENTS LOAN SCHEME.

Thelin_J.R&Wilkinson. (2011). A history of American higher education (2nd ed.).

Baltimore: The Johns Hopkins University Press.

visual-paradigm. ( 2012, January 27). visual-paradigm.com. Retrieved from

https://www.visual-paradigm.com/tutorials/data-flow-diagram-dfd.jsp

Yogesh.D. (2017). International Journal of Information Management.

27
 APPENDICES
SQL SYNTAX FOR DATABASE DESIGN.
Creating the chat Table

CREATE TABLE `chat` ( `chat_id` int(11) NOT NULL, `chat_name` varchar(60) NOT
NULL,

`date_created` datetime NOT NULL, `chat_password` varchar(30) NOT NULL,

`userid` int(11) NOT NULL) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Creating the chat_member Table

CREATE TABLE `chat_member` (

`chat_memberid` int(11) NOT NULL,

`chatroomid` int(11) NOT NULL,

`userid` int(11) NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1;

Creating the user Table

CREATE TABLE `user` (

`userid` int(11) NOT NULL,

`username` varchar(30) NOT NULL,

`password` varchar(150) NOT NULL,

`uname` varchar(60) NOT NULL,

`photo` varchar(200) NOT NULL,

`access` int(1) NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1;

28
SYSTEM CODE

<!DOCTYPE html>

<html>

<html lang="en" >

//linking to the css file

<link rel="stylesheet" type="text/css" href="home.css">

<body>

//creating side bar

<div id="sidebar">

<div class="toggle-btn"></div>

<span></span>

<span></span>

<span></span>

<ul>

<li><a href="about.php">ABOUT</a></li>

<li><a href="HESFB-Final-Advert-2018.pdf">Eligible Courses</a></li>

<li><a href="terms.php">TERMS&CONDITIONS</a></li>

<li><a href="contact.php">CONTACT HESFB</a></li>

<li><a href=" https://ilmis.hesfb.go.ug/index.aspx">APPLY ONLINE</a></li>

</ul>

</div>

</body>

</html>

29
//now creating nav bar

<html>

<link rel="stylesheet" type="text/css" href="task.css">

<body>

<ul>

<li><a>HOME PAGE</a></li>

<li><a>DISBURSMENTS</a>

<ul>

<li><a><a href="upload.php">upload documents</a></a></li>

<li><a><a href="disbursment.html">fill disbusment form</a></a></li>

<li><a>recent disbusments made</a></li>

</ul>

</li>

<li><a>CAREERS</a>

<ul>

<li><a href="https://ugfacts.net/list-internships-uganda-undergraduate-
postgraduates/">Internship</a></li>

<li><a href="https://theculturetrip.com/africa/uganda/articles/10-top-
organisations-to-volunteer- for- in-uganda/">voluntary work</a></li>

<li><a><a href="https://www.greatugandajobs.com/jobs">Jobs</a></li>

</ul>

</li>

<li><a>LATEST NEWS</a>

30
 </li>

<li><a>Chat Room</a>

<ul>

<li><a><a href='user/'>chat</a></a></li>

</ul>

</li>

<li><a><a id="exit" href="user/logout.php">LOGOUT</a> </li>

</ul>

</body>

</html>

This is just part of the system code and for any case, the entire zipped code can be
downloaded from:

31