SMART QUEUEING SYSTEM
LAB REPORT
Submitted by
Sresanjai [RA2111026010236]
Lohith[RA2111026010232]
Balakathir [RA2111026010218]
Jephrin [RA2111026010215]
Under the Guidance of
Dr.N.Arivazhagan
Assistant Professor, Department of Computational Intelligence
In partial satisfaction of the requirements for the degree of
BACHELOR OF TECHNOLOGY
in
COMPUTER SCIENCE ENGINEERING
with specialization in Artificial Intelligence & Machine Learning
SCHOOL OF COMPUTING
COLLEGE OF ENGINEERING AND TECHNOLOGY
SRM INSTITUTE OF SCIENCE AND TECHNOLOGY
KATTANKULATHUR - 603203
MAY 2023
COLLEGE OF ENGINEERING &
TECHNOLOGY SRM INSTITUTE OF
SCIENCE & TECHNOLOGY
S.R.M. NAGAR, KATTANKULATHUR – 603 203
CHENGALPATTU DISTRICT
BONAFIDE CERTIFICATE
Register
No.
RA2111026010215
_RA2111026010236,
Certified
to
be
RA2111026010232,
the
bonafide
RA2111026010218,
work
done
by
Sresanjai,Lohith,Balakathir,Jephrin of II Year/IV Sem B.Tech Degree Course in the
Practical Software Software Engineering and Project Management 18CSC206J in
SRM INSTITUTE OF SCIENCE AND TECHNOLOGY,
Kattankulathur during the academic year 2022 – 2023.
FACULTY-INCHARGE
HEAD OF THE DEPARTMENT
Dr.N.Arivazhagan
Dr.R
Assistant Professor Department of Computational
Intelligence
SRM Institute of Science and Technology
Kattankulathur Campus, Chennai
Annie
Uthra
Professor
and
Head,
Department of Computational Intelligence SRM
Institute
of
Science
and
Kattankulathur Campus, Chennai
Technology
TABLE OF CONTENTS
CHAPTER
NO
TITLE
PAGE NO
ABSTRACT
1
1
PROBLEM STATEMENT
1
2
STAKEHOLDERS & PROCESS MODELS
3
3
IDENTIFYING REQUIREMENTS
4
4
PROJECT PLAN & EFFORT
5
5
WORK BREAKDOWN STRUCTURE & RISK
ANALYSIS
6
6
SYSTEM ARCHITECTURE, USE CASE & CLASS
DIAGRAM
8
7
ENTITY RELATIONSHIP DIAGRAM
10
8
DATA FLOW DIAGRAM
11
9
SEQUENCE & COLLABORATION DIAGRAM
12
10
DEVELOPMENT OF TESTING FRAMEWORK/USER
INTERFACE
13
11
TEST CASES & REPORTING
12
ARCHITECTURE/DESIGN/FRAMEWORK/IMPLEMENTATION
CONCLUSION
REFERENCES
13
15
ABSTRACT
The Smart Queueing System is a novel approach to manage queues in a variety of settings such as
retail stores, hospitals, and transportation centers. The system uses sensors and cameras to collect
data on the number of people waiting in line and their behavior, and then analyzes this data to
optimize the queue management process. This includes predicting wait times, determining the most
efficient queue configuration, and dynamically adjusting queue length and wait time thresholds to
ensure a smooth and efficient customer flow. The system also incorporates real-time customer
feedback and integrates with mobile applications to enable customers to join queues remotely and
receive notifications when it is their turn. Overall, the Smart Queueing System has the potential to
improve customer experience, reduce wait times, and increase operational efficiency in various
industries.
Project Description :
A Smart queueing system is one which operates on customizable algorithm integrated with android app.
This takes it is customizable depend on the time and complexity of the Printing shops.
Once the order/query for order is raise the backend operation gets in hand to give the desired output
to save time.
ONE PAGE BUSINESS CASE TEMPLATE
DATE
31-01-2023
SRESANJAI.H.A
SUBMITTED
BY
LOHITH KUMAR . P
BALAKATHIR.S.R
JEPHRIN ESTHER.V
TITLE / ROLE
SMART QUEUEING SYSTEM
THE PROJECT
In bullet points, describe the problem this project aims to solve or the opportunity it aims to develop.
A Smart queueing system is one which operates on customizable algorithm integrated
with android app.
This takes it is customizable depend on the time and complexity of the Printing shops.
Once the order/query for order is raise the backend operation gets in hand to give the
desired output to save time.
THE HISTORY
In bullet points, describe the current situation.
Use of this automation system can benefit1.Printing places of higher Load.
2.High intense area like banks, offices and independent vendors
3.Any other domain with a customized plan can work
LIMITATIONS
List what could prevent the success of the project, such as the need for expensive equipment, bad weather,
lack of special training, etc.
•
•
•
Vendors should provide correct value to make it efficient.
May have some collision error between files . But ,can be corrected.
People without mobile will find it hard to understand the queue.
APPROACH
List what is needed to complete the project.
Ui/Ux
User friendly easy to use interface.
Backend
Servers and client end to end connections.
Algorithm
Customizable algorithm based on preference.
Database
A place holder to store the work for a while
testing
Alpha & Betta testing to get quality assurance.
BENEFITS
In bullet points, list the benefits that this project will bring to the organization.
{$}Convenience
Easy to use app for both Vendor and customers.
{$}Less Disputes
This system will make it wiser for both vendor and buyer
because of algorithmic approach.
{$}Parallel Processing
User can stay in a place and give order/query to make it
working. Simple
Project Title:
Agile Methodology

the Agile methodology is known for its flexibility, whereas Waterfall
is a structured software development methodology.




Waterfall is a Linear Sequential Life Cycle Model, whereas Agile is a
continuous iteration of development and testing in the software
development process.
Agile performs testing concurrently with software development,
whereas in Waterfall methodology, testing comes after the “Build”
phase.
Agile allows changes in project development requirements, whereas
Waterfall has no scope of changing the requirements once the
project development starts.
Comparing the Waterfall methodology vs Agile, which follows an
incremental approach, whereas the Waterfall is a sequential design
process.
Stakeholder
Name
Activity/ Area
/Phase
Interest
Influence
Priority (High/
Medium/ Low)
User
Raising query
High
High
high
Support
Solving queries
High
High
high
Developer
Handles the
efficient
algorithm
high
high
high
Vendors
Setting the
environment to
work
High
high
high
Stakeholder
Interest
Estimated project
Impact
Estimated priority
Owner
Achieves the goals,
increase the sales
High
1
Sponsors
Provides fund for new
venture. And
mentoring support
High
3
Managers
Handles the resources
and act in meaningful
way to run.
HIgh
3
End users
Raising query
High
4
Support
Solving queries
High
5
System Requirements
Android 5.0+
Windows 8+
Functional Requirements
1. Authentication of Users and Clients.
2. Verification of documents Between the processes.
3. Customized input on Both ends for error handling.
4. Synchronization of notification.
5. Raising query and support.
Non-Functional Requirements
1. The Connection between the backend and the client interface should be seamless.
2. Request rate must be less than 2seconds.
3. Must be able to fit the input given by Clients.
4. Should be precise in request and query as it has more potential in peak hours.
Estimated Number of Lines of Code (SLOC) : 2500 SLOC
Effort = a(kLOC)b
Development Time = c(Effort)d
Effort = 2.4(2.5)1.05
= 2.4(2.617)
= 6.281 persons month
Assign Team :
1.
2.
3.
4.
SressanjaiBalakathir
Lohith
Jephrin
PROJECT LEADER
- PROJECT MANAGER
- PROJECT MEMBER
- Project Member
Budget Control :
Dev. Time
= 2.5(6.28)0.38
= 2.5(2.01)
= 5.02 months
Controlling the budget in a Smart queueing system requires careful planning,
monitoring, and management. Here are some key strategies to help you keep
your project within budget:
Develop a detailed budget plan: Before the project begins, develop a detailed
budget plan that outlines all of the costs associated with the project. This plan
should include all project costs, such as software, training, Installation and any
other expenses. The plan should be based on realistic estimates of the costs of
the project and should be periodically reviewed and updated throughout the
project.
Monitor spending: Monitor spending closely throughout the project to ensure
that costs stay within budget. Track spending on a regular basis and compare
actual costs to the budgeted costs to identify any areas where spending is
exceeding the budget. This will enable the project manager to take corrective
action to bring spending back within budget.
Use cost-saving measures: Implement cost-saving measures where possible to
reduce project costs. This may involve negotiating with vendors for better
pricing, using open-source software instead of commercial software, using
cloud-based resources instead of on-premises resources, and minimizing travel
and other expenses.
Manage project scope: Ensure that the project stays within scope and does not
expand beyond the original requirements. Scope creep can cause costs to
increase, so it is important to manage the scope carefully and to avoid adding
unnecessary features or requirements to the project.
Optimize resource utilization: Optimize the utilization of resources, including
labor, equipment, and materials, to ensure that they are being used efficiently
and effectively. This may involve adjusting schedules or shifting resources to
different areas of the project to avoid bottlenecks and delays.
Use project management software: Use project management software to track
spending, manage resources, and monitor progress. This will enable the project
manager to identify potential budget issues before they become significant
problems and to take corrective action to keep costs under control.
Regularly review and adjust the budget: Regularly review and adjust the
budget throughout the project to ensure that it remains accurate and realistic.
This will enable the project manager to make adjustments to the budget as
needed to accommodate changes in project scope, resource requirements, or
other factors.
In summary, controlling the budget in a smart queueing system requires a
proactive and vigilant approach to planning, monitoring, and management. By
developing a detailed budget plan, monitoring spending, using cost-saving
measures, managing project scope, optimizing resource utilization, using
project management software, and regularly reviewing and adjusting the
budget, it is possible to keep costs under control and ensure the success of the
project.
Risk Management
SWOT ANALYSIS:
SWOT analysis is a useful tool for analyzing the strengths, weaknesses,
opportunities, and threats of a product, service, or organization. In the case of
SQS, a SWOT analysis might look like this:
Strengths:
1. Automation: The software can automate many tasks, such as scheduling
maintenance and generating reports, which can save time and reduce errors.
2. Customization: The software can be customized to meet the specific needs of
different users, such as type of algorithms to be used for time efficiency.
3. Data management: The software can store data on maintenance history,
repair costs, and other information that can help users make informed
decisions about queueing system.
4. User-friendly interface: The software can be designed with an intuitive
interface that makes it easy to use, even for people with little technical
knowledge.
Weaknesses:
1. Cost: The software can be expensive to purchase and maintain, which can be
a barrier for small businesses or individual users.
2. Technical issues: The software may have technical glitches, bugs, or
compatibility issues with other software, which can cause frustration and
delays.
3. Dependence on technology: The software relies on technology, such as
computers and internet connectivity, which can be vulnerable to outages or
cybersecurity threats.
Opportunities:
1. Growing market: As more and more people rely on these paper works for
official works, the demand for SQS software is likely to increase.
2. Expansion into related markets: The software could be adapted to other
related markets, such as Schools, Colleges and commercial places.
3. Integration with other software: The software could be integrated with
other software, such as email, chrome extensions to offer a more
comprehensive solution.
10
Threats:
1. Competition: The organization do these with delivery system to
feed peoples need.
2. Rapidly changing technology: The software may become
outdated quickly as new technologies emerge, which could make it
less valuable over time such as online documents.
Cost Estimation:
SYSTEM ARCHITECTURE :
USE CASE DIAGRAM :
CLASS DIAGRAM :
ER Diagram of University Database
DFD Level 0
DFD Level 1
Sequence Diagram
Collaboration Diagram
Executive Summary
The interface framework contains the functional modules which is been tested manually with the
user test. The covers the basic functions such as login, uploading documents, queuing with smart
meter. It aims to solve both the basic problem of queue and tested.
Test Plan
Scope of Testing
Functional: Customization of algorithm for smart queueing, uploading documents, notification,
printing process.
Non-Functional: verification, speeding the range of operation, User authentication.
Types of Testing, Methodology, Tools
Category
Methodology
Tools Required
Functional
Requirements
Manual
Word Template
Non Functional
analytics
Crash analytics
requirements
Test Case
Functional Test Cases
Test Test Scenario
ID
(#)
Test Case
Execution Steps
Expected
Outcome
Actual
Outcome
Status
Remarks
1.
Verify User
Registration
from India
Accept
Valid India
Mobile
Number on
the Page#1
1. User clicks on
User
Registration
link
User should
be taken to
the next
page for
entering
more user
details.
Next
screen
showing
the follow
up status
Pass /fail
Success
2.
Uploading
documents of
specified size
Don’t
Accept size
larger than
threshold
value.
1.Uploads the
document.
Successfully
uploaded
Shows the
message
uploaded.
Pass/fail
success
3.
Checking
Oauth must 1.The client
authentication be verified request is done.
to give
2.server
access
authorizes the
token.
Success/failed
success
1. verified
verified
successfully.
2. wrong
token.
3. token is
checked.
4.
File format
Allowed file
type(pdf,
docx, jpg)
5.
notify
Users is
notified
when
process
done.
1. Checks the
format of
file.
2.verifies the
type.
1.checks the
progress is done.
2.notifes both the
vendor&
customer.
Format
accepted.
accepted
Accepted/failed Accepted.
Notification
message
sent
Message
sent
Message not
sent/message
sent
Message
sent.
6.
Algorithm
triggers
Algorithm
button just
call the
methods.
1.trigger is
invoked.
Options are
displayed
Options
Options/error
options
Rectified
2.calls the
methods.
7.
Reverting
error
Reverts the 1.files is sent
error
2. printed with
caused in
error due to
processinig.
customers error.
Error is
rectified
rectified
Error is
rectified/error
8.
Payment
gateway
Testing the
api’s to
contact
banks.
1.api’s integrated.
Payment
success.
paid
Paid/error
paid
contact support
queueing
Testing the
smart
queue
based on
vendors
input.
1.finding best
algorithm to
queue.
Pick your
docs in
some x
time.
Order
ready
Order
ready/still
optimizing
Testing the
standard of
format
generate
by using
ready
made
formats
option.
.1relevant format
is choosed.
Document
is ready.
Document Document
ready/error in
ready
format
9.
10.
Ready made
formats
2.checking
connection with
banks.
2.orderdly
contacting.
Optimizing.
Ready to
pint
2.selection of
mode of output
Non-Functional Test Cases
Test Test
ID
Scenario
(#)
1.
Load
test(file)
Test Case
Execution
Steps
Expected
Outcome
Actual
Outcome
Status
Remarks
Testing the
load it can
accept in file.
Uploading
the files
excessively.
Limit exceeded
Limit
exceeded
Error/limit
exceeded
error
2.
Load
Testing the
test(request) no of request
the system
can handle
Spamming
the server
with fake
requests.
Reached max
limit try after
some time.
error
3.
Security test
testing the
loopholes on
data loss.
4.
Crash test
Testing on
Dumping the
the occasion resources.
of limits the
system
malfunctions.
Reverse
engineering
the system
Irregular data
Irregular
Erased/maintained Maintained.
data in
document.
5.
Algorithm
optimization
Testing the
correctness
of
optimization
Crashed/normal crashed
functioning
Manually
Optimized/not
calculating
optimized
complexities.
optimized
Error/system at
peak
error
Handles crash and
reports
Reports
Optimized/error in
calculations
Error in
calculations.
Category
Progress Against Plan
Status
Functional Testing
Green
Completed
Non-Functional Testing
Amber
In progress
Functional
Test Case Coverage
(%)
Status
Module ID
70%
Completed
Loginpage#1
Code Implementation:
CONCLUSION:
The smart queueing system allows us to book time slot and
ignore the queues so that we better use the time (parallel)
which gives us flexible time to convenience using a android
app from both consumer and vendor side.
REFERENCE:
1. https://www.jetir.org/view?paper=JETIR2005325
2. https://en.wikipedia.org/wiki/Queue_management_syst
em
3. https://www.qmatic.com/resources/queuemanagement-system
4. https://www.qmatic.com/resources/queuemanagement-system
5. https://www.bufferbloat.net/projects/cerowrt/wiki/Sm
art_Queue_Management/