GARDEN CITY UNIVERSITY COLLEGE

FACULTY OF APPLIED SCIENCES

Department of Computer Science

Automated Co-operative System:

A case study of Goodnews Credit Union

A Project presented to the Department of Computer Science, in partial fulfilment of the

requirements for the degree of Bachelor of Science in Computer Science

By

GREGORY APEATU (02220415)

April,2018
 DECLARATION
I hereby declare that the entire thesis work entitled, “AUTOMATED CO-OPERATIVE
SYSTEM” submitted to the department of Computer Science, Garden City University College,
in fulfilment of the requirement for the award of the degree of BSc Computer Science, is a
legitimate record of my own work carried out under the supervision of MR. KWAKU AFREH.

I further declare that the thesis either in part or full, has not been submitted earlier by me or
others for the award of any degree in any University.

GREGORY APEATU ………………………. …………………..

(Student) Signature Date

I, Mr. Kwaku Afreh declare that I supervised this student in undertaking his final year project.

MR. KWAKU AFREH ……………………….. …………………..

(Supervisor) Signature Date

i
 ACKNOWLEDGEMENTS
I am very grateful to all who in their diverse ways contributed immensely to making this work a
success. My sincere gratitude goes to my supervisor Mr. Kwaku Afreh for his selfless
contribution towards my project. The support provided by my family during the period I
embarked on this project is well acknowledged.
My healthful thanks to Mr. Osman Yakubu, Head of Department, Computer Science for
opportunity given me to undertake this project.
I acknowledge all who have in any way contributed to the success of this project.
Finally, to the staff of Goodnews Credit Union and Customers who availed themselves to me and
provided qualitative information to contribute to this success. God bless you all

ii
 ABSTRACT
Credit Unions play an important role in providing loans to weaker sections of the society and
hence contribute to the economic development of a nation. It is believed that credit unions have
serviced these group of the market which remained outside the traditional banking scope and this
contributed immensely to the development of their communities. Data for the study was obtained
from both primary and secondary sources. The study focused on Goodnews Credit union which
provides clients with products for savings mobilization, credit accessibility and loan services.
The study further revealed that reasons why people save with the union were because of the ease
with which they access loans and also the lower interest rate that is charged on the loans This
project will deal with the design and implementation of a Co-operative system which will aid the
firm in undertaking their operations. With the advent of mobile network communication like
SMS Technology the system will conveniently provide transaction details to members via their
Mobile phones or devices. For the successful completion of this software, suitable methodologies
and platforms will be used to aid in meeting the requirements of the system making it easier to
use.

iii
 Table of Contents
DECLARATION ............................................................................................................................. i

ACKNOWLEDGEMENTS ............................................................................................................ ii

ABSTRACT................................................................................................................................... iii

LIST OF FIGURES ...................................................................................................................... vii

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

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

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

1.0 Introduction ...................................................................................................................... 1

1.1 Background & History ..................................................................................................... 1

1.2 Statement of Existing Problem......................................................................................... 2

1.3 Aims and Objectives ........................................................................................................ 3

1.4 Justification of the Problem.............................................................................................. 3

1.5 Scope and Limitation of Research ................................................................................... 4

1.6 Proposed Chapter Outline ................................................................................................ 4

CHAPTER TWO ............................................................................................................................ 5

2 LITERATURE REVIEW ....................................................................................................... 5

2.1 Introduction ...................................................................................................................... 5

2.2 Existing System ................................................................................................................ 6

2.3 The Proposed System ....................................................................................................... 7

2.3.1 Benefits of the Proposed System .............................................................................. 7

CHAPTER THREE ........................................................................................................................ 8

3 METHODOLOGY ................................................................................................................. 8

3.1 Data Collection ................................................................................................................. 8

3.1.1 Interview ................................................................................................................... 8

3.1.2 Document Sampling.................................................................................................. 9

iv
 3.2 Software Development Methodology .............................................................................. 9

3.3 Development tools and platform .................................................................................... 10

CHAPTER FOUR......................................................................................................................... 13

4 SOFTWARE REQUIREMENTS SPECIFICATIONS ........................................................ 13

4.0 Introduction .................................................................................................................... 13

4.1 Functional Requirements................................................................................................ 13

4.1.1 Member Registration .............................................................................................. 13

4.1.2 Update Records ....................................................................................................... 13

4.1.3 Contribution ............................................................................................................ 13

4.1.4 Loan ........................................................................................................................ 13

4.1.5 Loan Payment ......................................................................................................... 13

4.1.6 Check Balance ........................................................................................................ 14

4.1.7 Report...................................................................................................................... 14

4.1.8 User Setup ............................................................................................................... 14

4.1.9 Withdrawal .............................................................................................................. 14

4.2 Use Case ......................................................................................................................... 15

4.2.1 Use Case Description .............................................................................................. 18

4.3 Non‐functional requirements.......................................................................................... 20

CHAPTER FIVE .......................................................................................................................... 21

5 SYSTEM DESIGN AND IMPLEMENTATION ................................................................. 21

5.1 System Architectural Design .......................................................................................... 21

5.2 Database Design ............................................................................................................. 23

5.2.1 Database Schema .................................................................................................... 27

5.2.2 Entity Relationship Diagram................................................................................... 27

5.3 User Interface Design ..................................................................................................... 28

v
 5.3.1 Login Interface ........................................................................................................ 30

5.4 SYSTEM TESTING PLAN ........................................................................................... 37

5.4.1 UNIT TESTING ..................................................................................................... 38

CHAPTER SIX ............................................................................................................................. 44

6 CONCLUSION ..................................................................................................................... 44

6.1 Summary ........................................................................................................................ 44

6.2 Limitations and Challenges ............................................................................................ 44

6.3 Recommendation and Future work ................................................................................ 45

REFERENCES ............................................................................................................................. 46

APPENDIX A ............................................................................................................................... 47

APPENDIX B ............................................................................................................................... 48

APPENDIX C ............................................................................................................................... 56

vi
 LIST OF FIGURES
Figure 3.1 Iterative and Incremental Methodology ........................................................................ 9
Figure 4.1 Use case for Auditor .................................................................................................... 15
Figure 4.2 Use case for Administrator .......................................................................................... 16
Figure 4.3 Use case for Cashier .................................................................................................... 17
Figure 4.4 Use case for Member ................................................................................................... 18
Figure 5.1 N-Tier Application ...................................................................................................... 22
Figure 5.2 Entity Relationship Diagram ....................................................................................... 27
Figure 5.3 Login Interface ............................................................................................................ 30
Figure 5.4 Login Error Screen ...................................................................................................... 30
Figure 5.5 Main Interface for Administrator ................................................................................ 31
Figure 5.6 Member Contribution Form ........................................................................................ 31
Figure 5.7 Member Withdrawal Form .......................................................................................... 32
Figure 5.8 Loan Application Form ............................................................................................... 32
Figure 5.9 Loan Payment Form .................................................................................................... 33
Figure 5.10 System User Setup ..................................................................................................... 33
Figure 5.11 Member Registration Form ....................................................................................... 34
Figure 5.12 Expenditure Calculator Form .................................................................................... 35
Figure 5.13 Income Form ............................................................................................................. 35
Figure 5.14 Reports on Account Numbers Assigned to Members and their Balances ................. 35
Figure 5.15 Interface for Auditor .................................................................................................. 35

vii
 LIST OF TABLES
Table 4.1 Hardware And Software Requirements ........................................................................ 14
Table 4.2 Use Case Description .................................................................................................... 19
Table 5.1 Customer Table ............................................................................................................. 23
Table 5.2 Guarantor Table ............................................................................................................ 23
Table 5.3 Guarantor Table ............................................................................................................ 24
Table 5.4 System User Table ........................................................................................................ 24
Table 5.5 Loan Table .................................................................................................................... 24
Table 5.6 Loan Application Table ................................................................................................ 25
Table 5.7 Loan Payment Table ..................................................................................................... 25
Table 5.8 LoanState Table ............................................................................................................ 25
Table 5.9 Logbook Table .............................................................................................................. 25
Table 5.10 Next of Kin Table ....................................................................................................... 26
Table 5.11 Operations Table ......................................................................................................... 26
Table 5.12 Profit Table ................................................................................................................. 26
Table 5.13 Rates Table ................................................................................................................. 26
Table 5.14 Transaction.................................................................................................................. 27

viii
 CHAPTER ONE

1 INTRODUCTION

1.0 Introduction
Accessibility to credit union services is highly recognized as an important tool for both low and
poor income groups to save their money, invest in productive purposes, and ultimately improve
their lives. The introduction of Co-operative savings and credit institution has provided millions
of its members with financial services. In Africa, the credit union organization has paved the way
for poor rural communities to have access to financial services. Credit unions are institutions
known for mobilizing savings and providing loans for productive purposes, and economic, and
social and cultural activities (Fidelis, 2009).

Credit union are also recognized as a feasible institution which use a combination of modern and
local management systems as part of their daily functioning. Credit unions as a form of co-
operative are designed primarily to provide members with efficient and inexpensive savings and
loans services. Members are generally expected and indeed encouraged to save on a regular basis
and these savings are lent on favorable terms, usually to members (Ojemark, 1980).

Co-operatives are institutional set –ups whose ownership as well as management are entrusted in
the hands of their members who double up as the patrons. In co-operatives, all members hold
equal rights at decision making irrespective of their level of skills or contribution to the resources
of the organization. The strengths of co-operatives include facilitation of resource pooling,
sharing risks and profits and trade facilitation for members and other clients

1.1 Background & History

Credit unions are a form of co-operative, designed primarily to provide their members with
efficient and inexpensive savings and loan services. (Goricke, 2007)Members are generally
expected and encouraged to save on a regular basis and these savings are lent on favourable
terms to members. In the decades following independence, alongside other types of co-
operatives, the credit union movements rapidly expanded especially in the rural part of most
African countries. In rural Africa, credit unions have taken on the character of multi-purpose co-
operatives; their activities go far beyond elementary custody of money and financial transactions
1
These tendencies can also be traced in the development of the co-operative saving and credit
unions in Ghana. The co-operative credit union movement of Ghana had originally started in
1955 when the first credit union was established by the local community in collaboration with
Roman Catholic Missionaries in Jirapa, in the Upper West region of Ghana. The idea was
introduced by Rev.Father John McNulty an Irish Canadian.

In 1960, when Pope John XXIII appointed Bishop Dery as the Bishop of Wa he encouraged the
formation of Credit Unions in all the Parishes. Among them were Nandom , Kaleo, Ko,
Daffiama, Wa, Lawra and Tumu. The Bishop gathered courage at that time and met the President
Dr. Francis Kwame Nkrumah to discuss issues relating to the Credit Unions movement in Ghana.
(CUA, 1998)

The President of the first Republic finally said – You are doing a good service to Ghana and I
encourage you to continue and it’s from here that Credit Unions began to develop throughout
Ghana. Memberships were considered such an honor and privilege that almost everybody wanted
to be a member.

Soon after, as Kirsch and Goricke (Goricke, 2007) have stated, local communities took over the
lead in the credit union movement as it moved further into more urban agglomerations and, by
the end of 1989, these movements had about 90,000 members. As credit unions expanded from
Jirapa throughout the Upper West region and the rest of Ghana, the Credit Union Association
(CUA) was formed in 1968 as an association at the national level to represent all its affiliated
credit unions in Ghana. According to the CUA definition (CUA, 1978): ‘a credit union is a free
association of people with a common bond who save and lend money to one another through co-
operative principles for productive and provident purpose’.

As such CUA's main functions include the expansion and consolidation of the credit union
movement in Ghana, provide administrative support to credit unions and form national and
international networks (CUA, 1978)

1.2 Statement of Existing Problem

The manual file system which was used in most credit unions in Ghana made room for
ineffective management of credit unions. The introduction of the computerized system for
managing its operations made it effective and transparent. In most credit unions in Ghana, loan
2
delinquency is a major problem and the inability of members to view or receive account
information has undermined their effectiveness. This is basically because of the weakness of the
existing system. Accessing and sharing of data by completely different departments has been
troublesome thanks to poor information management The proposed system will help facilitate
loan process and track down debtors when defaulted and also makes it possible for members to
receive or view account information in the comfort of their homes or workplace.

1.3 Aims and Objectives

The main aim of the system is to develop a web based application that will promote local
participation and as such contribute to sustainable, and reliable management of Credit union in
Ghana.

By the end of this project; the system will be able to;

 To record all personal information of its members and provide accurate reports on data
 To facilitate easy access to loans
 To record individual regular contributions and withdrawals
 To provide SMS alerts to members upon transactions

1.4 Justification of the Problem

Due to the problem stated above, it is necessary to develop software to help solve problem like:

Member Accessibility: The proposed system will enable members of the union to receive
account information in the comfort of their homes or work places

Security: System users of the software will have access pertaining to a specific access role when
they are defined. There would be audit trails for transactions for data entry, updating and deletion
of records.

User Friendliness: With provision of the graphical user interface, the proposed system will
make retrieval and storing of data fast and maintained efficiently. Moreover, the graphical user
interface will provide users a platform to deal with the system very easily.

Report Generation: Reports can be easily generated in the proposed system so user can
generate report as per the requirement.

3
To have high accuracy: The level of accuracy in the proposed system will be higher. All
operations would be done correctly and it ensures that whatever information is accurate

1.5 Scope and Limitation of Research

The project scope includes, developing an application that will be able to
 Keep records of its members
 Keep member regular transactions
 Facilitate easy access to loans and repayments
 Produce reports of accounts
 Provide SMS Notification on transactions

My project is such that, it is capable of being changed and advance feature would be included in
the next release in future. The feature that is not included in my project is the system cannot
allow users to do transactions online

1.6 Proposed Chapter Outline

The following outlines a summary of what each chapter entails;
Chapter One - the introduction of the system such as the general overview, background and
history of the foundation of the research. It also outlines the problems why it is important
undertaking this project as well as the aims and objectives of the software. It also states the
scope of the research work and finally a summary of each chapter.
Chapter two - literature review of the research.
Chapter three - research methodologies such as the data collection, the software
development methodology and finally the platform and tools to be used.
Chapter four - system requirement specification which outlines the functional requirements
that states the functions of the system, use cases which illustrates behavioural requirements
and finally non-functional requirements of the system such as speed, security, availability,
etc.
Chapter five - system architectural design, the database design and finally the user interface
design and finally the ways the software will be tested.
Chapter six -conclusion of the system stating the challenges faced and some
recommendation for the system so as to help produce a better system in the future.
4
 CHAPTER TWO

2 LITERATURE REVIEW

2.1 Introduction
Credit unions all over the world have been and continue to be an important institution for
development in most countries in recent times. ‘While they need seen several successes and
failures throughout this era, no different establishment has brought such a large amount of
individuals along for a standard sense’ than they need done. Concept of development, which
highlights the relationship between rural communities and policies of the state, credit unions and
other development organizations, will be reviewed. Particular attentions are paid to discussions
specifically associated with native establishments and also the socio-cultural dimensions of
credit union management.

On the basis of the approaches, the theory and practice of the newly developing field of
indigenous Knowledge Systems, the local institutional patterns, the practices and procedures, as
well as their implications for credit unions will be discussed (Ojemark, 1980). The development
of credit unions and their management is not an exclusive or an isolated practice. They are
affected by both internal socio-economic regulations and by external interventions and
influences.

Effective mobilization of native resources for endogenous development, therefore necessary to

the continuity and property of credit unions, depends on the participation of the local people
similarly as well as on appropriate management system that is ready to integrate and regulate the
varied structure relations and stakeholders concerned within the credit unions. The integration of
the various practices and procedures in the management of credit unions will be assessed within
the context of an integrated management approach. This integrated approach to credit union
management will be analyzed and described in more details to serve as an analytical structure for
the study. Credit union organizations in Africa, which are an expression per excellence of local
institutions, can essentially be referred to as indigenous institutions which have evolved in the
area over many generations Credit unions which have been established later on the basis of the
initiative and free will of the local community are as such generally managed by the members
themselves. The members are guided largely by the local socio-cultural values and norms, while
in some cases external influences have come to play an increasingly important role. This type of

5
local institutions has been widely used for centuries among the rural communities of Africa as is
also well documented by the studies of (Armburuster, 1984).

As the studies on Credit Unions by (Laidlaw, 1980) and (Prakash, 2003) have indicated, the
concept of Credit unions movements in general refers to a group of people working together to
attain certain socio-economic and cultural goals, using the philosophy and principles embedded
in the concept of Credit union (Fidelis, 2009)
Credit unions cover a kind of collective human action that is taken into account to be distinct
from standard public and personal enterprises. Since their origin, there has been a large vary of
approaches to the study of credit union. The classical definition, as was restated by (Digby,
1970), refers to Credit union as; ‘An association of persons, usually of limited means who have
voluntarily joined together to achieve a common economic and social goal through the formation
of a democratically controlled business organization making equitable contributions to the
capital required and accepting a fair share of the risks and benefits of the undertaking’. This
definition emphasizes that Credit union are associations of people who join together voluntarily
to meet their common socio-economic needs. The generally accepted description of a Credit
Union used by (ILO, 2013) is also based on this definition. ILO has also stressed that members
of Credit Union should accept a fair share of the benefits and risks involved in the Credit union
undertakings. Likewise, in my study, the credit union Goodnews Co-operative Credit union will
be analyzed through multidimensional approaches. Indeed, some parts of the credit union
movement tend to concentrate predominantly on economic activities as Farm work, building
houses, and financial services, whiles others focus on serving the social and cultural needs and
objectives of their members

2.2 Existing System

Credit union, with its definition being a group of people coming together with a common motive,
by putting or making contributions for their future support to use and also support the
communities, and its operation differs by the country of operation. The existing system used by
Goodnews Credit Union is a desktop application called Digibank. The system helps
computerizes member details and transactions and generate daily (as well as monthly, quarterly
and annual) reports.

These are the drawbacks of the existing system;

6
  The system sometimes shutdown unexpectedly
 The system sometimes double debit and double credit member accounts
 The system could not provide notification such as SMS on various transaction
 Searching for member details was difficult with the system

2.3 The Proposed System

The proposed project will provide an advanced way by effortlessly capturing and storing of
documents faster unlike the existing which was very slow.

With HTML platform, the user will interact with the system by following simple interface
instruction to achieve an objective without blemish. By the security status of MySQL server,
member’s information can now be secured from authorized users. Even with authorizes users,
one has to provide his or her personal credentials to have access to the system. Preventive
measures like login form will be included in the program.

2.3.1 Benefits of the Proposed System

System users of the credit union can now save and retrieve documents within seconds. A web
based database system for all member details and transaction will be saved to ensure data is
accessible by multiple users, with this data will be linked to other divisions that depend on the
information for strategic decisions and reporting purposes. The system will be able to provide
SMS notification to members on transactions.

7
 CHAPTER THREE
3 METHODOLOGY
3.0 Introduction
This chapter describes the data collection procedures, methodology and tools and languages used
in development of the system. In order to manage the return investment in ICT for institution, it
is essential that the advantages, risks and value effectiveness of using new technology and new
media are well understood in the context of application.

3.1 Data Collection

On my field of study, I took two different approaches to gather our records/data for the propose
project. These approaches include

 Interview
 Document Sampling

3.1.1 Interview
Interview is a conversation where questions are asked and answers are given. In common
parlance, the word ‘interview’ refers to a one on one conversation with one person acting in the
role of the interviewer and the other in the role of the interviewee. The interviewer asks
questions, the interviewee responds, with participants taking turns talking.

The type of interview used during my data collection was unstructured interview. Unstructured
interview is an interview in which questions are not prearranged. With this type of interview, it
varies widely, with some questions being prepared in advance in relation to a topic that the
researcher wishes to cover. It tends to be informal and free flowing.

Unstructured Interview was the main source of my data collection approach because individual
understanding of the existing system may differ among them; therefore, interviewing some of the
members helped me to know individual knowledge of the existing system. Through the selected
members, I was able to know what they want their system to look like, and also ideas that will
make them have more interest and participation in the Credit union

At the end of the interview, I was able to know that

8
  Members had to visit the union to know their account detail
 The users of the system complained that the system sometimes double debit and credit
member accounts and the system automatically shutdowns unexpectedly which was a
major problem
 Members were afraid of losing their money through poor data management

3.1.2 Document Sampling

On the other side of records gathering, document sampling approach was successful on its edge
of usage. Document sampling was used to get understanding into existing files and existing
system approaches. This includes scanning through a lot of written documents to do analysis of
the problem at hand. Data collected from the document analysis were analysed to address the
goals and objective of this project.

3.2 Software Development Methodology

A system development methodology in software engineering is a framework used to structure,
plan, and control the process of developing an information system.

The iterative and incremental SDLC Model is the methodology we used for the intended project.
The iterative process starts with a simple implementation of a subset of the software
requirements and iteratively enhances the evolving versions until the full system is implemented.
At each iterative, design modification is made and new functional capabilities are added. The
basic idea behind this model is to develop a system through repeated cycles and smaller portions
at a time. By using iterative model, a high level design of the system was created before I
actually began to build the product.

Figure 3.1 Iterative and Incremental Methodology

9
The phases and activities performed include:

Requirement analysis: Requirements and specification of the software are collected. As with
most any development project, the first step is to through an initial planning stage to map out the
specification documents, establish software and hardware requirements and general prepare for
the next stages of the cycle

Design: High-end functions are designed during this stage. An analysis is performed to nail
down the appropriate business logic, database models, and the like that will be required at this
stage in the project. The design stage also occurs here, establishing any technical requirements
(languages, data layers, services etc.) that will be utilized in order to meet the needs of the
analysis stage

Code: Coding of the system is done during this stage. The actual implementation and coding
process can now begin. All planning, specification, and design documents are coded and
implemented into the initial iteration of the project

Testing: Once the system is deployed, the next step is to go through a series of testing
procedures to identify and locate any potential bugs or issues that have cropped up

Evaluation: Once all stages have been completed, it is time for a thorough evaluation of
development up to this stage. This allows the entire team, as well as clients to examine where the
project is at, where it needs to be, what can or should change and so on.

3.3 Development tools and platform

The development tools and platform used for the intended project include

 Microsoft Visual Studio Code

Is an integrated development environment used to develop computer programs such as web
applications, websites, web services, mobile Applications etc.? Microsoft visual code was used
because of its advanced features such as intellisense which highlights and autocomplete syntax
and also provide smart completions based on variable types, functions definitions and imported
modules.

10
  XAMPP server
XAMPP which stands for Cross-platform(X), Apache(A), MySQL(M), PHP(P) and Perl(P).
It is a simple, lightweight Apache distribution that makes it extremely easy for developers to
create a local web server for testing purposes. XAMPP has components which include

1. Apache: Is the actual web server application that processes and deliver web content to a
computer
2. MySQL: Is an open source relational database management system based on Structured
Query Language. It runs on virtually all platforms, including Linux, Unix and Windows.
MySQL was used for my database aspect because it is scalable in the sense that it can
handle almost any amount of data up to as much as 50millions or more. The default size
limit is about 4GB. However, you can increase this number to a theoretical limit of 8TB
of data and its ability to support several development interfaces which include JDBC,
ODBC, and scripting (PHP and Perl), letting you create database solutions that run on
major platforms including Linux, UNIX, and Windows. MySQL includes solid data
security layers that protect sensitive data from intruders. Rights can be set to allow some
or all privileges of individuals. Passwords are also encrypted.

3. PHP which stands for hypertext Pre-processor is a server scripting language, and a
powerful tool for making dynamic and interactive websites. PHP was used because its
efficient, as you know you can enhance the performance of the website built in PHP, as it
is scalable when writing the codes as well as reliable too when you need to deal with a lot
of web pages. PHP also uses its own memory, so the workload of the server and loading
time gets reduced automatically, which results in faster processing speed. It also dynamic
and works with HTML to display dynamic elements on the page

 HTML which stands for Hypertext Markup Language is used to create web pages that
are displayed on the World Wide Web. HTML code ensures the proper formatting of text
and images so that your Internet Browser can display them as they are intended to look. It
also provides a basic structure of the page upon which Cascading Style Sheets are
overlaid to change its appearance.

11
 JavaScript is a scripting language primarily used on the web to enhance HTML pages
and is commonly found embedded in HTML code. JavaScript was used alongside with
HTML because it allows the pages to react to events, exhibit special effects, accept
variable text and also validate data.

12
 CHAPTER FOUR

4 SOFTWARE REQUIREMENTS SPECIFICATIONS

4.0 Introduction
This chapter describes the features and behaviour of the system or software application. It
includes a variety of elements that attempts to define the intended functionality required by the
customer to satisfy their different users.

4.1 Functional Requirements

A functional requirement specifies specific behaviour or functions of the system or what the
system must do. These include:

4.1.1 Member Registration

The system shall be capable of accepting and storing records of eligible members into the
scheme. Information such as Personal Details, Guardian Details, next of kin Details and
Member’s photograph are captured and stored into the database. The system automatically
generates a unique account number for each member registered

4.1.2 Update Records

The system shall be able to permit a user to find out a member’s details from the database
depending upon account number assigned. It shall provide the necessary controls for data entry
and record update.

4.1.3 Contribution
The system shall accept contribution to the scheme throughout the working hours of the week.
The system shall assist users to receive member contribution payment or someone on behalf of a
member. Information such as member account number, amount, payee’s name is captured and
stored into the database

4.1.4 Loan
The system shall allow members who have contributed into the scheme continuously for six
months to apply for loan

4.1.5 Loan Payment

The system shall assist users to accept repayments of all loans collected from the scheme with
the required interest charged.

13
4.1.6 Check Balance
The system shall allow users to preview and generate reports on Member’s financial details

Total contribution of a member and loan payment status can be checked on the system.

4.1.7 Report
The system shall be able to generate and print reports on periodic, quarter and yearly and also
provide management with detailed and required reports to be used for various forms f decision

4.1.8 User Setup

The system shall allow users to setup users such as Cashier, System Administrator, and Auditor
etc. and also assign roles to each.

4.1.9 Withdrawal
The system shall assist users to make withdrawals twice a month depending on the type of
account opened.

The main categories of system requirement are hardware and software which has been
tabulated below

Hardware Required Software Required

CPU: Intel Dual Core or higher Operating System: Microsoft Windows 7

Desktop/Laptop or higher

RAM: 1GB or higher Front End tools: PHP, JavaScript, HTML

HDD: 10 GB or higher Back End tools: MySQL Server

Keyboard, Monitor, Mouse, Printer

Table 4.1 Hardware And Software Requirements

14
4.2 Use Case
A use case describes what the system does, not how it does it work. The use model reflects the
view of the system of the user outside of the system.

Figure 4.1 Use case for Auditor

15
Figure 4.2 Use case for Administrator

16
Figure 4.3 Use case for Cashier

17
 Figure 4.4 Use case for Member
4.2.1 Use Case Description

Below gives the description of each use case

Actor Use Case Description

Administrator Login The administrator login to the system with his/ her
username and password.

Create System The administrator create, update and delete system users
User
Assign User The administrator is able to assign roles to system users
Role

Send Message The Administrator is able to send message to members

upon registration
Print Report The Administrator is able to print reports
Approve/Reject The Administrator is able to reject or approve member
loan request loan request

18
 Add/Edit/Delete The administrator would be able to create, edit and delete
a member

Logout After all activities, the administrator finally logs out of

the system.
Cashier Login The Cashier log into the system with his/ her username
and password.
View Members The Cashier is able to view member records

Reset his/her The Cashier is able to reset his or her Password

Password
Receive Member The Cashier is able to receive the member contribution
Contribution
Send Message The Cashier is able to send messages upon transaction

Logout After all activities, the cashier will logout from the
system

Auditor Login The auditor login to the system with his/ her username
and password.

Audit The Auditor audits administrator

Administrator
Audit Cashier The Auditor audits cashier

Audit Member The Auditor audits Member

Logout After all activities, the auditor will logout from the
system
Table 4.2 Use Case Description

19
4.3 Non‐ functional requirements

Non-functional requirements describe how the system works. It essentially specifies how the
system should behave. One could also think of non-functional requirements as quality attributes
of a system. Non-functional requirements cover all the remaining requirements which are not
covered by the functional requirements. They specify criteria that judge the operations of a
system, rather than specific behaviors.

Below are the non-functional requirements of the system:

 Usability: The system should be useful to enhance with further technology in the future
to improve its features compared to the existing system
 Security: The system is provided with authentication without which no user can be
permitted to access. Backups of databases would be consistent and the system should be
able to validate information in its respective fields
 Availability: The system should be available at all times and it will be up and running to
deliver useful services at given time
 Speed: The system shall assist the user with maximum speed to enhance productivity.
 Maintainability: The system shall be able to accept change to accommodate new
requirements
 Efficiency: The system should be able to perform in all independent paths that all the
logical conditions are satisfied
 Reliability: The system should pertain to all the situations so that it can be recoverable in
any error conditions.

20
 CHAPTER FIVE

5 SYSTEM DESIGN AND IMPLEMENTATION

5.1 System Architectural Design

A system architecture is the conceptual model that defines the structure, behaviour, and more
views of a system. An architecture description is a formal description and representation of a
system, organized in a way that supports reasoning about the structures and behaviours of the
system

My system has three layers which makes it possible for users to communicate effectively with
the system. These layers support direct flow of information on system development. These layers
include:

 Presentation Layer
 Application Layer
 Data Layer

Presentation Layer: This layer helps system users to interact directly with the system such as
graphic user interface (GUI)

Application Layer: This layer encapsulates the system logic (such as language rules and data
validation), this layer binds the user interface and the database together

Data Layer: This layer is where all data in the system are stored. You can securely store data on
this layer, do transaction, and even search through volumes of data in a matter of seconds.
MySQL database server was used in the project because for N-Tier architecture, one needs to use
non-embedded database server. (Clements, 1996)

21
 Figure 5.1 N-Tier Application
(Clements, 1996)

22
5.2 Database Design
This table shows a brief description of Customer

tblcustomer
Fields
Field Type Description
Accnumber varchar(10) Customer Accounts number
firstname varchar(15) Cusomer's Family Name
lastname varchar(15) Customer's last Name
middlename varchar(15) Customer's Middle Name
Gender Varchar(10) Customer gender
Gender enum('Male','Female') Customer's gender
DOB date Customer's date of birth
Phone Varchar(15) Phone number of member
Hometown Varchar(30) Hometown of member
Postaladd Varchar(50) Postal address of member
Housenumber Varchar(30) House number of member
Idtype Varchar(30) Type of id of member
Idnumber Varchar(20) ID number of member
Regdate Date Date member registered
Image Varchar(100) Image of member
acctype Varchar(15) Account Type
Registeredby Varchar(100) Name of staff who registered member
Table 5.1 Customer Table
This table shows a brief description of Guarantor

Field Type Description

Id Int(11) Primary key
Accnumber varchar(10) Member Accounts number
Fullname varchar(50) Guarantors full Name
Occupation Varchar(20) Guarantors occupation
Address Varchar(100) Guarantors address
Salary Float Monthly salary of guarantor
Phone varchar(15) Customer's phone number
Table 5.2 Guarantor Table

23
This table shows a brief description of Guardian
Field Type Description
Accnumber varchar(10) Customer Accounts number
gname varchar(15) Cusomer's Family Name
Occupation Varchar(30) Guardian occupation
Postadd Varchar(50) Postal address of guardian
Phone Varchar(15) Phone number of guardian
Table 5.3 Guardian Table
This table shows a brief description of system User
Field Type Description
Id Int(11) Systemuser id
Username Varchar(30) System user username
Password Varchar(64) Systemuser password
Type Varchar(25) Type of staff
Passwordchanged Varchar(5) Staff must change password
Fullname Varchar(100) Staff fullname
Contact Varchar(10) Staff phonenumber
Table 5.4 System User Table

This table shows a brief description of loan

Field Type Description

ID int(11) Primary Key
Accnumber Varchar(10) Account number of member
Amount Float(10,2) Amount of loan
Monthlypayment Float(10,2) Amount of money to be paid monthly
Totalpayment Float(10,2) Total loan
Startdate Date Date to start paying loan
Duedate Date Date to finish paying loan
Interest Float(10,2) Loan interest
Staff Varchar(100) Name of staff during loan activity
Check whether member has finish
Hasfinishedpaying Varchar(5)
paying loan
Table 5.5 Loan Table

24
This table shows a brief description of loan Application

Field Type Description

ID int(11) Primary Key
Accnumber Varchar(15) Account number of member
Amount Float(10,2) Loan amount requested
Date Date Date of loan application
Status Varchar Status of loan application
Table 5.6 Loan Application Table
This table shows a brief description of loan Payment
Field Type Description
ID int(11) Primary Key
Accnumber Varchar(16) Member accounts number
Amounpaid Float(10,2) Total amount paid
Dateofpayment Date Date of payment of loan
Requireddate Date Date to finish loan payment
Staff Varchar(100) Name of staff who issued payment
Table 5.7 Loan Payment Table

This table shows a brief description of loanstate

Field Type Description
ID int(11) Primary Key
Accnumber Varchar(16) Account number of member
Requiredmonthly Float(10,2) Amount required to pay monthly
Loanamount Float(10,2) Amount of loan and interest
Lastdatepaid Date Date to finish paying loan
Nextdatetopay Date Date of next loan payment
Table 5.8 LoanState Table

This table shows a brief description of Logbook

Field Type Description
ID int(11) Primary Key
Staff Varchar(100) Name of staff
Date Date Date of activity
Time Time Time of activity
Type Varchar(15) Type of activity
Table 5.9 Logbook Table
25
This table shows a brief description of Next of kin
Field Type Description
Accnumber Varchar(10) Primary Key
Fullname Varchar(100) Fullname of next of kin
Occupation Varchar(50) Occupation of next of kin
Phone Varchar(15) Phone number of next of kin
Postadd Varchar(100) Address of next of kin
Table 5.10 Next of Kin Table

This table shows a brief description of Operations

Field Type Description
ID int(11) Primary Key
Type Varchar(20) Type of operation
Amount Float(10,2) Amount of the particular operation
Description Varchar(50) Description of operation
Bywho Varchar(50) Name of staff involved in the operation
Date Date Date of operation
Table 5.11 Operations Table

This table shows a brief description of Profit

Field Type Description
ID int(11) Primary Key
Total Float(10,2) Total profit
Date Date Date
Table 5.12 Profit Table

This table shows a brief description of Rates

Field Type Description
ID int(11) Primary Key
Loaninterest Float(10,2) Interest rate for every loan collected
Registrationfee Float(10,2) Registration fee upon registration
Withdrawalrate Float(10,2) Withdrawal rate during withdrawals
Datemodified Date Date updated
Loanperiod Int(11) Number of month given to pay loans
Table 5.13 Rates Table

26
This table shows a brief description of Transaction

Field Type Description

ID int(11) Primary Key
Accnumbr Varchar(10) Member accounts number
Date Date Date
Type Varchar(15) Type of transaction
Amount float Amount involved during transaction
Staff Varchar(100) Staff
Bywho Varchar(50) Name/account number of transaction
Table 5.14 Transaction

5.2.1 Database Schema

A database schema is the skeleton structure that represents the logical view of the entire
database. It defines how the data is organized and how the relations among them are associated.
It formulates all the constraints that are to be applied on the data. A database schema defines its
entities and the relationship among them. (Lance, 2018)

5.2.2 Entity Relationship Diagram

Figure 5.2 Entity Relationship Diagram

27
5.3 User Interface Design
User interface design focuses on anticipating what users might need to do and ensuring that the
interface has elements that are easy to access, understand and use to facilitate those actions.

Making user interaction as simple as possible when designing the user interface is very important
and this must be considered during functional requirement phase of a software design.
To create an operational, usable and user friendly interface, the technical functionality with
visual element must put into consideration.
In actual fact, there are ten fundamental “heuristics” principles that must be followed when a
user interface program is to be design. These are more of a rule of thumb rather than usability
specific rules. (Nielsen, 1994)

The following are 10 heuristics general principles stated by Jakob Nielsen in his book titled
“The ten usability heurists”:

Visibility of system status

During the design of a system, the user interface design should make sure the interface is able
to inform the user what is going on at every point in time with appropriate feedback.
Match between system and the real world

The system should be able to communicate to the user in the language the user understands
rather than computer language that is, making information appear in natural and logical order.
User control and freedom

User often make mistake by clicking buttons which are not relevant to his/her current task,

therefore, a clearly mark “exit” button should have designed on the interface. Or better still,
“undo” and “redo” should to place on the interface too.
Consistency and standards

Platform conventions are important part of user interface design because user should be able
to know that a word that is read before still means the same thing when the same is encountered
on another line.
Error prevention

28
It is better to carefully design a software where there is no is no error. Either eliminate error
prone conditions or check for them and present users with a confirmation option before they
commit to the action.
Recognition rather than recall

The user should not be forced to remember what he/she had seen before from one part of the
dialogue to another. Objects, actions and many other options should be made very visible so that
the user will easily remember while instructions for use of the system should be visible or easily
retrievable whenever appropriate.
Flexibility and efficiency of use

Accelerators, unseen by the novice user, may often speed up the interaction for the expert user
such that the system can cater to both inexperienced and experienced users. Allow users to tailor
frequent actions.
Aesthetic and minimalist design

Information which is not relevant to the dialogue should not be placed on the design because all
other dialogue with compete the relevant information thereby diminishing their visibility.
Help users recognize, diagnose, and recover from errors

Error messages should be expressed in plain language (no codes), precisely indicate the problem,
and constructively suggest a solution.
Help and documentation

Even though it is better if the system can be used without documentation, it may be necessary to
pro-vide help and documentation.
Any such information should be easy to search, focused on the user's task, list concrete steps to
be carried out, and not be too large.

29
5.3.1 Login Interface
This login interface authenticates every entity who wants to use the system. This interface checks
for unauthorised users who do not have username and password stored in the system.

Figure 5.3 Login Interface

Figure 5.4 Login Error Screen

30
The main program interface for administrator where various programs are selected

Figure 5.5 Main Interface for Administrator

Figure 5.6 Member Contribution Form

This form is used to capture or make payment into the scheme. Payment can be made by self or
any other person, provides the payee provides an account number of the account holder

31
This form is used to process member withdrawals

Figure 5.7 Member Withdrawal Form

Figure 5.8 Loan Application Form

This form is used to process capture details for loan application provided the member has been in
the scheme for six months or more.

32
This form is used to capture loan payments for a member

Figure 5.9 Loan Payment Form

Figure 5.10 System User Setup

This for is used to setup new system users by the administrator

33
 Figure 5.11 Member Registration Form
A user uses the membership registration form to capture all the information about a new
member. Such information includes: Full name, Postal Address, Type of ID, Date of Birth,
Phone Number, Hometown, ID Number, Next of kin, Guardian Details and picture as well. A
unique account number is automatically generated for the member upon registration. The
information is then sent to database for storage.

34
 Figure 5.12 Expenditure Calculator Form
This form is used to capture organizational expenses

Figure 5.13 Income Form

This form is used to capture organizations income

35
Figure 5.14 Report on Account Numbers assigned to Members and their Balances

36
 Figure 5.15 Interface for Auditor
This interface gives the auditor the ability to audit administrator, cashier and member

5.4 SYSTEM TESTING PLAN

The system went through various stages of testing to validate and verify if it has met the
functional and non-functional requirements. Functional testing deals with verifying that the
system is providing the same output as required by the end user or business. The software was
tested by providing it with various form of input data so that output can be evaluated to see how
it conforms, relates or varies as compared to its base requirements. Various modules of the
software were tested and integrated with all components. This processes were conducted and the
results from various interactions between sub-modules and their interfaces fixed.

The ambition of this documentation is to establish a plan of testing activities that will ensure the
robust of the credit union system

 Items to be tested
 Features to be tested and not to be tested
 Test Case
 Testing Approach
 Pass/Fail criteria, Suspension and Resumption conditions
37
Pass/Fail criteria

The feature will pass or fail depending upon the results of testing actions. If the actual output
from an action is equal to the expected output specified by a test case, then the action passes.
Should any action within a test case fail the entire feature or sub-feature fails?

Pass Criteria

All the testing features of the system is expected to pass the test without any failure

Suspension Condition’s

This test will be suspended if:

 There is a fault with a feature that prevents its testing

 The control is not as specified
 A severe problem has occurred that does not allow testing to continue
 An excessive amount of bugs that should have been caught during unit test phase are
found during more advanced phases of testing

Resumption Condition’s

Test can only resume when:

 Errors or problems encountered that caused the suspension has been solved

5.4.1 UNIT TESTING

The various components of the system were tested to find errors. Errors were found and fixed.
Errors in terms of wrongful data entered such as where numbers, were not allowed to be entered
and character strings are not supposed to be entered are entered and errors found and fixed. I was
able to validate various components such as phone numbers, in their text boxes, and correct dates
entries in their date time pickers.

38
Login Testing

This test case is derived from a set of constraints that username must be unique and password
length must be at least six characters

TEST CASE 1

Test Objective: To verify the login

Test Description: To check whether the passwords and usernames entered by the system users
(Administrator, Cashier, and Auditor) are correct match to identify the user

Requirement verified: YES

Action Expected results

Enter the login name Prompt user to enter username when empty

Enter the password Prompt user to enter password

Pass: YES Fail: No

Problems/Issues: No

Notes: Successfully executed

39
Registration Testing

This test case is derived from a set of input conditions that must be satisfied in order to continue
the registration process of a new member to join the scheme

TEST CASE 2

Test Objective: To verify the registration

Test Description: To check whether the registration details has been entered correctly or not

Registration verified: YES

Actions Expected Results

Enter the name Prompt to enter the name

Enter the Date of Birth Prompt to enter age

Enter the Gender Prompt to enter gender

Enter the Mobile Number Prompt to enter mobile number

Enter the Next Of Kin Prompt to enter the Next of kin

Enter Guardian information Prompt to enter Guardian Information

Pass: YES Fail: No

Problems/Issues: No

Notes: Successfully executed

40
Contribution Testing

This test case is derived from the set of input conditions that must be meet to accept a
contribution amount into a member account.

TEST CASE 3

Test Objective: To test for correct inputs

Test Description: To verify for correct inputs to accept contribution from members

Requirements verified: YES

Actions Expected Results

Make sure that all field are filled All fields are non-empty

Appropriately

Entering contribution Amount Prompt user to enter only numbers into textbox

Payee’s Name Payee’s name must not be empty

Pass: YES Fail:

Problems/Issues: No

Notes: Successfully: executed

41
Loan testing

This test case is derived from constraint that whenever a member is not more six months he/she
cannot access loan facility

TEST CASE 4

Test Objective: To apply for a loan

Test Description: To check whether member is qualified or not

Requirements verified: YES

Actions Expected Results

Input account number Check and prompt user if account number

Does not qualify or qualified

Member with pending loan Denied access for loan facility

Pass: YES Fail:

Problems/issues: No

Notes: Successfully executed

42
Validation and Verification

Validation and Verification comprises the confirmation that the application uses accurate and
useful data to meet the users’ requirements. This is initiated to ensure that the application

 Meets the requirement of the user.

 Performs its functions as expected.
 Can be implemented with the same characteristics.
 Can satisfy the needs of its stakeholders.

Validating Phone Number Field

43
 CHAPTER SIX

6 CONCLUSION

6.1 Summary
Credit unions are community based co-operative institutions which provide financial services to
their members who own and democratically manage them. These are an important means
through which local savings are mobilized, credit is provided and transformed into productive
and development activities. These products and services are mainly savings, business advice and
loans

However, trends in these contributions indicate their great potential in enhancing overall deposit
mobilization and credit availability. Credit union also provide an alternative avenue for savings
and access to credit for small savers and borrowers for whom the procedure and requirements of
the traditional banks are too burdensome. In terms of methodological orientation, in this study
several methods of data collection and analysis were employed. Local publications and archival
documents have been studied, and interviews and discussions held with some officials in the
credit union movement.

After obtaining insightful information about credit unions, the case study focused on a local
credit union in Kumasi in the Ashanti Region of Ghana specifically the credit union located at
Ayeduase called Goodnews Co-operative Credit Union, with a combination of various research
methods and techniques, I was able to accomplish my task with maximum percentage.

In conclusion, I believe this system will solve a lot of problems encountered in the existing
system.

6.2 Limitations and Challenges

Several challenges were encountered during the research process. These problems include:

 Access of information: Since the institution happens to be a financial institution,

information on members were difficult to disclose.
 Non co-operation: Members were afraid to lose their job by giving out information
about the top management operations

44
6.3 Recommendation and Future work
I hereby recommend that in the near future the system can be extended to incorporate other
advanced features like the ability to allow members to do transactions online

45
 REFERENCES
1977, k., 1977. Microfinance as a tool for economic growth. [Online]
Available at: https://thebftonline.com/archive/more.php?ID=3368

Clements, P. C., 1996. A survey of architectural description. [Online]

Available at: Stackoverflow.com

CUA, 1978. CUA. [Online]

Available at: www.cuaghcom

CUA, 1998. The Co-Operative Credit Union. [Online]

Available at: https://en.wikipedia.org/wiki/The_Co-operative_Credit_Union

Fidelis, k., 2009. African confederation of Co-operative Savings & Credit Association. [Online]
Available at:
http://accosca.org/index.php?option=com_content&view=article&id=88&Itemid=211

Goricke, K., 2007. The Co-operative Credit Union Association. [Online]

Available at:
https://openaccess.leidenuniv.nl/bitstream/handle/1887/12295/Thesis.pdf;sequence=1

ILO, 2013. Financial co-operatives: A safe bet in a crisis. [Online]

Available at: http://www.ilo.org/global/about-the-ilo/newsroom/news/WCMS_210300/lang--
en/index.htm
[Accessed April 13].

ISO 9000, 2018. Quality Assurance. [Online]

Available at: https://www.techopedia.com/definition/9038/quality-assurance-qa
[Accessed Thursday April 2018].

Lance, A., 2018. Oracle Database Concepts. [Online]

Available at: https://www.tutorialspoint.com

Nielsen, J., 1994. 10 heuristic Principles-Jakob Nielsen's. [Online]

Available at: http://www.uxness.in/2015/02/10-heuristic-principles-jakob-nielsens.html

Ojemark, 1980. Human Development through Credit Union. [Online]

Available at:
https://books.google.com.gh/books/about/Human_Development_Through_Credit_Unions.html?i
d=nhEjAQAAMAAJ&redir_esc=y

46
 APPENDIX A
GLOSSARY

Auditor: A person who is responsible for evaluating the validity and reliability of a company or
organization’s financial statements

SMS: SMS also known as Short Message Service uses standardized communication protocols to
enable mobile devices to exchange short text messages

Use Case: A diagram that summarize the details of the system users and their interactions with
the system

UML: The Unified Modeling Language(UML) is a general purpose modeling language that is
intended to provide a standard way to visualize the design of a system

PHP: Hypertext Preprocessor(PHP) is an open source general purpose scripting language that is
used for web development

MySQL: Is an open source relational database management system used on the web

Case Study: A process or record of a research into the development of a particular person, group
or situation over a period of time

Methodology: Is a systematic analysis of the methods applied to a field of study

Testing: Is an investigation conducted to provide stakeholders with information about the quality
of a software product

GUI: The graphical user interface(GUI) is a type of user interface that allows users to interact
with electronic devices through graphical icons and visual indicators

N-Tier: Multitier architecture is a client-server architecture in which presentation, application

processing, and data management functions are physically separated

Debit: The act of taking money from an account

Credit: The act of adding money to an account

Staff: A user of the system

47
 APPENDIX B
USER MANUAL

Introduction

The first most important step in Software Installation is to verify that the target meets the general
hardware requirements of this application.

Features include:

 Database that contains all entries made into the database

 Server to host the database

The General System Specification

The minimum system specification needed to ensure a smooth running of the application is:

 A system with a minimum of 10 gigabyte hard drive

 A Processor Speed of 1.0GHz or higher
 1GB memory
 Windows XP Operating System or Higher
 XAMPP or WAMPP Server
 A computer with its Peripherals or a Laptop

48
TECHNICAL MANUAL

Installation Instructions

Step 1: Installing XAMPP Server

Start the installation and click on next buttons till Select Component section appears

49
Step 2

The select components section just shows components which you wish to install on your
computer. But, here we will go with the select all components for further development purpose

Now continue installation by clicking the “Next”

Step 3

By default, XAMPP installs on your computer’s system drive (c:\xampp). You can also install it
at any location on your PC.

50
Step 4

Complete Installation

Wait till installation process is completed, Once the installation is completed, just click on
“Next” button, and it will move you to the final section of an installation process

Step 5

While installing XAMPP, if your computer pops up a firewall security notice like the following,
Uncheck the ‘Public Network’ and Check the ‘Private Network’ and click ‘Allow access’.

51
Step 6

Open XAMPP Control Panel

Find XAMPP Control panel from installation directory and click ‘xampp control’

Step 7

Start the Apache and MySQL

52
Start the Apache and MySQL by clicking a start button. It will shine with a green color when
started

Step 8

Start your Browser

Open your browser (Chrome, Firefox etc.) and just write ‘localhost’ in the address bar and hit
enter

It will take you to XAMPP language selection. After choosing a language, you will move to final
XAMPP dashboard

53
Click on phpMyAdmin at the top right corner of the page

Step 9

Create a new database as shown in the diagram above and name the database as “union”.

Step 10

54
Click on the import tab of the newly created database as shown in the diagram above:

Click on the button “browse” to open the dialog box. Please select the database file “union.sql”
on the CD.

Make sure to select the option” SQL” and then click “Go” as shown in the figure above.

A message will appear that the database was successfully imported. From here, the website is on.

NB: To launch the web site that is now properly created; type http://localhost/union on your web
browser’s address bar

55
 APPENDIX C
Sample Code

The code below lists the number of member of members in the firm(View Members)

<div class="right_col" role="main">

<!-- top tiles -->

<div class="col-md-12 col-sm-12 col-xs-12">

<div class="panel panel-primary">

<div class="panel-heading">

<center>

<h2 CLASS="panel-title"> LIST OF MEMBERS</h2>

</center>

</div>

<div class="panel-body">

<div class="table-responsive">

<table id ="table" class="table table-striped table-hover table-bordered">

<thead>

<tr class="info">

<th>ACCOUNT NO</th>

<th>ACCOUNT TYPE</th>

<th>NAME</th>

<th>CONTACT</th>

<th>GENDER</th>

<th>BALANCE GH¢</th>

<th>PROFILE</th>
56
 </tr>

</thead>

<tbody>

<?php

$sql="select * from vcustomer";

$stmt=$db->prepare($sql);

$stmt->execute();

foreach($stmt as $row){

?>

<tr>

<td><?php echo $row['accnumber']; ?></td>

<td><?php echo $row['AccountType']; ?></td>

<td><?php echo $row['firstname']." ".$row['lastname']; ?></td>

<td><?php echo $row['phone']; ?></td>

<td><?php echo $row['gender']; ?></td>

<td class="danger"><?php echo $row['balance']; ?></td>

<td><div class="text text-danger"> <a class="btn btn-primary btn-sm"

href="cashierviewuser.php?view=<?php echo $row['accnumber']?>">view</a></div></td>

</tr>

<?php } ?>

</tbody>

</table>

</div>

</div>

</div>
57
58