Final OHD
Final OHD
Final OHD
Submitted by
ASWIN G
(Reg.No.2122K0507)
MARCH - 2023
Department of Computer Science
KPR COLLEGE OF ARTS SCIENCE AND RESEARCH
(Affiliated to the Bharathiar University, Coimbatore)
CERTIFICATE
This is to certify that this project report entitled
ONLINE HELP DESK FOR CAMPUS FACILITIES
Is a Bonafide record of project work done by
ASWIN G
(Reg. No. 2122K0507)
In a deep sense of gratitude, I express my most sincere thanks to our beloved Principal
Dr. P. GEETHA, KPR College of Arts Science and Research, Coimbatore and the
management of my college for providing all the necessary facilities to carry out this project.
ASWIN G
CERTIFICATE ii
ACKNOWLEDGEMENT iii
1. INTRODUCTION 2
3. SYSTEM DESIGN 13
3.1 File design 13
3.2 Input Design 14
3.3 Output Design 15
3.4 Database Design 16
3.5 System Development 18
6. CONCLUSION 26
BIBLIOGRAPHY 28
APPENDICES
The objective of this web application is to provide a convenient and efficient way for users to
calculate their daily calorie needs and body fat percentage. The application consists of two
main pages: "calories.html" and "method7.html". The "calories.html" page contains a form
where users can input their weight, height, age, fat percentage, and activity level. The form
uses the "POST" method to send the user inputs to the server, which then calculates the daily
calorie needs based on the user inputs and sends the result back to the user. The
"method7.html" page contains a table with body fat classifications for both women and men.
It also includes a form with input fields for the user's weight, height, age, fat percentage, and
activity level. When the user submits the form, the application calculates the body fat
percentage using the Jackson/Pollock 7 Caliper Method and displays the result on the page.
The web application is designed to be user-friendly and accessible, using the Bootstrap
framework for styling and layout purposes. The application uses JavaScript to perform the
calculations and manage the form inputs. The use of a web-based application allows users to
access the system from any device with an internet connection, making it a convenient tool
for tracking fitness and diet goals.
Overall, the web application aims to improve health and wellness management for users by
providing a centralized location for calculating daily calorie needs and body fat percentage. The
system offers a range of benefits, including improved accuracy, convenience, and efficiency, and
has the potential to be a valuable tool for fitness enthusiasts and health professionals.
The Online Helpdesk for Facilities in the College Campus project is a web-based application
designed to streamline the process of submitting and tracking facility-related requests within
the campus community. The system provides a centralized location for reporting issues and
submitting requests for a variety of facilities, including classrooms, laboratories, residence
halls, dining facilities, and more.
The project aims to address the current challenges faced by students, faculty, and staff in
reporting and tracking facility-related issues on campus. Often, these requests are submitted
through various channels, including email, phone calls, and in-person visits, which can result
in delays and a lack of accountability. The Online Helpdesk for Facilities in the College
Campus project offers a comprehensive solution to these challenges by providing a user-
friendly interface for submitting and tracking requests, and by offering a range of features
that enhance the user experience.
The system is designed to be easily accessible and user-friendly for all members of the
campus community, including students, faculty, and staff. The project is built using PHP
programming language and MySQL database management system to ensure that the system
is scalable, secure, and reliable. The system features a simple and intuitive user interface that
allows users to submit requests quickly and easily and provides real-time updates on the
status of their requests.
Overall, the Online Helpdesk for Facilities in the College Campus project aims to improve
facilities management and enhance the overall campus experience for students, faculty, and
staff by providing a centralized location for reporting and tracking facility-related issues. The
system offers a range of benefits, including improved communication, accountability, and
efficiency, and has the potential to be a valuable tool for facilities management teams and
campus administrators.
Mayugam InfoTech is the leading global supplier of quality solutions for advanced software
development and we hold certain commitments, to achieve the benchmark status of a global
provider of high-quality IT solutions and products. By providing integrated best-of- breed
solutions and professional excellence for the end-to-end software development life cycle,
Mayugam InfoTech enables organizations to improve quality and predictability, while
reducing time- to market and overall cost.
Our team provides knowledge and expertise in training and implementation, project
management, prototyping and product development to ensure optimal usage of our products
and efficient development of our customers' applications. Our solutions and experts enable
companies to work faster, cheaper, and smarter. Our professionals are highly skilled at
implementing our products and solutions, integrating and resolving technical issues as they
arise.
"We shall deliver information technology products and services that meet the needs of our
clients and achieve the highest level of customer satisfaction."
"To provide expert solutions for integrating people and technology, and to ensure our clients
success by arming them with powerful, intelligent, superior analytical applications and
products, comprising our technology solutions and services"
Front - End
HTML
Hypertext Markup Language (HTML) is the standard markup language for creating
web pages and web applications. With Cascading Style Sheets (CSS) and JavaScript it forms
a triad of cornerstone technologies for the World Wide Web.
Web browsers receive HTML documents from a web server or from local storage and
render them into multimedia web pages. HTML describes the structure of a web page
semantically and originally included cues for the appearance of the document.
HTML elements are the building blocks of HTML pages. With HTML constructs,
images and other objects, such as interactive forms, may be embedded into the rendered page.
It provides a means to create structured documents by denoting structural semantics for text
such as headings, paragraphs, lists, links, quotes and other items. HTML elements are
delineated by tags, written using angle brackets. Tags such as <img /> and <input />
introduce content into the page directly. Others such as <p>...</p> surround and provide
information about document text and may include other tags as sub-elements. Browsers do
not display the HTML tags but use them to interpret the content of the page.
HTML can embed programs written in a scripting language such as JavaScript which
affect the behavior and content of web pages. Inclusion of CSS defines the look and layout of
content. Designed to be usable by all Open Web developers, this reference page links to
numerous resources about HTML5 technologies, classified into several groups based on their
function.
CSS is the language for describing the presentation of Web pages, including colors,
layout, and fonts. It allows one to adapt the presentation to different types of devices, such as
large screens, small screens, or printers. The separation of HTML from CSS makes it easier
to maintain sites, share style sheets across pages, and tailor pages to different environments.
This is referred to as the separation of structure from presentation.
CSS is used to define styles for your web pages, including the design, layout and
variations in display for different devices and screen sizes. The style definitions are normally
saved in external .css files. With an external style sheet file, you can change the look of an
entire website by changing just one file.
Bootstrap is a free and open-source front-end web framework for designing websites
and web applications. It contains HTML- and CSS-based design templates for typography,
forms, buttons, navigation and other interface components, as well as optional JavaScript
extensions. Unlike many web frameworks, it concerns itself with front-end development only.
Server-side Scripting
PHP
PHP is a general-purpose scripting language that is especially suited to server-side
web development, in which case PHP generally runs on a web server. Any PHP code in a
requested file is executed by the PHP runtime, usually to create dynamic web page content
or dynamic images used on websites or elsewhere.
PHP code may be embedded into HTML or HTML5 markup, or it can be used in
combination with various web template systems, web content management systems and
web frameworks. PHP code is usually processed by a PHP interpreter implemented as a
module in the web server or as a Common Gateway Interface (CGI) executable. The web
server software combines the results of the interpreted and executed PHP code, which may
be any type of data, including images, with the generated web page. PHP code may also
be executed with a command-line interface (CLI) and can be used to implement
standalone graphical applications. PHP has been widely ported and can be deployed on
most web servers on almost every operating system and platform, free of charge.
2.1.1 DRAWBACKS
Lack of centralized location: There is no centralized location for reporting facility-related
issues on campus, leading to confusion among users and delays in addressing requests.
Lack of transparency: The current system lacks transparency, as users cannot easily track
the progress of their requests, and there is no way to ensure accountability for staff members
responsible for addressing facility-related issues.
Manual processes: The existing system relies heavily on manual processes, including data
entry and tracking, which can result in delays, errors, and inefficiencies.
Limited communication channels: The current system only provides limited
communication channels, such as phone calls and email, which can make it difficult for users
to report issues quickly and efficiently.
Inefficient response times: Due to the lack of a centralized location and inefficient manual
processes, response times to facility-related issues can be slow, leading to frustration among
users and potential safety hazards on campus.
The proposed system streamlines the process of submitting and managing requests and
ensures that requests are assigned to the appropriate Facilities Management Personnel for
prompt resolution. Users can submit requests through an online form, providing details such
as the location of the facility, the type of issue, and the urgency of the request. The system
then assigns the request to the appropriate Facilities Management Personnel based on the type
of request and the location of the facility. Facilities Management Personnel can update the
status of requests as they are resolved or escalated, and the system notifies Students and
Faculty/Staff of the progress of their requests and any updates or resolutions.
2.2.1 FEATURES
User registration and login: The system will require users to register and log in before
submitting requests.
Request submission: Users will be able to submit requests for facilities through an online
form. The form will include fields for the user's contact information, the type of facility issue,
the location of the issue, and a description of the problem.
Notification system: Once a request has been submitted, the system will automatically notify
the appropriate department or staff member responsible for handling the issue.
Status tracking: Users will be able to track the status of their requests through the system.
They will receive notifications when the issue has been resolved or if additional information
is needed.
Reporting and analytics: The system will include reporting and analytics features that will
allow administrators to track the number and types of requests submitted, as well as the
response time and resolution rate.
System design is the phase that bridges the gap between the problem domain and the existing
system in a manageable way. This phase focuses on the solution domain, i.e. “how to
implement?”
It is the phase where the SRS document is converted into a format that can be implemented
and decides how the system will operate.
In this phase, the complex activity of system development is divided into several smaller sub-
activities, which coordinate with each other to achieve the main objective of system
development.
● Statement of work
● Requirement determination plan
● Current situation analysis
● Proposed system requirements including a conceptual data model, modified DFDs,
and Metadata (data about data).
The input design is the link between the information system and the user. It comprises the
developing specification and procedures for data preparation and those steps are necessary to
put transaction data in to a usable form for processing can be achieved by inspecting the
computer to read data from a written or printed document or it can occur by having people
keying the data directly into the system. The design of input focuses on controlling the
amount of input required, controlling the errors, avoiding delay, avoiding extra steps and
keeping the process simple. The input is designed in such a way so that it provides security
and ease of use with retaining privacy. Input Design considered the following things:
Input Design is the process of converting a user-oriented description of the input into a
computer-based system. This design is important to avoid errors in the data input process and
show the correct direction to the management for getting correct information from the
computerized system.
It is achieved by creating user-friendly screens for the data entry to handle large volumes of
data. The goal of designing input is to make data entry easier and to be free from errors. The
data entry screen is designed in such a way that all the data can be performed. It also provides
record viewing facilities.
A quality output is one, which meets the requirements of the end user and presents the
information clearly. In any system results of processing are communicated to the users and to
other systems through outputs. In output design it is determined how the information is to be
displaced for immediate need and also the hard copy output. It is the most important and
direct source of information to the user. Efficient and intelligent output design improves the
system’s relationship to help user decision-making.
1. Designing computer output should proceed in an organized, well thought out manner; the
right output must be developed while ensuring that each output element is designed so that
people will find the system can use easily and effectively. When analysis design computer
output, they should Identify the specific output that is needed to meet the requirements.
3. Create document, report, or other formats that contain information produced by the system.
The output form of an information system should accomplish one or more of the following
objectives.
Database design is the process of producing a detailed data model of database. This data
model contains all the needed logical and physical design choices and physical storage
parameters needed to generate a design in a data definition language, which can then be used
to create a database. A fully attributed data model contains detailed attributes for each entity.
The term database design can be used to describe many different parts of the design of an
overall database system. Principally, and most correctly, it can be thought of as the logical
design of the base data structures used to store the data. In the relational model these are
the tables and views. In an object database the entities and relationships map directly to
object classes and named relationships. However, the term database design could also be used
to apply to the overall process of designing, not just the base data structures, but also the
forms and queries used as part of the overall database application within the database
management system (DBMS).
The process of doing database design generally consists of a number of steps which will be
carried out by the database designer.
A large database defined as a single relation may result in data duplication. This
repetition of data may result in:
So, to handle these problems, we should analyse and decompose the relations with
redundant data into smaller, simpler, and well-structured relations that are satisfy desirable
properties. Normalization is a process of decomposing the relations into relations with fewer
attributes.
The main reason for normalizing the relations is removing these anomalies. Failure to
eliminate anomalies leads to data redundancy and can cause data integrity and other problems
as the database grows. Normalization consists of a series of guidelines that helps to guide you
in creating a good database structure.
Insertion Anomaly: Insertion Anomaly refers to when one cannot insert a new tuple
into a relationship due to lack of data.
Deletion Anomaly: The delete anomaly refers to the situation where the deletion of
data results in the unintended loss of some other important data.
Updatation Anomaly: The update anomaly is when an update of a single data value
requires multiple rows of data to be updated.
User Registration and Login: Users will be able to create an account and log in to
the system using their credentials.
Request Submission: Users will be able to submit requests related to the facilities in
the campus. The requests can be categorized based on the type of facility (e.g.,
classrooms, laboratories, restrooms, etc.), urgency, and priority.
Status Tracking: Users will be able to track the status of their requests and receive
updates on the progress of their requests.
Notification: Users will receive notifications via email when there are updates on
their requests.
Communication: Users will be able to communicate with the relevant personnel (e.g.,
maintenance staff, custodians, security personnel, etc.) regarding their requests.
Reports: The system will generate reports that provide an overview of the requests
raised, the status of the requests, the response time, and other relevant metrics.
The purpose of system testing is to identify and correct errors in the candidate system.
Testing is done to achieve the system goal. Testing is vital to the parts of the system are
correct; the goal will be successfully achieved. Inadequate testing or non-testing leads to
errors that may not appear until months later. The various types of testing done on the system
are:
⮚ Unit Testing
⮚ Integration Testing
⮚ Validation Testing
⮚ Quality Assurance
UNIT TESTING
INTEGRATION TESTING
Programs are invariably related to one another and interact in the total system. Each
program is tested to see whether it conforms to related programs in the system. Each portion
of the system is tested against the entire module with both the test data and the live data
before the entire system is tested as a whole.
VALIDATION TESTING
The validation testing is performed for all the data in the system. The data are
completely validated according to the companies request and requirement. The function or
performance characteristics confirming specification is uncovered and an efficiency list is
created.
● The Project is tested completely and various errors found are rectified.
● Security is maintained by providing a separate login for the users.
● Duplication of records are not allowed.
● Various validations are performed to ensure that important data are not missed.
● Testing is performed with some sample inputs from the company and the output is verified
and found right.
To follow the concept of white box testing we have tested each form. I have created
independently to verify that Data flow is correct, all conditions are exercised to check their
validity, all loops are executed on their boundaries.
The term black box indicates that the internal implementation of the program being executed
is not examined by the tester. Boundary value analysis is a technique of black box testing in
which input values at the boundaries of the input domain are tested. It has been widely
recognized that input values at the extreme ends of, and just outside of, input domains tend
to cause errors in system functionality.
Implementation is the stage in the project where the theoretical design is turned into a
working system. The most crucial stage is achieving a successful new system and giving a
user confidence that the new system will work efficiently and effectively in the
implementation stage. The stage consists of
IMPLEMENTATION PROCEDURES
In conclusion, the Online Help Desk system for facilities in college campuses is a web-based
platform designed to improve the maintenance and management of facilities in a college
campus. The system aims to provide a convenient and efficient way for students and faculty
members to submit maintenance requests and track their status.
The system was designed and developed using PHP programming language, MySQL
database management system, and HTML/CSS for the user interface. The proposed system
addressed the limitations of the existing system, which involved manual submission of
maintenance requests and lacked a centralized system for tracking requests.
Through the implementation of the proposed system, we were able to achieve the following
objectives:
The testing and implementation of the system showed that it was reliable and efficient in
improving the maintenance process. Future implementation of the system could involve the
integration of a mobile application for ease of access and notification. Overall, the proposed
system is a significant improvement over the existing system, providing a more convenient
and efficient way of managing facilities on a college campus.
In the future, there are several ways in which this system could be further developed and
enhanced. Some possible areas for future implementation include:
1. Mobile App: Developing a mobile app for the system would allow users to submit
and track requests on the go, and would provide greater flexibility and convenience.
2. Integration with Campus Services: Integrating the system with other campus services
such as maintenance, security, and IT support would provide a more comprehensive
solution for managing campus-related requests.
3. Data Analytics: Adding data analytics functionality to the system would allow
administrators to identify patterns and trends in request data, which could help to
improve facilities management and planning.
Overall, the Online Helpdesk for Facilities in the College Campus project has the potential to
be an invaluable tool for improving facilities management and enhancing the overall campus
experience for students, faculty, and staff.
Data flow diagram is a structured analysis tool for showing the movement of data
through the different transformations or processes in the system. Named bubbles show the
processes and data named arrows, entering or leaving the bubbles, represent flows. A
rectangle represents a source or sinks and is a net originator or consumer of data. A source or
sink is typically outside the main system study. DFD can be hierarchically organized which
helps in partitioning and analysing the large system, such systems are called levelled DFD’s.
For the hierarchy to be consistent it is important that net input or output of a DFD for a
process are the same input and output of the process in the higher level DFD. The refinement
stops until each bubble is atomic.
The data flow diagram may be used to represent a system or software at any level of
abstraction. In fact, DFD may be partitioned into levels that represent increasing information
flow and functional detail. A level 0 DFD is called a Context Level DFD. This model
represents the entire software element as a single bubble with input and output data indicated
by incoming and outgoing arrows respectively.
DFD is a Graphical representation of the flow data through an information system, modeling
in DFD primary steps creates an overview of the system.
Types of DFD
1) Physical DFD
An information dependent view of the current system showing what the data’s are
carried out and how they are performed.
2) Logical DFD
Entity
An Entity is the source of data the source in a DFD represents, these entities that are
outside the content of the system. Entities are representing rectangles.
Process
The process is the manipulation or work that transforms data, performing computation,
making decisions.
Data Store
A data store is a process that stores data between processors for lateral retrieval by the
same process.
DB
Data Flow
It’s a moment of data between the entity process and datastore. Data Flow is an interface
between the components of the DFD. It’s represented by an arrow.
LEVEL 1
<!DOCTYPE html>
<html lang="en">
<head>
<style>
/* config.css */
:root {
--baseColor: #606468;
}
/* helpers/align.css */
.align
{ display:
grid;
place-items: center;
}
.grid {
inline-size: 90%;
margin-inline: auto;
max-inline-size: 20rem;
}
/* helpers/hidden.css */
.hidden
{ border: 0;
clip: rect(0 0 0 0);
height: 1px;
margin: -1px;
overflow: hidden;
padding: 0;
position: absolute;
width: 1px;
}
/* helpers/icon.css */
:root {
--iconFill: var(--baseColor);
}
.icons
{ display:
none;
}
.icon {
block-size: 1em;
display: inline-block;
fill: var(--iconFill);
inline-size: 1em;
vertical-align: middle;
ONLINE HELPDESK FOR CAMPUS FACILITIES 36
GOKUL S – 2022K0552
}
--loginInputBackgroundColor: #3b4148;
--loginInputHoverBackgroundColor: #434a52;
--loginLabelBackgroundColor: #363b41;
--loginSubmitBackgroundColor: #007bff;
--loginSubmitColor: #eee;
--loginSubmitHoverBackgroundColor: #6610f2;
}
.login {
color: var(--loginColor);
}
.login label,
.login input[type="text"],
.login input[type="password"],
.login input[type="submit"] {
border-radius: var(--loginBorderRadus);
.text--center {
text-align: center;
}
</style>
</head>
</html>
<body class="align">
<div class="grid">
<form action="validation.php" method="POST" class="form login">
<div class="form field">
<label for="login username"><svg class="icon">
<use xlink:href="#icon-user"></use>