DESIGN AND IMPLEMENTATION OF ONLINE MARRIAGE

REGISTRATION SYSTEM

By

AHMAD USMAN YERIMA

NAS/CSC/18/1456

DEPARTMENT OF MATHEMATICS, FACULTY OF NATURAL AND APPLIED

SCIENCE
AL-QALAM UNIVERSITY, KATSINA.

January, 2023.
 DESIGN AND IMPLEMENTATION OF ONLINE MARRIAGE

REGISTRATION SYSTEM

By

AHMAD USMAN YERIMA

NAS/CSC/18/1376

A PROJECT SUBMITTED TO THE DEPARTMENT OF COMPUTING

AND INFORMATION TECHNOLOGY, COLLEGE OF COMPUTING
AND INFORMATION SCIENCE AL-QALAM UNIVERSITY, KATSINA.

KATSINA STATE

IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE AWARD OF

THE BACHELOR OF SCIENCE (HONOURS) DEGREE IN COMPUTER SCIENCE
JANUARY, 2023

ii
 DECLARATION
I, AHMAD USMAN YERIMA, with registration number “NAS/CSC/18/1456” hereby declare
that this project “DESIGN AND IMPLEMENTATION OF ONLINE MARRIAGE
REGISTRATION SYSTEM” has been carried out by me under the supervision of Yakubu
Ibrahim Galadima, It has not been presented for award of any degree in any institution. The
information derived from the literature has been duly acknowledged and a list of references
provided.

______________________ __________________

Signature Date

i
 CERTIFICATION
This is to certify that this project was undertaken by AHMAD USMAN YERIMA, with
registration number NAS/CSC/18/1456 duly supervised and approved as having met the
requirement for the award of Bachelor of science (B.Sc Hons) degree in the department of
COMPUTER SCIENCE, Al-Qalam University, Katsina State.

Yakubu Ibrahim Galadima …………………………….

Project Supervisor (Sign & Date)

Mal. Abubakar Sadik …………………………….

Project Coordinator (Sign & Date)

Dr. Mansur Abubakar …………………………….

Head of department (Sign & Date)

……………………………. …………………………….
EXTERNAL EXAMINER (Sign & Date)

ii
 ACKNOWLEDGEMENTS
In the name of Allah, the most Gracious the most Merciful, Praise be to Allah, the Cherisher,
Sustainer, provider, protector of one and All, complete blessings and salutations be upon our
beloved Prophet Muhammad (S.A.W), his family, companions and all those who follows Him,
those who are following him and shall follow him up to the day of reckoning.
Special dedication to my parents Alhaji Usman Yerima and Hajiya Zubaida Baba Muhammad
for their relentless support and compassion towards me, Rabbir-Hmhuma Kama Rabb Yani
Saghira and to my family Haj. Rahila Baba Muhammad, Dr. Nasma Usman Yerma, Haj. Mastura
Baba Muhammad, Haj. Hadiza Baba Muhammad, Haj. Jawahir Baba Muhammad, Amina
Usman Yerima, Umma-Diya, Umma-Inna, Sadiq Usman Yerima Prof. Muktar Yerima. Late
Mansur Baba. Abubakar Yerima, Alh. Usman Yerima (Ayari), Yaya Adamu, Mal. Imran Ahmad
Abubakar (Dan goriban Daura) and Hon, Mal. Ahmed Yerima (Sarkin Malaman misau) whom
stand faithful with me and always encourage me toward every single thing that I will ever face. I
will say am blessed having you as my family and to my friends that turned to my brothers are
Ajimi, Papaske, Jujis, Bamanga, Bangis, Abdulrashid, Babbah, Big, Buba, NDA, KK, Mada,
Majikira, Maigoro, Giade, Dan wasa, Mandela, Yusbel, Adalala, Puna, KKG, Mai kwai, Freak,
Muhsin, Jabir, Al-ameen, Ansufati, Ibrahim, Suleiman, Isha,Mrak, Sega, Saluhu, Copper,
Angas,Officer JTF,Officer Dan- Jumma, Ogochuku Okoye and Al-Dusar family I love you all.
Also expressing my sincere appreciation to My Supervisor, Yakubu Ibrahim Galadima who had
been a father, mentor and a teacher to me. Enormous thanks goes to my faculty base supervisor
and all academic and non-academic staff of the Department Of Computing And Information
Technology, College Of Computing And Information Science Al-Qalam University, Katsina.

iii
Contents
DECLARATION..............................................................................................................................i

CERTIFICATION...........................................................................................................................ii

ACKNOWLEDGEMENTS...........................................................................................................iii

ABSTRACT.................................................................................................................................viii

CHAPTER ONE..............................................................................................................................9

INTRODUCTION...........................................................................................................................9

1.0 INTRODUCTION.................................................................................................................9

1.1 BACKGROUND OF THE STUDY......................................................................................9

1.2 STATEMENT OF THE PROBLEM...................................................................................10

1.3 AIM AND OBJECTIVES OF THE STUDY......................................................................11

1.4 SIGNIFICANCE OF THE STUDY....................................................................................11

1.5 SCOPE OF THE STUDY....................................................................................................11

1.6 CHAPTER SUMMARY.....................................................................................................11

CHAPTER TWO...........................................................................................................................12

LITERATURE REVIEW..............................................................................................................12

2.0 INTRODUCTION...............................................................................................................12

2.1 REVIEWED RELATED WORK........................................................................................12

2.2 CONCEPTUAL FRAMEWORK........................................................................................14

iv
 RECORD MANAGEMENT SYSTEM....................................................................................14

Types of Record Management...................................................................................................14

Manual Record Management.....................................................................................................14

Problems Associated with Manual Records Management System............................................15

DEFINITIONS..........................................................................................................................15

DRAWBACK OF EXISTING WORKS...................................................................................15

2.3 CHAPTER SUMMARY.....................................................................................................15

CHAPTER THREE.......................................................................................................................16

SYSTEM ANALYSIS AND DESIGN.........................................................................................16

3.0 INTRODUCTION...............................................................................................................16

3.1 SOFTWARE DEVELOPMENT MODEL..........................................................................16

Figure 3.1 Waterfall Model.......................................................................................................16

METHOD OF DATA COLLECTION......................................................................................17

3.2 REQUIREMENT ENGINEERING.....................................................................................18

Functional requirement..............................................................................................................18

3.3 SYSTEM DESIGN..............................................................................................................19

UML Use-case Diagrams..........................................................................................................19

Figure. 3.2: Use-Case diagram for System................................................................................20

Flowchart of Proposed System..................................................................................................20

v
 Figure. 3.3: Flowchart of the Proposed System.........................................................................21

3.4 CHAPTER SUMMARY.....................................................................................................21

CHAPTER FOUR.........................................................................................................................22

SYSTEM IMPLEMENTATION...................................................................................................22

4.0 INTRODUCTION...............................................................................................................22

4.1 SYSTEM IMPLEMENTATION.........................................................................................22

4.1.1 Description of the application modules/screen.................................................................22

Figure. 4.1: Login Page.............................................................................................................23

Figure. 4.2 Admin Home...........................................................................................................23

Figure. 4.3 Verified Application................................................................................................24

Figure. 4.4 Rejected Application...............................................................................................25

Figure. 4.5 View Report............................................................................................................25

Figure. 4.6 User Dashboard.......................................................................................................26

4.2 SYSTEM TESTING............................................................................................................26

Table 4.1: represent the procedure that the system tested different pages................................27

4.3 SYSTEM REQUIREMENT................................................................................................27

4.4 SYSTEM EVALUATION...................................................................................................28

4.5 CHAPTER SUMMARY.....................................................................................................28

CHAPTER FIVE...........................................................................................................................29

vi
SUMMARY, CONCLUSION AND RECOMMENDATIONS....................................................29

5.1 INTRODUCTION...............................................................................................................29

5.2 SUMMARY.........................................................................................................................29

5.3 CONCLUSION....................................................................................................................29

5.4 RECOMMENDATION.......................................................................................................29

REFERENCE................................................................................................................................31

APPENDICES...............................................................................................................................32

APPENDIX A................................................................................................................................32

SCREEN SHOT.............................................................................................................................32

Figure. 5.1: Login Page.............................................................................................................32

Figure. 5.2 Admin Home...........................................................................................................33

Figure. 5.3 Verified Application................................................................................................34

Figure. 5.4 Rejected Application...............................................................................................35

Figure. 5.5 View Report............................................................................................................35

Figure. 5.6 User Dashboard.......................................................................................................36

APPENDIX B................................................................................................................................37

SOURCE CODE............................................................................................................................37

vii
 ABSTRACT

Marriage Registration System is an online service or agency that helps citizen to register with
the government. Through their services cut across almost every disciple but in this project work,
marriage registration is considered. The current process of civil registry is being operated
manually and due to this procedure, numerous problems are been encountered. A design was
taken to computerized the manual process in order to check this problem. The implementation of
this project work is designed using CS4 Dreamweaver (Adobe Collection Suit), PHP (Hypertext
Processor) scripting language and JavaScript and MYSQL (Structural Query Language)
database in other to have a robust design.

viii
 CHAPTER ONE
INTRODUCTION
1.0 INTRODUCTION
In this chapter is the introduction of the proposed study. It covers the study details such as
background of the study, problem of the statement, aim and objectives, significance of the study,
scope and limitation of the study, and the expected outcome of the study.
1.1 BACKGROUND OF THE STUDY
E-Marriage Registration that provides successful help to manage the Register Registration
process and also manage remove Register. This is the ongoing project for Marriage Registration.
This project fully removes early child marriage and also remove deceitful people who are got
married many. As it is a new idea it needs a very powerful and comprehensible presentation that
will have the right influence on the user. The Recognition of Customary Marriages Act 120 of
1998 provides legal recognition to traditional African marriages and sets up a process whereby
these marriages are formally registered with the Department of Home Affairs. With reference to
testimonies from Msinga, a rural district of KwaZulu-Natal, this article examines how the current
registration process is out of touch with reality and difficult to comply with, especially in respect
of polygamous marriages. Customary marriages therefore often remain unregistered. While
customary marriages are legally valid despite not being registered, in practice registration has
become the threshold for recognising the existence of these marriages when marital status is in
question. As a result, non-registration is effectively non-recognition and deprives women and
children of the significant benefits and protections associated with marriage. More broadly, the
article will argue that the registration process actually undermines several of the Act's objectives
- leaving women living in rural, customary law contexts in a vulnerable position, Souza (2013).
Marriage registration as a window into state building and state-family relations in Maoist China.
It focuses on the interaction between officials and citizens as they tried to make sense of the new
state's unprecedented demand that people register their marriages prior to their consummation.
Marriage registration was expected to make Chinese society more “legible” to the state, as well
as contribute to a “healthier” nation. While much of the literature of Maoist China would
anticipate state success, archival evidence points to widespread evasion and resistance, as well as
accommodation, to the state's effort to reshape family relations, Diamant (2021).

9
Vital registration (also known as civil registration) is the continuous collection, recording,
collation, analysis, presentation and distribution of data on the occurrences and characteristics of
vital events, such as live birth, death, fetal death, marriage, divorce, adoption, legitimization of
birth, recognition of parenthood, annulment of marriage, or legal separation. Records from these
events are called vital statistics (Brolan and Gouda, 2017; Mikkelsen et al., 2015). Vital statistics
are necessary for countries to compile accurate, complete and timely vital statistics about birth,
death and marriage, which, along with population census, are central to estimating population
size and demographic dynamics. The cause of death data from civil registration systems, for
instance, is vital for pinpointing diseases and injuries that have become common in a population
(UNICEF, 2018). Given the huge importance of vital statistics to the public and the policy-
makers, it is worrisome that this issue has received so little attention in literature focusing on
post-colonial states such as Nigeria, especially in terms of the contextual factors that challenge
this crucial practice. In part, this is because vital statistics are taken for granted in the global
centers of research where all births, deaths and marriages are routinely registered. In these
countries, vital statistics are readily available for governments to monitor and to use for social
and economic planning in key sectors such as health, education, employment and housing
(Williams, 2014). However, governments in low and middle-income countries like Nigeria have
the same need for data for planning development and for ensuring the effective use of limited
resources.  
As a result, there is now a momentum-building within these countries and within the global
development community towards the strengthening of civil registration and vital statistics
(CRVS) systems (Makinde et al., 2016).
1.2 STATEMENT OF THE PROBLEM
Marriages are generally still carried out only in traditional ways without official registration.
This method is completely inconsistent with concerning Marriage in Nigeria. To identify and
evaluate these problem factors, cause of the traditional marriage which were not recorded in the
government in the form of economic factors, education, and pregnancy outside of marriage.
traditional marriages that are not officially registered according to Law Number 1 of 1974
concerning the status and position of the wife and husband as well as the status and position of
the child are considered invalid and never exist. The indigenous people must marry according to
the applicable rules so as not to cause problems in the future.

10
1.3 AIM AND OBJECTIVES OF THE STUDY
The aim of this study is to design and implement a marriage registration system that provides an
opportunity for marriage register and common people without any problem.
The objectives of this study are:
i. To design a web application that allow user to register marriage certificate online.
ii. To develop a system that will helps admin to control the functionality of the system.
iii. To implement and test the new system.
1.4 SIGNIFICANCE OF THE STUDY
The basic functionality of this system is making the process user friendly for Register. It helps
admin to control the Register Registration system. Admin can update, delete and also add the
register.
1.5 SCOPE OF THE STUDY
Designing and implementing a marriage registration is a broad study, however, all the areas
cannot be covered at once, and this work is therefore limited in the automation of the process of
checking the programming process and availability of services about the system.
1.6 CHAPTER SUMMARY
Chapter one is the introduction of the proposed project. It covers the project details such as
problem statement, scope and limitation of the study, aim and objectives, significance of the
study. The problem statement describes the issue faced by the user in the current system and the
development of the project. While the objectives explain the study target which is expected to be
accomplish by the of the development phases. Lastly, the study scope will list out the limitation
of the project to be developed.

11
 CHAPTER TWO
LITERATURE REVIEW
2.0 INTRODUCTION
A literature review is account of what has been published on a topic by accredited scholars and
researchers. The purpose is to convey to the reader what knowledge and ideas have been
established for a particular topic and what their strengths and weaknesses.
2.1 REVIEWED RELATED WORK
Scholars generally agreed that birth management system is the efficient way of Marriage
Registration. For this reason, researchers have shown interest designing marriage registration
system.
According to Wirastri (2012), Analysis of past and present legislation concerning marriage
registration for Muslims in Indonesia - shortcomings in law are failure of responsible institutions
to implement regulations - use of case law to illustrate complexities surrounding unregistered
marriage practices.
According to Deborah et al (2008), analyzes data from states that have extended legal
recognition to same-sex couples. Analyses show that same-sex couples want and use these new
legal statuses. Furthermore, they react more enthusiastically when marriage is possible. More
than 40% of same-sex couples have formed legal unions in states where such recognition is
available. Same-sex couples prefer marriage over civil unions or domestic partnerships. In the
first year that marriage was offered in Massachusetts, 37% of same-sex couples there married. In
states that offered civil unions, only 12% of same-sex couples took advantage of this status in the
first year and only 10% did so in states with domestic partnership registries.
According to Souza (2013), The Recognition of Customary Marriages Act 120 of 1998 provides
legal recognition to traditional African marriages and sets up a process whereby these marriages
are formally registered with the Department of Home Affairs. With reference to testimonies from
Msinga, a rural district of KwaZulu-Natal, this article examines how the current registration
process is out of touch with reality and difficult to comply with, especially in respect of
polygamous marriages. Customary marriages therefore often remain unregistered. While
customary marriages are legally valid despite not being registered, in practice registration has
become the threshold for recognising the existence of these marriages when marital status is in
question. As a result, non-registration is effectively non-recognition and deprives women and

12
children of the significant benefits and protections associated with marriage. More broadly, the
article will argue that the registration process actually undermines several of the Act's objectives
- leaving women living in rural, customary law contexts in a vulnerable position.

According to Sadjilli (2020), SIMKAH is a government policy that began to be implemented

simultaneously in KUA throughout Indonesia in 2018, in order to assist and facilitate the
performance of KUA employees in presenting data. Another purpose of SIMKAH is as an
Information Technology-based marriage registration system. As we know, before the
implementation of the SIMKAH application program, marriage registration at KUA was still
done manually. As for the formulation of the problem that the researcher examines, namely how
the application of the Marriage Management Information System or SIMKAH in the
administration of marriage registration services at the KUA where the researcher conducts
research, as well as the effectiveness or not of the Marriage Management Information System or
SIMKAH at the KUA where the researcher conducts research. The purpose of this researcher is
to determine the application and effectiveness of the Marriage Management Information System
or SIMKAH at the KUA in the registration of marriage services at the KUA where the researcher
is conducting research. The method used in this research is descriptive method with an empirical
juridical problem approach. Empirical juridical research is legal research regarding the
application of normative law in action on any particular legal event that occurs in society. Data
collection techniques were carried out using literature study and interviews with the Head of
KUA and KUA staff where researchers conducted research.

According to Fujian (2019) Marriage registration system is the institutional prerequisite of the
appearance of non-marital cohabitation, which would not impact the current marriage system.
The legislative regulation of cohabitation and the marriage registration system can complement
each other. Legal recognition of non-marriage cohabitation, although to some extent weakens the
value orientation of the marriage law, will not change the dominant status of marriage and the
realization of family law goals. Incapable relieving of marriage crisis could not attribute to the
legal recognition and protection of non-marital cohabitation; instead, we should face up to and
reflect on the problems confronting the marriage system itself. Legislation of non-marital
cohabitation does not exclude the marriage system and therefore people can choose their own
gender combination modes according to their needs. Marriage is still the indispensable

13
organization for the human self-reproduction and healthy development of children, which should
be given priority of protection and different treatment to non-marital cohabitation. In this way,
the dominant position of marriage and family pattern can be consolidated.

2.2 CONCEPTUAL FRAMEWORK

RECORD MANAGEMENT SYSTEM
According to Records Management Vendor, 2019, Records Management system is a computer
program (or set of programs) used to track and store records, they commonly provide specialized
security and auditing functionalities tailored to the need of users. In this case, the URGMIS will
be used to take and store records such as birth and death certificates.

International Standard Organization (ISO), (2001) defines record management as “The field of
management responsible for the efficient and systematic control of the creation, recipient,
maintenance, use and disposition of records including the processes for capturing and
maintaining audience of information about business activities and transaction in form of a
record.”

Conolly, (2020) defines a record as digital information with value to an organization like
database. Databases are now such an integral part of our clay-to-day work that we are not aware
we are using one. Charles (2020) noted that, a records management system is an agency- wide
system that considers the reasons, the processes, and the means necessary for a document to exist
and be used in Record Management System (RIVIS) must cover the entire life span of the
document, from its generation to its destruction. It provides for the effective storage, retrieval,
manipulation, achieving and viewing of information, records, documents, or files that are related
to a single subject. RMS allows one resource of data input and multiple reporting mechanisms
and enables an agency to deal with its records in a simple environment. It should provide the
ability to generate project statistics for management.
Types of Record Management
Manual Record Management
This involves a variety of diverse disciplines. At the simplest, it indexes and organizes paper
documents. In the registrar department, this is usually a matter of filing the deaths and births
documents and making them available for retrieval. BeIl, (2018).

14
Problems Associated with Manual Records Management System.
Records retrieval with manual system is time consuming. A lot of storage space is required for
manual record. Poses security threats to individual records. Difficulty in records management.

DEFINITIONS
A marriage certificate (sometimes: marriage lines) is an official statement that two people are
married. In most jurisdictions, a marriage certificate is issued by a government official only after
the civil registration of the marriage. In some jurisdictions, especially in the United States, a
marriage certificate is the official record that two people have undertaken a marriage ceremony.
This includes jurisdictions where marriage licenses do not exist. In other jurisdictions, a marriage
license serves a dual purpose of granting permission for a marriage to take place and then
endorsing the same document to record the fact that the marriage has been performed. A
marriage certificate may be required for a number of reasons. It may be required as evidence of
change of a party's name, on issues of legitimacy of a child, during divorce proceedings, or as
part of a genealogical history, besides other purposes.
DRAWBACK OF EXISTING WORKS
It makes a clear observation on the existing system of marriage registration is manual process
carried out using paper, pen and the list of registered people. Its features and the problems it
encounters. The online marriage management system was designed in such a way that it will
meet the user requirement. It will also avoid the problem faced by the manual register system.
2.3 CHAPTER SUMMARY
This chapter is considered as literature review of this project which includes; introduction,
Online Marriage Management System, and similar works that are related to this project,
drawback of existing works.

15
 CHAPTER THREE
SYSTEM ANALYSIS AND DESIGN
3.0 INTRODUCTION
This chapter will present the overview of the techniques chosen for this work, the instruments
and tools used for collecting data, the justification of all the choices made, how the data is
analyzed as well as how the conclusion is drawn based on the available data.
3.1 SOFTWARE DEVELOPMENT MODEL
Waterfall Model
However, the researcher in this project work used the Waterfall Model effectively. This model
has five phases:
1. Requirement analysis and specification
2. Design
3. Coding and unit testing
4. Integration and system testing
5. Implementation
The phases always occur in this order and do not overlap. The developer must complete each
phase before the next phase begins. This model is named “Waterfall Model”, because its
diagrammatic representation resembles a cascade of waterfalls. Waterfall model is the simplest
model of software development paradigm. It says the all the phases of SDLC will function one after
another in linear manner. That is, only when the first phase is completed then the second phase will
start and so on.
This model assumes that everything is carried out and taken place perfectly as planned in the
previous stage and there is no need to think about the past issues that may arise in the next phase.

Analysis

Design

Coding &
Testing

Integration &
Figure 3.1 Waterfall Model System Testing

16
This model does not work smoothly if there are some issues left at the previous phase. The
sequential nature of model does not allow us to go back and undo or redo our actions. This model
is best suited when developers have already designed and developed similar software in the past
and are aware of all its domains.
Justification for the Selected Method (Waterfall Model)
The researcher chose Waterfall model because of its certain advantages as can be seen below:
1. The waterfall model is the oldest and the most widely used paradigm for software
engineering.
2. This model provides a systematic and sequential approach to software development.
3. It is very useful where the requirements are well understood.
4. And above all, the user involvement of the method gives more room for both the user and
the developer to have a better understanding of the proposed system.
METHOD OF DATA COLLECTION
Method of data collection presents or contains the pattern of material use to get the information
needed in enhancing successful presentation of the research. Good method of data collection lead
production of the desired result, whereas improper method results in undesired or in accurate
result. The success of any project depends on the accuracy of the available data. Accurate
information can be collected with help of certain methods or techniques. The techniques and
instruments in data collection include: Primary sources and secondary sources.
 Primary Sources
In Primary sources of data, the data is collected by the researcher based on answers, opinion or
actions of the audience or people affected by the research. These include observation, oral
interview, questionnaire, case studies, and scientific experiments.
 Secondary Sources
These include the use of textbooks, dictionaries, journals, newspapers, electronic books and
internet downloads to collect data and aid comprehension of the system design.
In this project work, closed observation was carried out by the researcher.
Justification of the Chosen Methods
 Observation

17
 The observation procedure helps to watch and describe behavior the way it occurs in the
natural setting, also the method helps in recording what actually happened rather than people’s
opinion.
 Secondary Sources
Similarly, data from the secondary sources are to provide data and information for testing
research hypothesis. The major advantage of using data from secondary source is that it allows
the researcher to view different facts about a subject matter so as to choose suitable solution.
3.2 REQUIREMENT ENGINEERING
The process to gather the software requirements from client, analyze and document them is
known as requirement engineering. The goal of requirement engineering is to develop and
maintain sophisticated and descriptive ‘System Requirements Specification’ document.
Requirement Engineering Process It is a four-step process, which includes:
 Feasibility Study
 Requirement Gathering
 Software Requirement Specification
Software Requirement Validation
Functional requirement
Requirement analysis is a software engineering technique that is composed of the various tasks
that determine the needs or conditions that are to be met for a new or altered product, taking into
consideration the possible conflicting requirements of the various users. Functional requirements
are those requirements that are used to illustrate the internal working nature of the system, the
description of the system, and explanation of each subsystem. It consists of what task the system
should perform, the processes involved, which data should the system holds and the interfaces
with the user. The functional requirements identified are:
a. Restrict unauthorized access of data: The system is designed in such a way not to allow
the user to access data files on system.
b. Security techniques: suggest security techniques which can create conducive working
atmosphere for organizations that are having data threatened.
a. Enhance key sharing mechanism: this allows the users to share and have access.

Non- Functional Requirements

18
It describes aspects of the system that are concerned with how the system provides the functional
requirements. They are:

Security: The subsystem should provide a high level of security and integrity of the data held by
the system.

Performance and Response time: The system should have high performance rate when
executing user’s input and should be able to provide feedback or response within a short time
span usually 50 seconds for highly complicated task and 20 to 25seconds for less complicated
task.

Error handling: Error should be considerably minimized and an appropriate error message that
guides the user to recover from an error should be provided. Validation of user’s input is highly
essential. Also, the standard time taken to recover from an error should be 15 to 20 seconds.

Availability: This system should always be available for access at 24 hours, 7 days a week.
Also, in the occurrence of any major system malfunctioning, the system should be available in 1
to 2 working days, so that the business process is not severely affected.

Ease of use: Considered the level of knowledge possessed by the users of this system, a simple
but quality user interface should be developed to make it easy to understand and required less
training.

Reduces stress, time consumption and cost of operation: involved in a manual security
system.
3.3 SYSTEM DESIGN
In requirement analysis, thorough investigation and cross-examination of the requirements for
the proposed system is carried out and at the end, a document is produced that clearly states,
without any ambiguity, what the user actually wants or what the system requires. After
successfully producing a comprehensive document on the actual requirement of any system, the
next phase is to use this document and produce another document called Software Design
Document (SDD) that clearly stipulates, to the programmer, how is the system going to be
implemented. Two major activities in System design are logical design and physical design.

19
UML Use-case Diagrams
Use case diagrams are usually referred to as behavior diagrams used to describe a set of actions
(use cases) that some system or systems (subject) should or can perform in collaboration with
one or more external users of the system (actors).

Figure. 3.2: The Use-Case diagram is the system views describing the detailed roles of the
system as shown below:

Figure. 3.2: Use-Case diagram for System

Flowchart of Proposed System
The flowchart shows the complete view of the whole proposed system design. Figure. 3.3 is the
physical design of proposed system show how the execution of the proposed system carried out.

20
 Figure. 3.3: Flowchart of the Proposed System
3.4 CHAPTER SUMMARY
This chapter provides an overview on methodology, methods of data collection which include
primary and secondary sources, justification of the methods chosen, technical tools used in the
research and the justification of the technical tools. The software and the hardware requirements
of the project were also stated.

21
 CHAPTER FOUR
SYSTEM IMPLEMENTATION

4.0 INTRODUCTION
This chapter provided a thorough description of how the proposed system is designed (given the
requirement) as well as how the design is used in implementing the system into actual software
using a computer programming language.
4.1 SYSTEM IMPLEMENTATION
Front End
The front end is the system architecture for a user. The front end is where the user input their
data and then processing it for the completion of the request made by the user. In this project,
PHP language for scripting, while HTML, BOOTSTRAP and JQuery for user interphase and
CSS was used for the design.
Back End
The Backend is the Server side of the system. In this project, was used PHP for the server
scripting language and MySQL for the database.
4.1.1 Description of the application modules/screen
This application is designed to compose of various pages; each of the pages performs certain
function. The following Figures show the different modules/pages of the system. Each Figure. is
preceded by a brief description of its compositions and functionalities

22
Figure. 4.1: Login Page

Figure. 4.1: Represent the login page which is generally the main page and it may also serve as a
landing page to attract users.
Figure. 4.2 Admin Home

23
Figure. 4.2: Represent the admin page when you first sign into the system admin dashboard,
you’ll see the default screen with widgets such as activity, verified application, rejected
application and all application, and search etc.
Figure. 4.3 Verified Application.

Figure. 4.3: Represent the list of verified marriage applications page.

24
Figure. 4.4 Rejected Application.

Figure. 4.4: Represent the list of rejected marriage application page.

Figure. 4.5 View Report.

Figure. 4.5: Represent the report of all applications.

25
Figure. 4.6 User Dashboard.

Figure. 4.6: Represent the user dashboard page where the user can register his form and also,
view whether his application was verified or rejected.
4.2 SYSTEM TESTING
“Testing is the process of executing a program or system with the intent of finding errors”.
Simply testing involves the processes of verifying and validating the program or application.
This is performed at the start of the system by the test team. It’s called black box testing. The
system is tested in a controlled environment. The purpose of system testing is to validate an
application’s accuracy and completeness in performing the function as designed. The system is
tested through the following testing approaches in table 4.1.

26
 Table 4.1: represent the procedure that the system tested different pages.

TEST FUNCTION DESCRIPTION EXPECTED ACTUAL STATUS

ID RESULT RESULT

1 User try to User try to register to User was register User were register Successful
register the system to the system to the system

2 User try to login User try to login to User was login to User were login Successful
the system the system to the system

3 User try to apply User trying to apply Marriage Marriage Successful

for marriage for marriage certificate was certificate were
certificate certificate applied applied

4 Admin try to Admin try to login to Admin was login Admin were login Successful
login the system to the system to the system

5 Admin try to Admin trying to Marriage Marriage Successful

approved approved marriage certificate was certificate were
marriage certificate from the approved from the approved from
certificate. system system the system

6 Admin try to Admin trying to Marriage Marriage Successful

reject marriage reject marriage certificate was certificate were
certificate. certificate from the rejected from the rejected from the
system system system

4.3 SYSTEM REQUIREMENT

The requirements needed to implement this system are as follows:
Hardware Requirements

27
The software designed needed the following hardware for an effective operation of the newly
designed system.
 Processor: 1,6 GHz CPU
 RAM: 1,75 GB RAM
 HDD: 40 GB of free space
 Microsoft Azure Virtual Machine Configuration: Basic Small VM
Software Requirements
The software requirements include: -
 Windows 8.1
 Xampp Server or hosting site
 Google Chrome or any other Browser.
4.4 SYSTEM EVALUATION
System evaluation is the process of accessing the performance of the complete system to
discover how it is likely to perform in real life compared to the former system. The learning
management system being implemented using PHP, HTML and MySQL is tested on different
browsers. The performance of the application is evaluated and rated with the manual system.
Response from the testing team indicate that the new system satisfies its stipulated user’s
requirement as defined in the problem statement of this research project.
The system was hosting online in other to evaluated the system
URL http://localhost/omrs/index.php
4.5 CHAPTER SUMMARY
In this chapter considered as system implementation of the system. Technical tools used and the
function of the technologies and tools you used the software, system requirement, describe both
software and hardware requirement needed to the software, system evaluation and system testing
report the test case of all the functions in pages in the software.

28
 CHAPTER FIVE
SUMMARY, CONCLUSION AND RECOMMENDATIONS

5.1 INTRODUCTION
This chapter summarized the main overview of the study, all the processes and procedures used
in gathering data, the system design and the implementation. Conclusions about the research
were also drawn. Recommendations for future use of the study were also stated.
5.2 SUMMARY
This project work covered the basic and important processes involved in designing and
developing a responsive marriage registration system that can be smoothly accessed by various
devices. The system is aimed to address and solve the problems associated with the current
(manual) means of registration.
In this chapter, it provides an overview on the whole project idea, problem statement, aims and
objectives that guides the study scope, limitations and finally significant of the project were fully
stated. This chapter is considered as literature review of this project which includes; introduction,
Online registration system, and similar works that are related to this project, drawback of
existing works. This chapter provides an overview on methodology, methods of data collection
which include primary and secondary sources, justification of the methods chosen, technical
tools used in the research and the justification of the technical tools. The software and the
hardware requirements of the project were also stated. Chapter four considered as system design
and implementation of the system. In system design have two major activities are logical design
and E-R diagram while in the system implementation is the ultimate goal of making a system
reality is achieved.
5.3 CONCLUSION
Today, this project is help to grow our Digitalization. Every government related work should
perform through the internet. Today, it is a reality in Nigeria. In the last couple of years, the
growth of many govt. work performed by web base application or E-Govt. site in Nigeria. So, the
E-marriage registration system help the people to growth the Digital Nigeria.
5.4 RECOMMENDATION
Our system can be developed further to include, Short Messaging Service (SMS) where by
members cellphone numbers has to be stored into the system database. Through small developed
stub the system can send notice to students and staff members directly to their phone number.

29
GSM based, the system can be advanced to a system with digital registration where the
registration can be typed or edited on the PC and then sent to every display connected to the
system.

30
 REFERENCE
Tolstoy Newtonraja and AdityaNafde . (2011). Online Course Registration System Project
Report. Florida: Computer and Information Science &Engineering at the University of
Florida.
Al-Shaikh, A. M. (2010). Online course registration. International Journal of Computer Science
and Security (IJCSS), Volume (4), Issue: (3), 15-35.
GeorgiosVarsamopoulos and Sandeep Kumar S. Gupta. (July 2005). Optimal Offline and Online
Registration. Arizona State: IEEE TRANSACTIONS ON MOBILE COMPUTING,
VOL. 4, NO. 5.
Gomez-Perez, A., Fernandez, M. and De Vicente, A.J. (1996) Towards a Method to
Conceptualize J.M.NC. Gunawardana, G.P. Ishara, R.G. Ragel* and S. Radhakrishnan.
(December 2008). Peradeniya University Research Sessions, Sri Lanka, Vol.13, Part II,
Sri Lanka.: Peradeniya University Research Sessions.
Noor Mohiuddin, NabiilahRajabalee and RaeesHameed. (2010). Web-based Course Registration
System using Component-Based Development. Florida: university of Florida. 7
Indiana University, Information Technology Services, Knowledgebase, What is a web portal?
Citedon 18th May 2009, http://kb.iu.edu/data/ajbd.html.
WIKIPEDIA, The Free Encyclopedia, Multitier Architecture, cited on 29th April 2009, 9.
http://en.wikipedia.org/wiki/multitier_architecture.
SOMMERVILLE I., Software Engineering, 7th Edition, 2004, ISBN: 0-321-21026-3, Pearson
Education Limited pp. 68. 11. http://www.wampserver.com/en/ - WAMP information

31
 APPENDICES
APPENDIX A
SCREEN SHOT
Figure. 5.1: Login Page

Figure. 5.1: Represent the login page which is generally the main page and it may also serve as a
landing page to attract users.

32
Figure. 5.2 Admin Home

Figure. 5.2: Represent the admin page when you first sign into the system admin dashboard,
you’ll see the default screen with widgets such as activity, verified application, rejected
application and all application, and search etc.

33
Figure. 5.3 Verified Application.

Figure. 5.3: Represent the list of verified marriage applications page.

34
Figure. 5.4 Rejected Application.

Figure. 5.4: Represent the list of rejected marriage application page.

Figure. 5.5 View Report.

Figure. 5.5: Represent the report of all applications.

35
Figure. 5.6 User Dashboard.

Figure. 5.6: Represent the user dashboard page where the user can register his form and also,
view whether his application was verified or rejected.

36
 APPENDIX B
SOURCE CODE
<?php
session_start();
error_reporting(0);
include('includes/dbconnection.php');
if (strlen($_SESSION['omrsuid']==0)) {
header('location:logout.php');
} else{
?>
<!DOCTYPE html>
<html lang="en">
<head>
<title>Online Marriage Registration System: Dashboard</title>
<!-- vendor css -->
<link href="lib/font-awesome/css/font-awesome.css" rel="stylesheet">
<link href="lib/Ionicons/css/ionicons.css" rel="stylesheet">
<link href="lib/perfect-scrollbar/css/perfect-scrollbar.css" rel="stylesheet">
<link href="lib/jquery-toggles/toggles-full.css" rel="stylesheet">
<link href="lib/rickshaw/rickshaw.min.css" rel="stylesheet">
<!-- Amanda CSS -->
<link rel="stylesheet" href="css/amanda.css">
</head>
<body>
<?php include_once('includes/header.php');?>
<?php include_once('includes/sidebar.php');?>
<div class="am-mainpanel">
<div class="am-pagetitle">
<h5 class="am-title">Dashboard</h5>
<form id="searchBar" class="search-bar" action="index.html">
<div class="form-control-wrapper">

37
 <input type="search" class="form-control bd-0" placeholder="Search...">
</div><!-- form-control-wrapper -->
<button id="searchBtn" class="btn btn-orange"><i class="fa fa-search"></i></button>
</form><!-- search-bar -->
</div><!-- am-pagetitle -->
<div class="am-pagebody">
<div class="row row-sm">
<div class="col-lg-12">
<div class="card">
<div id="rs1" class="wd-100p ht-200"></div>
<div class="overlay-body pd-x-20 pd-t-20">
<div class="d-flex justify-content-between">
<div>
<?php
$uid=$_SESSION['omrsuid'];
$sql="SELECT FirstName,LastName from tbluser where ID=:uid";
$query = $dbh -> prepare($sql);
$query->bindParam(':uid',$uid,PDO::PARAM_STR);
$query->execute();
$results=$query->fetchAll(PDO::FETCH_OBJ);
$cnt=1;
if($query->rowCount() > 0)
{
foreach($results as $row)
{ ?>
<h4>Welcome to Our System || <?php echo $row->FirstName;?> <?php echo
$row->LastName;?></h4><?php $cnt=$cnt+1;}} ?>
</div>
</div><!-- d-flex -->
</div>
</div><!-- card -->

38
 </div><!-- col-4 -->
</div><!-- row -->
</div><!-- am-pagebody -->
<?php include_once('includes/footer.php');?>
</div><!-- am-mainpanel -->
<script src="lib/jquery/jquery.js"></script>
<script src="lib/popper.js/popper.js"></script>
<script src="lib/bootstrap/bootstrap.js"></script>
<script src="lib/perfect-scrollbar/js/perfect-scrollbar.jquery.js"></script>
<script src="lib/jquery-toggles/toggles.min.js"></script>
<script src="lib/d3/d3.js"></script>
<script src="lib/rickshaw/rickshaw.min.js"></script>
<script src="http://maps.google.com/maps/api/js?
key=AIzaSyAEt_DBLTknLexNbTVwbXyq2HSf2UbRBU8"></script>
<script src="lib/gmaps/gmaps.js"></script>
<script src="lib/Flot/jquery.flot.js"></script>
<script src="lib/Flot/jquery.flot.pie.js"></script>
<script src="lib/Flot/jquery.flot.resize.js"></script>
<script src="lib/flot-spline/jquery.flot.spline.js"></script>
<script src="js/amanda.js"></script>
<script src="js/ResizeSensor.js"></script>
<script src="js/dashboard.js"></script>
</body>
</html>
<?php } ?>
<?php
session_start();
error_reporting(0);
include('includes/dbconnection.php');
if (strlen($_SESSION['omrsaid']==0)) {
header('location:logout.php');

39
 } else{
?>
<!DOCTYPE html>
<html lang="en">
<head>
<title>Online Marriage Registration System</title>
<!-- vendor css -->
<link href="lib/font-awesome/css/font-awesome.css" rel="stylesheet">
<link href="lib/Ionicons/css/ionicons.css" rel="stylesheet">
<link href="lib/perfect-scrollbar/css/perfect-scrollbar.css" rel="stylesheet">
<link href="lib/jquery-toggles/toggles-full.css" rel="stylesheet">
<link href="lib/rickshaw/rickshaw.min.css" rel="stylesheet">
<!-- Amanda CSS -->
<link rel="stylesheet" href="css/amanda.css">
</head>
<body>
<?php include_once('includes/header.php');?>
<?php include_once('includes/sidebar.php');?>
<div class="am-mainpanel">
<div class="am-pagetitle">
<h5 class="am-title">Dashboard</h5>
</div><!-- am-pagetitle -->
<div class="am-pagebody">
<div class="row row-sm">
<div class="col-lg-4">
<?php
$sql ="SELECT ID from tblregistration where Status is null ";
$query = $dbh -> prepare($sql);
$query->execute();
$results=$query->fetchAll(PDO::FETCH_OBJ);
$totalnewapp=$query->rowCount();

40
?>
<div class="card">
<div id="rs1" class="wd-100p ht-200"></div>
<div class="overlay-body pd-x-20 pd-t-20">
<div class="d-flex justify-content-between">
<div>
<h6 class="tx-12 tx-uppercase tx-inverse tx-bold mg-b-5">Total</h6>
<p class="tx-12">New Application</p>
</div>
<a href="new-marriage-application.php" class="tx-gray-600 hover-info"><i
class="icon ion-more tx-16 lh-0"></i></a>
</div><!-- d-flex -->
<h2 class="mg-b-5 tx-inverse tx-lato"><?php echo
htmlentities($totalnewapp);?></h2>
</div>
</div><!-- card -->
</div><!-- col-4 -->
<div class="col-lg-4 mg-t-15 mg-sm-t-20 mg-lg-t-0">
<?php
$sql ="SELECT ID from tblregistration where Status='Verified' ";
$query = $dbh -> prepare($sql);
$query->execute();
$results=$query->fetchAll(PDO::FETCH_OBJ);
$totalverapp=$query->rowCount();
?>
<div class="card">
<div id="rs2" class="wd-100p ht-200"></div>
<div class="overlay-body pd-x-20 pd-t-20">
<div class="d-flex justify-content-between">
<div>
<h6 class="tx-12 tx-uppercase tx-inverse tx-bold mg-b-5">Total</h6>

41
 <p class="tx-12">Verified Application</p>
</div>
<a href="verified-marriage-application.php" class="tx-gray-600 hover-info"><i
class="icon ion-more tx-16 lh-0"></i></a>
</div><!-- d-flex -->
<h2 class="mg-b-5 tx-inverse tx-lato"><?php echo htmlentities($totalverapp);?></h2>
</div>
</div><!-- card -->
</div><!-- col-4 -->
<div class="col-lg-4 mg-t-15 mg-sm-t-20 mg-lg-t-0">
<?php
$sql ="SELECT ID from tblregistration where Status='Rejected' ";
$query = $dbh -> prepare($sql);
$query->execute();
$results=$query->fetchAll(PDO::FETCH_OBJ);
$totalrejapp=$query->rowCount();
?>
<div class="card">
<div id="rs3" class="wd-100p ht-200"></div>
<div class="overlay-body pd-x-20 pd-t-20">
<div class="d-flex justify-content-between">
<div>
<h6 class="tx-12 tx-uppercase tx-inverse tx-bold mg-b-5">Total</h6>
<p class="tx-12">Rejected Application</p>
</div>
<a href="rejected-marriage-application.php" class="tx-gray-600 hover-info"><i
class="icon ion-more tx-16 lh-0"></i></a>
</div><!-- d-flex -->
<h2 class="mg-b-5 tx-inverse tx-lato"><?php echo htmlentities($totalrejapp);?></h2>
</div>
</div><!-- card -->

42
 </div><!-- col-4 -->
</div>
<div class="row row-sm" style="margin-top: 1%">
<div class="col-lg-4 mg-t-15 mg-sm-t-20 mg-lg-t-0">
<?php
$sql ="SELECT ID from tblregistration ";
$query = $dbh -> prepare($sql);
$query->execute();
$results=$query->fetchAll(PDO::FETCH_OBJ);
$totalreg=$query->rowCount();
?>
<div class="card">
<div id="rs3" class="wd-100p ht-200"></div>
<div class="overlay-body pd-x-20 pd-t-20">
<div class="d-flex justify-content-between">
<div>
<h6 class="tx-12 tx-uppercase tx-inverse tx-bold mg-b-5">Total</h6>
<p class="tx-12">Total Application</p>
</div>
<a href="all-marriage-application.php" class="tx-gray-600 hover-info"><i
class="icon ion-more tx-16 lh-0"></i></a>
</div><!-- d-flex -->
<h2 class="mg-b-5 tx-inverse tx-lato"><?php echo htmlentities($totalreg);?></h2>
</div>
</div><!-- card -->
</div><!-- col-4 -->
</div>
</div><!-- am-pagebody -->
<?php include_once('includes/footer.php');?>
</div><!-- am-mainpanel -->
<script src="lib/jquery/jquery.js"></script>

43
 <script src="lib/popper.js/popper.js"></script>
<script src="lib/bootstrap/bootstrap.js"></script>
<script src="lib/perfect-scrollbar/js/perfect-scrollbar.jquery.js"></script>
<script src="lib/jquery-toggles/toggles.min.js"></script>
<script src="lib/d3/d3.js"></script>
<script src="lib/rickshaw/rickshaw.min.js"></script>
<script src="http://maps.google.com/maps/api/js?
key=AIzaSyAEt_DBLTknLexNbTVwbXyq2HSf2UbRBU8"></script>
<script src="lib/gmaps/gmaps.js"></script>
<script src="lib/Flot/jquery.flot.js"></script>
<script src="lib/Flot/jquery.flot.pie.js"></script>
<script src="lib/Flot/jquery.flot.resize.js"></script>
<script src="lib/flot-spline/jquery.flot.spline.js"></script>
<script src="js/amanda.js"></script>
<script src="js/ResizeSensor.js"></script>
<script src="js/dashboard.js"></script>
</body>
</html>
<?php } ?>

44