DESIGN AND IMPLEMENTATION OF SUSU COLLECTION SYSTEM

BY

ABDALLAH HAIRIYA WUNNAM

(20200204131)

SUPERVISOR: DR. MOSES APAMBILA AGEBURE

A System Project Report Submitted in Partial Fulfillment of the Requirements

for the Award of the Diploma in computer science C. K. Tedam University of
Technology and Applied Sciences.

OCTOBER, 2022

1
 DECLARATION

I hereby declare that the project was carried out by Abdallah Hairiya Wunnam in the

department of computer science and that no part of it has been presented for another

diploma or certificate in this university or elsewhere. Related works by others which

served as source of knowledge have been duly acknowledge and referenced.

SIGNATURE................................ DATE:.................................

STUDENT NAME: ABDALLAH HAIRIYA WUNNAM

STUDENT ID: 20200204131

i
 CERTIFICATION

I certify that this work was carried out by Abdallah Hairiya Wunnam in the department

of computer science as part of requirement for the award of diploma in computer

science of C.K Tedam university of technology and applied sciences (CKT-UTAS)

Navrongo campus

SIGNATURE................................ DATE: .................................

SUPERVISOR: DR. MOSES APAMBILA AGEBURE

SIGNATURE: .................................... DATE: ............................

HEAD OF DEPARTMENT: PROF. MOHAMMED IBRAHIM DAABO

(Department of Computer Science)

ii
 ABSTRACT

This project creates a system that will enable Susu saving activity to be performed on

the fly using computer devices. The existing manual and system have been studied

and analyzed to obtain a safety saving and reliable system. Evolutionary water-fall

model is based on building actual functional water-fall model with minimal

functionality in the beginning. The new system that is developed in this project runs

on all computers. The system was developed using PHP, JavaScript, Bootstrap,

HTML and CSS for the website. MySQL was used as the database engine for the

system.

iii
 ACKNOWLEDGEMENT

First, I express my heartiest thanks and gratefulness to almighty Allah for his divine

blessing makes it possible to complete the final year project successfully.

I am really grateful and wish to express my profound indebtedness to Dr Moses

Apambila Agebure, Lecturer, Department of Computer Science. His endless patience,

scholarly guidance, continual encouragement, constant and energetic supervision,

constructive criticism, valuable advice has made it possible to complete this project.

I would like to express my heartiest gratitude to Dr. Mohammed Ibrahim Daabo,

faculty members and the staff of Department of Computer Science in CK Tedam

University of Technology and Applied Sciences.

iv
 DEDICATION

To my beloved parents.

v
 TABLE OF CONTENTS
DECLARATION ............................................................................................................ i
CERTIFICATION .......................................................................................................... ii
ABSTRACT .................................................................................................................. iii
ACKNOWLEDGEMENT ............................................................................................ iv
DEDICATION ............................................................................................................... v
ABBREVIATIONS ..................................................................................................... viii

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

INTRODUCTION ........................................................................................................ 1
1.1 Background of the study .......................................................................................... 1
1.2 Statement of the problem......................................................................................... 1
1.3 Objectives of the study ............................................................................................. 1
1.4 Scope and limitations of the study ........................................................................... 2

CHAPTER TWO.......................................................................................................... 3
LITERATURE REVIEW ............................................................................................ 3
2.1 Introduction .............................................................................................................. 3
2.2 Review of existing systems ...................................................................................... 3
2.2.1 Agalloch Financial Monitor (AGAMON) ......................................................... 3

CHAPTER THREE ..................................................................................................... 6

METHODOLOGY ....................................................................................................... 6
3.1 Introduction .............................................................................................................. 6
3.2 System Methodology................................................................................................ 6
3.2.1 Procedure Identification..................................................................................... 6

3.2.2 Waterfall Design ................................................................................................ 7

3.2.3 System Analysis ................................................................................................ 8

3.4 Proposed System Design ........................................................................................ 10

3.5 System Implementation .......................................................................................... 10

vi
 3.5.1 Choice of Programing Language ..................................................................... 10

3.5.2 Hardware Requirement .................................................................................... 11

3.5.3 Software Requirement ..................................................................................... 11

CHAPTER FOUR ...................................................................................................... 12

DESIGN AND IMPLEMENTATION ...................................................................... 12
4.1 Introduction ............................................................................................................ 12
4.2 Use Case Diagram .................................................................................................. 12
4.3 Database Design ..................................................................................................... 13
4.3.1 System Model of View ........................................................................................ 14
4.3.2 Collector Login Interface .................................................................................... 14
4.3.3 List Members Interface .................................................................................... 14

4.3.4 Add New Member Interface ............................................................................ 14

4.3.6 Update Payment Interface................................................................................ 16

4.3.7 Delete Member Interface ................................................................................. 16

4.3 System Review and Maintenance........................................................................... 17

CHAPTER FIVE ........................................................................................................ 18

CONCLUSION AND RECOMMENDATIONS ..................................................... 18
5.1 Introduction ............................................................................................................ 18
This chapter rounds off the research study with summary of findings, conclusions,
limitations and recommendations. More so, this chapter gives suggestions for
future research into the study area. .............................................................................. 18
5.2 Conclusion .............................................................................................................. 18
5.3 Recommendations .................................................................................................. 18
5.3.1 Areas of Future Research .................................................................................... 18
REFERENCE ............................................................................................................. 20

vii
 ABBREVIATIONS

UID: user Identification

MS: Microsoft

PC: Personal Computer

HTML: Hypertext Markup Language

SQL: Structured Query Language

IT: Information Technology

PHP: Hypertext Preprocessor

GUI: Graphical User Interface

viii
 CHAPTER ONE

INTRODUCTION

1.1 Background of the study

The need for information that is accurate when they are needed is one of the major

problems of management, as they are often used in the making of vital decisions.

Consequently, wrong or delayed information can lead to very costly mistakes which

may cost the firm or the individual a lot thereby portraying bad or poor managerial

ability.

Hence the need for susu collection is considered to be solution to these needs

identified. The traditional susu collection system bears a lot of negative effect to the

customers, especially to the incident that demands urgent attention.

The susu system is the most modern susu system. This system was built to perform

balance checks and who contributed.

1.2 Statement of the problem

The main problem this project seeks to address is to solve the problem of contributor

information lost and also solve the problem of losing information when needed in the

future.

1.3 Objectives of the study

Main objective

The main objective of this project is to develop a software for small susu enterprise.

1
 Specific objectives include:

I. To enable more people to have trusted their contribution to a good collector

II. To enable more people to know their contribution information is kept well.

1.4 Scope and limitations of the study

The project is fully and working software that can run on computer, capable of holding

all contribution information. This project will also show the limitations on the

operation of contribution before retrieving the money.

2
 CHAPTER TWO

LITERATURE REVIEW

2.1 Introduction

Susu collection is one of Ghana’s most ancient traditional banking systems. In the

Akan language, the term ‘Susu’ means “small small” as to indicate the saving

contribution paid on a daily basis by those economically active poor that decide to join

the scheme. In particular, Susu collection is a system in which a person decides to

make a daily contribution to another person, the Susu collector, for an agreed period,

usually a month (31 days). For the deposit collection service, the Susu collector is

remunerated with a fee. Hence, the Susu Collection system provides a way for saving

up (Rutherford 1999), i.e. saving small amounts of money over a period of time to

build a lump sum that may be used when needs arise in the future. The typology of

clients engaged in the Susu collection scheme spans through a great variety of socio-

economic and occupational groups running micro and small businesses in the informal

sector such as petty traders, farmers, salaried workers and artisans that are normally

excluded from mainstream banking.

2.2 Review of existing systems

2.2.1 Agalloch Financial Monitor (AGAMON)

Wherever you are in the world, you can manage, monitor, and administer Client loans,

savings and investments, Susu, and other financial products with the help of Agalloch

Financial Monitor (AGAMON), an intuitive web and mobile tool. It was created by a

group of seasoned Indian and Ghanaian E-Commerce experts and microfinance

specialists with the primary objective of resolving micro-finance management

challenges. It is an online application, so as long as there is internet access, it can be

3
accessed anywhere, at any time. Directors and Managers may quickly track loan

disbursement & recoveries, savings, and investments made by their loan officers with

the help of this feature, all without having to physically be in the office. A new

financial institution and its branches may be set up on the platform using the

application. (MOBILE APP/SOFTWARE FOR RURAL BANKS, - Agalloch Consult |

Facebook, 2014)

2.2.2 A susu conceptual model

In one academic model, susu collection is defined as; Susu collection is an age-old

collective savings model in Ghana where SUSU enterprise agents visit customers daily

gathering small savings and then returning them on request at the end of a cycle

(usually a month). Each cycle, one day’s worth of saving is deducted to cover cost of

collection.

According to this model susu can be said to consist of three inter-related concepts:

I. Susu Accounting

II. Susu Brokerage

III. Susu Financial Information Services

Most services in the categories designated Accounting and Brokerage are transaction-

based. The non-transaction-based services of an informational nature are however

essential for conducting transactions – for instance, balance inquiries might be needed

before committing a money remittance. The accounting and brokerage services are

therefore offered invariably in combination with information services. Information

services, on the other hand, may be offered as an independent module.

4
 susu may also be used to help in business men or women saving situations and

calculations.

Susu collection system Services susu can offer services such as the following:

Account Information

I. checking of account contribution history

II. number of people participating saving

III. names of people participating

Payments, Withdrawals

I. amount of daily saving

II. amount of withdrawal

5
 CHAPTER THREE

METHODOLOGY

3.1 Introduction

This chapter includes the methodology that was used or followed in designing the

proposed system. In order to focus on the processes of susu collection and how the

application works, the study analyzed the works of the current manual system of susu

collection to be able to come up with a more advanced system, the relationship that the

current system has with the collector, and the flexibility to changes of the current system.

The most suitable methodology used in developing this system was prototyping.

3.2 System Methodology

3.2.1 Procedure Identification

The waterfall paradigm is being applied to this project. The first Process Model to be

introduced was the Waterfall Model. (SDLC - Waterfall Model, 1970) It is often referred

to as a "linear sequential life cycle model." It is really simple to use and understand. In a

waterfall model, each stage must be completed before the next one can begin; there is no

overlap between them. The waterfall model served as the first SDLC approach for

software development. The waterfall paradigm, which represents the software

development process through a linear sequential flow, is used. This suggests that a phase

of development can only commence if the one preceding it is done. In this waterfall

paradigm, the phases do not overlap.

6
3.2.2 Waterfall Design

The waterfall is a sequential design process in which progress is seen as flowing

steadily downwards (like a waterfall) through the phases of analysis, system design,

implementation, testing, deployment and maintenance

The several stages of the Waterfall Model are depicted in the figure below.

Figure 3.1: Waterfall model

The Waterfall model's phases are:

I. Collection and analysis: In this stage, requirements and all necessary

information was taken her for the development of the system.

II. System Design: After considering the essential specifications from the

previous phase, a system design is created in this step. This system design

was used to define the hardware and system requirements, as well as the

overall system architecture.

7
 III. Implementation: Discrete programs or components are initially assembled

into the system, which is then combined with assistance from the system

design stage. Unit testing is the process of developing and evaluating each

unit's performance.

IV. Integration and Testing: After testing has been done to find faults and errors,

all of the units created during the implementation phase are merged into a

system.

V. Deployment: Once the project has undergone functional and non-functional

testing, it is deployed.

VI. Maintenance: It's possible that using the program will cause a number of

issues. Patches are released to fix specific issues. A number of upgraded

versions of the product have also been released. To deploy these

enhancements to the application, maintenance is performed.

3.2.3 System Analysis

A system is a harmonious arrangement of components hardware and software; that

interact to achieve a common goal (Stella and France, 2006). Analysis is the focus of

system development and is the stage when system designers’ works at two levels -

what to do and how to do. Analysis of susu collection system involves a detailed study

of various operations performed by it.

Every system is created against at least a particular problem; that is systems are

created to solve problems. This susu collection system solves the problem of lost,

fraud etc. The existing traditional susu collection is a manual one, that is, it uses

manual methods where susu collector takes contributors records on a piece of papers.

8
 In comparison with the manual traditional susu collection, susu collection system is an

automated system that simplifies the activities of the manual traditional susu collection

with better integration and updates of the manual traditional susu collections activities.

This automated system is designed and developed with Microsoft visual studio code

and Microsoft SQL management server. System analysis squarely deals with the

software development activities. Three basic stages are involved in designing and

delivering a good susu collection system (and any other system), namely; I. A

thorough analysis of the system. A problem understood is half solved.

II. Development of an effective automated system susu collection system; to meet

requirement in an effective and efficient way.

III. Developing, installation, testing of system components, training, management,

programming, monitoring of the system – susu collection system.

3.3 Constraints of the Existing System

The existing system which is a manual traditional susu collection of susu collection is

associated with the following constraints or problems;

I. Unreliability: this system (the existing system) can be manipulated since

human beings are directly involved in the process of collection; Humans can

easily misplace information as long as the information is on a piece of paper.

II. It brings up confusion between collectors and savers when the collector lost

the information of all members that contributed.

9
3.4 Proposed System Design

The proposed susu collection system is designed for institutions of business and is

specifically restricted to all business men and women. The context diagram of the

system is shown in figure 3.1.

3.5 System Implementation

Designing or developing a system is one thing, another is implementing, not just

implementing it, but the successful implementation. Implementation of any

information system or automated system depends on the hardware, software and

people. Hence, the hardware being mainly a personal computer (PC) with printers,

scanners and any peripheral that is needed.

The software for the implementation of this automated system is MS SQL server 2016

which serves as the database but there is no need for this software if a student or an

organization desire to make use of it. The operating system must be a Microsoft

windows operating system. The people consist of the users of the system which

encompasses of collector, organization and savers.

All the collectors must be trained and computer literates else the system’s aim and

objective will be defeated.

3.5.1 Choice of Programing Language

The system is designed using Microsoft visual studio code, MYSQL for database

management. Hence, the program testing simply involves running it on a web browser

application on a local host server provided by Apache 2.0 and supported webserver

2.0 application.

10
 3.5.2 Hardware Requirement

The following hardware components are needed

i. Personal computer (PC) – a desktop or laptop ii. Printer – a desk jet or inkjet iii.

Scanner

ii. Preferably color scanner pictures.

The personal computer should have a minimum of

i. Pentium 4 Processor

ii. 512 kb RAM

iii. GB Hard disk

3.5.3 Software Requirement

The needed software is as follows:

i. Chrome

ii. Microsoft SQL server

iii. Text editor/ Microsoft visual studio code.

11
 CHAPTER FOUR

DESIGN AND IMPLEMENTATION

4.1 Introduction

This chapter focuses, on the requirements for this system implementation. Information

about the installation is also discussed, moreover, the system is described in UML

(Unified Modeling Language) and the use case diagram is given. Finally, a discussion

of the developed system is presented.

4.2 Use Case Diagram

Update

Logi
Use Add new
member
Delete

Update
Paid
member

12
 4.3 Database Design

Database is critical for all business. A good database does not allow any form of

anomalies and stores only relevant information in an ordered manner. If a database has

anomalies, it is affecting the efficiency and data integrity. Database files are the key

source of information into the system.

It is the process of designing database files, what is the keys source of the information

into a system. The files should be properly designed and planned for collection,

accumulation, editing and retrieving the required information.

Database page

Figure 4.1 Entity Relationship Diagram

13
4.3.1 System Model of View

4.3.2 Collector Login Interface

The login interface is used to enter authentication credentials to access a restricted

page or form. A login generally requires the user to enter pieces of information,

username and password.

Figure 4.2: Collector Login Interface

4.3.3 List Members Interface

List member page is used by authenticated people to know each member in a group

for data source. It allows users to send queries as well as display payments.

Figure 4.3: members Interface

4.3.4 Add New Member Interface

New users can input their data and submit to a company or individual.

14
 Figure 4.4: Add a new member Interface

4.3.5 Paid Members Interface

Paid members is the process that is used to evaluate whether a product, service or a

system complies with regulations, specifically or conditions imposed at the start of a

development phase.

Figure 4.4: paid members Interface

15
4.3.6 Update Payment Interface

Update payment is the process where by a member pays his/her contribution to the

collector, the collector has to update the saver payment into the system by entering the

UID and the amount to update the saver payment into the system.

Figure 4.5: update payment Interface

4.3.7 Delete Member Interface

Delete member in this process, when a member quits from saving his/her payment into

the system. To delete the member from the account you will have to open the delete

member and write in the UID into the delete space to delete the member.

Figure 4.6: delete member Interface

16
 4.3.8 Update Password Interface

Update password in this process, when a collector learns that the people are getting to

know his/her password to prevent scam or suspicions of people getting your password

you will have to input the old password in other to register a new password. Figure

4.5: update password Interface

Figure 4.5: update password Interface

4.3 System Review and Maintenance

After successful testing and implementation, system review and maintenance is

necessary to do checks and balances and for the following:

i. Comparison of the system’s actual performance versus the anticipated

performance objectives.

ii. Assessment of each facet of the system with respect to present criteria.

iii. Correction of any error that may occur after its use for say one month.

iv. Updating of new features.

v. Unexpected problems

17
 CHAPTER FIVE

CONCLUSION AND RECOMMENDATIONS

5.1 Introduction

This chapter rounds off the research study with summary of findings, conclusions,

limitations and recommendations. More so, this chapter gives suggestions for future

research into the study area.

5.2 Conclusion

Automated systems have proved to be more successful when compared to manual

susu.

The susu collection system redefines the manual traditional susu, hence averts

conflicts and confusion. Since the value of every degree is the reputation of the

5.3 Recommendations

As a result of the outcome of this paid work, it is recommended that higher institutions

in Ghana should adopt and implement this susu collection system to help in reducing

confusion between savers and collectors.

5.3.1 Areas of Future Research

In the future, the following components can be added to the system in order to

improve its effectiveness and efficiency:

i. The system only accepts files in .csv file extension. In future the system

can be expanded to accept (. json, .xml, .sql, and .txt) file formats.

ii. A chat area could also be integrated into the system to allow sending

messages.

18
 iii. Settings and About page could be integrated in future.

Institution and the saver produced, the susu collection system will in no distant time

‘pocket’ the manual traditional susu system with the utilization of biometric

technology and video surveillance.

19
 REFERENCE

Byron, S.G. (2001). Theory and Problems of Programming with visual basic Schaum’s

Outline. McGraw – Hill USA. Sikiru, O.A. (2009).

Implementation of an Online Job recruitment system. An unpublished M.IT Thesis,

University of Lagos, Nigeria. Stella, C.C. and Franca, A.E (2006).

Principles of System Analysis and Design.Root print and publisher, Benin city – Nigeria.

Suhansa, R., George, Y. and Ronald, W. (2021). Journal of Industrial Technology.

Volume 27 Number 3. P1-8. Uzoka. (1998).

Wheatear; Ingham; Whitfield; and Shrivastava, (1994). Physical ID system: Implications

for integration and standardization, International Journal of Physical

Distribution and Logistics Management, Vol.34, No.2, pp.123-139.

20