Design and Development of a Queue Management System for

Soul Care Garden Hotel.

By

ZAINAB IBRAHIM IZANG

VUG/CSC/19/3380

A PROJECT SUBMITTED TO

THE DEPARTMENT OF COMPUTER AND INFORMATION TECHNOLOGY

FACULTY OF NATURAL AND APPLIED SCIENCES, VERITAS
UNIVERSITY, ABUJA

IN PARTIAL FULFILMENT OF THE REQUIREMENTS FOR THE AWARD OF

THE BACHELOR OF SCIENCE DEGREE (BSc) IN COMPUTER SCIENCE

i
 9th June 2023

DESIGN AND DEVELOPMENT OF A QUEUE

MANAGEMENT SYSTEM FOR SOUL CARE GARDEN

HOTEL.

ii
 CERTIFICATION

This is to certify that this project entitled “Your Project topic ” was carried out by “Your

Name “ with matriculation number “Matric Number” in the Faculty of Natural and

Applied Sciences, Veritas University, Abuja for the award of Bachelor of Science in

Computer Science.

Name __________________

MR VICTOR OMOPARIOLA

(Project Supervisor) Sign and Date

Name
__________________
DR.ESSIEN,J.

Sign and Date

(Head of Department)

Name
__________________
Prof. SIMON K.OKWUTE

(Dean of Faculty) Sign and Date

Name __________________

PROF.OLUMIDE OWOLABO

(External Examiner) Sign and Date

iii
 DEDICATION

This is to certify that this Thesis/Report entitled [Design and Development of

a Queue Management System for Soul Care Garden Hotel], which is

submitted by [ZAINAB IBRAHIM IZANG ] in partial fulfilment of the

requirement for the award of degree for B.Sc. in computer science to the

Department of natural and applied sciences , veritas university Abuja, Nigeria,

comprises of only my original work and due acknowledgement has been made

in the text to all other materials used.

iv
v
 ABSTRACT

The proposed system is designed as an online solution to the long wait time

and crowd with the pandemic we faced . The queue management system aims

help service provider manage their customers efficiently. The system will be

designed to ease customer flow management, which is useful for managers of

the service provider. In addition, help provide the customer with clarity into

hotel traffic and waiting time before leaving their destination. The app was

developed using the waterfall methodology, was successfully tested, and

produced desirable results. Development of the application willcontinue with

for future update and further enhancements.Development Technology and

Tools use in the building the Application is the Ionic 5 Angular7 with visual

studio codeand Firebase DB, which comprises of Typescript frame work, Ionic

UI components and the reason for using this tools is that it is easy to

learn, native Integration, hybrid application development and also works well

with google API further more good for big data.I

vi
 TABLE OF CONTENTS

TITLE PAGE-----------------------------------------------------------------------------------------I

CERTIFICATION-----------------------------------------------------------------------------------II

DEDICATION--------------------------------------------------------------------------------------III

ACKNOWLEDGEMENT------------------------------------------------------------------------IV

ABSTRACT------------------------------------------------------------------------------------------V

TABLE OF CONTENTS--------------------------------------------------------------------------VI

LIST OF FIGURES-------------------------------------------------------------------------------VII

LIST OF TABLES-------------------------------------------------------------------------------VIII

LIST OF EQUATIONS---------------------------------------------------------------------------IX

LIST OF APPENDIX-------------------------------------------------------------------------------X

CHAPTER ONE INTRODUCTION------------------------------------------------------------1

1.1 overview
1.2Background and Motivation12
1.3Statement of the Problem13
1.4Aim and Objectives14
1.5Significance of the Project14
1.6Project Risks Assessment15
1.7Scope/Project Organization16
CHAPTER 2: LITERATURE REVIEW17
2.1Introduction17
2.1.1Soulcare garden18
2.2Historical Overview18
2.3 Related Work18
2.4Summary19
CHAPTER 3: REQUIREMENTS, ANALYSIS, AND DESIGN20
3.1Overview20
vii
3.1.1Proposed Model20
3.2 Methodology20
3.2.1WaterFall Model21
3.3Requirement Analysis21
3.4Requirements Specifications21
3.4.1Functional Requirement Specifications22
3.4.2Non-Functional Requirement Specifications23
3.5System Design24
3.5.1 Application Architecture24
3.5.2Use Case25
3.5.3Activity Diagrams25
3.5.4User Interface Design27
CHAPTER 4: IMPLEMENTATION AND TESTING28
4.1Overview28
4.2Main Features28
4.3Implementation Problems29
4.4Overcoming Implementation Problems29
4.5User Guide29
4.6Testing31
4.6.1 Test Plans31
4.6.2Test Report Summary33
CHAPTER 5: DISCUSSION, CONCLUSION, AND
RECOMMENDATIONS33
5.1Overview33
5.2Objective Assessment34
5.3Limitations and Challenges34
5.4Future Enhancements34
5.5Recommendations35
5.6Summary35

REFERENCES---------------------------------------------------------------------------------------3

APPENDIX-------------------------------------------------------------------------------------------4

viii
ix
 LIST OF FIGURES

Figure 1Use Case diagram10

Figure 2Activity Diagram11
Figure 1Entity Relationship Diagram12

x
 LIST OF TABLES

Table 1Functional Requirement Specifications7

Table 2Non-Functional Requirement Specifications8

xi
 LIST OF EQUATIONS

CPUCentral Processing Unit

ERDEntity Relationship Diagram
ITInformation Technology
DB Database
UI User Interface
QMS Queue Management System

xii
 CHAPTER ONE

INTRODUCTION

ONE.1 BACKGROUND OF THE STUDY

the world system, Nigeria to be specific, is one of the major country that is

been faced with improper queue management. Queues (or waiting lines) help

facilities or businesses provide service in an orderly fashion. Forming a queue

being a social phenomenon, it is beneficial to the society if it can be managed

so that both the unit that waits and the one that serves get the most benefit

(Shukla and Shrivastar R.K., 2016). Efficient queue management is very

essential anywhere in order to keep the people involved in the system to be on

the move (Ajah, 2017). Queue Management has been an issue for a long time in

many organizations especially in banks and government departments and is

common to places that are overcrowded such as; markets, motor parks, banks,

worship places, recreational centers, school and hotels. Due to the growing

technology nowadays, it is not only important to provide convenience to the

public consumers, but to help the person behind the counters to manage the

existing queue so that the service will be delivered efficiently and effectively

(Rushdi, 2013). The COVID-19 pandemic that has hit the Globe (world) made

it mandatory to consider proper queue management in human daily activities,

organization, sects and so on. As overcrowded places can cause rapid spread of

1
this disease. In the past years of the country WHO declared a public health

emergency of international concern, lots of countries went into a state of

emergency leaving lots of establishment unmanned. In Nigeria today, we

struggle to find resources to control the pandemic which has made the country

to suffer setbacks. Some measures were set in place to control the spread of the

COVID-19 pandemic by implementing social distancing, usage of a nose mask,

and hand sanitizers, In other to manage the current state of the country,

guidelines were given for some businesses to reopen by working short hours,

controlling crowded environments which lead to the poor turnover for some

businesses, especially markets, motor parks, banks, worship places, recreational

centers, and hotels. This project work is focus on reducing the overcrowding

places and aid social distancing by using virtual method to manage queue

effectively. The proposed method uses mobile application software to

implement a Queue Management System. This proposed method also help

service provider sufficiently and manage customers. Queue Management

software gives them the flexibility to help customers analyze the queue status

virtually and the system puts the user in the queue and takes decisions on which

customer to serve first and helps the customer receive appointment updates and

alerts via their mobile devices.

2
1.2 Problem of the statement

In our existing system all the booking of rooms in a hotel are done manually, so

it was more time taking for an executive and customer to book, search rooms

and collect payment in hotel. The need to build up this queue management

system framework through inventive Development tremendously influenced

the progression of this task. This task will plan and execute a reservation

framework dependent on the queue management system. The system should be

able to reserve a customer, initiate a checking for space available to take action

of making a reservation for the customer, if not send notification feedback to

the customer through the application software and email. The expense of the

establishment of any queue management system framework relies upon a few

elements. To start with, the sort of customers wait time being minimize is of

incredible thought the queue management system Provide customers with

clarity into hotel traffic and wait times before they even step foot in your hotel,

by doing so customers can search for the nearest 3 location with the shortest

wait and can check-in virtually online, saving their spot in the queue, or

schedule a future reservation

1.3 Aim and Objective of the study

The aim and the objectives (main function) of the project is;

1. To design and develop a queue management system for Soul Garden Hotel.

3
 2. To analyse the method of Approach used in managing queue at soul care

garden hotel.

3. To design a queue management system for soul care garden hotel

4. To develop and implement queue management system for soul care garden

hotel.

5. To evaluate the performance, the queue management system.

1.4 Motivation

The growing popularity and spread of smart phones and tablets have led to a

change in how computer systems are designed. Technological developments

have also made sure mobile devices are capable of helping in most sectors of

our daily lives. Also the increase in COVID19 cases which has become a

problem for customer service oriented companies Technology is a necessity in

our lives and this project contributed to this factor whereby customers can

receive appointment updates and alerts sent to their phones. We have chosen

the Android Operating System, as it is the most popular, ethical, user-

controlled, operating system and it still is developing.

1.4 Methodology

The project aims at designing an application to minimize the wait times of the

user via an android application using a queue management system. The

application is run on all android devices. The system will require mapping

system, appointment, Customer Feedback, Alerting, identification, and internet

4
 connection. The Hotel Management System will allow remote access to hotel

database only for customer after the authorization procedures. The customer

could search, book rooms and give feedback.

1.5 Significance of the project

The implementation of this project has the potential to benefit the academic

field, the Local Society, Humanity, and the world as a whole. The knowledge

to the academic field by providing safety to people being congested in a place

with the pandemic the world is going through now, so far available solution to

the pandemic is to minimize movement and control crowded areas. This project

is not the first, but has more room for development and each part of the

implementation of the project will be open for more development as technology

advances. The contribution to the academic field is that doing things online

help go back to our daily routine more safely and smartly, the pandemic is just

another opportunity to help build new ways to cope in life. And it will give

highlight for those who may develop interests to make a further study on

similar topics.

1.6Project Risks Assessment

The project's risk assessment describes events that may be hard to control or
slow down the workflow of this project. This section also includes precautions
to be followed in case of such events.
RISKS
1 Inability to carry out research due to loss of hardware/software resources
• Be aware of and observe school IT security procedures
• Secure Android mobile phone when not in use.

5
 2 Loss of work due to equipment failure /loss
• Weekly data backup to H drive and GIT HUB
3 Software availability (Unavailability of API’s)
• Alternative API’s will be checked for. Software requirements will be identified
in good time for possible contentious API’s
4 Late delivery of hardware component
• Hardware requirements will be identified in good time to be able to order them
in good time
5 Exams may halt work progress
• Accelerate workflow in order to finish before on time.

1.7 Scope and limitation of the research

The project, which is in order of queue managing and controlling, is to manage

the queue virtually using android application and sending feedbacks to the

customer. The limitation of this project is the need for language translation and

addition of voice translation for non-educated or unskilled customer.

CHAPTER 2 LITERATURE REVIEW

2.1 Overview

This thesis is comprised of five chapters. The first Chapter provides an

introductory knowledge of the project, as well as its scope and limitations. The

historical background, review of past work and theory of the subject matter

are covered in chapter two, chapter three describes the implementation, and

tests, result and limitation are discussed in chapter four. Finally, a conclusion is

reached in chapter five with recommendations for future work.

6
2.2 Introduction.

This literature review was undertaken mainly to implement the use of Queue

management systems, how they are structured, designed and implemented

in many different organizations and how it can aid in solving queue

management issue facing soul garden hotel (Ndung’u, 2018). To formulate

another method which will proffer a suitable solution using the concept of

queue management system. A queue management system is the organization of

queues of people within a retail or public sector department. It can be either

reactive through a system that can organize the existing queue or proactive

through queue management statistics gathering system, so that the trends can be

identified and anticipated. People that join queue in a standing line queue are

direct to the next position by the system or be given issued with a ticket. With a

ticketed system, customers are took out of the standing line queue, which can

give comfort and less stress for the customers as well as their turns are not

neglect. This queuing environment is an essential part of our daily lives and it

is important for manufacturer to build the most cost-effective queuing solution

(Uddin Md. et al, 2016).

2.3 Review of past works

In controlling queue system many approaches or methods have been used in

managing queue properly. Past works across this subject was

reviewed, to achieve more functionality in the proposed method used in this

7
project work. The past works review is as follows; in research (Ndung’u, 2018)

A virtual queue management system was implemented using web

application programming language (Such as; PHP, HTML, JavaScript, and

CSS), MYSQL database for the webserver running the application,

Wampserver. For web server, Firebase cloud storage for data exchange

between the application and the web server, Android studio (API 7) for

launching the application. The scope of the work is limited to only educated or

skilled personnel’s alone. The research (Ndung’u, 2018) uses Intel Galileo gen-

2, LCD (16*2), PCF8574N, wire jumper for interconnection, trim pot 10k,

DS1307RTC module, Plastic Container, 6*6*1 push button 4pin, screw PCB

stand, Buzzer 6-12V, Resistor 10Kohms to implement an automated queue

management system. This system has three Rules governing its operation,

which are as follows; all service counters are multipurpose type,

service counter only for customer choosing service A, each service has service

counter. The system is restrictive to be able to real-world situations exactly (the

theoretical solution may prove insufficiently informative to be useful). Then

research (Hossain Md., 2011) is a microcontroller based electronic queue

control system, which was implemented using 16F721C, a low-cost 8_bit PIC

microcontroller and entirely and entirely software controlled and these control

programs have been developed using the PIC assembly language. This research

work is not web based, so it requires the customer to be at the location. A smart

8
queue management system for banking sector was designed in research (Jhala,

2012) with a small interface, easily accessible with smart phones for a queue

management with SMS notification. It can be limited by network traffic. The

research (Ngorsed, 2010) implementation of Hospital

Service Queue Management System with wireless approach was made, when

customers, patients and stakeholder can access their queue remotely over the

internet through a web application. In (Alias, 2007) research, a queue

management system was designed and this was controlled by PIC 16F877, push

button, decoder, latch, LED, seven segment, buzzer and voltage regulator

circuit, the operational of this system 8 were programmed using the

basic programing language. The research work (M.E. El-Nagger, 2010)

described a methodology designed to support the decision-making process by

developing seaport infrastructure to meet future demand. In order to determine

an optimum number of berths at a seaport using queuing theory, the optimum

number of berths that minimizes the total port costs can be decided. Then

(Vasumathi.A, 2010) formulated a suitable simulation technique which will

reduce idle time of servers and waiting time of customers for any bank having

ATM facility. The research (S. A. AL-Jumaily, 2011) have presented a new

technique for queuing system called automatic queuing system. The proposed

technique showed improvements in average waiting time. Also (Sundari, 2011)

Have used the highly suitable modeling tool for MMC queueing model, the

9
stochastic Birth-death Markov process and have eliminated the long waiting

hours for customers. The (Patel, 2012) have discussed how queueing theory can

be applied to a busy bank ATM and how the service should be improved so that

the banks do not lose their customers. This research can help bank ATM to

increase its QoS (Quality of Service), by anticipating, if there are many

customers in the queue. The work at (S. K. Dhar, 2013) have discussed the

application of queuing theory to the Bank ATM. This research can help bank

ATM to increase its QoS (Quality of Service), by anticipating, if there are

many customers in the queue. Because the bank can now estimate the number

of customers waits in the queue and the number of customers going away each

day. Then the research (S. Vijay, 2014) recommends changing the present

queuing system to alternate queuing system where the passengers do not need

to wait so long. It was proved that this model of the queuing system is feasible

and the results are effective and practical. Then, the research at (Ahsan, 2015)

have proposed by shifting a server from day to night. From

the performance, measurement of the proposed model the waiting time

decreased expectedly at night shift than day shift. So this model can be used as

an improvement technique for the service of the restaurant. In research we

(Jhala, 2016) have described a methodology designed to support the decision-

making process by the banks to meet the demand. In order to determine an

optimum number of servers, queuing theory is applied. The Waiting and

10
service Costs were determined with a view to determining the optimal service

level.

2.4 Basic features of a queue management system

A. Arrival of customers: It is a process of arrival for customers into the queue

management System. Classification of arrival of customers (Shastrakar,

2016) as Single line or multiple lines, Finite or infinite. Single customer or

customers come in bulk. Arriving customers are totally under control or

partially or no control, Deterministic or Probabilistic process, Empirical or a

Theoretical Probability Distribution, Independent or conditionally dependent

variables, Sometimes arrivals of customers is stationary.

B. Service Discipline: It works on the rule by which customers are selected

from the queue for service. Rules are classified (Shastrakar, 2016) as: i. First-In

First-Out (FIFO) ii. Last-In First out (LIFO) iii. Service for Random Order

(SRO) iv. Priority Service. (PS) In queuing system (Alias, 20070, there are

many types of queue model like SPF (Shortest Processed first), FIFO (First in

First Out), SQ (Single Queue), Multiple Queues, diffuse Queue and Head of

Queue. In (Alias, 2007) SPF, its more often used by the restaurant. SPF more

accurately describes a model where transactions of short expected length are

dealt with sooner (as in a 10 items only queue in a supermarket). SPF can work

well but is problematic if the customers do not perceive the right degree of

fairness from the system. SPF works as (Md. Nasir Uddin et al, 2016)

11
scheduling policy that choose lesser time execution to process first. In a

supermarket, a specific paying counter only process transaction which customer

buying goods less than 10 goods. SPF can work well because of its simplicity

and minimizes the average amount of waiting time for each process. However,

the setback is that it requires long time to complete if short process is

continually add and customers do not perceive the right degree of fairness from

the system. It is important to explain why customers are being serve in that

order and ensure the understanding of customers to see the logic of this

alternative approach. It is necessary to explain why customer are being served

in an order other than simple First in First out (FIFO) and ensure that

consumers understand and see the logic of this alternative approach.11 FIFO is

the model of service provision (Alias, 2007) which is most fairly, where each

customer is served in the order in which they registered for service. In service

models where all customers think of themselves as equal, this model is

important. The single queue is the familiar snake or corral queue format. Each

person waiting is served in turn and the format of the queue discourages

pushing in. It also provides visible reassurance to customers that they will be

served in fairly and that the queue is progressing. For the multiple queues, this

is the format that we have always seen at the supermarkets. Like a number of

individual. Take-a-ticket queue models are example of diffuse queue. There is

no formal queue line but customer register place in the process with a ticket

12
(Mohamad Fazli Bin Alias, 2007). The head of queue, this is the place where

the next person to be served waits in a single queue environment. It’s vital that

they can see along the line of service position to avoid significant gaps in

service provision (Shastrakar, 2016). With more than checkouts, this factor

becomes increasingly significant. In order to maintain fairness in the queuing

system, there are the rules have been set for the Queue Management System

concept: - · Queue must be fair. · Queues must be managed systematically and

not allowed to descend into a free-for-all. · The process must include positive

feedback of progress. · The process must be clearly identified; start

& ends must be visible. · The perception of waiting time should be well

managed.

2.4.1 Advantages of queue management system

In this system (Shastrakar, 2016). it provides many advantages to the customer

service provider and the customer itself. The advantages are –

a) Staffs dealing with customers who have been well treated andget less

stressed and this increases job satisfaction.

b) Staff can serve more customers per hour if those customers are fed to each

counter efficiently. c) Help the management by producing statistical reports on

information such as arrival rates and patterns, waiting and service times, and

default and reneging cases.

d) Enabling managers to monitor and set performance thresholds.

13
e) Customer will be treated with fairness and in more relaxed environment.

f) The queue flow will be smoother and increase the efficiency of queue

management.

C. Nature of Customer As usual it is depending on the nature of arriving

customers whether he is willingly accepted a waiting line or refuses it

(Shastrakar, 2016). If the system is filled up to its capacity, then the arriving

customer is naturally rejected. In some other cases if there is a rejection of the

primary system, the customer accepted secondary system and ‘queue up’ in an

informal waiting line to enter in to the system. We note that there are mainly

four items, which must be specified for any given Queuing System.

i. Balking: If the customer experiences that waiting time are very large as the

queue is moving very slowly, the customers might balk and refuse to join the

queue.

ii. Reneging: After joining the queue customer experience that it will take too

much time to enter the system which is worthless then he customer reneges i.e.

leaves the queue.

iii. Collusion: Several customers may cooperate and only one of them may

stand in the queue to reduce the waiting time and buy the required service.

iv. Jockeying: If there is more number of queues, there is a way for customers

to change the queue, which gives fast service than the other. In this process, the

customer scans the lines forchanging it.

14
 2.4.2 Customer Flow Management

There are few manager (Md. Nasir Uddin et al, 2016) of service provider know

what happens with their customers throughout the whole interaction process in

real-time. If the supply and production managers know the flow of material and

product in detail, why does not the head of operations know the flow of

customers equally well? Is the flow of customers less important than the flow

of material and products? Is the flow of customers more difficult to monitor

and control? By knowing absolutely, the customers are a key success factor for

any service provider that wants to be competitive. Therefore, Customer Flow

Management (CFM) is managing the flow of customers and their experience

from initial contact to final service delivery. The Customer Flow Management

process consist of several phases including pre-arrival, arrival, queuing or

waiting, serving, post serving and managing customer service operation, the

resulting framework for making informed business decisions and the frames the

boundaries of CFM.

i. Pre-arrival CFM can start before the customers physically visits the shop or

service center by implementing a method to book appointments before arrival.

This reduces the time spent waiting by the customer and produces a positive

impact on the customer’s service experience.

15
ii. Arrival Customers need to be place in an appropriate queue on arrival. Customer

Flow Management stresses the possibility of segmenting the customers in

different queues rather than entering all customers in the same queue.

iii. Queuing/waiting: Most customers will endure a period of waiting after queue

entry. A balanced and controlled waiting period is the desired optimum results

of any managers. No one (Md. Uddin et al, 2016) wants to have a completely

empty waiting area as it reflected that you are overstaffed or impression of

abandonment. Equally, too many customers waiting are simply as off-putting.

In the case of a hospital or public service center, certain citizens might not

accept it as they can demonstrate this during elections. CFM can help managers

get the balance rightly by improving staff planning and by adding more

flexibility to the process.

iv. Serving: When calling the customer forward, staff can start preparations if the

service chooses to identify and tracking customer’s history before the customer

actually arrives at the service point.

v. Post-serving After a customer has been serve, a case handling function can

continue to manage the case throughout its lifetime if needed and each step is

document and process. vi. Managing Managers can use the gathered data in

CFM process to evaluate the current processes. Reports can be generating on

employee-customer interactions, service times and customer wait times.

16
Operational inefficiencies can be identified and addressed through process

changes or training.

D. Service mechanism: The service mechanism is worked on the policy decided

for the service facility for the customers who are serviced and leave the service

system. Service mechanism follows single channel-single phase, single

channel-multiphase, multichannel-single phase, and multichannel-multiphase.

F. Eisting Queue Management System There are many products (Md. Nasir

Uddin et al, 2016) available on the market produced by many queue

management Companies for delivering optimum customer service, which are

Stand Alone Queue System and Centralized Control Queue System. i. Stand

Alone Queue System Stand Alone Queue System (SAQS) design based on First

Come First Serve, FCFS queue model, where there is only one service counter

operation. All customers will be managing at the single counter. This system

operates by calling or displaying number in sequential or randomized order and

the customers will be treating fairly. The SAQS is performing well in a single

department, service operation environment such as clinic.

ii. Advance Queue System Advance Queue System (AQS) based on SAQS

design where additional service counters are add to give flexibility in queue

system process. This system can support up to 32 service counters and

additional of 60 counters. It also can provides useful queue features as well as

comprehensive reports. Besides that, it allows manager of real-time monitoring

17
status for the queue management analysis. AQS is performing well in bank,

hospital or any organization that has multiple department service operation.

iii. Centralized Control Queue System Centralized Control Queue System

(CCQS) design is use for higher range of customers in different department.

This system has the capability to support up to 20 departments which each

department can have up to 32 service counters and 60 counters. CCQS is

network compatible because each department has been located at different part

of a building or even in geographical area. Thus, CCQS is connecting through

LAN or Internet and it also provide real-time status monitoring.

2.5. History of waiting lines theory

In Waiting Lines Theory (Shastrakar, 2016) a model is constructed and record

the inter-arrival time of customers and time required service mechanism to

complete the service. In 1909, Agner Krarup Erlang, father of Waiting

Lines Theory, which is also called Queuing Theory, had its beginning in the

research on the Waiting Line Theory. The first developers of Queuing Theory

as applicable to the telephone industry were Tore Olaus and Erlang. Erlang

experimented with fluctuating demand in telephone, traffic, later he published a

report addressing the delays in automatic dialing equipment and its

cost. Further, he was extended to problems that are more generaland to business

applications of the waiting lines. Engset’s formulations were not known until

later because of the delay in publishing and traffic engineers to develop better

18
 systems first used Erlang’s model. Engset’s main work was not in Queuing

Theory and traffic engineering and his contributions are not as well known. The

Danish mathematician, Erlang developed models that accounted for callers that

dropped due to frustration from waiting for an operator and those that were

patient enough to wait for their call to be connected. Erlang

(M/D/1) queuingmodel in 1917 and (M/D/K) queuing model in 1920.

2.5.1 Characteristics of Queuing System

There are six items, which must be specified for any given queuing System.

1. Mean arrival time of customer, 2. Mean service time of server, μ 3.

Customer’s behavior in the system 4. Capacity of the system 5. Number of

service counters 6. The service rate is faster than arrival rate. Classification of

Probabilistic Queuing Models

i. Poisson-Exponential, Single server-Infinite population model

(M/M/1:∞/FCFS)

ii. Poisson-Exponential, Single server-Finite population model (M/M/1:

N/FCFS)

iii. Poisson-Exponential, Multiple server-Infinite population models (M/M/S:

∞/FCFS)

iv. Poisson-Exponential, Multiple server-Finite population model

(M/M/S:N/FCFS) Other Queuing models are:

(i) Poisson Arrivals and Erlang Service Distribution (M/ Ek / 1).

19
(ii) Poisson Arrivals and General Service Time Distribution (M /G/1)

(iii) Poisson Arrivals and Regular Service Time Distribution (M / D/1)

(iv) Constant Arrival Rate and Constant Service Rate (D/ D/1)

2.6 Summary
The literature review in this chapter proved that the implementation of and
integration of QMS is severely underdeveloped. It shows that it is essential to
have management systems present in-order to make this skill acquisition
program more effective and efficient.
Therefore, it is vital to explore techniques that prove to offer an easy to use and
reliable experience. Chapter 3 presents the requirement analysis and the
methodology adopted in solving the problems highlighted in this chapter.

20
 CHAPTER 3: REQUIREMENTS, ANALYSIS,
AND DESIGN
3.1 INTRODUCTION

This chapter details the chosen methodology used in the project, and the

approach chosen for the selected methodology. The tools and techniques used

in the implementation of the project. The ethical considerations of this project

are also observed in this chapter. The requirement analysis and specification

of the project are also clearly stated in this chapter.

3.2 RESEARCH METHODOLOGY

The research methodology is consisting of different stages.

· The first stage involves that how many papers covers different areas

where queuing system is used.

· The second stage is concerned with establishing a classification scheme

described.

· The third stage involves distribution of papers over the years.

Search Strategy Search strategies and screening process follows the

following steps:

Sources of information

21
· IEEE Xplore (http://ieeexplore.ieee.org)

· Science Direct (www.sciencedirect.com)

· ACM Digital Library(www.acm.org/dl)

· WileyInterscience(http://www.interscience.wiley.org/)

· www.ijstr.org

3.3 STUDY SELECTION

The search engine in the above digital database hits quantity of studies, articles.

Research papers posted by using journals, conference complaints and

workshops are concept to be worthy and dependable. Keyword based totally

search is hired to pick out the maximum relevant works. The keywords used

are “Queuing machine”, “Banking”. The criteria used for exclusion of a

research paper consist of unpublished papers, non-English papers, text-books,

Master and Doctoral dissertations, non-peer-reviewed papers. In end result

indicates the distribution of paper from 2000 to 2020. Table 1 suggests the

described search method and variety of results received. From the returned

studies, first beside the point research are excluded on the premise of title.

Certain studies could not be envisioned from the identify, after which their

summary is considered. If even abstract is not obvious then after analyzing the

total textual content of papers, irrelevant research is excluded. In some library

seek when large quantity of studies again then follows a few superior seek.

22
TABLE 3.1 SEARCH SELECTION

S. Exclude

d
no

. E-source Studies returned Keyword used

based on
based on based on
full text
title abstract

1 http://ieeexplore.ieee.org 83 107 4 Queuing system, Banking

2 www.sciencedirect.com 473 1237 5 5 Queuing system, Banking

Queuing system, Banking,

3 http://dl.acm.org 307 298 2 Customer management

4 www.interscience.wiley.com 6 3 1 Queuing system, Banking

Table 3.1 is showing the search selection

3.4 PROPOSED MODEL

23
The software application to be developed will be run on android devices and

can be downloaded through the Google Play Store. As stated before, the main

function of this application is to design a queue management system for a hotel

system. The Hotel queue management application will allow users to have

access to the map location of the nearest branch to them and get the traffic

status of the branch they intend to go with the user of an android smartphone

and an iQueue application. Users will access to Soul care garden hotel through

iQueue.

3.5 METHODOLOGY

The best methodology for the development of this project would be the

waterfall model, Waterfall model is preferable as it has provision for changes

and the changes can be implemented in the maintenance phase. This is because

the waterfall model is simple and easy to understand and use for the developer

and the other users. This model also allows for early design changes and places

emphasis on requirement and design before writing any single line of code

which ensures minimal time wastage and effort in design changes. It is really

easy to use, handle, and best for projects of a such as this one. The waterfall

model consists of seven developmental stages that are executed in a sequential

order, which implies that a preceding stage needs to be completed before

24
moving on to the next phase of development. The figure 3.1 below represents

the waterfall model along with all its seven stages.

Waterfall

Figure 3.1 system Methodology

The seven developmental stages in Waterfall model are:

i. Requirement Gathering and analysis: This phase involved performing a

feasibility study and

ascertaining all possible requirement of the queue management system.

ii. System Design: This phase involves getting specifications, functional and

non-functional requirements of both software and hardware required to develop

the system. This step also involved defining the system architecture.

25
iii. Implementation/Coding: With outcome from system design of the

developed system prototype, the system was developed in small programs

called units, which were pushed to the next stage to be tested.

iv. Integration and Testing: All the units developed in the implementation

were integrated into the system, isolated and fully tested. Once verified to be

working, the entire system was tested to detect any undetected failures or faults.

v. Operation/Deployment of system: Once testing was done, the developed

system was deployed and tested with live customer data.

vi. Maintenance. Maintenance of the developed system was to be done in

continuum to ascertain that all functional and nonfunctional requirements were

reached and any changes to the software and hardware would not affect the

customer environment.

3.5.1 SYSTEM DESIGN

System design is an important part of any system that is worth implementing.

In this section, we shall look into the hardware, functional and non-functional

system requirements, data aspect and process design for the Queue

Management System (QMS).

3.5.2 HARDWARE REQUIREMENTS

Consist of hardware requirements to be met in order to successfully run the

system:

26
 Desktop Computer

To be used for design and development of the system. The computer had these

specifications:

➢ Intel® Core(TM)i3-4000MCPU@ 2.40GHz 2.40GHz

➢ 4.00GB RAM

➢ 500 GB Hard Disk Drive

➢ Windows 10 pro.

Tablet or Smart Phone

It was to be used for registering and login in users on mobile, joining nearby

queues and sending notifications in real time.

3.6 SOFTWARE REQUIREMENTS

To successfully run the system, there are a number of software requirements

had to be met which were:

i. Operating System: Windows 10 Pro versions of OS (x64 bit) was used for

the project work.

ii. Database Management System: A database to store the details of various

room numbers, the available ones and booking space. The following data based

was to be used for the web server and the mobile-based application.

iii. MySQL Database: For the Web server running the application.

iv. Android Ionic: For the running the android application.

v. Laravel: Has been used as a web server.

27
vi. Android Studio: At least API 7 or above.

vii. Programming Languages: PHP, HTML and CSS

The mobile application is written with ionic. Ionic Framework is an open

source UI toolkit for building performant, high-quality mobile using web

technologies such as; HTML, CSS, and JavaScript with integration's for

popular front-end frameworks like Angular, React, and Vue. The mobile

application use API (Restful) as server for a means of communication with

database for storage and exchanging data. That Representational state

transfer API (RESTful) is written with laravel. Laravel is a free, open-source

PHP framework, created by Taylor Otwell and intended for the development of

web applications following the model–view–controller architectural pattern and

based on Symfony.

3.6.1 REQUIREMENT ANALYSIS

A breakdown of the requirements of the mobile application and the

classification of each requirement falls under.

3.6.2 FUNCTIONAL REQUIREMENT SPECIFICATIONS

The functional requirements of a system are the descriptions of what the system

should do the services that it provides and the limitations on its operation.
28
These requirements reflect the needs of customers for a system that serves a

certain purpose such as status check for availability, queue reservation, or

requirement elicitation. Having the functional requirements in mind, we define

use-cases for better guiding the interfaces development from a user perspective

and proceed with a general use-case diagram for the overall picture.

TABLE 3.2:FUNCTIONAL REQUIREMENT SPECIFICATIONS

Table 3.2 is showing the functional requirements of the proposed application,

iQueue. The requirement numbers and descriptions have been shown as

written above.

3.6.3 NON-FUNCTIONAL REQUIREMENT SPECIFICATIONS

A non-functional requirement is a description of how the system should behave

under certain conditions or input from the user.

Non-Function Requirements Non-Function Category

The Queue Management system must be web accessible, and run on the cloud Deployment

The email alert must go out within 5 minutes of the ticket being created or closed Operability

The email must have a reliability of 99.99% that it will be sent out Performance / Reliability

The Queue Management system man must support both English and Hausa interfaces Localization

Table 3.3:Non-Functional Requirement Specifications

29
Req. Description

No.

R-101 When launched, the application shall stay running unless there is an intentional shutdown of the

application or the platform.

R-102 The application will have a Face book, Google account signup by default.

R-103 The application will display a message if the connection to iQueue fails.

R-104 The application will boot within 5 seconds.

R-105 The iQueue will remain on unless the user turns it off.

R-106 The iQueue will boot into a command line and run the queue management process.

Table 3.3 is showing the non-functional requirements of the proposed

application iQueue. The requirement numbers and descriptions have been

shown as written above.

3.7 SYSTEM DESIGN

This system is comprised of three major parts, The Queue Management

System, the Reservation System, and the Search Engine Optimization will

guide you to achieve the reservation and securing you a spot at the hotel and it

gives you feedback which will send out an email with the confirmation that

your reservation has been secured.

3.7.1 SYSTEM/APPLICATION ARTIFACTS

This section shows the various System and Application artifacts used in the

development of this application.

30
3.7.2 APPLICATION ARCHITECTURE

Figure 3.2: Application architecture for Home Page.

The figure above shows a general overview of the application architecture of

the proposed application/system.

3.8 DATABASE DESIGN

TABLES

Users Table as shown in table 3.4 below;

31
Company Table as shown in table 3.5 below;

32
Passwords Reset Table as shown in table 3.6 below;

USE CASE

A Use Case diagram depicts the interaction between the users and the system.

It shows the functions of the system from the user’s point of view and the

various actions the user as the actor carries out.

Figure 3.3: Use case diagram for the proposed system, showing an

interaction between user and system.

Figure 3.4: Activity Diagram for the reservation.

USER INTERFACE DESIGN

Figures 3.6: A first view of the user interface of the Proposed Application.

33
INPUT DESIGN

Login Page

34
Registration account page

35
Booking of room

3.10Summary
In this chapter the requirement analysis and design, functionalities and
requirement gathering techniques used in the design of this system. The Data
was deliberately examined and Requirement Gathering Techniques utilized in
building the system

36
 CHAPTER 4: IMPLEMENTATION AND
TESTING
4.1 INTRODUCTION

This chapter is dedicated to going over the main features of the application
and going through details of its implementation, and Identifying any problems
experienced during the implementation. After problems have been Identified
details on how and why the problems occurred will be provided, as well as
how said problems were overcome. The chapter will also go through the
testing plan by identifying all major components and report on their behavior.
We will also go through the test and error report summary and look at
corrections for those errors. Finally, The user guide will be provided and then
the contents of this chapter will be summarized.
4.2 Testing
Testing is one of the most important parts of a software development life cycle.
It helps to provide verification and validation on whether all of our functional
requirements are met. This is done by generating test data and feeding it to the
application to monitor the behavior. This helps to identify the vulnerabilities
and limitations of our application. If a feature fails to meet expectations, it will
be isolated from other components and examine.
The following sub-chapters go through features to be tested and documents the
performance of each component. A test report will also be provided towards the
end.
4.2.1 Tests Plans (for Unit Testing, Integration Testing, and
System Testing)
Below is the test plan for “QMS”.
1.1 Test Identifier:
TEST LEVEL: Master Test Plan
AUTHOR’S NAME: Zainab Ibrahim izang
AUTHOR’S CONTACT: izangzainab155@gmail.com

37
 4.2.1.2 Features Not To Be Tested

• External APIs
• Internet protocols

4.2.1.3 Approach

by using the built-in debugger for visual studio code, we’ll be able to stop the
app at each breakpoint to examine the app’s data flow. By using the
“console.log” function at the end of each method, we’ll be able to see exactly
what each method is returning.

4.2.1.4 Test Deliverables

The deliverables of this test plan are:

• Test cases
• Test report

• Traceability matrix

• Test results

• Error report

4.3.1 Test Suite (for Unit Testing, Integration Testing, and System
Testing)
Test case TC-001(User Login)
Test Suit ID R-116
Test Case ID TC-001
Test case summary To ensures, users can log in
Related Requirement R-116
Prerequisite The web app must be opened in a browser
Uninterrupted internet connection must be available
Must be a registered
Test Procedure Navigate to the site using URL
login

Test Data User password

Expected Result The user should be logged and navigated to the dashboard
Actual Result The application logged in the user
Status Test case passes
Remarks The test was successful
Created by Zainab Ibrahim izang
Date Created 15 February 2023
Executed by Zainab Ibrahim izang

38
Date of Execution 5 march 2023
th

Test Environment Hardware: DELL Laptop

Software: Browser – google chrome

Table 3.1 Test Suite Performed for Login

Test case TC-003(Logout)

Test Suit ID R-112
Test Case ID TC-002
Test case summary This test case is designed to make sure application logout user
Related Requirement R-112
Prerequisite must be a logged-in user
must be on the user’s dashboard
must click on the log out button
Test Procedure
Login
Click logout
Test Data Logout
Expected Result The user should be logged out redirected to the login page
Actual Result The user is logged out
Status Test case passes
Remarks The test was successful
Created by Zainab Ibrahim izang
Date Created 13th February 2023
Executed by Zainab Ibrahim izang
Date of Execution 14th February 2023
Test Environment Hardware: DELL Laptop
Software: Browser – google chrome
Table 3.2 Test Suite Performed for Login

Test case TC-003(Role-based access control)

Test Suit ID R-113
Test Case ID TC-003

39
Test case This test case ensures that the only the correct user is allowed to access a route
summary

Related R-113
Requirement
Prerequisite The web app must be opened in a browser
Uninterrupted internet connection must be available
Must be a registered
Test Procedure Open sited
Attempt to log in with different user types and observe the behavior

Test Data login

Expected Result The application should only allow the right user access to a particular route and display an alert
for unauthorized users. i.e. users cannot access the admin dashboard
Actual Result An alert was displayed for unauthorized users and denied them access
Status Test case passes
Remarks The test was successful
Created by Zainab Ibrahim izang
Date Created 18th February 2023
Executed by Zainab izang Ibrahim
Date of 18th February 2023
Execution
Test Hardware: DELL Laptop
Environment Software: Browser – google chrome

Table 3.3 Test Suite Performed for role-based authorization

Test case TC-005(find branches)

Test Suit ID R-118
Test Case ID TC-005
Test case summary This test case is designed to make sure new users can find organizations by search

Related Requirement R-118

Prerequisite User must be logged in

User must be on Find organization page

Test Procedure Login

Navigate to find branches page
Type in the state you want to make reservation find your branch closest
Test Data State name
Expected Result The app should filter out organizations from the given state in the search index
Actual Result The app filters out organizations from the given state in the search index

40
Status Test case passes
Remarks The test was successful
Created by Mubarak isah
Date Created 1st of March 2023
Executed by Zainab Ibrahim izang
Date of Execution 21st February 2023
Test Environment Hardware: DELL Laptop
Software: Browser – google chrome

Table 3.4 Test Suite Performed to find organizations

Test case TC-006(Customers/Usersprogress)

Test Suit ID R-119
Test Case ID TC-006
Test case This test case is designed to make sure the application sets the users progress and makes it visible
summary to their supervisor and admin

Related R-119
Requirement
Prerequisite Be logged it
Find branch
Start internship

Test Procedure Login in

Click on start reservation button on the dashboard

Test Data Current date

Expected Result The application should set the user’s start, expected end date, and store it in the database. Then
display it to the authorized users
Actual Result The application sets the user’s start, expected end date, and then store it in the database. Then
display it to the authorized users
Status Test case passes
Remarks The test was successful
Created by Zainab Ibrahim izang
Date Created 5th march 203
Executed by Zainab izang Ibrahim
Date of Execution 24th February 2023
Test Environment Hardware: DELL Laptop
Software: Browser – google chrome

Table 3.5 Test Suite Performed to Users progress

41
 4.3.2 Error Reports and Corrections
• Logical errors and bugs due to coding. This was corrected by revising coded
and changing logic to fit each function.
• Insufficient permissions. This was due to user not being able to read or write
from unauthorized routes. This is good because it shows that the back end did
not allow unauthorized users.
• Runtime error. This was caused because of plugins installed on google chrome.
It was corrected by disabling the plugins

4.4 Use Guide

The user guide provides new users instructions on how to get started and
use the application. Once a new user has signed in, they are expected to set-
up their profile, once that is done, they can now begin their reservation by
navigating to the user dashboard and await further instruction from the
admin. On the admin page, user details can be accessed by clicking on the
displayed user. This then. Expands and reveals several functions that can be
performed by clicking on the particular button. All buttons have a
descriptive label that describes the function it performs.

4.5 DATABASE TESTING

The database systems used in this project are MySQL by Oracle Technologies.

Database testing was done after system development to check whether the

database was able to store the desired data as well as testing its integration with

other components of the system. The developer used various categories of data

to test the integrity of the database. First normal range data was used and the

results were valid after processing. Extreme data was used to test whether the

system could accommodate the extreme ranges. Further, exceptional data was

used to test how the system would respond when subjected to invalid data.
42
Consider the following test data performed on the Users table. The two fields

under test are Email and password.

4.6 Overcoming Implementation Problems

To overcome these problems and constrained the development of this
application, all issues were isolated and examined. Most of the bugs were
fixed by searching online for people who have experienced the same or
similar issues and checking for the solution. If a specific is unique to and
cannot be found, the best thing to do was to post the problem online a
websites’ such as Stack- overflow and Git-hub, then within a few hours,
Developers reply with a possible solution.
To solve the issue of role-based authorization preventing google user, the
documentation for firebase was examined, this revealed a method called
“New User” this returns a Boolean value that allows us to write functions
depending on if it is true or false.

FIELD NAME DATA TYPE TEST DATA RESPONSE COMMENT

FIELD NAME DATA TYPE TEST DATA RESPONSE COMMENT

Email varchar admin@admin.com Accepted Valid

Email varchar Admin.com Rejected Invalid

Email Varchar admin@admin.com Rejected Valid

(email already exists)

Password Varchar Password01 Accepted Valid

Password Varchar #PAssword Rejected Invalid

(Confirmation

Error)

Table4.1 Database testing

4.7 UNIT TESTING

43
Unit involves testing software with a small piece of source code. QMS is built

on top of the Laravel php framework, thus has access to a custom TDD library.

When performing tests, some assertions would be made, and the testing

function would then assert if true or false.

Source code for unit testing were created by the developer as a part of software

development. The following unit tests were performed to ascertain

functionality.

TEST TEST NAME TEST SOFTWARE TEST

CASES DESCRIPTION ENVIRONMENT

(TC#)

TC1 Navigation This test verifies if the user is able to navigate QMS Windows Home

Tests the site and access all Edition, 500GB HDD,

4GB RAM, Apache

URLs in the application. Testing a login Server, PHP Engine, MySQL

scenario Server

44
Figure 4.1-unit test navigation

TC2 Authentication This test verifies the username and password to QMS Windows Home

Tests access QMS Edition, 500GB

HDD,

4GB RAM, Apache

Server, PHP Engine,

MySQL Server

45
FIGURE 4.2-UNIT TEST AUTHENTICATION
INTERFACE TESTING

Interface testing was performed to evaluate if all units of the interface

transferred control to each other. To perform the interface tests, the developer

created a checklist that outlined all the functional requirements of the system

and the various test cases to assess them.

46
 Description

TR01 Create an account for users of the application

TR02 The system services choices for users

TR03 The system shows branches to be selected manually

TR04 The nearest branch is selected manually

TR05 The user generates a queue number

TR06 The system view ticket information

Table4.2Functional requirements

TEST CASES

The table below shows how each of the functional requirements were assessed

using Test Cases.

TEST CASE 1 (TC1)

TEST FUNCTIONAL TEST DESCRIPTION SOFTWARE REQUIREMENT

CASE TEST TEST ENVIRONMENT

TR01 Login and account Verify and authenticate user using QMS Windows Home

create email and password. Edition, 500GB

HDD, 4GB RAM,

Apache Server, PHP

Engine, MySQL

Table 4.3 Test Case 1

47
TEST CASE 2

TEST FUNCTIONAL TEST DESCRIPTION SOFTWARE REQUIREMENT

CASE TEST TEST ENVIRONMENT

TR02 The system The system shows the available QMS Windows Home

services accommodation and their respective Edition, 500GB

functions HDD, 4GB RAM,

Apache Server, PHP

Engine, MySQL Server

Table 4.4 Test Case 2

TEST CASE 3

TEST FUNCTIONAL TEST DESCRIPTION SOFTWARE REQUIREMENT

CASE TEST TEST ENVIRONMENT

TR03 Branches available The system displays the available QMS Windows Home

branches and their location. Edition, 500GB

HDD, 4GB RAM,

Apache Server, PHP

Engine, MySQL

48
 Server.

Table 4.5 Test Case 3

TEST CASE 4

TEST FUNCTIONAL TEST DESCRIPTION SOFTWARE REQUIREMENT

CASE TEST TEST ENVIRONMENT

TR04 Nearest branch The nearest branch is displayed and QMS Windows Home

Location can be selected manually. Edition, 500GB

HDD, 4GB RAM,

Apache Server, PHP

Engine, MySQL Server.

Table 4.6 Test Case 4

TEST CASE 5

TEST FUNCTIONAL TEST DESCRIPTION SOFTWARE REQUIREMENT

CASE TEST TEST ENVIRONMENT

TR05 Generation of a queue The system generate a queue number QMS Windows Home

number and it will be on the ticket or receipt. Edition, 500GB

HDD, 4GB RAM,

Apache Server, PHP

Engine, MySQL Server.

49
Table 4.7 Test Case 5

TEST CASE 6

TEST FUNCTIONAL TEST TEST DESCRIPTION SOFTWARE REQUIREMENT

CASE TEST ENVIRONMENT

TR06 Notification/receipt or After completion or successful QMS Windows Home

ticket information process, the system display ticket or Edition, 500GB

receipt. HDD, 4GB RAM,

Apache Server, PHP

Engine, MySQL

Table 4.8 Test Case 6

4.7.1 USABILITY TESTING

The table below summarized tests that were performed to ascertain the usability

and experience of users while interacting with the system.

Table 4.4 Usability Testing

Element Output

Flow from start to finish Yes

50
Feedback from Actions performed Instant Feedback

Tokens Received Received

Seamless Navigation Yes

Performance Optimal

Failure or crashes None

Runtime error messages None

Slow or delayed loading Acceptable

4.7.2 INTEGRATION TESTING

The purpose of this testing was to check whether the various modules of the
system are well integrated and working harmoniously. All the form modules
were well connected with the database and processing of data was successfully
done. The reports generated outputs successfully as expected from the database
and in the correct formats.
4.8 Summary
This chapter demonstrated in clear detail, the main features of the applications
and describes the techniques used to implement those features. The problems
that occurred during the implementation were also identified and the chapter
went over all of the ways method, which were used to overcome those
problems. The chapter then goes through the test plan, procedures, and
documents the results of those tests. Errors found during the test procedure
were also documented and the corrections for those errors and a user guide
were also provided. The next chapter will discuss the conclusions, reconditions,
and future enhancements.

51
 CHAPTER 5: CONLUSION AND
RECOMMENDATION
5.1Introduction
This chapter is the final chapter of this thesis. In it, we will go over an
objective assessment of the project as a whole in section 5.2. Then discuss the
limitations and challenges faced during the development of this project in
section 5.3. In section 5.4, we will also go over plans for future enhancements
for this project. Finally, recommendations will be made, based on the findings
of this project.
5.2Objective Assessment
This project has gone according to plan, all of its functionalities have been
implemented, and all functional requirements were satisfied. The project is
designed and coded in such a way that any further modifications that are
needed in the future can be easily implemented without affecting the
functionality of the system. By building upon my foundation of object-
oriented programming to develop such apps that solve our immediate issue in
our current environment. This app has the potential to be used by every
university in Nigeria as there is nothing like it that has been built so far in this
country. In addition, it will serve as a benchmark by which everyone who
develops a similar application will be judged.
5.3Limitations and Challenges
During the development process, there was an outbreak of a deadly called
COVID-19, this out-break spread worldwide and was declared as a national
emergency when the first case was recorded in Nigeria. Due to this, a
nationwide lockdown was announced which prevented civilian movements
and the federal government announced that all educational institutions were to
close immediately. Because of this. I and other students were unable to attend
our weekly project assessment classes. This class was valued because it
provided constructive feedback about this project, and also gave
recommendations and ideas on how to solve bugs and errors and ideas on how
to implement certain features. The lockdown also prevented interactions with

52
 other lecturers for outside counsel and opinions. However, communications
with the assigned supervisors continued via formal online interactions like
sending e-mails. Demonstrations of the project were performed by screen
recording the application and providing voice-over narrations.
5.4Future Enhancements
The end of this project does not mark the end of the application’s
developments. Future updates and improvements will be added. The design of
the app will also change over time to fit modern UI design trends.
There are currently plans to deploy the application to mobile users. Ionic and
Angular already provide us with the tools necessary for this. It uses capacitors,
which is a technology that allows us to wrap our web application in its current
state with a mobile frame, and deploy it to both android and iOS users. In
addition, to make the mobile versions of the application run better,
optimizations will be made to allow better native integration, meaning the app
will have access to the device’s components such as the camera and fingerprint
sensor or any other tool provided for biometric authentication.
The app will also be enhanced by adding quality of life improvements such as
more search filters in the admin page, which will help them to sort user data as
the application is used more and more by different departments and gains many
more users.
Plans are also in place to evolve the application so that will allow major project
supervision, as there is no implementation in place for that system. Finally, bug
fixes will be done as real-world users discover them because they are free to
interact with the application is an unexpected way, which can help highlight
unnoticed problems or bugs.

5.5 Recommendations
Based on the findings of this project, it is clear that there is a serious lack of
development in facilitating and automating our systems used for academic
processes with that in mind, the following recommendations are made.
Nigerian universities that have a department dedicated to computer science and
information technology should utilize the skill of staff and students in that
department to provide technology solutions to any and all of the institution's
underlying problem and update current systems to use modern computer
technologies,
Students should also be able to identify issues in their immediate environment
and seize the opportunity to develop meaningful apps for their community.
Developing such a mentality will allow Nigerians to solve our problems one by
one and eventually develop a technologically aided society.
5.6Summary

53
This chapter concluded this project thesis. In it, we were able to give an
objective assessment of the project itself. In addition, discussed limitations and
challenges such as the nationwide lockdown, we discussed plans for future
improvements such as native interactions, mobile app optimizations, and plans
for evolving the application for major project supervision. Finally, we
discussed the author's recommendation for academic institutions and Nigerians.

CONCLUSION

The aim of developing a queue management system for soul care gardens hotel

is to make queue management easy for the organization, as the world is still

suffering from the dilemma of COVID’19 pandemics and other diseases that

involves contact ; this queue management system is to enhance the social

distancing rule set by the government. The system design uses android

application that can be downloaded from play store or link. In the application,

the input of the customers (registration and log in) are being taken, then shows

the customer the available rooms and their prices, then the customer can book

and pay without wasting time, after which the customer will come to the hotel

and claim the room. The system can manage queue smartly without

supervision. The system development was successful, all the interface of the

project is functioning as required and the aim of the project was achieved.

54
REFERENCES

Bank ATM Bhavin Patel, Pravin Bhathawala; Case Study for Queuing Model;
International Journal of Engineering Research and Applications (IJERA) Vol.
2, Issue 5(2012)
Damodharf Shastrakar, Sharad S Pokley, KD Patil, “Literature Review of
Waiting Lines Theory and its Applications in Queuing Model” In proc.
International Journal of Engineering Research and Technology(IJERT)
ISSN;2278-0181(2016).
Dr. Ahmed S. A. AL-Jumaily, Dr. Huda K. T. AL-Jobori; Automatic Queuing
Model for Banking Applications; International Journal of Advanced Computer
Science and Applications, Vol. 2, No. 7, (2011)
M.E. El-Naggar; Application of Queuing Theory to the container terminal at
Alexandria seaport; Journal of Soil Science and Environmental Management;
Volume 1, Issue 4 (2010)
Manoon Ngorsed, Poonphon Suesaowaluk, “Hospital Service Queue
Management System with Wireless Approach” Graduate School of e-learning
in Information Communication Technology Assumption University, Bangkok
Thailand.
Md. Belayat hossain, Md. Nahid Hossain, Md. Enamul Hoque Chowdhury and
Md. Habibur Rehman, “Design and Development of microcontroller-based
Electronic Queue Control System” DUJASE Vol. 2(1) 11-15 JULY 2011.
Md. Manjurul Ahsan, Md. Raisul Islam , Md. Ashikul Alam; Study of Queuing
System of a Busy Restaurant and a Proposed Facilitate Queuing
Md. Nasir uddin, Mm Rashid, Mg Mistafa, Belayat H, Sm Salam, Na Nithe and
DZ ahmed, “Automated Queue Management System” In proc. Global Journal
of Management and Business Research (GJMBR) ISSN; 2249-4588 and print
ISSN; 0975-5853 Vol.16 issue 1 Version 1.0 2016.
Mohamad Fazli Bin Alias, “Queue Management System” Facaulty of
Electrical and Electronic Engineering University Malaysia Pahang. November
2007.

55
Mrs. S.Maragatha Sundari, Dr. S.Srinivasan; M/M/C Queueing Model For
Waiting Time of Customers In Bank Sectors; Int. J. of Mathematical Sciences
and Applications, Vol. 1, No. 3, September (2011)
Ndung’u Michael Ngugi, Josphat karami Mwai, Mwangi Njomo, “Virtual
Queue Management System” In proc. International Journal of social science
and information technology (IJSSI) ISSN; 2412-0294 Vol. 4 issue 5, August
2018.
Nityangini Jhala and Pravin Bhathawala, “Smart Queue Management System
for Banking Sector” In proc. International Journal of Business Management
and Economic Research. ISSN; 2349-2333 Volume 3, Number 1 (2016). Pp.
29-34.
Nityangini Jhala, Pravin Bhathawala; Application Of Queuing Theory In
Banking Sector; IOSR Journal of Mathematics (IOSR-JM); Volume 12, Issue 2
Ver. II (Mar. - Apr. 2016)
S. K. Dhar, Tanzina Rahman; Case Study for Bank ATM Queuing Model;
IOSR Journal of Mathematics; Volume 7, Issue 1 (2013)
S. Vijay Prasad and V. H. Badshah; Alternate queuing system for tatkal
railway reservation system; Advances in Applied Science Research-(2014)
Vasumathi.A, Dhanavanthan P; Application of Simulation Technique in
Queuing Model for ATM Facility; International Journal of Applied
Engineering research, Volume 1, No 3, (2010)

APPENDICES

Appendix A - Project Document

The project documentation for the Design and Development
of a Queue Management System for Soul Care Garden Hotel:
DETAILED PROJECT DOCUMENTATION

Candidate Name: ZAINAB IBRAHIM IZANG

Student Id No: VUG/CSC/19/3380

Soul care App

Design and Development of a Queue Management System for Soul
Care Garden Hotel.
Course of Study: B.Sc. Computer Science

56
Background Study and Objectives
The proposed system is designed as an online solution to the long wait time and
crowd with the pandemic we are facing now. The queue management system
aims help service provider manage their customers efficiently. The system will
be designed to ease customer flow management, which is useful for managers
of the service provider. In addition, help provide the customer with clarity into
hotel traffic and waiting time before leaving their destination. The app was
developed using the waterfall methodology, was successfully tested, and
produced desirable results. Development of the application will continue with
for future update and further enhancements.

Appendix B – Source Codes

import { Component, OnInit } from '@angular/core';

import { HttpClient } from '@angular/common/http';
import { Router } from '@angular/router';
import { AuthService } from './../../services/auth.service';
import { StorageService } from './../../services/storage.service';
import { AuthConstants } from '../../config/auth-constants';
import { ToastService } from './../../services/toast.service';

@Component({
selector: 'app-login',
templateUrl: './login.page.html',
styleUrls: ['./login.page.scss'],
})
export class LoginPage implements OnInit {

public postData = {
email: '',
password: ''
};

constructor(private http: HttpClient, private router: Router, private authService:

AuthService, private storageService: StorageService, private toastService: Toas
tService) { }

ngOnInit() {
}

57
validateInputs() {
let email = this.postData.email.trim();
let password = this.postData.password.trim();
return (
this.postData.email &&
this.postData.password &&
email.length > 0 &&
password.length > 0
);
}

loginAction() {
if (this.validateInputs()) {
this.authService.login(this.postData).subscribe(
(response: any) => {
if (response.user) {
// Storing the User data.
this.storageService.store(AuthConstants.AUTH, response.user);
this.router.navigate(['home']);
} else {
this.toastService.presentToast('incorrect password.');
}
},
(error: any) => {
this.toastService.presentToast('Incorrect credentials.');
}
);
} else {
this.toastService.presentToast('Please complete the information above.');
}
}

58
59
60
61
62
63
64
65