TITLE PAGE

DESIGN AND IMPLEMENTATION OF AN ONLINE SECONDARY SCHOOL REGISTRATION

SYSTEM: A CASE STUDY OF ZARIA CHILDREN'S SCHOOL

By

FATIMA SANUSI

(U19CS2063)

IN PARTIAL FULFILMENT OF THE REQUIREMENTS FOR THE AWARD OF BACHELOR OF

SCIENCE HONOURS (B.Sc. Hons), DEGREE IN COMPUTER SCIENCE FACULTY OF
PHYSICAL SCIENCES, AHMADU BELLO UNIVERSITY ZARIA

A PROJECT SUBMITTED TO THE DEPARTMENT OF COMPUTER SCIENCE, AHMADU

BELLO UNIVERSITY, ZARIA-NIGERIA IN PARTIAL FULFILMENT OF THE
REQUIREMENTS FOR THE AWARD OF THE DEGREE OF BACHELOR OF SCIENCE (B. Sc.
Hons.) IN COMPUTER SCIENCE

SUPERVISOR

PROF. SAHALU B. JUNAIDU

SEPTEMBERJUNE, 2024
 DECLARATION
I FATIMA SANUSI (U19CS2063) hereby declare that this project titled “Design And
Implementation Of An Online Secondary School Registration System” has been carried
out under the supervision of Prof. Sahalu B. Junaidu. It has not been presented for the award
of any degree in any institution. All sources of knowledge has been specifically acknowledge
by means of reference.

Signature S
 CERTIFICATION
This project entitled “Design And Implementation Of An Online Secondary School
Registration System” by Fatima Sanusi (U19CS2063) meets the requirements governing
the award of the degree of Bachelor of Science Computer Science and is approved for its
contribution to knowledge and literary presentation.

PROF. SAHALU B. JUNAIDU Date

(Project Supervisor)

Date
DR. M ABDULKARIM
(HOD Computer Science)

EXTERNAL SUPERVISOR

Name_________________________________ _____________________

Signature______________________________ Date
 DEDICATION
I dedicate this project to Allah, the Almighty, my strong pillar, my source of motivation,
wisdom, guidance, knowledge and understanding, who gave me the grace and energy all
through this worthy endeavour. I also dedicate this work to my parents, whose worthy
support has pushed me to give my all to the completion of this work. To my lovely siblings
whom have been motivating and giving the best support in moving forward in every way
possible. To my superior supervisor and lecturers and others, thank you. God bless you.
 ACKNOWLEDGMENT
My deepest gratitude and sincere thank goes to Allah who has provided me all that was
needed to carry this project to completion. There was never lack or want. Throughout this
entire study, He took care of everything that would have stopped me in my tracks and
strengthened me even through my most difficult times.

I appreciate my HOD of this great department, Dr. M. Abdulkarim for leading and nurturing
the vision of this great institution, Ahmadu Bello University, Zaria, where I have been trained
to take up my destiny of dominion. I also appreciate my supervisor, Prof. Sahalu B. Junaidu
who has shown exemplary leadership of Leader.

My sincere thanks also go to the entire academic staff both past and present of the
Department of Computer Science.

My utmost regard also goes to my parents who painstakingly laid the foundation for my
education giving it all it takes. I am and will forever be grateful to my friends for growing
educationally with me and motivating me positively. I can’t find the words that express my
gratitude. I also from the depth of my heart appreciate everyone for every positive
contribution. God bless you.
 ABSTRACT
Previous studies have used the LAMP stack (Linux, Apache, MySQL, PHP) for student
registration systems, such as the one at Unity International School Abuja. However, this
research introduces a more modern, scalable approach by adopting the MERN stack
(MongoDB, Express.js, React.js, Node.js). This new system is designed to be user-friendly
and efficient, automating the student registration process by generating unique registration
numbers without duplication and incorporating a performance ranking feature. The system
aims to replace the manual registration process, improving both registration and
performance evaluation.This project brings forth a computing solution to the registration
process of students of Zaria Children’s School Education Trust, Zaria as an alternative to the
archaic procedure that is employed currently. This online operation will be designed to be
user-friendly. The programming languages to be employed for the new interface’s design and
implementation are MangoDB, Express.JS, React and Node.JS

This system will be designed to process student’s registration into the school. The system
employed an algorithm that will serially create the students’ Registration number without a
duplicate in them thereby making the new platform effective in delivering its functions. This
work is expected to eliminate the manual process of registration in the school.
Table of Contents

TITLE PAGE.....................................................................................................................................................1
DECLARATION.................................................................................................................................................2
CERTIFICATION...............................................................................................................................................3
DEDICATION...................................................................................................................................................4
ACKNOWLEDGMENT......................................................................................................................................5
ABSTRACT.......................................................................................................................................................6
3.1 METHODOLOGY.....................................................................................................................................22
3.2 WATERFALL MODEL AND PROTOTYPING................................................................................................22
3.3 REQUIREMENT ENGINEERING.........................................................................................................24
3.3.1 SYSTEM REQUIREMENTS.................................................................................................................24
3.3.2 HARDWARE REQUIREMENTS...........................................................................................................24
FUNCTIONAL REQUIREMENTS.........................................................................................................24
3.3.3.............................................................................................................................................................24
NON FUNCTIONAL REQUIREMENTS.................................................................................................24
3.3.4.............................................................................................................................................................24
3.4 DESIGN TOOL...................................................................................................................................25
3.4.1 USE CASE DIAGRAM.........................................................................................................................26
3.4.2 ACTIVITY DIAGRAM.........................................................................................................................27
3.4.3 DATA FLOW DIAGRAM (DFD)...........................................................................................................28
3.4.4 SYSTEM FLOW CHART......................................................................................................................29
3.5 DATABASE DESIGN..........................................................................................................................29
3.5.2 Entity Relation Ship Diagram (ERD)................................................................................................32
3.6 TEST DESIGN....................................................................................................................................33
STAGES OF TESTING.........................................................................................................................34
3.6.1.............................................................................................................................................................34
Unit Testing................................................................................................................................................34
Integration Testing......................................................................................................................................34
User Acceptance Testing............................................................................................................................34
TITLE PAGE.....................................................................................................................................................1

DECLARATION.................................................................................................................................................2

CERTIFICATION...............................................................................................................................................3
DEDICATION...................................................................................................................................................4

ACKNOWLEDGMENT......................................................................................................................................5

ABSTRACT.......................................................................................................................................................6

3. METHODOLOGY.......................................................................................................................................27

3.0 WATERFALL MODEL AND PROTOTYPING.........................................................................................27

3.1 REQUIREMENT ENGINEERING.........................................................................................................29

3.1.1 SYSTEM REQUIREMENTS.................................................................................................................29

3.1.2 HARDWARE REQUIREMENTS...........................................................................................................29

3.1.3 FUNCTIONAL REQUIREMENTS.........................................................................................................29

3.1.4 NON FUNCTIONAL REQUIREMENTS.................................................................................................29

3.2 DESIGN TOOL...................................................................................................................................30

3.2.1 USE CASE DIAGRAM.........................................................................................................................31

3.2.2 ACTIVITY DIAGRAM.........................................................................................................................31

3.2.3 DATA FLOW DIAGRAM (DFD)...........................................................................................................32

3.2.4 SYSTEM FLOW CHART......................................................................................................................34

3.3 DATABASE DESIGN..........................................................................................................................34

3.4 TEST DESIGN....................................................................................................................................36

3.4.1 STAGES OF TESTING.........................................................................................................................37

Unit Testing................................................................................................................................................37

Integration Testing......................................................................................................................................37

User Acceptance Testing............................................................................................................................37

Title Page........................................................................................................................................................1

DECLARATION.................................................................................................................................................2

CERTIFICATION...............................................................................................................................................3

DEDICATION...................................................................................................................................................4
ACKNOWLEDGMENT......................................................................................................................................5

ABSTRACT.......................................................................................................................................................6

3. METHODOLOGY.......................................................................................................................................27

3.0 WATERFALL MODEL AND PROTOTYPING.........................................................................................27

3.1 REQUIREMENT ENGINEERING.........................................................................................................29

3.1.1 SYSTEM REQUIREMENTS.................................................................................................................29

3.1.2 HARDWARE REQUIREMENTS...........................................................................................................29

3.1.3 FUNCTIONAL REQUIREMENTS.........................................................................................................29

3.1.4 NON FUNCTIONAL REQUIREMENTS.................................................................................................29

3.2 DESIGN TOOL...................................................................................................................................30

3.2.1 USE CASE DIAGRAM.........................................................................................................................31

3.2.2 ACTIVITY DIAGRAM.........................................................................................................................31

3.2.3 DATA FLOW DIAGRAM (DFD)...........................................................................................................32

3.2.4 SYSTEM FLOW CHART......................................................................................................................34

3.3 DATABASE DESIGN..........................................................................................................................34

3.4 TEST DESIGN....................................................................................................................................36

3.4.1 STAGES OF TESTING.........................................................................................................................37

Unit Testing................................................................................................................................................37

Integration Testing......................................................................................................................................37

User Acceptance Testing............................................................................................................................37

Title Page........................................................................................................................................................1

Declaration.....................................................................................................................................................2

Certification....................................................................................................................................................3

Dedication......................................................................................................................................................4

Acknowledgment............................................................................................................................................5
ABSTRACT.......................................................................................................................................................6

3.0 METHODOLOGY...............................................................................................................................27

3.1 WATERFALL MODEL AND PROTOTYPING.........................................................................................27

3.2 REQUIREMENT ENGINEERING.........................................................................................................29

3.2.1 SYSTEM REQUIREMENTS.................................................................................................................29

3.2.2 HARDWARE REQUIREMENTS...........................................................................................................29

3.2.3 FUNCTIONAL REQUIREMENTS.........................................................................................................29

3.2.4 NON FUNCTIONAL REQUIREMENTS.................................................................................................29

3.3 DESIGN TOOL...................................................................................................................................30

3.3.1 USE CASE DIAGRAM.........................................................................................................................31

3.3.2 ACTIVITY DIAGRAM.........................................................................................................................31

3.3.3 DATA FLOW DIAGRAM (DFD)...........................................................................................................32

3.3.4 SYSTEM FLOW CHART......................................................................................................................34

3.4 DATABASE DESIGN..........................................................................................................................34

3.5 TEST DESIGN....................................................................................................................................36

3.5.1 STAGES OF TESTING.........................................................................................................................37

Unit Testing................................................................................................................................................37

Integration Testing......................................................................................................................................37

User Acceptance Testing............................................................................................................................37

DECLARATION........................................................................................................................................3

CERTIFICATION.......................................................................................................................................4

DEDICATION...........................................................................................................................................5

ACKNOWLEDGMENT..............................................................................................................................6

ABSTRACT..............................................................................................................................................7

TABLE OF CONTENT...............................................................................................................................8

LIST OF FIGURES...................................................................................................................................11

CHAPTER ONE......................................................................................................................................12

1.0 INTRODUCTION..................................................................................................................12

1.1 PROBLEM STATEMENT....................................................................................................13

1.2 AIMS AND OBJECTIVES..........................................................................................................13

1.3 PROJECT JUSTIFICATION.......................................................................................................13

1.4 SCOPE AND LIMITATION.......................................................................................................14

1.4.1 SCOPE......................................................................................................................................14

1.4.2LIMITATION............................................................................................................................14

1.5 DEFINITION OF MISCELEANOUS TERMS...........................................................................14

CHAPTER TWO.....................................................................................................................................16

LITERATURE REVIEW............................................................................................................................16

2.0 INTRODUCTION..................................................................................................................16

2.1ONLINE REGISTRATION SYSTEM.........................................................................................16

2.1.1 EXAMPLES OF REGISTRATION SYSTEM.........................................................................17

1. VEHICLE REGISTRATION.........................................................................................................17

2. BIRTH REGISTRATION..............................................................................................................17

3. VOTER’S REGISTRATION.........................................................................................................17

4. BUSINESS REGISTRATION...................................................................................................18
 2.2 WEB PORTAL............................................................................................................................18

2.3 ONLINE COURSE REGISTRATION........................................................................................20

2.4 DATABASE MANAGEMENT SYSTEM..................................................................................21

2.4.1 MYSQL IMPLEMENTATION................................................................................................21

CHAPTER THREE...................................................................................................................................23

3.0 INTRODUCTION..................................................................................................................23

3.1 METHODOLOGY.......................................................................................................................23

3.2 WATERFALL MODEL AND PROTOTYPING........................................................................23

3.3 REQUIREMENT ENGINEERING.............................................................................................25

3.3.1 SYSTEM REQUIREMENTS...................................................................................................25

3.3.2 HARDWARE REQUIREMENTS............................................................................................25

3.3.3 FUNCTIONAL REQUIREMENTS..........................................................................................25

3.3.4 NON FUNCTIONAL REQUIREMENTS................................................................................25

3.4 DESIGN TOOL...........................................................................................................................26

3.4.1 USE CASE DIAGRAM............................................................................................................27

3.4.2 ACTIVITY DIAGRAM............................................................................................................27

3.4.3 DATA FLOW DIAGRAM (DFD)............................................................................................28

3.4.4 SYSTEM FLOW CHART........................................................................................................30

3.5 DATABASE DESIGN.................................................................................................................30

3.6 TEST DESIGN............................................................................................................................32

3.6.1 STAGES OF TESTING............................................................................................................33

Unit Testing........................................................................................................................................33

User Acceptance Testing...............................................................................................................33

CHAPTER FOUR....................................................................................................................................34

4.1 SYSTEM IMPLEMENTATION.................................................................................................34

4.1.1 INTERFACE DESIGN.............................................................................................................34

 4.2 SYSTEM TESTING....................................................................................................................35

4.2.1 UNIT TESTING.......................................................................................................................36

4.2.2 FUNCTIONAL TESTING........................................................................................................36

4.2.3 INTEGRATION TESTING......................................................................................................37

4.3 SYSTEM EVALUATION...........................................................................................................37

4.3.1 USER TESTING.......................................................................................................................37

4.3.2 RESULTS.................................................................................................................................37

4.3.2.1 HOME PAGE........................................................................................................................38

4.3.2.2 REGISTRATION PAGE.......................................................................................................38

4.2.3.3 LOGIN PAGE........................................................................................................................40

4.2.3.4 ADMISSION STATUS.........................................................................................................40

4.3.3 SYSTEM CHANGE OVER.....................................................................................................41

4.3.4 USER ANALYSIS....................................................................................................................41

CHAPTER FIVE......................................................................................................................................43

5.0 SUMMARY.................................................................................................................................43

5.2 CONCLUSION............................................................................................................................43

5.3 FUTURE IMPROVEMENTS......................................................................................................44

REFERENCE...........................................................................................................................................45

APPENDIX.............................................................................................................................................47
 CHAPTER ONE

1.10 INTRODUCTION

The advancement in technology has influenced various sectors, including education. The manual
process of student registration in schools has posed significant challenges, such as time consumption,
errors, and inefficiency. This project focuses on designing and implementing an online registration
system for Zaria Children School to enhance the registration process. The system will utilize the
MERN stack (MongoDB, Express.js, React, Node.js) to create a user-friendly interface and streamline
the registration process.

Online registration is a method of registration that could very easily be used to manage the data of its
student population and while at the same time providing them with enhanced incentives. The ultimate
aim being the ease with which information can be exchanged and transferred. It makes easy the
registration procedure via an internet-connected, user-friendly system and dematerializes all
credentials using strategic process and tools [1]. The system of education practised today is one in
need of tremendous amount of information on both staff and students. This online onboarding makes
schools more efficient in carrying out their most important duty of imparting knowledge in students
by introducing a minimal-cost and free of breach registration procedure that promotes for simplified
access to students records by the stakeholders concerned [2]. All admitted students are expected to
onboard online and settle their tuition fees. In a number of situations, enrolling and registering a new
student takes into cognizance some manual procedures which brings about time-wastage for the
students. Student’s registration is done by students mostly at a registration centre. Students have to
move physically to campus to complete the registration process

1.21.1 PROBLEM STATEMENT

The current manual registration process at Zaria Children School is cumbersome and prone to errors.
This leads to inefficiencies, delays, and difficulties in managing student data. Below are some of these
problems include:

[i.] Manual registration processes are usually bedevilledbedeviled by various problems that lead to the
misplacement or inappropriate input of the details of students.
 i.[ii.] The pre-survey of student registration system that was done manually is very time consuming
which wastes a lot of time and resources when trying to complete the whole procedure.
ii.[iii.] Students usually waste a lot of time in completing the process which is compounded by the fact
that it can only be done by their physical presence on ground in school.

An online registration system is needed to address these challenges and improve the overall
registration experience.

1.32 AIMS AND OBJECTIVES

The primary aim of this project is to design and implement an online registration system for Zaria
Children School. The objectives include:

i. To develop a user-friendly interface for student registration.

[ii.] To automate the registration process and reduce manual errors.
[iii.] To ensure secure storage and management of student data.
ii.[iv.] To provide easy access to registration information for students and administrators.
iii. To provide ranking system for higher performance in the entrance examination
iv. Develop different report types for use by the users of the system
[a.] Reports?

1.43 PROJECT JUSTIFICATION

Implementing an online registration system will significantly improve the efficiency and accuracy of
the registration process at Zaria Children School. It will save time, reduce errors, and provide a better
experience for both students and administrators.

1.54 SCOPE AND LIMITATION

1.54.1 SCOPE

The project will cover the design and implementation of an online registration system for Zaria
Children School, including user registration, login, data management, and administrative
functionalities.

1.54.2 LIMITATION

The project will be limited to the registration process and will not include other school management
functionalities such as grading or attendance tracking.

1.65 DEFINITION OF MISCELLANEOUS TERMS

MongoDB: A NoSQL database program that uses JSON-like documents with optional schemas.

Express.js: A web application framework for Node.js, designed for building web applications and
APIs.

React: A JavaScript library for building user interfaces, maintained by Facebook and a community of
individual developers and companies.

Node.js: An open-source, cross-platform JavaScript runtime environment that executes JavaScript

code outside a web browser.

Administration: This is an authority that is charged with any responsibility of either teaching,
securing or any jobs as such.

E: this is usually used to refer to the internet. Even though it actually stands for electronic.

Internet: this is a network that allows computers to connect and communicate with other computers
across the local or globe network.

Design: this is a procedure of bringing about a new thing.

Implementation: this is the deployment of designed system to carry out its new functions.

Transaction: this is an exchange between two parties in which both parties’ profit.

Student: This is an individual who is learning and taking classes at any learning institution.

Database: This a group of data carefully organized that maintains the operational evidences of a
transaction.

Portal: this is a platform that is employed to access different web interfaces such as registration
process.

Registration: This is a process of detailing out one’s personal information in order to become a
member or have access to certain resources in an organization or institution. CHAPTER TWO

Exam – this is an organized procedure meant to test the knowledge of students towards giving them a
certificate.

IS: Information systems

 CHAPTER TWO

2.1 .0 INTRODUCTION

This chapter reviews relevant literature on online registration systems, web portals, and database
management systems. It explores existing systems, their challenges, and the technologies employed in
developing online registration platforms, with a focus on the MERN stack.

2.21 CONCEPTUAL FRAMEWORK

The conceptual framework defines the structure and components of an online registration system,
illustrating how each part interacts to achieve the desired outcomes. It encompasses user interfaces,
data management, and system integration, emphasizing the need for seamless and efficient operations.

2.21.1 Online Registration System

An online registration system automates the process of enrolling students into educational institutions.
It replaces manual, paper-based methods with digital solutions that offer numerous advantages, such
as improved accuracy, efficiency, and user convenience (Rivest et al., 2016).

2.21.2 Web Portals

Web portals act as gateways to various online services, providing users with a unified platform to
access different functionalities. In the contextString of education, web portals facilitate
communication, information dissemination, and various administrative processes (Zhang & Dimitroff,
2005).

2.21.3 Database Management Systems

Database Management Systems (DBMS) are crucial for storing, retrieving, and managing data
efficiently. They ensure data integrity, security, and accessibility, which are essential for any online
registration system (Connolly & Begg, 2015).

2.32 REVIEW OF RELATED LITERATURE

2.32.1 Existing Online Registration Systems

Several institutions have implemented online registration systems to streamline their enrollment
processes. These systems vary in complexity and functionality, depending on the specific needs and
resources of the institution.

2.32.2 Case Studies of Online Registration Systems

Case Study 1: University of Lagos (UNILAG)

The University of Lagos implemented an online registration system to streamline student enrollment
and administrative processes. The system utilized a combination of web technologies such as HTML,
CSS, PHP, and MySQL.

 Challenges:

i. Technical Glitches: The system occasionally experienced downtime during peak

registration periods.

ii. User Training: Students and staff needed training to effectively use the new system.

iii. Scalability: The system initially struggled to handle the large volume of users during
registration periods.

Case Study 2: Covenant University

Covenant University adopted an online registration system to enhance its administrative efficiency.
The system was built using the LAMP stack (Linux, Apache, MySQL, PHP) and offered features for
course registration, fee payment, and student information management.

 Challenges:

i. Security Issues: The system initially faced security vulnerabilities, which required
additional measures to protect student data.

ii. Lack of Mobile Support: The system was not fully optimized for mobile devices,
limiting accessibility for some students.

Case Study 3: Lagos State University (LASU)

Lagos State University implemented an online registration system to manage student enrollment and
administrative tasks more effectively. The system was developed using modern web technologies and
aimed to reduce the administrative burden on staff.

 Challenges:

i. Technical Support: Required ongoing technical support and maintenance to ensure

smooth operation.

ii. User Adoption: Some students and staff were initially resistant to adopting the new
system.
 iii. Performance Issues: The system occasionally experienced slow performance during
high-traffic periods.

Case Study 4: University of Nigeria, Nsukka (UNN)

The University of Nigeria, Nsukka introduced an online registration system to modernize its
administrative processes. The system was built using a combination of PHP, MySQL, and other web
technologies.

 Challenges:

i. Infrastructure: Required reliable internet connectivity, which was sometimes a

challenge in certain areas.

ii. User Training: Both students and staff needed training to fully utilize the system's
features.

iii. System Maintenance: Ongoing maintenance was necessary to address technical issues
and keep the system up-to-date.

2.32.3 Limitations of Existing Systems

Existing online registration systems often face several limitations:

i. Scalability: Difficulty in handling increasing volumes of data and users (Chen et al., 2017).
ii. Security: Vulnerabilities that can lead to data breaches and unauthorized access (Kim, 2016).
iii. User Experience: Lack of intuitive and user-friendly interfaces (Brown, 2018).
iv. Integration: Challenges in integrating with other systems and platforms (Williams, 2019).

2.43 THEORETICAL FRAMEWORK

The theoretical framework for this study on online registration systems is grounded in several key
theories and models.

2.43.1 Information Systems Theory

Information Systems (IS) theory provides a comprehensive foundation for understanding the design,
implementation, and management of information systems within organizations. It encompasses a
broad range of concepts and principles that guide the effective integration of technology into business
processes to enhance organizational performance.

Key Components of Information Systems Theory:

1. Systems Thinking: IS theory promotes a holistic view of information systems, considering
them as integrated and interdependent components that work together to achieve
organizational objectives. This perspective helps in understanding how different elements of
an information system interact and influence each other.

2. Alignment with Organizational Goals: A central tenet of IS theory is the alignment of

technological solutions with organizational goals and strategies. Effective information systems
should support the organization's mission, enhance operational efficiency, and contribute to
overall strategic objectives (Alter, 2008).

3. User-Centered Design: IS theory emphasizes the importance of user needs and preferences in
the design and implementation of information systems. User-centered design ensures that the
system is intuitive, user-friendly, and meets the specific requirements of its intended users.
This approach enhances user acceptance and satisfaction.

4. Information Quality: High-quality information is crucial for effective decision-making. IS

theory underscores the significance of accurate, relevant, and timely information. Information
quality impacts the reliability and usefulness of the system in supporting business processes.

5. System Quality: The technical aspects of an information system, including its performance,
security, and scalability, are critical for its success. IS theory advocates for robust system
architecture that can handle current and future demands while ensuring data security and
integrity.

6. Service Quality: The quality of support services provided to users, such as training, technical
support, and maintenance, is vital for the sustained effectiveness of an information system. IS
theory highlights the role of continuous support and improvement in maximizing system
benefits.

7. Change Management: Implementing new information systems often requires significant

organizational change. IS theory integrates change management principles to address
resistance to change and facilitate smooth transitions. This includes strategies for
communication, training, and stakeholder engagement.

8. Evaluation and Feedback: Ongoing evaluation and feedback mechanisms are essential for the
continuous improvement of information systems. IS theory supports the use of performance
metrics and user feedback to identify areas for enhancement and to ensure the system evolves
with changing organizational needs.
Applications in Online Registration Systems:

In the contextString of online registration systems, IS theory provides valuable insights for designing
systems that align with educational institutions' goals, such as improving efficiency, accessibility, and
data accuracy. By focusing on user-centered design, these systems can better meet the needs of
students, faculty, and administrative staff, leading to higher adoption rates and satisfaction levels.
Ensuring high-quality information and robust system performance is crucial for the reliability and
effectiveness of online registration processes. Moreover, incorporating change management practices
can help institutions navigate the transition to online systems, addressing potential challenges and
resistance from stakeholders.

2.43.2 Technology Acceptance Model (TAM)

The Technology Acceptance Model (TAM), developed by Fred Davis in 1989, is a widely recognized
framework that explains how users come to accept and use a technology. TAM posits that two
primary factors, perceived ease of use and perceived usefulness, significantly influence user
acceptance and usage behavior.

Key Components of TAM:

[1.] Perceived Usefulness (PU): Perceived usefulness is defined as the degree to which a person
believes that using a particular technology will enhance their job performance. If users
perceive that a technology will improve their efficiency, productivity, or overall job
performance, they are more likely to adopt it. In the contextString of online registration
systems, perceived usefulness might involve users believing that the system will save time,
reduce errors, and streamline the registration process.

1.[2.] Perceived Ease of Use (PEOU): Perceived ease of use refers to the degree to which a person
believes that using a particular technology will be free of effort. Technologies that are
perceived as easy to learn and use are more likely to be adopted. For online registration
systems, this means the system should be user-friendly, with intuitive navigation and clear
instructions, to ensure users can complete tasks without unnecessary difficulty.

2.[3.] Attitude Toward Using (ATU): Attitude toward using is influenced by both perceived
usefulness and perceived ease of use. If users have a positive attitude towards a technology,
believing it to be beneficial and easy to use, they are more likely to adopt it. Positive attitudes
can be fostered through effective communication, training, and support.
 3.[4.] Behavioral Intention to Use (BI): Behavioral intention to use is a strong predictor of actual
system usage. It represents the user's readiness and plan to use the technology. This intention
is shaped by the user's attitude toward the technology and their perception of its usefulness and
ease of use.

4.[5.] Actual System Use: Actual system use is the end result of the TAM process. It represents
the real-world adoption and utilization of the technology by users. The ultimate goal of TAM
is to predict and explain this usage behavior, providing insights into how and why users decide
to engage with a particular technology.

2.43.2.1 Applications in Online Registration Systems:

When applying TAM to the adoption of online registration systems in educational institutions, several
practical implications emerge:

i. Design and Development: Developers should focus on creating a system that is both useful
and easy to use. This involves incorporating features that directly benefit users, such as real-
time updates, automated notifications, and error-checking mechanisms, while also ensuring the
interface is simple and intuitive.

ii. Training and Support: Providing comprehensive training and ongoing support can enhance
users' perceptions of ease of use and usefulness. Workshops, tutorials, and helpdesks can
address initial concerns and assist users in navigating the system effectively.

iii. Communication: Clear and consistent communication about the benefits of the online
registration system can positively influence users' attitudes. Highlighting success stories,
efficiency gains, and user testimonials can help build a positive perception of the system.

iv. Feedback Mechanisms: Implementing feedback mechanisms allows users to share their
experiences and suggestions for improvement. This not only helps in refining the system but
also demonstrates that user input is valued, further enhancing their attitude towards the system.

v. Monitoring and Evaluation: Regularly monitoring usage patterns and evaluating system
performance can provide insights into areas that may require additional attention.
Understanding why users may be reluctant to adopt the system can inform targeted
interventions to address these barriers.

2.43.3 Systems Development Life Cycle (SDLC)

The Systems Development Life Cycle (SDLC) is a process for planning, creating, testing, and
deploying information systems. It includes stages such as requirement analysis, system design,
implementation, testing, deployment, and maintenance (Royce, 1970).

2.54 MERN STACK TECHNOLOGY

The MERN stack is a web development framework consisting of four key technologies: MongoDB,
Express.js, React.js, and Node.js. MongoDB serves as the NoSQL database, providing a flexible,
document-oriented data storage solution.

2.54.1 Overview of MERN Stack

The MERN stack comprises MongoDB, Express.js, React, and Node.js. It is a popular framework for
building modern web applications, known for its efficiency, scalability, and ease of use (Sharma,
2020).

i. MongoDB: A NoSQL database that stores data in flexible, JSON-like documents (Banker,
2011).
ii. Express.js: A web application framework for Node.js that simplifies the development of
server-side applications (Holmes, 2012).
iii. React: A JavaScript library for building user interfaces, particularly single-page applications
(Facebook, 2013).
iv. Node.js: A JavaScript runtime that allows developers to run JavaScript on the server side
(Tilkov & Vinoski, 2010).

2.54.2 Advantages of MERN Stack

i. The MERN stack offers several advantages for developing online registration systems:
ii. Unified Language: JavaScript is used throughout the stack, simplifying development and
debugging (Sharma, 2020).
iii. Scalability: MongoDB’s flexible schema design allows for easy scaling as data volumes grow
(Banker, 2011).
iv. Performance: Node.js provides a non-blocking, event-driven architecture, enhancing
application performance (Tilkov & Vinoski, 2010).
 v. Component-Based Architecture: React enables the creation of reusable UI components,
improving code maintainability (Facebook, 2013).

2.65 IMPLEMENTATION STRATEGIES

An implementation strategy is a detailed plan for deploying new systems or processes within an
organization, covering resource allocation, timelines, risk management, training, and support. It
ensures alignment with organizational goals and addresses potential challenges to integrate new
initiatives smoothly (Smith, 2023).

2.65.1 Agile Methodology

Agile methodology promotes iterative development, where requirements and solutions evolve through
collaboration between cross-functional teams. It is well-suited for projects requiring flexibility and
rapid delivery (Beck et al., 2001).

2.65.2 Waterfall Model

The Waterfall Model follows a linear and sequential approach to software development. Each phase
must be completed before moving on to the next, making it suitable for projects with well-defined
requirements (Royce, 1970).

2.65.3 Prototyping

Prototyping involves creating an early model of the system to gather user feedback and refine
requirements. It helps identify potential issues early in the development process and ensures the final
system meets user needs (Budde et al., 1992).

2.76 SUMMARY

This chapter provided a comprehensive review of literature related to online registration systems, web
portals, and database management systems. It explored existing systems, their limitations, and the
theoretical frameworks underpinning their design and implementation. The MERN stack technology
was highlighted as a modern and efficient solution for developing online registration systems, offering
numerous advantages over traditional stacks.
 CHAPTER THREE (SYSTEM ANALYSIS AND DESIGN)

This chapter gives an introduction to the methodology adopted and the justification on the
chosen developmental model. The different phases of the model will be carefully analyzed;
the chapter will then identifies and describes the tools used to perform the software
development processes

3. 1 METHODOLOGY

A methodology when used in software development refers to a framework that is employed

for use in order to structure, plan, and control the whole procedure of developing an
information system. There are many procedures that can be applied depending on its
suitability to the project in question . They includes; Waterfall model system, V-model
system, Incremental model system, Rapid Application Development model system, Proto
type model system, Spiral model system, Agile model system, Iterative model systemetc.
For the purpose of this project work the waterfall model system is selected as the procedure
to be used to develop the CRRS. Below is a brief overview on how the scope of each phases
were visited in this project work.

3.2 WATERFALL MODEL AND PROTOTYPING

The methodology that might be useful is the project life cycle and prototype. The project life
cycle methodology and prototyping is a methodology that allows users to review all stages
until the management/users are okay with the Online Registration System. Figure 3.1 is a
diagram of the waterfall model system.
 Requirement Gathering

RequirementAnalysis

System Design

Implementation

Testing And Validation

Figure 3.1 the waterfall model for the system study and design

Waterfall model with Prototyping will be employed as a model of Online Registration

System. Waterfall model comprises of phases that are sequentially moving from one to
another. One development phase must be fully done before the next begins. The Waterfall
model presents a very advanced-level view of all processes occurring during development,
and it indicates to developers the series of events they should expect to come in contact with.
The Selection stage is where an online application will be selected according to the needs of
applicants. After conducting a complete study on the application that is selected, the next is
on mapping out the difficulties.
Planning is an important stage in which a plan or strategy is drafted and all necessary
changes are implemented so that there won't be any further need to make any last minute
changes any further The plan will be drafted so that there is progress in the application
development. The current registration system employed for use within Nigeria and other
countries also have been studied. The plan is then meticulously followed so that the system
can be deployed for use.
3.3 REQUIREMENT ENGINEERING

This is where data and information regarding the user’s requirement are gathered. The
requirements are broken down into user requirements and system requirements, with the
system requirement broken into functional and non-functional requirements.

3.3.1 SYSTEM REQUIREMENTS

System requirement are those things, needed for the efficient working of the new system.
These include:

Software Requirement
Hard Requirement
3.3.2 HARDWARE REQUIREMENTS

Hardware refers to the physical component of the computer. This houses the software, the
combinations of hardware and also software is important for the effective running of the new
system that was designed for online registration System. The hardware requirements that are
needed for the effective running of the new system are stipulated below as follows: monitor,
CPU 512mb of RAM, 1.0MHz processor, keyboard, mouse, printer and internet access.

3.3.3 FUNCTIONAL REQUIREMENTS

[3.3.4]
3.3.3.1[3.3.4.1] Admin should be able to login, Add Student Record, view students ID card
[3.3.4.2]
3.3.3.2[3.3.4.3] Admin should be able to view Record of students, edit/delete a student,
and generate report for applicants.

3.3.3.3[3.3.4.4] Student should be able to register through the system

[3.3.4.5]
3.3.4[3.3.5] NON FUNCTIONAL REQUIREMENTS
[3.3.6]
3.3.4.1[3.3.6.1] The software shall support multiple users at the same time.
 3.3.4.2[3.3.6.2] The software performs well and runs on the web application smoothly.

3.4 DESIGN TOOL

The design tool employed for use in the project is the UML. The Unified Modeling Language
is a world recongnised graphical notation used in analysing the software analysis and designs.
UML has symbols to aid in explaining and keeping record of every aspect of the application
development process. When a world-recognised notation is used, it provides an effectives
means of exchange of information.

View Applicants, Accept/Reject Admin

Applicants Generate Report

Student

Apply for Admission, Check

and Print Admission Letter
Online
Registration
Figure 3.2: High level Design of Proposed System
3.4.1 USE CASE DIAGRAM

This is an all round sequence of closely related actions initiated by an actor; it symbolises a
special way to use the system.

Use Case Diagram: A diagram that depicts the use cases and actors for a system.

Fig 3.3 Use Case Diagram

 3.4.2 ACTIVITY DIAGRAM

Activity diagram is a very important diagram in Unified Modelling Language (UML) which is
used to explain dynamic parts of the system. Activity diagram is essentially a flow chart to used
to signify the flow of information from one activity to another. The activity can be
explained as one of the functions of the system; therefore, the control of flow is drawn from one
operation to the other. This flow can either be a sequential, branched or concurrent one.

Login

Admin login

[Not successful]

[Successful]

Admin operation

Register Manage View Generate

Student Student students report

Logout

Fig 3.4 UML Activity Diagram

e
explained as one of the functions of the system; therefore, the control of flow is drawn from one
operation to the other. This flow can either be a sequential, branched or concurrent one.

Fig 3.4 UML Activity Diagram

3.4.3 DATA FLOW DIAGRAM (DFD)

• A diagrammatic representation of the flow of data between external entities and the
processes and data stores within a system

• Difference from system flowcharts:

• DFDs represents logical data flow which is not dependent of technology

•
• Flowcharts describes even the minute details of physical systems

Add students View students Generate Reports Apply for admission

Admin
Records

Online Registration System

Fig 3.5 Data Flow Diagram
 • DFDs represents logical data flow which is not dependent of technology

• Flowcharts describes even the minute details of physical systems

Add students View students Generate Reports Apply for admission

Records
Fig 3.5 Data Flow Diagram
[3.4.4] SYSTEM FLOW CHART

Start

Select option

View Yes List of Applicants

Applicants

Manage Applicants
Edit
applicant?

Admitted? Generate report

Logout user
Log out?

Return

Fig 3.6 Admin Page

3.5 DATABASE DESIGN

Database is a carefully selected items having related information. In the creation of online
registration system, the various related entities are: students, Admindepartment, faculty,
level, session and entrance scoreadmin Documents.file.
Table Document 3.1 Students TableDocument

FIELD NAME DATA TYPE FIELD SIZE

Form id Integer/auto 20

Surname TextString 20

Othername TextString 20

Sex TextString 50

Age Integer 10

Address TextString 50

State TextString 20

LGA TextString 15

Marital status TextString 30

DOB TextString 10

Class_Apply TextString 50

Date Date\time 8

Disability TextString 50

Session TextString 30

Date Text 50

Phone TextString 30

Passport File 50
DocumentTable 3.2 Admin DocumentTable

# Name Data Type Null Extra

1 Id int(4)Auto No AUTO_INCREMENT

2 Firstname varchar(50)Stri No
ng

3 Surname varchar(50)Stri No
ng

4 Phone varchar(30)Stri No
ng

5 Username varchar(30)Stri No
ng

6 Password varchar(30)Stri No
ng

7 Role_id varchar(30)Stri No
ng

8 Status varchar(30)Stri No
ng

Document 3.3 Entrance Score Document

# Name Data Type Null Extra

1 Id intAuto No AUTO_INCREMENT

2 studentID String No

3 Score String No
 Document 3.3 Session Document

# Name Type Null Extra

1 Id integer No AUTO_INCREMENT

2 Session String No

3 Term String No

3.5.2 Entity Relation Ship Diagram (ERD)

adminID lastNam
studentID lastName
e

FirstName DAteOfBirth FirstNa Email

Gender
Gender me

Email
student M
Manages 1 Admin
;;]ino’j
;;]ino’j
address 1

ID Grade

Score

EntranceExamsScore M Manages
;;]ino’j
3.6 TEST DESIGN

In order to achieve this, the researcher embarked onr re-checks the logic of the design tool to
rectify any bug if necessary, and also makes sure that there’s no disconnect between the
logic behind the actual program and the logic of the design tool.

Therefore, the researcher carefully prepared valid or invalid test data. The valid test data of
this research work for the online registration system development of a software package of
registration form were first manually processed and then processed with the program. The
researcher then makes a comparation between the work put forth by the designed solution and
the work by other candidates. All these are in order to ensure that any embarrassing bug is
detected and resolved or eliminated.
Then, the valid test data were employed as bugs to the new system as a challenge in order to
see if it will respond in an appropriate style.

3.6.1[3.5.1] STAGES OF TESTING

[3.5.2]

[3.5.3]
Unit Testing

Unit testing specifies on testing module, script or component that has been designed by PHP
and JavaScript. In the case for this work, is a test on collecting of user data in registration
and database.

Integration Testing

Once the unit testing has been carried out with it being okay for each components or script,
the integration testing then begins in order to ensure the online registration work fine. The
functional and non-functional requirements are tested at this stage. An example of integration
testing is generation of tuition fee report for new students.

User Acceptance Testing

User acceptance testing in the final phase of testing system and perhaps Online Registration
System before the system is deployed for operational uses, s,.it is tested with data supplied by
the system client instead of with simulated test data. Acceptance testing may make apparent
mistakes or omission in the system design, because the real data challenges the system in
better ways from the test data. Acceptance testing may also reveal where the system’s
requirements facilities do not really meet the user’s needs or the system performance is poor
and unacceptable.
 CHAPTER FOUR
SYSTEM IMPLEMENTATION AND TESTING

1.1 SYSTEM IMPLEMENTATION

This chapter deals with software deployment and testing of a system that is designed from the

previous chapter (chapter three), during the system testing each component of this system

was tested independently and the test result was documented in a tabular form, the system

will be tested after all the component are integrated together as a single system. Lastly, we

present some snapshot of some modules from the system.

The proposed system being an online registration system is targeted towards students who

want to apply for admission.

1.1.1 INTERFACE DESIGN

There are two modules in this phase, these include: administrator module and Student’s

module

The Administrator’s module: The administrator views List of registered students, Manage

student’s record, confirm/rejects student admission and change password.

Fig 4.1 Admin Page

The Student’s module: The students register for admission, view admission status, update

profile and change password.

Fig 4.2 Student Page

1.2 SYSTEM TESTING

The system was challenged by being tested during all phases of its development, in order to

identify and delete bugs. While the development lasted, a parallel testing was carried out to

bridge any gap between the manual output report and automated report. Even though the

presentation style of the automated report varied a bit , there is uniform information.

Integration of modules: Some modules were observed to work more effectively

independently then when integrated.

I tested the performance of the software in different web browsers. It was observed to work

best with a Mozilla Firefox browser.

The query language was tested for its ability to generate different Kinds of test results. It was

observed that the input data structure in the database design have to correspond to the user’s

input. E.g. typing student registration number with space in between as in ―162020 4030‖ in

the login input table would not bring up the required report if the table design structure does

not condone space in between. Again, character length specified in the design table must be

used in the character data entry.

The cascading style sheet was tested by changing the settings until a suitable rendering was

obtained. The higher the parameters value the more visualised and suitable outlook it

presents. The system was run on a localhost at the end of the deployment and it was observed

to perform very well.

1.2.1 UNIT TESTING

Unit testing prioritizes on testing module, script or component that has been designed by

PHP and JavaScript. In the case of this project, is a test on capturing of user data in

registration and database. Figure 4.4 shows unit testing of admin dashboard of the system.

Figure 4.3 Admin Dashboard online registrations System

1.2.2 FUNCTIONAL TESTING

In Testing of softwares, Functional testing is a process of testing functionalities of the system

and ensuring that the system is working in tandem with the functionalities specified in the

plan document (). The aim of this testing is to ascertain whether the system is functionally

excellent. An instance of functional testing is accepting/rejecting applicants by admin.

1.2.3 INTEGRATION TESTING

Once the unit testing has been carried out with satisfactorily result for each components or

script, the integration testing then commences in order to make sure that the online

registration System parts work together effectively. The functional and also the non-

functional requirements are challenged at this phase. An instance of integration testing is

generation of successful applicants reports based on the number of student registered.

1.3 SYSTEM EVALUATION

System evaluation is the state of examining the performance of a fully-developed system to

find out how it is probable to perform in real market situations (Wikipedia, 2021). This helps

a lot because it makes us to become fully aware of how end users will respond to some

features embedded in the design of the software

1.3.1 USER TESTING

This is the final phase of the system testing and also the online on boarding before the system

is finally deployed and accepted for use. The system is examined with data provided by the

client rather than with simulated test data. Acceptance testing may bring to the surface errors

that were previously not taken into much account because the real data will challenge the

system in a tougher way in comparation to the test data. Acceptance testing may also reveal

requirements problems where the system’s facilities do not really meet the user’s needs or the

system performance is unacceptable.

1.3.2 RESULTS

Processed data generated by a system is referred to as results or output. This has as its

contents among many others data mined at a level of software, which example is the end-
result of successful registered applicants on screen, or at a physical level, such as printed

document in different formats as specified in the design of the system

1.3.2.1 HOME PAGE

Figure 4.4 Home page

Figure 4.4 is Home page or the start page of online registration System. This page consists of

different menu such as Registration and Login pages.

1.3.2.2 REGISTRATION PAGE

Figure 4.5 Registration Page

Figure 4.5 Is a user login page of online registration System that allows applicants to register

for unity international school Abuja programme.

4.2.3.3 LOGIN PAGE

Figure 4.6 Login Page

Figure 4.6 is Login page of online registration System. This page allows admin and

applicants to login into the system with their username and password.

4.2.3.4 ADMISSION STATUS

Figure 4.7 Login Page
Figure 4.7 is Admission Status page of online registration System. This page allows

applicants to see their admission status.

1.3.3 SYSTEM CHANGE OVER

This is the systemic method of changing an already existing document into a magnetic type,

when it has been tested and found to be free of errors.

There exists a number of methods of changing to a new system. These are: parallel

changeover method, direct changeover method, phase and pilot changeover method when the

new and old systems are put into use at the same time.

To enhance the benefit of this project work, the parallel change over method would be

adopted, because of its importance as regards showcasing the working process of both the

new and the old system in order to fully be able to identify the changes.

1.3.4 USER ANALYSIS

User analysis is a procedure by which professionals who design products such as engineers,

designers and developers collect feedback from the end users of the products in order to be

able to make the necessary changes an improvement to such products to gain more users,

further the user experience and ultimately make more profit.

To ensure the use of the right methods in collecting feedback and generally know how to go

about collating user feedback and monitoring the behaviours of users, it is important to

realise the numerous benefits involved in the procedure. The following are reasons why

collecting user feedback is important:

 Understanding how end users interact with your product: This helps you learn what

you users do with the features present on your product, which is their favourite

feature and why that is so.

 Developing The profile of users based on their actions and attributes: With user

analysis, you can be better equipped to understand the distinct personas of your

users and help you to fully integrate that into your products’ subsequent version.

 Gathering quantifiable amount of data on the users: User analysis helps to to be able

to quantify the tastes and preferences of your users and integrate them in your

subsequent designs.

 Product design: User analysis helps to you to make informed decision when

designing other products and services and a clearly detailed customer feedback

which is usually the result of a good user analysis brings about informed decisions as

regards the design of new products, new/updated features, and also on boarding

strategy. .
 CHAPTER FIVE
SUMMARY, CONCLUSION AND RECOMMENDATIONS

5.0 SUMMARY

The whole work is based on the employment of computer system for use with regards the

registration of students in Unity international school.

The work tries to analyse the current manual system in use in comparation to the new system

being proposed, while outline the aims of the new system, the problems it hopes to solve and

going ahead to deploy it for use. The work was successfully developed using PHP, html,

CSS, and bootstrap, a user- friendly programming language, and the package was tested and

improved upon which yielded an E-registration system.

Even though no project work can perfect be used as an adjective to qualify it, the importance

of this particular one cannot really be overemphasized. It has a lot of benefits chief among

which is the real reduction in the amount of time taken to process information and create

solutions for problems arising.

5.2 CONCLUSION

Technology, organization and people must come together and push each other to enhance the

performance of the entire system. Appreciating the role of information systems in the process

of students’ registration helps to bring about sanity to the whole process. By so doing, the

authority of an institution can be better equipped to address students complains in a timely

and effective manner. When fully deployed, this system would make it possible for students

to carry out their registration process from wherever they might be on the globe. This would

bring about an effectiveness in the whole nature of the authority’s effectiveness.

Despite the challenges faced during the implementation phase of this work, my aim has been

very well attained. Moreover, in trying to bring this project to fruition, a reduction in the
amount of time spent has been very well achieved. This challenge has therefore imparted in

me knowledge that I couldn’t have obtained through any other means which is all that is

involved in the design and implementation of any work.

5.3 FUTURE IMPROVEMENTS

Based on already attained objective of this work, and the knowledge obtained while its design

and implementation lasted, there is need to make the following suggestions for further

enhancement.

1. Secondary schools should automate their registration system for greater effectiveness,

organization, and reliability. Doing this will ensure that all problems encountered by

students during registration are eliminated.

2. One very significant aspect of research project is funding. Research institutions, industries

concerned and even governments should provide student with research grants in order to

get to do their projects with peace of mind.

3. Finally, the whole process of students’ project should be close monitored in order to

achieve a maximum output of result.

 REFERENCE
[1] Band, S., Muijis, D., & Lindsay, G. (2005). Evaluation of Capital Modernization Funding’s

for electronic registration in selected secondary schools, 2ndinterim report January,

2005.

[2] Boyd, J.M. (2002). An Investigation of the Effectiveness of Web Registration for

Incentive Travel Programs and Meetings.

[3] Ramos et al ―COMPUTERIZE ENROLLMENT SYSTEM‖ B.Sc Research Study, College of

Computer Study, Urdaneta City University, 2011.

[4] Academic Planning Division, ―Twenty Years (1962-1982) of Academic Development in

the Nigerian Federal, University System in: 20 Tears of University Education in Nigeria‖, pp.

84-90. NUC, 1988.

[5] Brakel, P.V. (2003). Information Portals: A strategy for importing external content,

Electronic Library, Vol. 21 ISS: 6, pp. 591-600.

[6] Valina et.al (2009), The Personal Research Portal: Web 2.0 Driven Individual

commitment with open access development, Knowledge Management for Development

Journal, Amsterdam. 3 (1) 35-48.

[7] Cabang et al. (2003)) what social factors affect students use of online registration: an

exploratory study, Association for Institutional Research 42nd Annual forum, June. Toronto,

Canada.

[8] 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.

[9] Development of Online Project Registration and Management System for Master

Coursework by Abdullah et.al, 2015.

[10] Online Admission System for School by, 2014 Patel Payal B.(11032211193) Patel Rinkal
B,2014
[11] Online Course Registration System by Tolstoy Newtonraja et al., 2009.

[12] Strauss, Howard (2000) Tech Talk Event CNI Spring Task Force Meeting, March 27-28.

[13] Development of Online Student Course Registration System by Rattan Singh, Ravinder

Singh, Harpreet Kaur and O.P Gupta , 2016

 APPENDIX
Database

Table structure for table ‘applicants’

--

CREATE TABLE IF IT DOES NOT EXISTS `applicants` (

`id` int(10) NOT NULL AUTO_INCREMENT,

`user_id` int(30) NOT NULL,

`firstname` varchar(200) NOT NULL,

`surname` varchar(200) NOT NULL,

`lastname` varchar(200) DEFAULT NULL,

`dob` varchar(20) NOT NULL,

`phone` varchar(20) NOT NULL,

`gender` varchar(10) NOT NULL,

`state_id` int(5) NOT NULL,

`lga_id` int(11) NOT NULL,

`address` varchar(200) NOT NULL,

`reg_no` varchar(200) NOT NULL,

`programme` varchar(100) NOT NULL,

`guidance` varchar(100) NOT NULL,

`session` varchar(100) NOT NULL,

`primary_certificate` varchar(100) NOT NULL,

`date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,

`status` int(1) NOT NULL DEFAULT '0',

`admission_status` varchar(100) NOT NULL DEFAULT 'In progress',

PRIMARY KEY (`id`)

) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=6 ;

-- Table structure for table `complains`

--
CREATE TABLE IF NOT EXISTS `complains` (
`complain_id` int(10) NOT NULL AUTO_INCREMENT,
`user_id` int(30) NOT NULL,
 `subject` varchar(200) NOT NULL,
`complain` varchar(500) NOT NULL,
PRIMARY KEY (`complain_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ;

Admin header php

<?php
session_start();

?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">

<head>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title ></title>

<link rel="stylesheet" type="text/css" href="./css/bootstrap.min.css" />

<link rel="stylesheet" type="text/css" href="./css/bootstrap-datetimepicker.min.css" />

<link rel="stylesheet" type="text/css" href="./css/font-awesome.min.css"/>

<link rel="stylesheet" type="text/css" href="./css/theme.css"/>

</head>

<body>

<div class="col-lg-12">

<div class="col-lg-2"></div>

<div class="col-lg-10">

</div>

</div>

<div class="container col-lg-12">

<div class="nav navbar-static-top row navbar-inverse" >

<div class="navbar-header">

<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-

target=".navbar-collapse">

<a href="#"><i class="glyphicon glyphicon-align-justify"></i></a>

</button>
 <a class="navbar-brand" href="index.php" style="color:white"><!---i class="fa fa-
graduation-cap"!---></i> <b>Unity International School Abuja</b>

</div>

<div class="navbar-collapse collapse">

<ul class="nav navbar-nav" >

<li><a href='index.php' style="color:white"> <i class="fa fa-home"></i>

Home</a></li>

<li><a href='applicants.php' style="color:white"> <i class="fa fa-users"></i> View

Applicants</a></li>

<li><a href='add-applicants.php' style="color:white"> <i class="fa fa-users"></i>

Add Applicant</a></li>

<li><a href='reports.php' target="_blank" style="color:white">Generate Report <i

class="fa fa-check-circle"></i> </a></li>

<li><a href='report.php' style="color:white"> <i class="fa fa-bullhorn" ></i>

Admitted Applicants</a></li>

<li><a href='complains.php' style="color:white"> <i class="fa fa-envelope"></i>

Applicants Complains</a></li>

<li><a href="changepassword.php" style="color:white"><i class="fa fa-edit"></i>

Change Password</a></li>

<li><a href="../applicant/logout.php" style="color:white"><i class="fa fa-sign-

out"></i> Logout</a></li>

</ul>

</div>

</div>

</div>

Applicant header php

<?php
?>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">

<head>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

<title>Unity International School Abuja</title>

<link rel="stylesheet" type="text/css" href="./css/bootstrap.min.css" />

<link rel="stylesheet" type="text/css" href="./css/bootstrap-datetimepicker.min.css" />

<link rel="stylesheet" type="text/css" href="./css/font-awesome.min.css"/>

<link rel="stylesheet" type="text/css" href="./css/theme.css"/>

</head>

<body>

<div class="col-lg-12">

<div class="col-lg-2"></div>

<div class="col-lg-10">

</div>

</div>

<div class="container col-lg-12">

<div class="nav navbar-static-top row navbar-inverse">

<div class="navbar-header">

<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-

target=".navbar-collapse">

<a href="#"><i class="glyphicon glyphicon-align-justify"></i></a>

</button>

<a class="navbar-brand" href="index.php" style="color:white"><i class="fa fa-

graduation-cap"></i>Unity International School Abuja</a>
 </div>

<div class="navbar-collapse collapse">

<ul class="nav navbar-nav" >

<li><a href='index.php' style="color:white"> <i class="fa fa-home" ></i>My

Application Form</a></li>

<li><a href='status.php' style="color:white"> <i class="fa fa-files-o" ></i>

Admission Status</a></li>

<li><a href='lodge_complain.php' style="color:white"> <i class="fa fa-edit"></i >

Lodge Complain</a></li>

<li><a href="changepassword.php" style="color:white"><i class="fa fa-edit"></i>

Change Password</a></li>

<li><a href="../applicant/logout.php" style="color:white"><i class="fa fa-sign-

out"></i> Logout</a></li>

</ul>

</div>

</div>

</div>

Header php

<?php

session_start();

?>

<!DOCTYPE html>

<html lang="en"><head><meta http-equiv="Content-Type" content="text/html;

charset=UTF-8">

<meta charset="utf-8">

<meta name="viewport" content="width=device-width, initial-scale=1.0">

<meta name="description" content="">

 <meta name="author" content="">

<title>Unity International School Abuja</title>

<!-- Bootstrap core CSS -->

<link href="./css/bootstrap.min.css" rel="stylesheet">

<link href="./css/bootstrap-datetimepicker.min.css" rel="stylesheet" media="screen">

<script type="text/javascript" language="javascript" src="./public/js/jquery.js"></script>

<script type="text/javascript" language="javascript"

src="./public/js/jquery.dataTables.js"></script>

<script type="text/javascript" language="javascript"

src="./public/js/bootstrap.min.js"></script>

<script type="text/javascript" language="javascript" src="./public/js/bootstrap-

modal.js"></script>

<script type="text/javascript">

$(document).ready(function(){

$('.toggle-modal').click(function(){

$('#logout').modal('toggle');

});

});

</script>

<!-- Custom styles for this template -->

<link href="./public/css/offcanvas.css" rel="stylesheet">

<link rel="stylesheet" href="./public/css/prettyPhoto/css/prettyPhoto.css" type="text/css"

media="screen" title="prettyPhoto main stylesheet" charset="utf-8">

<link href="./public/css/facebox/facebox.css" media="screen" rel="stylesheet"

type="text/css">

<link href="./public/css/font-awesome.min.css" rel="stylesheet" type="text/css">

</head>

<body style="zoom: 1;">

<!--Header-->

<div class="navbar navbar-fixed-top navbar-inverse" role="navigation">

<div class="container">

<div class="navbar-header">

<button type="button" class="navbar-toggle" data-toggle="collapse" data-

target=".navbar-collapse">

<span class="icon-bar"></span>

<span class="icon-bar"></span>

<span class="icon-bar"></span>

</button>

<a class="navbar-brand" href="index.php" style="color:white"><!---i class="fa fa-

graduation-cap"!---></i>Unity International School Abuja</a>

</div>

<div class="collapse navbar-collapse">

<ul class="nav navbar-nav">

<li><a href="index.php" style="color:white"><i class="fa fa-home"></i>

Home</a></li>

<li><a href="register.php" style="color:white"><i class="fa fa-home"></i>Apply

Now</a></li>

<li><a href="" style="color:white"><i class="fa fa-edit"></i> News</a></li>

<li><a href="about.php" style="color:white"><i class="fa fa-question-circle"></i>

About-Us</a></li>

<li><a href="contact.php" style="color:white"><i class="fa fa-question-

circle"></i> Contact-Us</a></li>

<!-- <li><a href="/justines/index.php?page=7">Site Map</a></li> -->

 </ul>

</div><!-- /.nav-collapse -->

</div><!-- /.container -->

</div><!-- /.navbar -->

### References

- Alter, S. (2008). Defining information systems as work systems: implications for the IS field.
European Journal of Information Systems, 17(5), 448-469.

- Banker, K. (2011). MongoDB in Action. Manning Publications.

- Beck, K., Beedle, M., van Bennekum, A., et al. (2001). Manifesto for Agile Software Development.

- Brown, J. (2018). User Experience Design: Beyond the Basics. Apress.

- Budde, R., Kautz, K., Kuhlenkamp, K., & Zullighoven, H. (1992). Prototyping: An Approach to
Evolutionary System Development. Springer-Verlag.

- Chen, J., Zhang, D., & Lee, W. (2017). Scalability in Cloud Computing. IEEE Transactions on
Computers, 66(1), 12-18.

- Connolly, T., & Begg, C. (2015). Database Systems: A Practical Approach to Design, Implementation,
and Management. Pearson.

- Davis, F. D. (1989). Perceived Usefulness, Perceived Ease of Use, and User Acceptance of
Information Technology. MIS Quarterly, 13(3), 319-340.

- Facebook. (2013). React: A JavaScript library for building user interfaces. Retrieved from
https://reactjs.org/

- Holmes, A. (2012). The Definitive Guide to Express.js. Apress.

- Johnson, M. (2019). Integrating Real-Time Analytics in Educational Systems. Journal of Educational

Technology Systems, 48(1), 24-38.

- Kim, J. (2016). Enhancing Security in Online Systems. Information Systems Journal, 26(3), 235-259.

- Rivest, R. L., Shamir, A., & Adleman, L. (2016). A Method for Obtaining Digital Signatures and Public-
Key Cryptosystems. Communications of the ACM, 21(2), 120-126.
- Royce, W. W. (1970). Managing the Development of Large Software Systems. Proceedings of IEEE
WESCON, 1-9.

- Sharma, A. (2020). Full-Stack React Projects. Packt Publishing.

- Smith, T., Allen, C., & Baker, R. (2018). Implementing Online Registration Systems: Lessons Learned.
Journal of Educational Technology, 45(2), 145-155.

- Tilkov, S., & Vinoski, S. (2010). Node.js: JavaScript on the Server. IEEE Internet Computing, 14(6),
80-83.

- Williams, K. (2019). System Integration Challenges in Modern Web Applications. Journal of Systems
and Software, 150, 67-78.

- Zhang, P., & Dimitroff, A. (2005). Web portals: The new gateways to Internet information and
services. Communications of the ACM, 48(5), 93-97.