FINAL YEAR PROJECT REPORT

LOAN MANAGEMENT SYSTEM

REPORT

SUBMITTED TO THE DEPARTMENT OF COMPUTER SCIENCE & IT

GHAZI UNIVERSITY DERA GHAZI KHAN

IN PARTIAL FULFILLMENT OF REQUIRMENTS FOR THE DEGREE OF

MCS (Master of Computer Science)

Submitted by

SHABANA PARVEEN

2020-GU-0012

Session 2020-2022

DEPARTMENT OF COMPUTER SCIENCE & IT

GHAZI UNIVERSITY DERA GHAZI KHAN, PUNJAB

PAKISTAN
 DEDICATION

ALL MY WORDS DEDICATED WITH RESPECT TO

MY LOVING PARENTS

WHOSE LOVE AND PRAYS ALWAYS ACCOMPANIES ME LIKE A SHINING STAR

WHENEVER I WAS IN DARKNESS

AND ENABLE ME TO REACH THIS STAGE.

MY PROJECT SUPERVISOR & MY TEACHER

i
 Acknowledgment
I would like to sincere gratefulness to Mr. Mui-zuud-din, lecturer in department of
Computer Science & IT Ghazi University DG Khan for his valuable advice and kind of
encouragement as internal guide during the whole process from time to time. He always
been a source of inspiration. Without his encouragement and help, this project would not
have materialized Last but not the least. I would like to express my sincere thanks to my
Family, Friends and specially my Sister Sohaila Parveen for his constant encouragement.

Shabana Parveen

ii
 Table of Contents
DEDICATION..........................................................................................................................................i
ACKNOWLEDGEMENT.....................................................................Error! Bookmark not defined.
LIST OF FIGURES/ PICTURES.............................................................................................................6
ABSTRACT.............................................................................................................................................8
Chapter 1..................................................................................................................................................9
Introduction...........................................................................................................................................1
1 Background to the problem and the HESFB...................................................................................1
1.0 Problem Statement......................................................................................................................2
1.1 Objectives of the Project.............................................................................................................2
1.1.1 Specific Objectives..................................................................................................................2
1.2 Purpose of the study....................................................................................................................2
1.3 Scope of the Project....................................................................................................................2
Chapter 2..................................................................................................................................................4
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 3..................................................................................................................................................6
Introduction...........................................................................................................................................6
3.0 Statistical hypothesis...................................................................................................................6
3.1 System Analysis and Design.......................................................................................................6
3.1.1 Current System Investigation..................................................................................................6
3.1.2 Analysis of Existing system....................................................................................................6
3.1.3 Problems of Existing system...................................................................................................7
3.1.4 Advantages of Proposed system..............................................................................................7
3.1.5 Design and implementation Methodology..............................................................................8
iii
 Software Requirements..........................................................................................................................8
3.1.6 Software tools used..................................................................................................................8
3.1.7 System Testing and Validation................................................................................................9
3.1.7.1 System Testing.......................................................................................................................9
3.1.7.2 System validation....................................................................................................................9
3.1.8 System Development Approach..............................................................................................9
Chapter 4................................................................................................................................................10
Introduction............................................................................................................................................10
4.0 System requirements.................................................................................................................10
Functional requirements......................................................................................................................10
4.0.2 Non-Functional requirements.................................................................................................10
4.1 System Operation Description...................................................................................................10
4.1.1 Features of the administration panel...........................................................................................10
4.1.2 Features of the user panel......................................................................................................12
4.2 Data flow diagrams...................................................................................................................12
4.2.1 The system context diagram..................................................................................................12
4.2.2 Level 1 Dataflow diagram.....................................................................................................13
4.3 Data modeling and design.........................................................................................................14
4.3.1 The Entity Relations Diagram...............................................................................................14
4.4 Data dictionary..........................................................................................................................15
THE HOME PAGE................................................................................................................................18
File Uploading Panel...........................................................................................................................19
Disbursement Form.............................................................................................................................20
Chat Room Panel.................................................................................................................................21
The New Student application on to the scheme panel........................................................................22
Administration Panel Access...............................................................................................................23
Administrators’ Panel..........................................................................................................................24
Add New User Panel...........................................................................................................................25
Chapter 5................................................................................................................................................26
iv
 Introduction.........................................................................................................................................25
5.0 Summary...................................................................................................................................25
5.1 Recommendations.....................................................................................................................25
Conclusion...........................................................................................................................................26
REFERENCES.......................................................................................................................................27

v
 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

vi
 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

vii
 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.

viii
 Chapter 1

Introduction
Chapter 1 Introduction

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 Background 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.

L
oan Management System 1
Chapter 1 Introduction

1.0 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.1 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.1.1 Specific Objectives

 To understand the pressing loopholes in the present system (manual system).

 To correlate the relevancy of the system among students on the scheme and the scheme
administrators.
 To learn more about the HESFB operations and analyze the supplementary add-ins into
the design

1.2 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.

L
oan Management System 2
Chapter 1 Introduction

1.3 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.

L
oan Management System 3
 Chapter 2

Literature Review
Chapter 2 Literature Review

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

Loan management system 4

Chapter 2 Literature Review

(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.

Loan management system 5

Chapter 2 Literature Review

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

Loan management system 6

Chapter 2 Literature Review

Stopper Bugs and on to that, it employs the cross-Platform Migration Strategy.

Loan management system 6

 Chapter 3

METHODOLOY
Chapter 3 Methodology

Introduction

Generally, the New system takes up four main stages in its development. These are;

 Software and information analysis

 Design

 Coding and implementation

 Testing and maintenance

Within these stages, particular concepts are looked up for and these are preceded as below.

3.0 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.1 System Analysis and Design

3.1.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.1.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.

Loan management system 7

Chapter 3 Methodology

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.1.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.1.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.

Loan management system 7

Chapter 3 Methodology

3.1.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.
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.1.6 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.

Loan management system 7

Chapter 3 Methodology

3.1.7 System Testing and Validation

3.1.7.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.1.7.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.1.8 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.

Loan management system 7

 Chapter 4

PRESENTATION OF THE PROPOSED SYSTEM

Chapter 4 Presentation of The Proposed System

Introduction
This chapter full comprehends the functioning system that was designed for the Higher Education
Financing Board with illustrations.
4.0 System requirements

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.0.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.1 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.1.1 Features of the administration panel

 Register new students on to the system.

Loan management system 10

Chapter 4 Presentation of The Proposed System

 Update information on the entire system

 Receive or view all uploaded documents by students.

 Reply to students‟ questions via the chat rooms.

Loan management system 11

Chapter 4 Presentation of The Proposed System

4.1.2 Features of the user panel

 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.
 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.
 User panel provides downloadable documents on all information about the HESFB.
 It opts to have a career class from which users are recommended with available internship,
volunteer and job opportunities.
4.2 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.2.1 The system context diagram

Figure 1: Context (Level 0) Diagram

Loan management system 12

Chapter 4 Presentation of The Proposed System

A “REQUEST” covers a l 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.2.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)

Loan management system 13

Chapter 4 Presentation of The Proposed System

4.3 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.3.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

Loan management system 14

Chapter 4 Presentation of The Proposed System

4.4 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

Loan management system 15

Chapter 4 Presentation of The Proposed System

Project Screenshots WAMP

Server IDE

Figure 4: Screen shot of the WAMP Server IDE

Loan management system 16

Chapter 4 Presentation of The Proposed System

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

Loan management system 17

Chapter 4 Presentation of The Proposed System

THE HOME PAGE

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

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

Loan management system 18

Chapter 4 Presentation of The Proposed System

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 Pane

Loan management system 19

Chapter 4 Presentation of The Proposed System

Disbursement Form

This form captures full details of the students Bio Data

Figure 8: Screenshot of the Disbursement Form

Loan management system 20

Chapter 4 Presentation of The Proposed System

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

Loan management system 21

Chapter 4 Presentation of The Proposed System

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

Loan management system 22

Chapter 4 Presentation of The Proposed System

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

Loan management system 23

Chapter 4 Presentation of The Proposed System

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

Loan management system 24

Chapter 4 Presentation of The Proposed System

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

Loan management system 25

 Chapter 5

SUMMARY

AND RECOMMENDATION
Chapter 5 Summary And RECOMMENDATIONS

Introduction

This chapter gives an overview of the loan management system aspects built, the proposes and
future prospects raised.

5.0 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.1 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.

Loan management system 25

 Conclusion

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

Loan management system 26

 References

REFERENCES

http://www.w3schools.com/php/default.asp

http://php.net/manual/en/tutorial.php

http://www.phptherightway.com/

https://www.w3schools.com/css/css_rwd_intro.asp

http://www.csstutorial.net/

http://www.asp.net/entity-framework

www.javascript.com/

http://www.jquery.com/

http://www.tutorialspoint.com/sql

Loan management system 27