Contents

CHAPTER 1: INTRODUCTION........................................................................................5
1.1 Introduction................................................................................................................5
1.2 Problem Statement.....................................................................................................6
1.3 Objective....................................................................................................................6
1.4 Scope and Limitation...............................................................................................6
1.4.1 Scope..................................................................................................................6
1.4.2 Limitations........................................................................................................6
1.5 Report Organization...................................................................................................7
CHAPTER 2: LITERATURE REVIEW.............................................................................8
2.1 Literature Review.......................................................................................................8
CHAPTER 3: SYSTEM ANALYSIS AND DESIGN......................................................10
3.1 System Analysis.......................................................................................................10
3.2 Requirement Analysis..............................................................................................10
3.2.1 Functional Requirement....................................................................................10
3.2.2 Non-Functional Requirement............................................................................12
3.3 Feasibility Analysis..................................................................................................12
3.4 Data Modeling..........................................................................................................14
3.5 Process Modeling.....................................................................................................15
3.6 System Design..........................................................................................................16
3.7Architectural Design.................................................................................................16
3.8 Database Schema Design.........................................................................................17
3.8.1 Relational Schema.................................................................................................19
3.9 Interface Design.......................................................................................................20
3.10 UI Interface............................................................................................................21
CHAPTER 4: IMPLEMENTATION AND TESTING.....................................................22
4.1: Implementation.......................................................................................................22
4.1.1: Implementation Details....................................................................................23
4.1.2: Tools Used.......................................................................................................23
4.2 Implementation Details............................................................................................24
4.3 Testing......................................................................................................................25
4.3.1 Testing cases for unit testing.............................................................................25

1
CHAPTER 5: CONCLUSION AND FUTURE RECOMMENDATION.........................28
5.1: Lesson Learned.......................................................................................................28
5.2: Conclusion..............................................................................................................28
5.3: Future Recommendation:.......................................................................................28

2
 Table of Figures
Figure 1 User side use case.....................................................................................11
Figure 2 Admin side use case..................................................................................11
Figure 3 Gantt Chart................................................................................................14
Figure 4 : ER Diagram of the System.....................................................................15
Figure 5: Context Level Diagram (DFD 0).............................................................15
Figure 6: System Architecture.................................................................................17
Figure 7 Interface Structure Diagram......................................................................20
Figure 8: User Interface of the system....................................................................21
Figure 9: Waterfall Model.......................................................................................22

3
 LIST OF ABBREVIATIONS

CSS Cascading Style Sheet

DFD Data Flow Diagram

ERD Entity Relationship Diagram

HTML HyperText Markup Language

JS JavaScript

PHP Hypertext Preprocessor

SQL Structured Query Language

4
CHAPTER 1: INTRODUCTION
1.1 Introduction

Web development refers to building, creating, and maintaining websites. It includes

aspects such as web design, web programming, and database design and management.
The large organizations mostly focus on the creative designing and they mostly design the
project by writing their own codes which can mean more to the users and can enhance the
skills of developer too, whereas, some of the small organizations prefer designing the web
based projects by using cms like word press and joomla, which is fast but it can make you
lazy and doesn’t helps developers to enhance their coding skills.
Web development can be done by using different languages like HTML, CSS, PHP,
Javascript, Python, sql, etc. HTML, CSS and java scripts are mainly used for the frontend
development that manages the user interface of the website. It helps to make the website
look attractive and dynamic. Whereas languages like Python, PHP are used to perform the
backend actions of the project. It can build the interaction between the frontend and the
database (designed by using sql). The backend decides how the system works and how
the internal structure of the programs processes and redirects the data to the user interface
of the system. 
Online Catering system is a web based system for any Peoples, Organizations that book
out Food system. This system enables the company to make their services available to the
public through the internet. Developing an Online Food Court Ordering system to
promote a greater count of food lovers to splurge into the field of Restaurant was the
objective of this study. Нis particular system provide the benefit of the easy ordering
process online from anywhere along with ample choices for the customers in less time
and less expenditures. Нis latest e‫ ٴو‬ort will definitely usher an edge in the existing manual
platform used so far for such an important aspect along with greater flexibility and
sophistication in the use of the technology. Нe system also aided E-ordering option for
the customers with multiple other benefits. Similarly, this project is also based on web
development. The purpose of our project is to design a web based Catering System portal
using the languages like HTML, CSS, Bootstrap, Jquery, JavaScript, PHP and sql.

5
1.2 Problem Statement
We searched for the systems that are built for online catering system purpose in our area.
After doing some researches we found out that no proper system is available where we
can provide our service to different areas through the same system or same application
software. Some apps are used to provide food only and some system are used for
providing donations to a specific organization only. After finding out these problems we
have decided to build a system where a caterer can provide direct help to different people
from different areas, different organizations according to the type of service they take.

Also, building a system like this will be difficult as there are many applications available
in the market. We have to create something new in our project which should be able to
overcome the problems with current systems available. Creating something uniqueness in
our project would be a challenging task for us.

1.3 Objective
The main objective of this project is to change the manual Online Catering system into a
web based computerized system. Other objectives are as follows:-

 To develop a system for online catering services.

 To provide our service or serve food to needy people.
 To provide service to different organizations.
 To make it easier for people to provide service in different areas through the same
system.

1.4 Scope and Limitation

1.4.1 Scope
 System Backup and System Restore
 Access to the System
 Information about the Order

1.4.2 Limitations
 User interface is only in English
 Internet reliance means internet is not everywhere yet so that area cannot be
connected.
 People who are not familiar with computers can’t use this application.

1.5 Report Organization

The report starts with the introduction of the project along with problem statements and
objectives of the project. Here, we have introduced why the system is built long with its

6
scope and limitations. Chapter 2 includes a brief review of studies that have been done
previously by other researchers along with requirement as well as feasibility analysis of
the system. The data modeling and process modeling techniques are used to give the
information about the system requirement .Chapter 3 discuss about the system design
along with the algorithm used. The system design can be database schema design,
interface design and process design. Chapter 4 explains about the tools that are used on
our project’s front end, back end and purpose of it. The modules used are also explained.
In addition the testing is also explained in this part. Chapter 5 discuss about the
conclusion of how project is accomplished, its findings and many more. We also discuss
about the recommendation for future enhancements of the project. In conclusion, this
chapter’s overview purpose of doing this project including its scopes and objectives.

CHAPTER 2: LITERATURE REVIEW

7
2.1 Background Study

Recently, food business has become popular business and had increased rate in business
sector. It has made rapid competition among them. Pujas Lera restaurant is one of the
restaurants which is located Infront of Muhammadiyah University of Surakarta. There are
lots of stands which provide some kinds of food. The manager of Pujas Lera restaurant
said that to do his business, he still uses paper-based system. One of the weaknesses when
doing such a system is the calculation of money which is done manually and the end
process of calculation is to know the income. If we use paper- based, it will spend much
time. Therefore, it can give disadvantage in many cases. Paper- based system will make
difficult the worker when giving service toward their customers or guests. Based on the
problem, the manager of Pujas Lera restaurant needs special software which is able to
help in doing restaurant management and giving better service to their customers

2.1 Literature Review

Online Catering System can encourage people to provide service to different areas and
create a positive relationship between them. It also motivates families or any organization
to help those who are in need. Work will be done so as to make people more engaged
with the System. In literature, a study about the systems related to service is proposed.

(Zeithaml&Bitner, 2003)In food delivery business Service Encounter does not happen
frequently because in online food ordering and delivery business there is no direct
interaction with restaurants. Consumers usually rely on information updated on restaurant
search engine portals. Customer make their choices, perception by reading reviews and
ratings given by critics and seasoned customers.. According to RedSeer Consulting firm
(www.redseer.com- Feb18)states that food delivery sector is continuously increasing 15%
per quarter.

Kamran Ahsanet. al (2013)In food ordering and delivery services cloud services are
playing very vital role in food ordering and delivery services such as customer service,
relationship management, supply chain management, etc.Due to technological moment
food ordering and delivery services wants to ensure that ordered food must deliver at right
place at right time and to right person.

The reviewed literature suggests that the magnitude and complexity of this problem has
been tackled by several studies. But based on our findings there was a great discrepancy
between user focus. We also did small research on people’s engagement with these
8
system. From the observation we found out that there is a need to incorporate techniques
that attract people more towards such system

After studying these above research and journals, we got a basic idea about the history
and about how the Catering System business took off. This research also gave us the ideas
about the UI design and how the Catering system works on the basis of both user and
admin’s view as a whole.

CHAPTER 3: SYSTEM ANALYSIS AND DESIGN

9
3.1 System Analysis
Before creating any web application or software, it is necessary to visualize the layout,
design and all features intended to be added. Requirements are necessary attributes in the
system to identify characteristics of the system. Once the requirements are set, developers
can start the technical work.

3.2 Requirement Analysis

Requirements must be quantifiable, relevant and detailed. The main purpose of
Requirement Analysis is to describe the functional and nonfunctional requirement of the
project. All the requirements specified here are high priority and has been specified
according to the requirement analysis. This document is intended to clarify the actual
need of the system and verify its functionality with other member involved to design the
system.

3.2.1 Functional Requirement

The functional requirements are mapped using Use Case diagrams as it shows the
functions of the system at the most basic level. Use Case shows the functions that are
included for the system to function as per requirement. Requirements mapped out in the
use case must be implemented in the system. Divided into admin based and user-based
requirements.

 Register and create profile

 Login into the system
 Add/Edit/Delete data on their Profiles
 View Request
 Search Request

Figure 1 User side use case

10
3.2.2 Non-Functional Requirement

i. Performance requirement

The risk factor was analyzed at the initial step for better performance of the
application. The overall performance of the application is reliable and enables the
user to use the application efficiently.

ii. Flexibility

The application should be flexible with the user interface.

iii. Maintainability

If any error occurs it should be easily maintainable.

iv. Scalability

It should be scalable based on addition of package.

v. Testability

It should be testable for various forms of testing.

3.3 Feasibility Analysis

Feasibility analysis of the project includes whether the system development is worth
continuing or not. This phase of analysis basically checks if the system will be beneficial
to the customers and what kind of impact will it have on them.

i. Technical Feasibility
This sector measures the availability of technical resources and expertise. This
project targets websites. This application is technically feasible as a highly
expert person is not required to use this application. Utilizing existing
technology will lower the risk of our project. This application will be
compatible in all browsers.

11
Operating System Windows 8.1 Pro (minimum)

Processor 1Ghz or higher

RAM 512MB or higher

Disk Space 1GB or higher

Internet Connection At least 1 Mbps

Server Software Application Software, File Software, Database Software

Web Tools HTML editors

Networking TCP, IP, FT0050’

Browser Any browser applicable

Device PC, Laptop, Android Device

Front-End Tool HTML, CSS, JS, Bootstrap

Back-End Tool PHP, MySQL, Database

Table 1: Software and Hardware Requirements

ii. Operational Feasibility

The main focus is on providing the information and communication between
customers and Online Catering system. It is an internet-based application so
the website may not load in the case of disconnection. This application is
developed with simple, attractive and user-friendly interfaces which can be
used easily. Similarly, those people who are accessing the application from
their personal computer for required information will not face any problem.
Thus, this project is operationally feasible. For the use of the system, the
customer must have the knowledge as follows:

 Users must have a laptop/computer in order to use system and must

have access to the internet.
 Users must have knowledge on how to use a website.

12
 iii. Economic Feasibility
The specific requirements and solutions have been identified to weigh the cost
and benefits of the alternatives. The hardware and software used are simple
and there is no other additional hardware requirement. It is based on the
existing system, so the cost will be minimum.

iv. Schedule Planning

This includes the project schedule and all time allocated for their completion.
The Gantt chart is as follow:
Weeks 1st 2nd 3rd 4th 5th 6th 7th 8th 9th 10th 11th 12th
Planning
Requirement
Analysis
System Design
Implementation
Testing
Documentation

Figure 3 Gantt Chart

3.4 Data Modeling

A data model is a mechanism that provides this abstraction for database application. Data
modeling is used for representing entities and their relationship in the database. E-
R(Entity Relationship) Model can be referred as a Data Model. E-R Model is a popular
high level conceptual data model. This model and its variations are frequently used for
the conceptual design of database application and many database design tools ordering its
concept.

13
 quantity

coupon_
N
address Gives Cash date

PhoneNo WORKS
Custname Sales_date
For
coupon_ coupon_
MobileNo
type type

Email ID Company 1 N N Updates 1 dailySales N_coupons

Gives Coupon
Employee

Recieves
coupon_
1 food_Cost
1 type Customer
1 name

Recieves generate Custname

3.5 Process Modeling

1
1
total_amt
foodblls
A DFD can be referred to as a Process Model. A data-flow diagram (DFD) is a graphical
billdate
representation
billNoof the "flow" of data through an information system Adata flow diagram
month year
(DFD) is a significant modeling technique for analyzing and constructing information
processes illustrates this 1
flow of information in a process based on the inputs and outputs.
generate

1 reciept_tNo

1
Reciepts
reciept_date

amtpaid
billno

Figure 4 : ER Diagram of the System

Sup_ID, Punch_No, Food_Type, Amt,

Expenditure_type

0.0
User Catering
Management

Final_Bill_Amt, Payed_Amt, Reports

Figure 5: Context Level Diagram (DFD 0)

14
3.6 System Design
System design is a process that overlaps significantly with the requirements development
process. It involves establishing the overall architecture of the system, identifying the
different system components and understanding the relationships between them.

Several diagrams were created in the design phase of the project such as system
architecture, UML class diagram, database, schema, system flowchart, E-R diagram, use
case diagram, sequence diagram and context diagram for the development process.

Structural Components

Client tier: The web browser or client is the interface interpretation of a web app
functionality with which the user interacts. Content delivered to the client is developed
using HTML, JavaScript, CSS. In general, the web browser or client manages how end
users interact with the application.

Web tier: The web application server manages business logic and data persistence and is
built using PHP. It comprises a centralized hub to support multi-layer applications.
XAMPP is used which is completely free, easy to install Apache distribution containing
PHP.

Database tier: The database server provides and stores relevant data for the application.
Furthermore, it may also supply the business logic and other information that is managed
by the web application server.

3.7Architectural Design
The main focus of the college web portal is to create a easy communication between
college administration and students. With the various user friendly functionalities users
can easily view upload or download information and communicate with college
administration from their comfort zone.

15
 Figure 6: System Architecture

3.8 Database Schema Design

Column Name Data Type and Attribute

ID INT PK(10)

USERNAME VARCHAR(100)

PASSWORD VARCHAR(100)

ADMIN LOGIN TABLE

16
 Column Name Data Type and Attribute

ID INT PK(10)

USERNAME VARCHAR(100)

PASSWORD VARCHAR(100)

USER LOGIN TABLE

Column Name Data Type and Attribute

ID INT PK(10)

DATETIME VARCHAR(100)

TITLE VARCHAR(250)

IMAGE VARCHAR(250)

FILE UPLOAD TABLE

17
3.8.1 Relational Schema
adminLogin(id , username , password)

userLogin(id , username , password)

FileUpload(id , datetime , title , image)

18
3.9 Interface Design

Figure 7 Interface Structure Diagram

19
3.10 UI Interface

Figure 8: User Interface of the system

20
 CHAPTER 4: IMPLEMENTATION AND TESTING

4.1: Implementation
There are various methodologies in software development practices. Among them,
waterfall mythology is implemented as the requirement desired by the organization is
fixed and need not be changed in the future. Waterfall method is popular for development
of IT projects in a Waterfall model, each phase must be completed before the next phase
can begin and there is no overlapping in the phases. In “The Waterfall” approach, the
whole process of software development is divided into separate phases. The outcome of
one phase acts as the input for the next phase sequentially. This means that any phase in
the development process begins only if the previous phase is complete.

Basic workflow in Waterfall methodology is given below:

Figure 9: Waterfall Model

21
4.1.1: Implementation Details
i. Requirement Gathering and Analysis:
All possible requirements of the system to be developed are captured in this
phase and documented in a requirement specification document.
ii. Design
The requirement specifications from first phase are studied in this phase and
the system design is prepared. This system design helps in specifying
hardware and system requirements and helps in defining the overall system
architecture
iii. Coding
The actual source code is finally written in this stage of implementation,
implementing all models, business logic and service integrations that were
specified in the prior stages. Different programming language such as HTML,
CSS, PHP and JavaScript has been used to develop the system.
iv. Testing
Post integration the entire system is tested for any faults and failures.
v. Operations and Maintenance
There are some issues which come up in the client environment. To fix those
issues, patches are released. Also to enhance the product some better versions
are released. Maintenance is done to deliver these changes in the customer
environment.

4.1.2: Tools Used

Sublime Text:Sublime Text Editor used to implement the system i.e. for coding the
system. The IDE interface makes it easy to debug code and find out problematic portion
of code for enhancement. It also has built-in plug-ins that allows live testing of code and
beautifying code for easy understanding.

HTML, CSS and Bootstrap: HTML primarily used to design the UI and provide
support to Bootstrap elements by proving containers for Bootstrap. CSS used to add
additional detailed design to the portal and Bootstrap used to overall design the portal by
extending tags from existing library.

JavaScript: Javascript is used to add events and triggers to the web portal, the web portal
uses JS for date and time purposes by directly getting the system time.

22
PHP: The PHP Hypertext Preprocessor (PHP) is a programming language used to create
dynamic content that interacts with databases. It has helped to send and get request and
data from and to databases like MySQL in the project and is used for developing web-
based software applications. 

MYSQL: MySQL is an open-source relational database management system (RDBMS).

We have used MySQL to store and retrieve data.

XAMPP Server: XAMPP is one of the widely used cross-platform web servers, which
helps developers to create and test their programs on a local web server. It is used in the
project development to locally host the portal and store its database centrally.

Visual Paradigm Online (Software Design Tool): Visual Paradigm used to generate
various UML diagrams for system analysis and design. Diagrams were created using this
tool in order to save time since all components are available with drag and drop functions
and it also allows backup the diagrams by syncing with Google account.

4.2 Implementation Details

(Description of procedures and functions)

There are different module descriptions which are described below:

User module:
This module is dedicated to user in which user are divided into two types one is general
user who can use genera functionalities of the system such as View Services, contacting
admin, viewing the gallery and about us section. Another type of user is authenticated
user who as registered in website as Customer they can login to the system with login id
and password which is initially provided by admin and can perform additional
functionalities such as viewing Services and uploading various files to System
administration.

Admin module:
Admin module is dedicated to the Catering administration staff in which admin can
control the whole activities of the system. Admin must login to the system to get access in
this module and it is responsible for adding or removing user accounts and managing the
functionalities.

23
4.3 Testing
Testing is the process of evaluating a system or its component(s) with the intent to find
whether it satisfies the specified requirements or not. Testing is executing a system in
order to identify any gaps, errors, or missing requirements in contrary to the actual
requirements.

4.3.1 Testing cases for unit testing

Unit testing is a software development process in which the smallest testable parts of an
application are individually and independently scrutinized for proper operation (Rouse,
Rouse, Margaret Rouse & James Denman). The main objective of unit testing is to isolate
return code to test and determine if it works as intended. Unit testing is an important in
the development process, because it can help detect early flaws in code which may be
more difficult to find in later testing stages.
 Admin login
 User login
 Adding and deleting accounts
 Managing posts
 Uploading files from user.

Test Test Test Test Expected Actual Order/Cancel
Case Scenario Steps Data Services Facilities
Id

T01 Check Enter Username: Admin must As Order

admin username admin_07 be logged expected
login and Password: in.
password 123

24
Test Test Test Test Expected Actual Order/Cancel
Case Scenario Steps Data Services Facilities
Id

T02 Check user Enter Username: User must As Order

login username user_07 be logged expected
and Password: in.
password 123

Test Test Test Test Expected Actual Order/Cancel

Case Scenario Steps Data Services Facilities
Id

T03 Check 1. Username: User must As Order

adding Admin user11 be added expected
account login Password:
2. Enter 9990
username
and
password
to login

Test Test Test Test Expected Actual Order/Cancel

Case Scenario Steps Data Services Facilites
Id

T04 Check 1. Id= 12 User As Order

deleting Admin account expected
Account login. with id 1
2. Enter must be
id to deleted..
delete.

Test Test Test Test Expected Actual Order/Cancel

Case Scenario Steps Data Services Facilities
Id

25
T05 Adding 1. Service Added test As Order
Item Admin will be must be expected
login. closed displayed
2. Enter tomorrow on notice
text. section.

Test Test Test Test Expected Actual Order/Cancel

Case Scenario Steps Data Services Facilities
Id

T06 Check 1. User File = The chosen As Book

uploading login. data.pdf file must be expected
files from 2. uploaded to
user Choose database of
and System.
upload
file.

26
 CHAPTER 5: CONCLUSION AND FUTURE RECOMMENDATION
5.1: Lesson Learned
The main objective of the project was to create a fully dynamic website that interacts with
the database and provide different services to the different user according to their
Demand. Throughout the project the most important lesson we learned is teamwork and
time management.
We learned different database operations as well as frontend events. Most importantly we
learned about real time software development process within limited time.
Documentation and debugging techniques were learnt as it plays vital role in development
of any software.
We learned about how communication, mutual understandings and leadership within
development team helps in development of software without any error and within limited
time bound.

5.2: Conclusion
Information technology have changed the life of people, online medium is becoming the
first choice in any commercial as well as non-commercial organizations. Website is
becoming the inseparable part of the organization. Catering website can be valuable
source of information and can be effective tool to improve communication, engagement,
strength, and build a solid trusting reputation within community.

The interface as well as the backend functionalities of the system is user friendly and easy
to use so any user with general knowledge of internet can easily use, manage and handle
the system. The system doesn’t need any complex tolls and hardware to run it can simply
run on any internet browser available. The system will help managing records of
customers from admin panel to Customers as well as Customer to admin so it can be
effective and time saving for both parties.

5.3: Future Recommendation:

It is worth mentioning that this project work is open for further enhancement, with the
expectation that it becomes more robust and better enhanced. There are still lots of areas
that can be improved further regarding our website as well as follows:

● Fully functional reservation platform so that payment can be done through online
transaction.

27
 ● The website can be made for multi-organization and any Consumer so that a
single website could be used to manage many More.
References:

[1] D. S. Biradar, G. Badiger, A. and S. Muttagi, Review on Literature Survey Share My

Food, 2021.
[2] I. Madisch, S. Hofmayer and H. Fickensche, "Research Gate," May 2008. [Online].
Available: https://www.researchgate.net/. [Accessed January 2022].

[3] Visual Paradigm Online. (2021) Object Management Group Organization.

[Online].https://online.visual-paradigm.com/app/diagrams/

[4]Researched on internet. Available at website https://www.rsisinternational.org/virtual-

library/papers/tag/literature-review-on-online-food-ordering-system-pdf/

Bibliography:

[1] "WEB CONTENT MANAGEMENT SYSTEM," International Journal of Innovative

Research in Advanced Engineering (IJIRAE), pp. 51-56, 2016. [Online].
http://www.iosrjournals.org/iosrjce/papers/Conf.17003/Volume-2/15.%2079-82.pdf

[2] MySQL. (2018) Oracle Corporation.

[Online].https://dev.mysql.com/doc/refman/8.0/en/fulltext-natural-language.html

28
Appendix I- System Screenshots

29
30
31
Appendix II – Source Code

Connection.php

<?php

$servername = "localhost";
$username = "root";
$password = "";
$database = "website";

//create connection
$conn = new mysqli($servername, $username, $password,
$database);

//check connection
if($conn->connect_error) {
die("Connection failed:" . $conn->connect_error);
}

//$sql = "CREATE TABLE logins (

//id INT(6) UNSIGNED AUTO_INCREMENT PRIMARY KEY,
//username VARCHAR(30) NOT NULL,
//password VARCHAR(30) NOT NULL
//)";

//$conn->query($sql);

?>

User.php

<?php include 'header.php';?>

<body class = "admin_body" style = "background-color:#343434 !

important; background:none;">

<div class="lockscreen-wrapper">
<div class="lockscreen-logo">
<a href="../index.php"><img src = "../img/cc.png"/></a>
<a style = "color:white;"
href="../index.php"><b>Yadav's</b>Catering</a>
</div>
<!-- User name -->
<div class="lockscreen-name">Administrator</div>

32
 <!-- START LOCK SCREEN ITEM -->
<div class="lockscreen-item">
<!-- lockscreen image -->
<div class="lockscreen-image">
<img src="../img/key.png" alt="User Image">
</div>ss
<!-- /.lockscreen-image -->

<!-- lockscreen credentials (contains the form) -->

<form class="lockscreen-credentials" action =
"login.php"method = "POST">
<div class="input-group">
<input type="hidden" name = "username" class="form-
control" placeholder="password" value = "chimney_admin">
<input type="password" name = "password" class="form-
control" placeholder="password" autofocus>

<div class="input-group-btn">
<button name = "login"class="btn"><i class="fa fa-
arrow-right "></i></button>
</div>
</div>
</form>

<!-- /.lockscreen credentials -->

</div>

<!-- JS -->
<script src="../js/jquery.js"></script>
<script src="../js/bootstrap.min.js"></script>
</body>
</html>

header.php

<?php include 'header.php';?>

<body class = "admin_body" style = "background-color:#343434 !

important; background:none;">

<div class="lockscreen-wrapper">
<div class="lockscreen-logo">
<a href="../index.php"><img src = "../img/cc.png"/></a>

33
 <a style = "color:white;"
href="../index.php"><b>Yadav's</b>Catering</a>
</div>
<!-- User name -->
<div class="lockscreen-name">Administrator</div>

<!-- START LOCK SCREEN ITEM -->

<div class="lockscreen-item">
<!-- lockscreen image -->
<div class="lockscreen-image">
<img src="../img/key.png" alt="User Image">
</div>
<!-- /.lockscreen-image -->

<!-- lockscreen credentials (contains the form) -->

<form class="lockscreen-credentials" action =
"login.php"method = "POST">
<div class="input-group">
<input type="hidden" name = "username" class="form-
control" placeholder="password" value = "chimney_admin">
<input type="password" name = "password" class="form-
control" placeholder="password" autofocus>

<div class="input-group-btn">
<button name = "login"class="btn"><i class="fa fa-
arrow-right "></i></button>
</div>
</div>
</form>

<!-- /.lockscreen credentials -->

</div>

<!-- JS -->
<script src="../js/jquery.js"></script>
<script src="../js/bootstrap.min.js"></script>
</body>
</html>

34