DEVELOPMENT OF FINANCE MANAGEMENT SYSTEM FOR

MWENGE CATHOLIC UNIVERSITY

NO NAME REG.NUMBER SIGNATURE

1. FRANSISKA FIDELIS T/DIP/2019/0022
2. RAYMOND D. MARCO T/DIP/2019/0014
3. VERONICA SWAI T/DIP/2019/0007
4. LEAH SICHONE T/DIP/2019/0094
5. JASTIN E. KIREMI T/DIP/2019/0055

A PROJECT REPORT SUBMITTED IN PARTIAL FULFILLMENT OF THE

REQUIREMENTS FOR THE
ORDINARY DIPLOMA IN COMPUTER SCIENCE OF MWENGE CATHOLIC
UNIVERSITY

MOSHI, TANZANIA

(JULY, 2021)

ABSTRACT

This project has conducted to access the precision of payments towards the students at
MWECAU in Moshi Kilimanjaro. The project will use different kind of computers to accomplish
the payments of the students.

1
The main objective of the project is to develop a software tool that will be used during the
payment process of the student’s fees for the university.

2
 DECLARATION

We, Fransiska Fidelis, Raymond D. Marco, Veronica Swai, Leah Sichone and Jastin E. Kiremi
the undersigned, state that, this PROJECT is the innovative work of ours and that it has never
been submitted to any other University for the same.

FRANSISKA FIDELIS
Signature: …………………………... Date: _________________
RAYMOND D. MARCO
Signature: …………………………... Date: _________________
VERONICA SWAI
Signature: …………………………... Date: _________________
LEAH SICHONE
Signature: …………………………... Date: _________________
JASTIN E. KIREMI
Signature: …………………………... Date: _________________

The above declaration is confirmed by:

Supervisor Name: LUCILLA CHUWA

Signature: ____________________ Date: __________________

ACKNOWLEDGEMENTS

3
Firstly, we would like to thank the almighty God for giving us health during our studying
activities, sound mind and gift of breathing until now as we are able to complete this project.

Secondly, we would like also to appreciate the great support of our project supervisor Madam
Lucilla Chuwa who spared her time supporting and directing us on various step of this project,
her comment and suggestion on how to code and write the project is of great significance.

Lastly, we would like also to thanks our parent for financially and more support they gave us
from the beginning of our studies until today we are completing this project. Furthermore, we
thank all our friends and those who participate to this project in one way or another and
supporting and helping us different activities concerning our project.

4
 DEDICATION

We dedicate that this project to our beloved Computer Science Department, ICT Students who
ensured security as well as all, those who helped us in any way or another.

We also in a special way we dedicate this to Mr. Fujo Mwampashua our loved one who inspired
and encouraged us in reminding extremely understanding when they lucked our co-operation,
they dearly value to us. May the precious of the holy spirit be abundantly to them.

5
 TABLE OF CONTENTS

ABSTRACT.....................................................................................................................................i

DECLARATION.............................................................................................................................ii

DEDICATION................................................................................................................................iv

LIST OF TABLES.......................................................................................................................viii

LIST OF FIGUREURES................................................................................................................ix

LIST OF ABBREVIATIONS..........................................................................................................x

CHAPTER ONE..............................................................................................................................1

INTRODUCTION...........................................................................................................................1

1.1 Background Information...............................................................................................1

1.2 PROJECT Objectives........................................................................................................1

1.2.1 General Objective...........................................................................................................1

1.2.2 Specific objectives..........................................................................................................1

1.3 Significant of the PROJECT..............................................................................................2

CHAPTER TWO.............................................................................................................................3

2. REVIEW OF THE EXISTING SYSTEMS................................................................................3

3. Introduction..........................................................................................................................6

3.1 Area of the Study...............................................................................................................6

3.1.1 Study area and Project Scope.............................................................................................6

6
 3.2 Data Collection Methods...................................................................................................6

3.2.1Questionnaire...................................................................................................................6

3.2.2 Observation.....................................................................................................................6

3.3 Project Conceptual Design................................................................................................7

3.3.3 Requirements Analysis...................................................................................................8

3.3.4 Functional Requirements...........................................................................................8

3.3.5 Non-Functional Requirements...................................................................................9

3.4 System Design...................................................................................................................9

3.4.1 Conceptual Design..........................................................................................................9

3.4.3 Entity-Relationship Diagram........................................................................................11

3.4.4 Database Schema..........................................................................................................12

3.5 System Development Approach......................................................................................16

3.5.1 Development Methodology..........................................................................................16

3.5.2 Tools and Technologies Used.......................................................................................16

3.5.3 Other Operating Environment Requirements IF APPLICABLE.................................17

CHAPTER FOUR.........................................................................................................................18

RESULTSAND DISCUSSION.....................................................................................................18

4. Introduction........................................................................................................................18

4.1 System Development.......................................................................................................19

4.2 System Testing and Validation........................................................................................27

7
CHAPTER FIVE...........................................................................................................................28

CONCLUSSION AND RECOMMENDATIONS........................................................................28

5. Conclusion...................................................................................................................28

5.1 Recommendations and Future Work...............................................................................28

REFERENCES..............................................................................................................................29

APPENDICES...............................................................................................................................30

QUESTIONNAIRES.....................................................................................................................30

5.2 Project Budget.....................................................................................................................36

LIST OF TABLE

8
Table 1:Finance Management System at MWECAU....................................................................27

Table 2: Project Budget.................................................................................................................36

9
 LIST OF FIGUREURES

LIST OF ABBREVIATIONS

ACRONYM DEFINITION

10
i. ARIS: Academic Registration Information System.
ii. CCP: Chuo Cha Police.
iii. CSS: Cascading Style Sheet.
iv. ECS: Electronic Clearing System.
v. EFT: Electronic Fund Transfer.
vi. FMS: Financial Management System.
vii. HTML: Hypertext Markup Language.
viii. KCMC: Kilimanjaro Christians of Medical College.
ix. MoCU: Moshi Co-operative University.
x. MWECAU: Mwenge Catholic University.
xi. PC: Personal Computer.
xii. PHP: Hypertext Preprocessor.
xiii. SQL: Structure Query Language.
xiv. SSL: Secure Socket Layer.
xv. UCFS: University College Finance System.

11
 CHAPTER ONE

INTRODUCTION

1.1 Background Information

Worldwide, most of the students use to pay tuition fees so as to carry out their studies in
order to graduate schools, colleges or universities, during the admission year of their studies,
the students normally pay the Tuition fees approaches differ from country to country. For
instance, in East Africa like Tanzania, the processes for paying tuition fees into tertiary
institutions are decentralized in the sense that each university or college has an equal chance
to decide on their way of paying tuition fees independently. Such decentralization is known
to cause problems in terms of setting standards, uniformity in the tuition fees payment
processes. This has been proved to be costly in terms of time. While some students will not
be able to pay tuition fees within a time to many colleges and Universities, instead they took
a lot of time to pay the tuition fees[ CITATION dis21 \l 1033 ].

1.2 PROJECT Objectives

1.2.1 General Objective

The main objective of the project is to develop a software tool that will be used during the
payment process of the student’s fees for the university.

1.2.2 Specific objectives

Specific objectives of this project are:

S01: We have established and identified all the requirement on FMS for Mwenge
Catholic University.

S02:We have signed the FMS based on collected requirements.

1
 S03: We have implemented, tested and validated the software.

1.3 Significant of the PROJECT

i. The financial Management System in any country play a crucial role in the economy's
use of currency. At Mwecau will help the students and the operator (s) to run the
payment process during the payment in saving time and costs.

ii. It will help in lowering the transaction cost and increase returns which will
motivate the student to use more, other than collecting the bank slips to the
finance office.
iii. The Financial Management System (FMS) will helpto allocate savings into
investment channels. At Mwecau will helps in mobilizing savings and make better use
of funds from the students.
iv. Financial Management System involves the application of all managerial functions
such as planning, organizing, directing, and controlling in the finance function to both
student and operator(s), hence will make known to the students and operator(s) how
much has been paid.
v. Finance Management System (FMS) will help both students and Operator(s) to
monitor and corporate performance of the payment at the university.

2
 CHAPTER TWO

2. REVIEW OF THE EXISTING SYSTEMS

Globally, there are different payment systems that evaluate the students’ tuition fees to the
schools, colleges and universities. The Financial Management System control the widening
access to higher education. But there are difficulties like, how to pay and retrieve money,
poor records keeping and management and mismanagement of school’s project. Finance
management system has the capability on reducing the time cost of payment processes
(through reduction of turnaround time for entire payment process), has facilitated on how to
encourage use of paperless, and how to ensure control over forgery during collections of bank
slip (Mahundu, 2016), (Walter Nyakanyanga, 03 January 2019).

The project review comes from the perspective data review plan of several data bases and
web-based systems. Although has different purpose compared to the aimed system, they
share a similar ideology. Those ideas are like the payment and retrieve of financial services
is based from each country, the database designed tool and programs that help this system
software to work effectively it depends on the way on how has been designed by the
programmer.

In developed countries like China has different systems such as PayPal, Pay Ease, Wire
Transfer, Skrill Nettler in China, Bank Transfer (T/T) overseas and Western Union. The
PayPal System used in china is safe, easy and convenient. This payment made through
system by the continuity scholars by clicking the PayPal button on the webpages of “make
payment” when applying and follow the directions. (payment methods in china). Although
PayPal system is safe there are some challenge Include problem of budgeting, problem of
delegation of authority. Such Financial Management Systems that face the named challenges
include University College Financial System (UCFS) in China. Joint University Programmed
Financial System in Hong Kong (JUPFS). And the Universities Colleges Financial Service

3
(UCFS) in the United Kingdom (Zhang, 2009). For instance, the CUCFS is one among the
unique college Finance system in the world due to its functionality.

In developing countries like Uganda Christian University Banking halls are flooded with
parents and students trying to clear their school fees in time for the new semester. For most of
them, the long queues the have to endure seem to be the biggest challenges like downtime
and inadequate knowledge. The most frequent reported cause for downtime was poor
network connectivity, intermittent power; and ineffective computers respectively. ((BoU)
2012). In a quest to achieve the mission of developing and maintaining efficient, reliable and
secure payment system for Uganda, the payments and settlements payment systems; Cash,
Cheques, Electronic Clearing Systems (ECS), Electronic funds transfer (EFT), Credit and
debit card payment systems (BoU, 2012).

Likewise, In Universities of Ghana has deployed a web acquiring solution christened

“UGPay”. This solution provides a platform for secure “online” payment of tuition,
graduation, application forms, fees as well as payments for other services rendered by or
needed from the university. Platform accepts both Visa card and master card issued anywhere
(introduction to UGPay).

Same applied to Tanzania some universities have been developed their Financial
Management System (FMS), among of such University is University of Dar es Salaam has
deployed the system of Academic Registration Information System (ARIS). This system
helps the students to pay Online using their username account by logging to their account and
the following the steps of payment process. If the payment procedures are successfully
received by the University, then the system will automatically show that you have paid in
your ARIS Account and you will receive the Message that confirms your payment receipt.
And if the payment made is incorrect un successful the system will ask the student to write a
new control number with the correct amount. (University of Dar Es Salaam Payment
Procedures). Academic Registration Information System (ARIS) faced some challenges like

4
poor policy and legal framework, lack of national identification system, transactional
difficulty.

In case of Mwenge Catholic University (MWECAU) uses PASTEL Software that is a

program used in their online Management System for the university. PASTEL option is
numerous and include remote access via the internet, automatic backups of their data,
seamless upgrades of their accounting software. Apart from using this software has got some
challenges to the users such challenges are poor customer relationship management,
Insufficient security management system, loss of efficiency, outdated and un accuracy and
poor speed of access.

All the above challenges for the PASTEL Software hinder the productivity causing
inefficiencies which result in increased cost, loss of revenue and decreased customer
satisfaction. For these reasons there is a need to eliminated the challenges by providing an
updated management system, improving security of the system and making it to work with
much high speed as designed.

Therefore, the designed system will be more helpfully to the customers hence will save their
time during the payment process whereby the staff responsible with payment (BASA) will
have time to concentrate with other things apart from dealing with Bank slips, collecting
manually from the students.

5
 CHAPTER THREE

MATERIALS AND METHODS

3. Introduction

In this chapter our project covers all materials and methods that we have used to develop our
project. Such materials include computer, printer and papers, the method used is
questionnaire, and observation.

3.1 Area of the Study

3.1.1 Study area and Project Scope

The project will be done at MWECAU located at Moshi rural district (southern part of Uru
ward) in Kilimanjaro Region (GADM 2018). The university is located to the high populated
area about 22,904(2012, census), centered by different institute including Moshi Co-operative
university (MoCu), Chuo Cha Police (CCP) Moshi, Kilimanjaro Christian Medical Centre
(KCMC) and Mweka the College of African wildlife.

3.2 Data Collection Methods.

3.2.1Questionnaire
We used questionnaire to collect data for our project from various required resources.

3.2.2 Observation

We used observation as tool to gather different information from various areas by watching
different kinds of activities involving payments system which are done daily to the finance
office.

6
3.3 Project Conceptual Design

Step1. Users and Operator (s)

It is the first step where students will use different type of computers such Phone, Desk top
computer and Laptop as illustrated above Step1. Users (user no. 1 to user no. 3) “log in” to
their system to do payment of school fees whereby the request from the students is directed to
the server via the internet services, whereby the data are stored in database. Likewise, to the
Operator (s) “log in” via the internet to check out who has completed paid the fees.

Step2. Internet access

It is the second step in which the Request and Response about payment ‘to’ and ‘from’ the
sever (Data storage) passes through. It will enable and establish the communication between
the students and FMS operator (s) hence both information about the request and report has to
pass through the internet.

Step3. Data Storage (Database)

These is the last step whereas the information from the students is stored and where the
operator (s) ‘login’ to view the information of the students about the payment via the internet.
It stores and provides data and information to both users and operator (s). The system
calculates the payment once the student pays the fees, the information about the student’s
payment is processed and stored for later use. Data storage, store processed data that the
student and the operator(s) re-ask to know about the calculation on the total payment done
and shows full information about the final credits and depts of the student and the university
at large.

Therefore, the diagram above shows the way on how FMS, has been designed in a better way
to be more helpful to save multiple students at once’s with one or more operator (s), to reduce

7
and save the total time and costs in general. So, by the implementation of FMS will play a
great role on finance Management of the university (Figure: 1).

3.3.1Data flow diagram:

Our system allows both admin and student to login into the system in which admin can
register a new student, add fee structure that guide the payment of the student per year and
view the payment done by the student. To the student side a student can do registration, make
payment and view payment. It also allow both Admin and Student to change password and
logout from the system (Figure: 2)

3.3.2 Entity relationship diagram (E-R):

Refers to graphical representation that represent depicts relationships among the people,
objects, places, concepts or events within an information technology system. From our
project the E-R diagram shows the following relation, Login, User, Student, Account,
Receipt, Roles, Department, Course and Exam (Figure: 3).

3.3.3 Requirements Analysis

i. Text analysis
ii. Statistical analysis
iii. Predictive analysis

3.3.4 Functional Requirements

A. User side function requirements

i. System will allow Student to do registration
ii. System will allow Student to login
iii. System will allow Student to logout
iv. System will allow Student to make payments
v. System will allow Student to view a payment

8
 vi. System will allow Student to search their payments
vii. System will allow Student to Edit and delete incorrect information
viii. System will allow Student to change password
B. Admin side function requirements
i. System will allow Admin to login and logout
ii. System will allow Admin to add fee structure
iii. System will allow Admin to register a student
iv. System will allow Admin to Edit and delete student
v. System will allow Admin to Edit and delete payments
vi. System will allow Admin to search for student’s program and year
vii. System will allow Admin to change password

3.3.5 Non-Functional Requirements

i. System Scalability
Our system can be updated to add new features
Our system is available at any time and accuracy
Our system can be embedded with another platform

ii. System Security

We used Secure Socket Layer (SSL) to keep sensitive information sent across the
Internet encrypted so that only the intended recipient can access it.

9
3.4 System Design

3.4.1 Conceptual Design

Step1.
Step1. FMS operator (s)
Users

Operator (s)
Report. Operator (s)
log in.
Student
Payment
User no. 3
Report

Report
Request from
Student both users and Step3.
FMS operator (s)
Payment Data storage
User no. 2 Step2. Response to (Database)
both users and
Internet access FMS operator

Report

Student
payment

User no. 1

Fig:1 Financial Management System (FMS) framework.

Figure 1: Financial management system (fms) framework

From our project we used DFD (Data Flow Diagram) which makes easy and supported us
during our development of the project.

3.4.2 Our Flow Data Diagram (DFD)

10
 Login

Admin Student

Add fee View

registration
structure payments

Registration Make payments View Payments

Change password

Logout

Figure; 2 shows the Data Flow Diagram FMS.

11
 3.4.3 Entity-Relationship Diagram

Figure;3 shows the entity relationship FMS.

3.4.4 Database Schema

The following are pictures show the database schema of our project.

i. Shows the tables that are present in our project.

12
ii. Shows the database table of the student.

iii. Shows the database table structure.

13
iv. Shows the database table program year.

v. Shows the database table program.

14
 ii. Shows the database table bill.

iii. Shows the database table fee structure.

15
3.5 System Development Approach

3.5.1 Development Methodology

We used rapid prototyping model as a tool because:

i. It does not waste much time compare to other model

ii. It Allows early user feedback.
iii. It is cost effectively, allows to do product testing without great financial risk

3.5.2 Tools and Technologies Used

Architectural design; The software has been used programing language that is PHP (server
side) which is compatible to other language like HTM, JavaScript, CSS (client side) also it is
compatible with many popular databases like MySQL.

Security; The software has secure socket layer (SSL) to keep sensitive information sent
across the Internet encrypted so that only the intended recipient can access it.

Platforms; The software is compatible to all windows version.

S03: To implement, test and validate the software.

16
Implementation; The software has been implemented online through free host which is 0fee.

Testing; The software has been done by using real users in which 10 staff officers and 100
students were selected randomly and purposively respectively.

Validation; The software has been validated based on data from the testing phase in order to
determine the customers intention whether are they satisfies specified requirements of the
software or not.

3.5.3 Other Operating Environment Requirements IF APPLICABLE

i. Computers (laptop, phones and desk top computer).

We used them for writing(coding), and searching for related material through google
application via the internet.
ii. Printer and papers.
We used them in printing different documents including Questioner papers and
project proposal
iii. Browser applications and internet
We also used them to help us to know the related objects(documents) and more detail
on how our project can be common and relatives to the users worldwide by comparing
other system all over the world.

17
 CHAPTER FOUR

RESULTSAND DISCUSSION

4. Introduction

Finance Management System that we have developed is going to be helpful to the

university, most of the students will use to pay their fees so as to carry out their studies in
order to graduate. The students will normally be paying the fees approaches differ from their
date of entrance, program and year of study. For instance, Certificate, Diploma, degree,
masters and PHD programs. The processes for paying fees to the university has an equal
chance to decide on their way of paying fees independently. The process of collecting bank
sleeps seems to be a problem in terms of setting standards, uniformity on the payment
processes. This has been proved to be costly in terms of time. While some students will not
be able to pay tuition fees within a time to the Universities, instead they took a lot of time to
pay the tuition fees[ CITATION dis21 \l 1033 ].

18
 4.1 System Development

The following are the interfaces that are present to the admin side

i. The system interface for admin’s login.

From this interface the admin login into the system by writing his or her Username and
password to get access into the system.

ii. Admin’s interface side after logging into the system

19
 From this interface shows the home page to the admin side whereby admin can click to the
student Registration to see the registered students and can add them.

iii. Admin’s interface side after clicking to the “Student’s Registration”

Here the admin can add a new student by clicking “New” to the left hand of the computer.

20
iv. Admin’s interface side after clicking “New” to add a student.

From this interface admin add the student by filling the form as shown on the picture above.

iv. Admin’s interface side after clicking “Manage Payment” to add a student

21
v. Admin’s interface side after clicking button “add fee structure” to add fee structure of
a registered a student

22
vi. Admin’s interface side after clicking “Settings” to change password

23
 The following are the interfaces that are present to the student side.

i. The system interface for Student’s login.

24
 From this interface the Student login into the system by writing his or her Username and
password to get access into the system.

ii. Student’s interface side after logging into the system

25
 From this interface shows the home page to the student side whereby student can click to the
student Registration to do registration.

iii. Student’s interface side after clicking to the “Student’s Registration”

Here the student can do registration by clicking “New” button to the left-landside of the
computer.

iv. Student’s interface side after clicking “New” button to do Registration.

26
 From this interface Student do registration by filling the form as shown on the picture above.

v. Student’s interface side after clicking “Make payment” button to make payments.

27
vi. Student’s interface side after clicking “ Pay button” to pay fee.

28
vii. Student’s interface side after clicking “View Payment” to view payments done.

29
viii. Student’s interface side after clicking “Settings” to change password

30
4.2 System Testing and Validation

Table 1:Finance Management System at MWECAU.

Unit Test performed Status

Admin’s side To the admin side’s, we tested our project by Results were correct as
viewing a registered student, and logging into a expected for a system to
system using admin username and password to be of our project.
check for the registered students and were perfect
brought a correct result as we designed and
implemented

Student’s side To the student’s side, we tested our project by Results were correct as
creating account, editing, viewing, and logging expected for a system to
using different usernames and password for a be of our project.
registered student and we got a result as we
expected to be of our project)

31
 CHAPTER FIVE

CONCLUSSION AND RECOMMENDATIONS

5. Conclusion

Achievements through the project:

Both Admin and Student can login and logout successfully in the system.
Both Admin and Student can change password successfully in the system.
Student can make payments in which Admin can view successfully in the system.
Admin can add fee structure to guide payment of the student successfully.

5.1 Recommendations and Future Work

Our recommendation point of view we would like to encourage the Computer science
department or the university to improve more this project by embedding in the university
system where there can be reachable to the users to access, hence is useful and it simplify
student’s payment as well as the organization management by giving clear amount deposited,
number of registered and paid students during the year of study.

32
 REFERENCES

[ CITATION Pra \l 1033 ]

(n.d.). Retrieved from www.bou.edu.bd result 2020.

(n.d.). Retrieved from http://www.mcafee.com/us/security_wordbook/firewall.html.

(n.d.). Retrieved from McAfee. (n.d). Firewall. Retrieved April 30, 2009, from security
workbook:.

(n.d.). Retrieved from Mint.com. (n. d). Retrieved April 28th,2009, from www.mint.com.

BoU. (2012). Uganda.

Mwecau admission office. (2019/2020). Retrieved from Mwecau.ac.tz.

MWECAU, d. a. (2021). financial management system. moshi: mwenge.

Walter Nyakanyanga 03 jan 2019 , mahundu, 2016.

33
34
 APPENDICES

QUESTIONNAIRES

Our project intends to answer the following questions:

P01: What are the requirement for designing a financial management system.
P02: What are design tools for designing a software based on financial management
system.
P03: What are tools test, validation tools and implementation process for a software
based on financial management system.

35
i. Our System development codes for home interface

<?php include 'db_connect.php' ?>

<style>
span.float-right.summary_icon {
font-size: 3rem;
position: absolute;
right: 1rem;
top: 0;
}
.imgs{
margin: .5em;
max-width: calc(100%);
max-height: calc(100%);
}
.imgs img{
max-width: calc(100%);
max-height: calc(100%);
cursor: pointer;

36
 }
#imagesCarousel,#imagesCarousel .carousel-inner,#imagesCarousel .carousel-item{
height: 60vh !important;background: black;
}
#imagesCarousel .carousel-item.active{
display: flex !important;
}
#imagesCarousel .carousel-item-next{
display: flex !important;
}
#imagesCarousel .carousel-item img{
margin: auto;
}
#imagesCarousel img{
width: auto!important;
height: auto!important;
max-height: calc(100%)!important;
max-width: calc(100%)!important;
}
</style>
<div class="containe-fluid">
<div class="row mt-3 ml-3 mr-3">
<div class="col-lg-12">
<div class="card">
<div class="card-body">
<marquee><h4>WELLCOME TO MWENGE FINANCE MANAGEMENT
SYSTEM</h4></marquee>

37
<hr>
</div>
</div>
</div>
</div>
</div>
<script>
$('#manage-records').submit(function(e){
e.preventDefault()
start_load()
$.ajax({
url:'ajax.php?action=save_track',
data: new FormData($(this)[0]),
cache: false,
contentType: false,
processData: false,
method: 'POST',
type: 'POST',
success:function(resp){
resp=JSON.parse(resp)
if(resp.status==1){
alert_toast("Data successfully saved",'success')
setTimeout(function(){
location.reload()
},800)
}
}

38
 })
})
$('#tracking_id').on('keypress',function(e){
if(e.which == 13){
get_person()
}
})
$('#check').on('click',function(e){
get_person()
})
function get_person(){
start_load()
$.ajax({
url:'ajax.php?action=get_pdetails',
method:"POST",
data:{tracking_id : $('#tracking_id').val()},
success:function(resp){
if(resp){
resp = JSON.parse(resp)
if(resp.status == 1){
$('#name').html(resp.name)
$('#address').html(resp.address)
$('[name="person_id"]').val(resp.id)
$('#details').show()
end_load()
}else if(resp.status == 2){
alert_toast("Unknow tracking id.",'danger');

39
 end_load();
}
}
}
})
}
</script>
<style>
.collapse a{
text-indent:10px;
</style>

ii. System development codes for Navigation Bar

<nav id="sidebar" class='mx-lt-5 bg-dark' >

<div class="sidebar-list">
<a href="index.php?page=home" class="nav-item nav-
home"><span class='icon-field'><i class="fa fa-home "></i></span> Home</a>
<a href="index.php?page=students" class="nav-item nav-
students"><span class='icon-field'><i class="fa fa-users "></i></span> Student
Registration</a>
<a href="index.php?page=payments" class="nav-item nav-
payments"><span class='icon-field'><i class="fa fa-receipt "></i></span> Manage
Payments</a>
<!-- <a href="index.php?page=site_settings" class="nav-item
nav-site_settings"><span class='icon-field'><i class="fa fa-cogs"></i></span> System
Settings</a> -->

40
 <div class="float-left">
<div class=" dropdown mr-4">
<a href="#" class="nav-item nav-student" id="account_settings" data-toggle="dropdown"
aria-haspopup="true" aria-expanded="false"><i class="fa fa-cog"></i> Settings </a>
<div class="dropdown-menu" aria-labelledby="account_settings" style="left: -2.5em;">
<a href="changepassword.php?page=changepassword" class="nav-item nav-
password"><span class='icon-field'><i class="fa fa-lock "></i></span> change
password</a>
<a class="dropdown-item" href="ajax.php?action=logout"><i class="fa fa-power-off"></i>
Logout</a>
</div>
</div>
</div>
</div>
</nav>

41
5.2 Project Budget

Table 2: Project Budget

Milestone Activities Tools Costs (USD)

Milestone I: Requirement Engineering Data collection& Analysis Printing Questionnaire papers,50

Documentation, Observation and case study

Milestone II: Designing and Development Coding Pc(hp) 200

Milestone I: Implementation, Testing & Validation Hosting Free domain(0fee) 50

42
 Grand Total 300

43
44