1.
Introduction
1.1. Overview of the system
The software is to design and develop a web-page for managing front office
operations, enabling website administrators to efficiently manage visitor and
student information.
This system allows administrators to add and edit visitor details, record
late-arriving students' information including name, department, entry time,
and date.
Additionally, it provides the ability to generate printable reports filtered by
specific
date and time, streamlining front office operations and enhancing
data management.
1.2. Problem definition and objective
The existing front office management process is manual, time-consuming,
and prone to errors, leading to inefficiencies in managing visitor and student
information. The lack of a centralized system hinders data accessibility,
reporting, and decision-making, ultimately affecting the overall productivity
and effectiveness of the front office operations.
Objective
1. To design and develop a web-based Front Office Management System to
automate and streamline visitor and student information management.
2. To improve data accuracy, security, and accessibility for authorized
personnel.
3. To enhance reporting capabilities, enabling administrators to generate
printable reports filtered by specific date and time.
4. To provide real-time updates and notifications for late-arriving students.
5. To develop a user-friendly interface for easy data entry, editing, and
retrievals
6. To ensure scalability and adaptability for future expansion and
integration with other systems
2. Requirement and Analysis
2.1. Problem definition
Manual front office processes are inefficient, error-prone, and lack
centralized
data management, hindering productivity, accuracy, and informed decision-
making.
2.2. Select the software development model.
Agile model
Page 1 of 7
2.3. Requirement specification includes existing system and proposed
system
Existing system:
The existing system for managing front office operations and student
attendance
is primarily manual and lacks integration, leading to various challenges
2.3.1. Justification of the proposed system
The proposed online front office management system and student late
attendance system are justified based on several key factors that
address the limitations of the existing system and provide significant benefits to
the organization.
2.3.2. Benefits of the proposed system
The proposed online front office management system and student late
attendance system offer a range of benefits that enhance operational efficiency,
improve user experience, and provide valuable insights.
2.4. Project Planning
Primary Goal: To develop a software system to manage the front office operations (such as
check-ins, visitors details, students late attendace) efficiently.
Secondary Goal: To allow front office staff to streamline their daily tasks, reducing manual
workload and errors.
Task Breakdown (Work Breakdown Structure - WBS):
Requirement Gathering: Define system features, user roles (admin), and
requirements.
System Design: Database schema, UI wireframes, system architecture.
Development:
o Frontend Development: Build responsive interfaces using HTML, CSS,
JavaScript.
o Backend Development: Create business logic in PHP, JavaScript
o Database Development: Set up database (MySQL) for storing data.
Testing: Unit and integration testing of individual components.
2.5. Project Scheduling Mon
P
Milestones: S
Milestone 1 (End of Week 2): System design finalized with a clear w
architecture and wireframes. g
Milestone 2 (End of Week 4): Backend and frontend components o
integrated, core functionalities ready. t
Milestone 3 (End of Week 6): Testing complete, all components are
functioning as expected.
Milestone 4 (End of Week 7): Project report and user manual completed.
Page 2 of 7
Regular feedback sessions with project guide to ensure moving in the func
right direction. requ
Fron
Man
Sys
will
vari
task
rese
che
che
and
imp
and
fron
ope
3.1
The
Man
Sys
dev
man
app
rese
2.6. Feasibility Study deta
[Link] Feasibility: gen
Technologies: The project will use familiar and widely supported The
technologies, such as HTML, CSS, JavaScript for the frontend, prim
PHP/JavaScript for the backend, and MySQL for database management. for
These technologies are accessible, easy to learn, and well-documented, suc
making the project technically feasible. hos
Development Environment: IDEs like Visual Studio Code are sufficient, offic
and have access to resources such as laptops and internet connectivity. offic
criti
[Link] Feasibility:
The system will simplify the front office operations by automating the 3.1
processes of , guest management, and reporting. End-users (front office
staff) will find the system easy to use due to its intuitive interface and
logical workflow.
Operational feasibility is high because the project addresses actual
needs of front office management, such as reducing errors and
increasing efficiency.
· S
Req
Spe
3. Software Requirement Specification (SRS) · U
3.1 Introduction · D
Man
3.1.1 Purpose
The purpose of this document is to specify the functional and non-
Page 3 of 7
· CRUD: Create, Read, Update, Delete operations. R
· Admin: The user responsible for managing the system and staff. a
t
D
f
t
3.D
D
G
s
e
a
3.1.4 References o
W3Schools. (2023). HTML, CSS, and JavaScript Documentation. m
Retrieved from [Link]. a
MySQL. (2023). MySQL Database Documentation. Oracle Corporation. r
Retrieved from [Link]/doc/. E
A
3.1.5 Overview
e
The Front Office Management System is a web-based application f
designed to streamline and automate the day-to-day operations of a front E
office. It aims to replace traditional manual processes with a digital a
system that manages guest reservations, check-ins, check-outs, d
invoicing, and reporting.
3.2 Overall description
3.2.1 Product perspective
The system is a standalone web application, accessible via browser, with
a backend database to store and manage guest, student data. It is built
with HTML, CSS, JavaScript for the frontend, and PHP for the backend,
using MySQL for data storage.
Key Features:
Invoice: Generate and track invoices.
Reporting: Create guest and students reports.
The system is designed for easy use with minimal training required.
3.2.2 Product functions
1. Visitor Management:
Visitor Registration: Allows front office staff to add visitor details at
the college gate, including name, purpose of visit, and time of
entry.
Invoice Generation: Automatically generates and prints invoices for
visitors based on their details and duration of stay.
2. Attendance Management:
Late Attendance Marking: Enables staff to mark students who
arrive late to class, capturing relevant details such as name, date,
and time of arrival.
Page 4 of 7
A
R
m
e
u
a
i
[Link]
Con
d
a
f
f
b
s
e
u
3.2
Ass
3.2.3 User characteristics 1.U
Admin Users:
Role: System administrators responsible for managing the overall
system.
Characteristics:
o Familiar with technical aspects of the system.
o Capable of managing user accounts and roles.
o Responsible for generating reports and overseeing operations.
o Must ensure data integrity and security.
[Link]
3.2.4 Constraints Con
[Link] Constraints:
Compatibility: The system must be compatible with various web
browsers (e.g., Chrome, Firefox, Safari) to ensure accessibility for
all users.
Internet Dependency: The application requires a stable internet
connection for access; limited connectivity may affect usability.
Database Management: The system is constrained by the
capabilities of the chosen database (MySQL) in handling
concurrent users and data volume.
[Link] Constraints: [Link]
Data Protection: The system must comply with data protection Res
regulations to ensure the privacy and security of user information.
Page 5 of 7
It is assumed that sufficient hardware resources (servers, computers)
will be available to host the application and support user operations.
Dep
[Link]
S
[Link]
3.3 S
f
r
e
t
3.3
1.U
(UI)
T
i
r
a
c
b
C
Page 6 of 7
The UI should offer different views based on user roles (admin, teacher,
etc...), ensuring a experience for each role.
[Link] Interface:
The system must communicate efficiently with the backend database
(MySQL) to store and retrieve information related to visitor entries,
attendance records, and user data.
The interface should allow real-time data retrieval to ensure up-to-date
information for reports and analysis.
[Link]/SMS Interface:
The system must be able to send email or SMS notifications to the
department heads (HODs) and other stakeholders regarding student
attendance or visitor details.
3.3.2 Functional requirements
3.3.3 Performance requirements
Page 7 of 7
3.3.4 Logical database requirements
3.3.5 Design constraints
3.3.6 Software system attributes
3.3.7 Organizing the specific
requirements
3.3.8 Additional comments
4. Software and hardware requirements
5. System Design
5.1. Introduction
5.2. Output design
5.3. Input design
5.4. E R Diagram
5.5. Database design
5.6. Module Description
5.7. Data Flow Diagram
6. System Development
6.1. Process Description
6.2 Source code
7. System Implementation
7.1. Testing
7.2. System Implementation
7.3. Security
8. Conclusion
9. Appendix
9.1. Sample input screens and outputs
screens
9.2 . Reports
10. Bibliography
Page 8 of 7
Page 9 of 7