Final Report Hall Management Module
Final Report Hall Management Module
Final Report Hall Management Module
Prepared By
Supervised By
January, 2024
CONTENTS
List of Figures iv
List of Tables v
Abstract vi
1 Introduction 1
1.1 Introduction: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.5 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.6 Organization of the Report . . . . . . . . . . . . . . . . . . . . . . . . 6
2 Related Works 7
2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Related Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3 Requirement Analysis 10
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.2 Feasibility Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.2.1 Technical Feasibility . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.2 Economic Feasibility . . . . . . . . . . . . . . . . . . . . . . . 11
3.2.3 Operational Feasibility . . . . . . . . . . . . . . . . . . . . . . 11
i
3.3 Requirement Specifications: . . . . . . . . . . . . . . . . . . . . . . . 12
3.3.1 Functional System Requirements : . . . . . . . . . . . . . . . . 12
3.3.2 Requirement Specifications for User Module: . . . . . . . . . . 14
3.3.3 Non-Functional System Requirements: . . . . . . . . . . . . . 15
3.4 Tools and Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.5 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4 Methodology 19
4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.2 Entity Relationship (ER) Model . . . . . . . . . . . . . . . . . . . . . 20
4.3 Use Case Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.4 Activity Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.5 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.6 Software Development Model Selection . . . . . . . . . . . . . . . . . 26
4.6.1 The Agile software development methodology . . . . . . . . . 27
4.7 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.7.1 Backend Integration . . . . . . . . . . . . . . . . . . . . . . . 28
4.7.2 Software Architecture . . . . . . . . . . . . . . . . . . . . . . 28
4.8 Proposed Methodology for Implementing the Hall Management Module 29
ii
5.2.8 Application From Student . . . . . . . . . . . . . . . . . . . . 40
5.2.9 Hall Super Dashboard . . . . . . . . . . . . . . . . . . . . . . 41
5.2.10 Hall Super Profile . . . . . . . . . . . . . . . . . . . . . . . . . 42
5.2.11 Student List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.2.12 Application List . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.2.13 Create Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.3 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6 Conclusion 47
6.1 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6.2 Limitations: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
6.3 Future Works: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
References 50
iii
LIST OF FIGURES
iv
LIST OF TABLES
v
ABSTRACT
vi
CHAPTER 1
INTRODUCTION
1.1 Introduction:
In today’s rapidly evolving digital landscape, the concept of a smart campus has emerged
as a trans formative solution for educational institutions. A smart campus represents a
vision where technology seamlessly integrates into every aspect of university life, revo-
lutionizing operations and experiences for students, faculty, and staff. This introduction
outlines the vision of a fully automated, cashless, and paperless smart campus, present-
ing a future where the entire university is automated and at the forefront of innovation.
This report focuses on Hall Management module which is imperative to create the
Smart Campus project as many other modules. This project has dependencies on two
sub modules which are student modules and administrative modules.
The Hall Management module is the main module which has the automated function
of providing the residential accommodation of an student. It also manages the hall
capacity, dinning and canteen and other co-curricular activities. It provides the full
information about an hall including of other stuffs and administrative persons. It is
controlled by three types of users, those are student, hall super which plays the role of
an admin and the university authority which plays the role of an super admin.
Student Module is one of the base modules which facilitates users which can be stu-
dents. Without this module students can’t use the automated accommodation facilities.
It uses an algorithm which can generate an list and the hall super can verified it.
Users through the Admin module of this project can control and manages the student
through his/her hall.
1
Figure 1.1: Hall Management Module Overview
1.2 Background
2
to errors, delays, and inconsistencies. This has led to a range of challenges, including
scheduling conflicts, inefficient resource allocation, and difficulties in accessing up-to-
date information.
Recognizing the need for a more efficient and streamlined approach, the Smart Cam-
pus project aims to introduce a digital solution to automate these processes. By lever-
aging modern technology, the project intends to replace manual methods with a mobile
application that can centralize and streamline the management of academic activities
and services at HSTU.
The development of the Smart Campus application involves many modules which
will bring together the whole project And Hall Management Module which enhances
the convenience of getting the residential facilities for students and gives the efficient
control in seat management directly to the university authority.
1.3 Motivation
The motivation for developing a hall management module for a university can stem
from several factors, including:
• Enhanced Security and Safety: With features such as access control, emer-
gency response management, and visitor tracking, the module can help ensure
3
the security and safety of residents, providing peace of mind for both students
and university staff.
• Scalability and Flexibility: As universities grow and evolve, they need scal-
able and flexible systems to accommodate changing needs and requirements. A
modular hall management system can be customized and expanded to meet the
evolving needs of the university and its residential community.
Overall, the motivation for developing a hall management module is to improve opera-
tional efficiency, enhance the student experience, ensure safety and security, and support
data-driven decision-making within the university’s residential community.
The management of university residential halls poses numerous challenges that require
efficient and effective solutions. Currently, many universities rely on manual processes
and outdated systems to handle tasks such as room assignments, billing, maintenance
requests, and security management. These manual processes are time-consuming, error-
prone, and often result in inefficiencies that impact both administrators and residents.
Furthermore, communication between hall administrators, resident advisors, and
students is often fragmented, leading to delays in addressing issues and resolving con-
cerns. Additionally, ensuring the safety and security of residents, as well as compliance
with regulatory requirements and university policies, presents significant challenges
without proper systems in place.
The HMM aims to automate and optimize processes related to room assignments,
reservations, billing, maintenance requests, and communication. It should also include
4
robust security and access control features to ensure the safety of residents and compli-
ance with regulations. By centralizing data and providing real-time access to relevant
information, the HMM will enable administrators to make informed decisions, improve
efficiency, enhance the student experience, and ensure the overall well-being of the
university’s residential community.
In summary, the Hall Management Module seeks to solve these problems by pro-
viding a streamlined, integrated system that enhances efficiency, communication, and
safety for both administrators and residents.
1.5 Objectives
5
tasks, maintenance inefficiencies, and security breaches through the implementa-
tion of automated processes and improved resource allocation.
• Chapter 3 encapsulates the requirement analysis and gave an step by step walk
through of the our work in details.
6
CHAPTER 2
RELATED WORKS
2.1 Introduction
In [5], they present Octopus, an Open Source, dynamically extensible system that
supports information management for internet of things applications in which its ar-
chitecture is based on web services.
Another interesting work [2], uses an ubiquitous computing platform based on NFC,
where these devices and applications interact with each other to provide an intelligent
environment.
In [11], they use an architecture with three layers; sensing, data storage and analyt-
ics. They focus on the classroom attendance, student study space usage, parking lot
occupancy and bus-stop waiting-times.
A framework is proposed in [9], that involves (a) smart people -support staffs, aca-
7
demic staffs and students-; (b) big data analytics; (c) smart classroom -smart band,
smart board and blended learning- and smart faculty -e-learning, automated building
management and smart attendance-. They mention that there are a lot of benefits in be-
coming a smart university, such as increasing the education quality, the research output
by implementing the right analysis and understanding lots of information through the
use of big data, improved ranking and performance.
In this study [1], a daily analysis of internet traffic is carried out, in addition, four
learning approaches were used to analyze and compare the collected information, how-
ever, they don’t mention any architecture for the treatment of that data.
In [6], they consider the self-learning property as a basic constitutive feature of a
smart university and validate mathematically this criteria, in addition, they consider
the smart university as a self-learning organization functioning on the basis of a team of
like-minded people that has an established mechanism, such as: learning ability, relation
convergence, the transfer and increase of knowledge, meeting the society requirements,
adapting promptly to contemporary economic conditions.
In [7], they developed and tested models of defining a smart university infrastruc-
ture development level, taking into account some indices of assessment like: the use of
smart platforms, smart technologies, smart knowledge management systems, the teach-
ing staff using smart technologies, the use of mobile devices during the learning process
and the use of the e-learning tools.
Another study [8], shows the technologies that are implemented in smart campuses
and smart universities which are: big data, cloud computing, internet of things and arti-
ficial intelligence. They indicate by “Smart campus” four thematic axes: infra-structure,
governance and management, services and education; and for “smart uni-versity” high-
lights the development of an architecture that contributes to the active application of
smart technologies and devices in the educational process.
In [10], they propose a system architecture for smart universities that provides smart
building monitoring and management. The proposed a solution that integrates hetero-
geneous geographically disparate sensor networks and devices and enables optimal op-
8
erations of the building while reducing its energy footprint.
In [3], they propose the concept of Smart University describing needs and ad-
vantages and ending with a possible architecture based on smart objects.
2.3 Conclusion
In conclusion, the reviewed studies highlight the growing interest and adoption of
technology-driven solutions in the academic sector, specifically in the context of smart
campuses and universities. These works demonstrate the potential of web services,
and smart objects to transform various aspects of academic management, infrastruc-
ture development, teaching and learning processes, and student services. By leveraging
these advancements, institutions can achieve improved efficiency, enhanced student ex-
periences, and optimized resource utilization. As the field continues to evolve, further
research and innovation in smart campus technologies are expected to drive continuous
improvements in academic environments
9
CHAPTER 3
REQUIREMENT ANALYSIS
3.1 Introduction
Requirement analysis for the Hall Management Module (HMM) involves a comprehen-
sive process of gathering, documenting, and prioritizing the needs and expectations of
stakeholders to ensure the effective design and implementation of the system. Engaging
with university administrators, residential staff, students, and IT personnel, the analy-
sis aims to understand overarching goals, operational challenges, and user preferences
related to residential hall management. Through interviews, surveys, workshops, and
prototyping, requirements are elicited and documented in a clear, structured format,
ensuring that they are well-defined and traceable to stakeholder needs. Stakeholder in-
put is prioritized using techniques such as MoSCoW analysis, guiding decision-making
and resource allocation. Validation of requirements through reviews and walkthroughs
ensures alignment with project objectives and stakeholder expectations. Ultimately,
thorough requirement analysis lays the foundation for the successful development of
the HMM, ensuring that it meets the diverse needs of stakeholders and contributes to
the efficiency, accountability, and satisfaction of residential hall management at the uni-
versity.
The feasibility study assesses whether it is viable to proceed with a more detailed anal-
ysis of the project.
10
3.2.1 Technical Feasibility
• The necessary software and hardware tools required for developing our web ap-
plication are readily available.
• All group members possess personal computers with sufficient processing power,
eliminating the need for additional hardware investment.
• Development costs for our web application were manageable due to the absence
of economic barriers.
• Our web application is compatible with various devices such as desktop PCs,
laptops, Android phones, iOS phones, and tablets, ensuring accessibility for a
wide range of users.
• Operating our system is user-friendly and intuitive, requiring only basic knowl-
edge of navigating websites.
• During the development process, we prioritized user interface and user experi-
ence, resulting in an easily understandable interface that allows users to quickly
find and utilize the system’s features.
By conducting this feasibility study, we have determined that the project is techni-
cally feasible, economically viable, and operationally feasible.
11
3.3 Requirement Specifications:
The functional system requirements for the “Hall Management System” are derived
from the analysis of users’ needs and expectations. These requirements define the spe-
cific features and functionalities that the system should possess to effectively manage
hall operations. The following functional system requirements have been identified:
• Super-admin: The role of super admin will be to assign and manage admins
i. e. hall super and other hall administration employees.
• Student: Students are the main user of this system. So the system should
provide all the academic and administrative services that are associated with
the hall.
2. Room Allocation: The system should automate the room allocation process
based on predefined criteria, considering factors such as student preferences, eli-
gibility, and availability of rooms. It should allocate rooms fairly and efficiently,
minimizing conflicts and manual intervention.
There are mainly 2 operation under this section-
12
availability of seats in that hall.
3. Room Availability: The system should provide a room application system where
students can view real-time room availability. It should display room and seat
details including the students staying in those seats which will facilitate informed
decision-making and verifying the students.
5. Canteen and dining related activities: There should be a scope to manage hall
dining automatically. Services like ordering food, advance token collection. Also
seeing and selecting the menu will be covered under this section.
7. Other services and rostering: There are many other services provided by hall
administration like hall cleaning and repairing, duty roster of employees and dis-
tribution of resources. There should also be medical services available for the
students and facilities to handle emergency health issues.
13
messaging functionalities. Many services would need to be handled according
to their current status and it should be maintained in this section. There will be
some services for the students
• Complain box
• Send feedback
1. User Registration: The system should allow the super-admin to create user ac-
counts and provide credentials to students, faculty, and staff. User registration
will be done by the super-admin, and users will be given their credentials to ac-
cess the smart campus system.
2. User Profiles: Each user should have a profile that includes their personal in-
formation, contact details, and role (student, faculty, staff). The system should
provide functionality for the super-admin to create and manage user profiles.
14
3. Role-based Access Control: The system should differentiate user roles (stu-
dents, faculty, staff) and provide role-based access control. Only authorized users
with administrative privileges (super-admin) should have the ability to create,
edit, or delete user profiles.
1. Security:
• User data should be securely stored and transmitted using encryption tech-
niques.
2. Performance:
• User data should be securely stored and transmitted using encryption tech-
niques.
3. Scalability:
5. Compatibility: The web application should be compatible with major web browsers
and device platforms, ensuring consistent performance and functionality across
different environments.
15
6. Maintenance and Support:
These requirements serve as a foundation for the development of the “Hall Man-
agement System”, addressing both functional and non-functional aspects to meet the
needs of users and ensure a reliable and efficient system.
16
3.4 Tools and Technologies
17
3.5 Conclusion
After conducting a thorough requirement analysis and selecting appropriate tools for
development, it becomes evident that the Hall Management Module (HMM) is a criti-
cal solution for addressing the challenges and inefficiencies associated with managing
university residential halls. By streamlining administrative processes, enhancing com-
munication, ensuring safety and security, and enabling data-driven decision-making,
the HMM offers significant benefits to both administrators and residents. Through the
selection of suitable tools and technologies, such as database management systems,
web development frameworks, and security protocols, the project team can ensure the
scalability, reliability, and security of the HMM. Furthermore, leveraging modern devel-
opment methodologies, such as Agile or DevOps, can facilitate iterative development,
rapid prototyping, and continuous improvement throughout the project lifecycle.
18
CHAPTER 4
METHODOLOGY
4.1 Introduction
The methodology section of the project report plays a pivotal role in delineating the
chosen approach and techniques harnessed to achieve the project’s multifaceted objec-
tives. It serves as a comprehensive blueprint for the development and implementation
of the Hall management module. The methodology encompasses an array of intricate
facets, spanning both the backend and frontend considerations, which collectively en-
sure a seamless and efficient system.
In the realm of backend considerations, the methodology delves into the nitty-gritty
of database design, outlining the schema, tables, and relationships necessary to encap-
sulate the project’s diverse modules. This meticulous design is not only fundamental
for data integrity but also instrumental for the efficient retrieval and storage of critical
information.
Moreover, the methodology extends to file structure, which is pivotal for the orga-
nization and management of project files and resources. A well-thought-out structure
ensures that code, assets, and documentation are readily accessible and maintainable.
Routing within the frontend is meticulously addressed. It designs a user-friendly
and intuitive path for users to navigate through the web application. The routing system
channels users to relevant pages based on their interactions, enhancing user experience
and ensuring they can easily access the functionalities they require.
API integration, another critical element, is detailed within the methodology. This
aspect focuses on the seamless integration of APIs into the frontend, enabling a dynamic
19
connection between the user interface and the backend, fostering the flow of real-time
data.
In summation, the methodology offers an intricate and systematic approach to the
development, integration, and management of the technical aspects of this project.
The ER model uses a collection of entities and relationships among these entities. An
Entity is an object in the real world that is distinguishable from other objects. The ER
diagram of the Hall management module is shown in figure 4.1.
20
4.3 Use Case Diagram
A use case diagram is used to represent the dynamic behavior of a system. It encap-
sulates the system’s functionality by incorporating use cases, actors, and their relation-
ships. It models the tasks, services, and functions required by a system/subsystem of an
application. In this project, Teacher, Student, Super-Admin can perform different tasks
which is described by use case diagram. Use case diagram of the Hall Management
Module is shown in figure 4.2 below:
The sequence diagram represents the flow of messages in the system and is also termed
as an event diagram. It helps in envisioning several dynamic scenarios.Left view of
Activity diagram of the Hall Management Module are shown in figure 4.3 below:
21
Figure 4.3: Activity Diagram(Left view)
22
Right view of Activity diagram of the Hall Management Module are shown in figure
4.4 below:
23
4.5 Data Flow Diagram
The sequence diagram represents the flow of data in the system. It helps in envisioning
data inflows and outflows. Data Flow diagram of Smart Campus System are shown in
figure 4.5, figure 4.6, figure 4.7 below:
24
• Data Flow Diagram for Student
25
• Data Flow Diagram for Admin
The Hall Management Module follows the Agile Model. This allows for the incremen-
tal addition and modification of features over time to adapt to evolving requirements
and user needs.
26
4.6.1 The Agile software development methodology
emerged in the late 1990s as a response to the limitations of traditional plan-driven ap-
proaches. Agile methods aim to deliver software rapidly and accommodate changing
requirements. It is rooted in the Incremental development approach to software devel-
opment. In Fig 4.8 Agile methodology is described. [4]
27
4.7 System Architecture
Database Design
In the Hall Mangement Module, the database schema is created by determining the
required tables, establishing relationships between them, and defining attributes and
constraints. The use of NoSQL schema called MongoDB.
State Management
Effective state management is vital for the synchronization and maintenance of data
across various frontend components. It entails overseeing the application’s state, en-
compassing factors like user authentication status, data sourced from the backend, and
the states of UI components. By adopting suitable CCS frameworks like Tailwind, de-
velopers can ensure the consistency and dependability of the application’s state.
The backend file structure in the Hall Management Module adheres to a monolithic ar-
chitecture, where all backend components and modules are consolidated within a single
repository. This streamlined structure simplifies the development, deployment, and up-
keep processes by housing all backend-related code, including database schemas, API
endpoints, and business logic, in one centralized location. It promotes seamless collab-
oration among backend developers and ensures the overall coherence and reliability of
the backend system.
28
Frontend File Structure
The file structure of the frontend may differ depending on the selected frontend frame-
work or library. Nonetheless, it typically consists of directories for organizing compo-
nents, routes, styles, and assets. This structured approach facilitates the management of
a modular and scalable frontend codebase, enhancing navigation, comprehension, and
extensibility of the frontend application.
Module
• Identify the areas where technology can be leveraged to enhance the Hall
Management Module.
• Engage with students, staff, and hall supers to gather insights and align the
hall management module with their needs and expectations, fostering inclu-
sively within the project.
29
management at HSTU, reducing reliance on manual processes and improv-
ing efficiency.
• Create a detailed implementation plan that outlines the steps, timeline, and
resources required for each goal.
• Consider any dependencies or potential risks that may arise during the im-
plementation and develop contingency plans.
• Assess and enhance the existing infrastructure to support the User and Hall
Management Module.
• Research and evaluate technology solutions that align with the identified
goals and objectives.
30
6. Implement and Test of the User and Module Registry Module system
• Involve key stakeholders and users in the testing process to gather feedback
and address any usability or functionality issues.
31
CHAPTER 5
RESULT AND DISCUSSION
5.1 Introduction
The Results and Discussion section offers a comprehensive assessment and evaluation
of the outcomes and findings derived from the implementation and utilization of the Hall
management module. This chapter aims to present and interpret the results obtained,
encompassing the system’s performance, functionality, user feedback, and its overall
impact on Academic activities and residence management at HSTU.
The chapter initiates by providing an overview of the project objectives and the
employed methodology for the implementation, setting the stage for the subsequent
analysis and discussion of the results. The results are presented in a well-structured and
coherent manner, encompassing both quantitative and qualitative findings.
The discussion segment critically examines the results, extracting meaningful in-
sights and implications for the Hall management module and its stakeholders. It ex-
plores the strengths, weaknesses, opportunities, and challenges identified during the
evaluation process. Furthermore, the discussion compares the achieved results against
the initial project objectives, identifying any gaps or areas that warrant improvement.
32
5.2 Overview of Hall Management Module
33
5.2.2 Halls of HSTU
The ”Halls” page of Hajee Mohammad Danesh Science and Technology University
(HSTU) serves as a centralized hub of information for the university’s residential halls.
It provides residents, prospective students, and stakeholders with essential details about
each hall, fostering transparency, accessibility, and engagement within the university
community. It is shown in figure 5.2 in detail
34
5.2.3 Home Page of a Hall
The ”Home of a Hall” page begins with a brief overview of the residential halls, high-
lighting their significance within the university community.This includes details such as
the hall’s name, location on campus, capacity, and special features.he page highlights
upcoming events, programs, and activities organized within the residential halls.It is
shown in figure 5.3 in detail
35
5.2.4 Sign Up Page
The ”sign-up” page in the Hall Management Module (HMM) facilitates the registration
process for new users, offering flexibility to select their user type based on their role
within the university community. Upon accessing the sign-up page, users are prompted
to provide their personal information, including their ID, email address, and a password
for account security. How it is shown in figure 5.4 in detail.
36
5.2.5 Login Page
The ”login” page for the Hall Management Module describes a secure entry point for
authorized super admin, admin and normal users. By entering their unique credentials,
such as a email and password, the all types of user can authenticate their identity and
gain access to the features and functionalities specific to their role. This login page pri-
oritizes security and confidentiality, ensuring that only authorized super admin users can
access and manage user accounts, define role-based access controls, and perform other
administrative tasks within the User Module. How it is shown in figure 5.5 in detail.
37
5.2.6 Student Dashboard
The ”Student Dashboard” of the Hall management module.It shows the basic profile
which includes image,contacts,address,notifications and Application.It contains pro-
file,application,and logout options. How it works is shown in figure 5.6 in detail.
38
5.2.7 Student Profile
The ”Profile” page in the Hall Management Module shows his information which is
stored in Student database.Student have the permission to edit some of their personal in-
formation.A student haven’t any permission to edit their name,student id,result,department,date
of birth etc. How it works is shown in figure 5.7 in detail.
39
5.2.8 Application From Student
The ”Application” page in the Hall Management Module allows student to apply for
residence and clearance purpose.Student can able to track their application via this page.
How it works is shown in figure 5.8
40
5.2.9 Hall Super Dashboard
The ”Hall Super Dashboard” page of the Hall management module.It shows the basic
profile which includes image,contacts,address,notifications and Application.It contains
profile,application list,student list and logout options. How it works is shown in figure
5.9 in detail.
41
5.2.10 Hall Super Profile
The ”Profile” page in the Hall Management Module shows his information which is
stored in teacher database.Hall super have the permission to edit some of their personal
information. How it works is shown in figure 5.10 in detail.
42
5.2.11 Student List
The ”All Students” page of the Hall management module shows the table of residential
student in that hall.The table also shows the department of the student.Hall super can
able to add and remove the a student from the list and the respective student is given or
lost their residential status in that hall. How it works is shown in figure 5.11 in detail.
43
5.2.12 Application List
The ”Application List” page of the Hall management module.It shows a table of list
which includes application serial,name,studentId,purpose,department and Action. Hall
super can see the applications and approved or reject from this section. How it works is
shown in figure 5.12 in detail.
44
5.2.13 Create Notice
The ”Create Notice” page of the Hall management module.It shows a form which in-
cludes the notice title,description and date. Hall super can be able to fillup this form
and create a notice for everyone to this respective hall. How it works is shown in figure
5.13 in detail.
45
5.3 Conclusion
46
CHAPTER 6
CONCLUSION
6.1 Conclusion
In conclusion, the Hall Management Module collectively fortified the academic ecosys-
tem at HSTU. This module have addressed critical needs within the institution, enhanc-
ing efficiency and convenience for both administrators and students.
The Hall management module have accomplished the vital goal of establishing role-
based access control, enabling precise management of user access to different sub mod-
ules. This role-based access control mechanism ensures that only authorized users,
including administrators and Superadmins, have the privilege to create, modify, or re-
move data. Such a system bolsters security and streamlines the user experience, deliv-
ering tailored access to specific features and services.
The User Module’s user profile management capability has facilitated the creation
and maintenance of detailed user profiles, encompassing personal information, contact
details, and designated roles. This enhancement has led to elevated user engagement
and personalized services within the full system.
Simultaneously, By automating tasks such as room assignments, billing, mainte-
nance requests, and emergency response, the Hall Management Module significantly
reduces manual workload and increases operational efficiency. Its integrated commu-
nication features foster transparent and timely interaction between administrators, res-
ident advisors, and students, facilitating prompt resolution of issues and enhancing the
residential experience.
As we move forward, it is imperative to continue monitoring, evaluating, and en-
47
hancing all the sub modules to ensure they remain attuned to the evolving needs of
users and the institution. Stakeholder feedback, which includes students, staff, and
transportation personnel, should be harnessed to drive further improvements, optimize
functionalities, and elevate the overall user experience.
By capitalizing on the capabilities of this modules, the Smart Campus project at
HSTU is poised to continually enhance its services, streamline administrative processes,
and provide an enriched and tailored experience for all users, ultimately reshaping the
educational landscape within the institution.
6.2 Limitations:
• Lack of Data: Implementing the dinning and stipend feature of the HMM require
field data from the hall authority. Collection of process in real time this services
48
can be implemented and served by this module
• Room Management: Creating different database for the room, the admin could
be able to manage student in a room.
• Dinning Facilities: Add this sub module for automation in dinning system will
help to students and hall stuff in managing.
• Stipend: Student will able to see his stipend in his/her account ,when we inte-
grated this project with the university account database.
Despite these limitations, addressing them through proactive measures such as robust
training programs, stringent security protocols, ongoing user support, and regular sys-
tem updates can help maximize the effectiveness and benefits of the Hall Management
Module for the university and its residential community.
49
REFERENCES
[1] A. I. Adekitan, J. Abolade, and O. Shobayo. Data mining approach for predicting
the daily internet data traffic of a smart university. Journal of Big Data, 6:1–23,
2019.
[3] M. Caţă. Smart university, a new concept in the internet of things. In 2015 14th
RoEduNet international conference-networking in education and research (RoE-
duNet NER), pages 195–197. IEEE, 2015.
50
[7] Y. S. Mitrofanova, A. A. Sherstobitova, and O. A. Filippova. Modeling the assess-
ment of definition of a smart university infrastructure development level. In Smart
Education and e-Learning 2019, pages 573–582. Springer, 2019.
51