21EJCCS207 Jaikakumari

Jaipur Engineering College and Research
Centre, Shri Ram ki Nangal, via Sitapura Academic Year- 2021-2022

RIICO Jaipur- 302 022.
Seminar Report
On
“Web Development with Python Django”
Submitted in partial fulfillment for the award of degree of
Bachelor of Technology
in
Computer Science & Engineering
Submitted By Guide
Jasika kumari Pradeep Kumar Sharma
21EJCCS207 Assistant Professor
Department of Computer Science & Engineering

Jaipur Engineering College & Research Centre
Jaipur, Rajasthan
i
CANDIDATE’S DECLARATION
I hereby declare that the report entitled “A review on “Web development with python django
” has been carried out and submitted by the undersigned to the Jaipur Engineering College &
Research Centre, Jaipur (Rajasthan) in an original work, conducted under the guidance and
supervision of Mr. Pradeep kumar sharma.
The empirical findings in this report are based on the data, which has been collected by me. I
have not reproduced from any report of the University neither of this year nor of any
previous year.
I understand that any such reproducing from an original work by another is liable to be
punished in a way the University authorities’ deed fit.
Date: 7 December, 2023 Jasika kumari

Place: Jaipur 21EJCCS207
BONAFIDE CERTIFICATE
i
This is to certify that the report of the seminar submitted is the outcome of the seminar work
entitled “A review on Web Web development with python django ” carried out by Jasika Kumari
bearing Roll No.: 21EJCCS207 carried under my guidance and supervision for the award of Degree in
Bachelor of Technology of Jaipur Engineering College & Research Centre, Jaipur (Raj.), India during
the academic year 2023-2024.
To the best of my knowledge the report
i) Embodies the work of the candidate.

ii) Has duly been completed.
iii) Fulfills the requirement of the ordinance relating to the bachelor of
technology degree of the Rajasthan technical University and
iv) Is up to the desired standard for the purpose of which is submitted.
Dr. Sanjay Gaur Mr. Pradeep

kumar sharma
Head of Assistant Professor
Department
Computer Science Computer Science
& Engineering & Engineering
JECRC, Jaipur JECRC, Jaipur
Place: Jaipur
Date: 7 December, 2023
i
PREFACE
Bachelor of Technology in Computer Science & Engineering is the Rajasthan Technical

University course (Approved by AICTE) having duration of 4 years. As a prerequisite of the
syllabus every student on this course has to make a report on seminar lab in order to
complete his studies successfully. And it is required to submit the report on the completion of
it.
The main objective of this report is to create awareness regarding the application of theories
in the practical world of Computer Science & Engineering and to give a practical exposure of
the real world to the student.
I, therefore, submit this seminar report on “A review on Web Scraping and its
Applications”, which was undertaken at JECRC, Jaipur. I feel great pleasure to present
this seminar report.
i
CERTIFICATE
This is to certify that the industrial training entitled “web development” is the bonafide
work carried out by Jasika Kumari student of B.Tech. in Computer Science &
Engineering at Jaipur Engineering College and Research Centre, during the year 2023-24 in
partial fulfillment of the requirements for the award of the Degree of Bachelor of Technology
in Computer Science & Engineering under my guidance.
Name of Guide: Mr. Pradeep kumar sharma

Designation: Assistant Professor
Place: Jaipur
Date: 7 December 2023
i
VISION OF CSE DEPARTMENT
To become renowned Centre of excellence in computer science and engineering and make
competent engineers & professionals with high ethical values prepared for lifelong learning.
MISSION OF CSE DEPARTMENT
1. To impart outcome based education for emerging technologies in the field of computer
science and engineering.
2. To provide opportunities for interaction between academia and industry.
3. To provide platform for lifelong learning by accepting the change in technologies
4. To develop aptitude of fulfilling social responsibilities.
PROGRAM OUTCOMES (POs)
1. Engineering knowledge: Apply the knowledge of mathematics, science, engineering

fundamentals, and Computer Science & Engineering specialization to the solution of complex
Computer Science & Engineering problems.
2. Problem analysis: Identify, formulate, research literature, and analyse complex Computer
Science and Engineering problems reaching substantiated conclusions using first principles of
mathematics, natural sciences, and engineering sciences.
3. Design/development of solutions: Design solutions for complex Computer Science and

Engineering problems and design system components or processes that meet the specified needs
with appropriate consideration for the public health and safety, and the cultural, societal, and
environmental considerations.
vi
4. Conduct investigations of complex problems: Use research-based knowledge and research

methods including design of Computer Science and Engineering experiments, analysis and
interpretation of data, and synthesis of the information to provide valid conclusions.
5. Modern tool usage: Create, select, and apply appropriate techniques, resources, and modern
engineering and IT tools including prediction and modeling to complex Computer Science
Engineering activities with an understanding of the limitations.
6. The engineer and society: Apply reasoning informed by the contextual knowledge to assess
societal, health, safety, legal and cultural issues and the consequent responsibilities relevant to
the professional Computer Science and Engineering practice.
7. Environment and sustainability: Understand the impact of the professional Computer

Science and Engineering solutions in societal and environmental contexts, and demonstrate the
knowledge of, and need for sustainable development.
8. Ethics: Apply ethical principles and commit to professional ethics and responsibilities and
norms of the Computer Science and Engineering practice.
9. Individual and team work: Function effectively as an individual, and as a member or leader
in diverse teams, and in multidisciplinary settings in Computer Science and Engineering.
10. Communication: Communicate effectively on complex Computer Science and Engineering

activities with the engineering community and with society at large, such as, being able to
comprehend and write effective reports and design documentation, make effective presentations,
and give and receive clear instructions.
11. Project management and finance: Demonstrate knowledge and understanding of the
Computer Science and Engineering and management principles and apply these to one’s own
work, as a member and leader in a team, to manage projects and in multidisciplinary
environments.
12. Life-long learning: Recognize the need for, and have the preparation and ability to engage
in independent and life-long learning in the broadest context of technological change in Computer
Science and Engineering.
vii
PROGRAM EDUCATIONAL OBJECTIVES (PEOs)
The PEOs of the B.Tech (CSE) program are:
1. To produce graduates who are able to apply computer engineering knowledge to provide
turn-key IT solutions to national and international organizations.
2. To produce graduates with the necessary background and technical skills to work
professionally in one or more of the areas like – IT solution design development and
implementation consisting of system design, network design, software design and
development, system implementation and management etc. Graduates would be able to
provide solutions through logical and analytical thinking.
3. To able graduates to design embedded systems for industrial applications.
4. To inculcate in graduates effective communication skills and team work skills to enable
them to work in multidisciplinary environment.
5. To prepare graduates for personal and professional success with commitment to their
ethical and social responsibilities.
viii
PROGRAM SPECIFIC OUTCOMES (PSOs)
PSO1 Ability to interpret and analyze network specific, cyber security issues, automation in real
world environment.
PSO2 Ability to design and develop mobile and web-based applications under realistic
constraints.
COURSE OUTCOMES (COs)
On completion of Industrial Training Graduates will be able to-
• CO1: Generate the report based on the Projects carried out for demonstrating the ability
to apply the knowledge of engineering field during training
• CO2: Demonstrate Competency in relevant engineering fields through problem
identification, formulation and solution.
MAPPING: CO’s & PO’s

Program Outcomes (POs)
Subject Code Cos
PO- PO- PO- PO- PO- PO- PO- PO- PO- PO- PO- PO-
1 2 3 4 5 6 7 8 9 10 11 12
CO-1 3 3 2 2 2 1 1 2 2 3 3 3
3CS7-30
Industrial Training
CO-2 3 3 3 3 3 1 1 2 2 3 3 3
ix
ACKNOWLEDGEMENT
It has been a great honour and privilege to undergo training at Upflairs, Jaipur. I am very
grateful to <Company Person> giving his valuable time and constructive guidance in preparing
the report for training. It would not have been possible to complete this report in short period of
time without their kind encouragement and valuable guidance.
I wish to express our deep sense of gratitude to our Industrial Training Guide Mr./Ms.
Pradeep Kumar Sharma, Jaipur Engineering College and Research Centre, Jaipur for
guiding us from the inception till the completion of the industrial training. We sincerely
acknowledge him for giving his valuable guidance, support for literature survey, critical reviews
and comments for our industrial training.
I would like to first of all express our thanks to Mr. Arpit Agrawal Director of JECRC, for
providing us such a great infrastructure and environment for our overall development.
I express sincere thanks to Dr. V. K. Chandna, Principal of JECRC, for his kind cooperation
and extendible support towards the completion of our industrial training.
Words are inadequate in offering our thanks to Dr. Sanjay Gaur, HOD of CSE department, for
consistent encouragement and support for shaping our industrial training in the presentable
form.
Also our warm thanks to Jaipur Engineering College and Research Centre, who provided us
this opportunity to carryout, this prestigious industrial training and enhance our learning in
various technical fields.
JASIKA KUMARI
21EJCCS207
x
ABSTRACT
FOODZARELLA - is the project name which is a responsive website make uses of HTML +
CSS + PYTHON. Foodzarella is a front-end based food ordering website. The usage of dynamic
styling using CSS gives a vibrant touch to the lifeless website. The website is divided into 5
sections. All sections use different types off CSS styling methods which make it eye-catching.
The project is incomplete as it is just the front-end part of the website.
After the usage of python3.9 the website would be fully functional. The Newsletter at the
bottom of the website will be generating automatic mails. Overall, this project of mine is being
developed to design a food ordering website.
In this course, we learnt the basic tools that every web page coder needs to know. We started
from the ground up by learning how to implement modern web pages with HTML and CSS. We
then advanced to learn how to code our pages such that its components rearrange and resize
themselves automatically based on the size of the user’s screen. We were able to code up a web
page that will be just as useful on a mobile phone as on a desktop computer. No “pinch” and
“zoom” required! Last but certainly not the least; we got a thorough introduction to the most
popular and incredibly powerful language of the web: Python. Using Python, we were able to
build a fully functional web application that utilizes ajax to expose server-side functionality and
data to the end user.
xi
LIST OF FIGURES
Fig: 2.2 Context Diagram for WCRS……………………………………….18
Fig. 2.3 Use Diagram for WCRS……………………………………………21
Fig. 3. System Design……………………………………………………...22
Fig. 3.1.1 Sale Person User Case Diagram…………………………………..23
Fig. 3.1.2 Member User Case Diagram……………………………………...25
Fig. 3.2 Online food ordering system database design………………………26
Fig. 3.3.1 Sequence Diagram………………………………………………...27
Fig. 3.3.2 Activity Diagram………………………………………………….28
Fig. 3.4 Deployment Diagram……………………………………………….28
Fig: 4.1 Header section.....................................................................................29
Fig: 4.2 About us section........................................……………………….….29
Fig: 4.3 Meal pictures section.................................………………………..…30
Fig: 4.4 How it works section............................... …………………………..31
Fig: 4.5 Location section..................................................................................31
Fig: 4.6 Customer review section..............................………………………...32
Fig: 4.7 Meal order section...............................................................................32
Fig: 4.8 Newsletter section...............................................................................33
Fig: 4.9 Footer section..................................................................................... 33
xii
LIST OF TABLES
The Online food ordering system is a web application where customer can see the list of food
items and add to cart to make order.
Step1: MySQL Database Tables. ...
Step2: List Food Items. ...
Step3: Manage Food Items Cart. ...
Step4: Process Order.
xiii
TABLE OF CONTENTS
Certificate----------------------------------------------------------------------------------------- i
Vision and Mission------------------------------------------------------------------------------- ii
Program Outcomes (POs)----------------------------------------------------------------------- iii
Program Education Objectives (PEOs) ------------------------------------------------------ iv
Program Specific Outcomes (PSOs)----------------------------------------------------------- iv
Course Outcomes (COs)------------------------------------------------------------------------- v
Mapping: COs and POs-------------------------------------------------------------------------- v
Acknowledgement--------------------------------------------------------------------------------- vi
Abstract---------------------------------------------------------------------------------------------- vii
List of Figures--------------------------------------------------------------------------------------- viii
List of Tables---------------------------------------------------------------------------------------- ix
1. INTRODUCTION------------------------------------------------------------------------------ 9-14
1.1 Purpose --------------------------------------------------------------------------------------- 9
1.2 Project Scope--------------------------------------------------------------------------------- 10
1.3 Document Convention ---------------------------------------------------------------------- 10-14
2. REQUIREMENT ANALYSIS--------------------------------------------------------------- 14-20
2.1 Hardware Requirement--------------------------------------------------------------------- 15
2.2 Software Requirement ---------------------------------------------------------------------- 16
2.3 Functional Requirement--------------------------------------------------------------------- 17
2.4 Non Functional Requirements ------------------------------------------------------------ 18
2.5 User Classes and Characteristics ----------------------------------------------------------- 19-20
3. SYSTEM DESIGN------------------------------------------------------------------------------- 21-28
3.1 Use Case Diagram--------------------------------------------------------------------------- 21-23
3.2 Data Base Design and Databases --------------------------------------------------------- 24-27
3.3 Sequence Diagram/Activity Diagram------------------------------------------------------ 28
3.4 Deployment Diagram ---------------------------------------------------------------------- 28
4. SCREEN SHOTS-------------------------------------------------------------------------------- 28-33
5. Conclusion ----------------------------------------------------------------------------------------- 34
xiv
1. Introduction
Web Developing Website is a collection of related web pages, including multimedia content,
typically identified with a common domain name, and published on at least one web server. A
website may be accessible via a public Internet Protocol (IP) network, such as theInternet, or a
private local area network (LAN), by referencing a uniform resource locator(URL) that
identifies the site. Websites can have many functions and can be used in various fashions; a
website can be a personal website, a commercial website for a company, a government website
or a non-profit organization website. Websites are typically dedicated to a particular topic or
purpose, ranging from entertainment and social networking to providing news and education.
All publicly accessible websites collectively constitute the World Wide Web, while private
websites, such as a company’s website for its employees, are typically a part of an intranet. Web
development is a broad term for the work involved in developing a web site for the Internet
(World Wide Web) or an intranet (a private network). Web development can range from
developing the simplest static single page of plain text to the most complex webbased internet
applications (or just ‘web apps’) electronic businesses, and social network services. A more
comprehensive list of tasks to which web development commonly refers, may include web
engineering, web design, web content development, client liaison, clientside/server-side
scripting, web server and network security configuration, and ecommerce development. Among
web professionals, “web development” usually refers to the main non-design aspects of building
web sites: writing markup and coding.
1.1 Purpose
• Your working hours

• Your location
• What foods you serve
• If you have any special events on your calendar
• What kind of ambiance you offer
• Whether you accept online reservations and online payments
• Whether they can place online orders for food delivery.
xv
1.2 Project Scope

The following sections describe the work that will be implemented with Project Scope release of
the software:
• Tablet on table: there will be a tablet on each table, this will allow the customers to browse
the food item for the time they wish, and food items that customer wish.
• Customer feedback: - Customer can enter the feedback about the service and the food served.
This helps the restaurant owner to analyses the service and makes necessary changes if needed.
• Offers for customer: The restaurant owner can post various offers on tablet.
• Time to serve: The menu includes the approximate time to be served of a particular food item.
This will help the customer to select the food item accordingly.
• Sorting an item: The food item will be sorted according to price, Season, and user ratings; this
helps the customer to select a food item which has a good rating and which is liked by a many
customers.
1.3 Document Convention
A user agent that elects to implement a topic (e.g., fonts, colors, aural style sheets, etc.) covered
by this specification must adhere to all pertinent sections of the specification in order to be
considered to conform to CSS2 for that topic. In such cases, a user agent may claim to conform
to part of the CSS2 specification.
A user agent that elects to implement all topics covered by this specification and that does so in
accordance with the specification may claim to conform to all of CSS2. The inability of a user
agent to implement a specific topic due to the limitations of a particular device (e.g., a user
agent cannot render colors on a monochrome monitor or a black and white page) does not imply
non-conformance.
In addition to the previous conditions, a user agent that uses CSS2 to display documents
conforms to the CSS2 specification if:
• It attempts to retrieve all referenced style sheets and parse them according to this
specification.
• It sorts the declarations according to the cascade order.
xvi
A user agent that outputs CSS2 style sheets conforms to the CSS2 specification if it outputs
valid CSS2 style sheets.
A user agent that uses CSS2 to display documents and outputs CSS2 style sheets conforms to
the CSS2 specification if it meets both sets of conformance requirements.
This specification also recommends, but doesn't require, that a UA observe the following rules
(which refer to functionality, not user interface):
• allow the reader to specify personal style sheets

• allow individual style sheets to be turned on and off
• approximate style sheet values even if it can't implement them exactly according to the
specification.
Conventions
Document language elements and attributes
• CSS property, descriptor, and pseudo-class names are delimited by single quotes.
• CSS values are delimited by single quotes.
• Document language element names are in upper case letters.
• Document language attribute names are in lower case letters and delimited by double
quotes.
Each CSS property definition begins with a summary of key information that resembles the
following:
'Property-name'
Value: Possible constant values or value types
Initial: The initial value
Applies to: Elements this property applies to
Inherited: Whether the property is inherited
Percentage values: How percentage values should be interpreted
xvii
The five categories have the following meanings:
Value
This part of the property definition specifies the set of valid values for the property. Value types
may be designated in several ways:
1.constant values (e.g., 'auto', 'disc', etc.) basic data types, which appear between "<" and ">"
(e.g., <length>, <percentage>, etc.). In the electronic version of the document, each instance of a
basic data type links to its definition.
2.non-terminals that have the same range of values as a property bearing the same name (e.g.,
<border-width> <background-attachment>, etc.). In this case, the non-terminal name is the
property name (complete with quotes) between "<" and ">" (e.g., <'border-width'>). In the
electronic version of the document, each instance of this type of non-terminal links to the
corresponding property definition.
3.non-terminals that do not share the same name as a property. In this case, the non-terminal
name appears between "<" and ">" (e.g., <border-width>) and its definition is located near its
first appearance in the specification. In the electronic version of the document, each instance of
this type of non-terminal links to the corresponding value definition.
HTML conventions
In this specification, most of the examples refer to HTML. For clarity, HTML elements are
written with upper case letters (e.g., HTML, BODY, EM, P) and HTML attributes are written
with lower case letters (e.g., src, class, id).
xviii
2. REQUIREMENT ANALYSIS
This investigates the necessary requirements of the project based on an understanding and
analysis of the needs of system users. It first introduces the process of Requirement
Engineering in hardware and software. The techniques utilised to gather and analyse
requirements are discussed which then leads to documents on functional and non-functional
requirements. These requirements are then translated into informative models to assist
decision-making and problem understanding in the Requirement Modelling phase. Finally,
the chapter reviews several techniques to manage software development activities that could
help to realise these requirements.
It is important to gain insight in to what kind of system should be implemented and the level
of change that may affect organization before determining which requirements are
appropriate for a given system . Hence, the steps taken after gathering the initial requirement
involve performing an analysis on information obtained.
Some of the basic techniques that could be applied during this process as discussed by and
are described in the following:
• Classification and organization of requirements, involves grouping related requirements

and organizes into logical clusters or modules. Using model of system architecture is a
common way to discover possible modules (sub-system) and associate related requirements
to them.
• Prioritization and negotiations, involves prioritization requirements resolve conflicting
requirements through negotiation with stakeholder. The concern is to achieve a set of agreed
requirements that considered views of stakeholder involved.
2.1 Hardware Requirements

We strongly recommend a computer fewer than 5 years old.
• Processor: Minimum 1 GHz; Recommended 2GHz or more

• Ethernet connection (LAN) OR a wireless adapter (Wi-Fi)
• Hard Drive: Minimum 32 GB; Recommended 64 GB or more
• Memory (RAM): Minimum 1 GB; Recommended 4 GB or above
• Sound card w/speakers
• Some classes require a camera and microphone
2.2 Software Requirement

xix
The following are the software required for Web development:
1. Operating System: Fedora or Ubuntu (Linux Distro)
2. Browser: Google Chrome (Latest Version)
3. Git: Command Line Version
4. Text Editor: Atom (Alternatively use Notepad++ for Windows)
5. PHP: PHP 7.0 (or greater) installed via your distro package manager or Home brew (Mac OS
X) or Apt (Debian based distro like Ubuntu)
6. MySQL: Either MariaDB (preferred) or MySQL (not recommended)
7. Web Server: Nginx (Recommended)
8. Apache: Apache (Not Recommended)
9. Server Side Language: PHP (Recommended
10. Database: MySQL (Recommended)
11. Web Hosting: Blue host ( Recommended ).
2.3 Functional Requirement

Functional requirements describe the features that the system has to provide. It often describes
the expected features the user can utilize to perform their task. It may cover certain business
processes and procedures that the software must follow and perform to achieve user goals –
sometimes termed business logic. Thus, FRs are often associated with desired behaviour
characteristics of developing software to produce the expected result. The primary FRs of the
WCRS are to support or assist restaurant workers in the process or management of the food-
ordering workflow. However, the granularity of the requirements may grow quickly as more
understanding of requirements derived from Table 2.2 and Table 2.3. Functional requirements
xx
of WCRS are listed in Appendix C. Some of the scenarios of the requirements are defined
clearer in use cases §3.2.2.
Fig. 2.2 Context Diagram for WCRS
xxi
Fig. 2.3 Use Case Diagram for WCRS
xxii
2.4 Non Functional Requirements

Non-functional requirements refer to characteristics and constraints with which the system must
comply. It concerned with quality aspects of software system and good user experience such as
performance, security, availability. Unlike FR, NFR does not usually related to functionality that
yields operation results directly. However, NFR do affect the experience or result quality when
the user using the system. This is pointed out by that: “NFR may affect the overall architecture
of a system rather than the individual components.” 48 The author further claimed that NFR
might also generate FR given that the example of implementing Security features could
introduce new system services. There are several concerns with respect to NFR in WCRS,
especially usability – or usability analysis. Users should feel comfortably navigating the system
using mobile devices. The user interface should provide clear indication of navigation path, and
the menu, colour and layout should look consistent to the users. Security is also a major
consideration when developing the system. Access control should be implemented to prevent
destructive actions. The list of NFR is tabulated in Appendix D.
2.5 User Classes and Characteristics

User classes are one of the commonly applied techniques in requirement. Its primary use is to
capture interactions between users with the system. Interactions that occur within a system could
be user interactions such as input gesture, communication with external systems, or
collaboration between components of the system. Knowing users’ preferred ways to interact
with the system also allows developers to capture precise requirements and build a more usable
system
• Creation and management of recipe collection;
• Creation and management of menu;
• Submission and management of order;
• Mean to interact with pending orders in kitchen;
• Order processing and notification order status on cooking completion;
xxiii
• Payment computation for order;
• Generation of bill and associated VAT;
• Mean to collect and store payment transaction details;
• Material inventory level monitoring;
• Recording and maintaining employee information;
• Employee login and privileges level control; and
• Reporting of sales and orders
xxiv
3. SYSTEM DESIGN
System design is the process of designing the elements of a system such as the architecture,
modules and components, the different interfaces of those components and the data that goes
through that system.
Fig. 3.System Design
xxv
3.1 Use Case Diagram

The following is the user case diagrams for the four types of FWOS users. The FWOS system
provides functions indicated by the user case diagram. The functions will be different based on
the privileges of the user types.
Fig. 3.1.1 Sale Person User Case Diagram
xxvi
Fig 3.1.2 Member User Case Diagram
xxvii
3.2 Data Base Design and Databases

• Customer
• Customer_id (PK)
• Customer_name
• Customer_phonenum
• Payment_method (Cash/Credit Card)
• Payment_status (Paid/Unpaid)
• Email_address
• Employee_id (FK)
• OrderF_id (FK)
• OrderD_id (FK)
• Employee
• Employee_id (PK)
• Employee_name
• Employee_position
• Employee_age
• Employee_phonenum
• password
• Food
• Food_id (PK)
• Food_name
• Food_size
• Food_price (Describe price of each food)
• Drinks
• Drink_id (PK)
• Drink_name
• Drink_size
xxviii
• Drink_category (which explains hot/cold)

• Drink_price (Describe price of each drink)
• OrderFood
• OrderF_id (PK)
• Customer_id (FK)
• Food_id (FK)
• Quantity_item
• Total_price
• OrderDrinks
• OrderD_id (PK)
• Drink_id (FK)
• Quantity_item
• Total_Price
Fig. 3.2 Online food ordering system database design-DB
xxix
3.3 Sequence Diagram/Activity Diagram

Sequence diagram consists of a menu list, food descriptions, orders, and a list of customer
orders. The sequence diagram is designed both in terms of consumers and personalized staff -the
sequence diagram of customer order shown in figure. The design of the interface is carried out
on various facilities provided by the system, both on splash green, menu lists, food and beverage
information, reservations, order history, and order lists for restaurant staff.
Fig. 3.3.1 Sequence Diagram
xxx
An Activity Diagram is a behavioural diagram. It depicts the behaviour of a system. Its primary
use is to depict the dynamic aspects of a system. The dynamic aspect of a system specifies how
the system operates to attain its function.
It is basically a flowchart to represent the flow from one activity to another activity. Activity
Diagrams are not exactly flowcharts as they have some additional capabilities including
branching, parallel flow, swimlanes, etc.
Fig.3.3.2 Activity Diagram
xxxi
3.4 Deployment Diagram
Deployment diagram describes the hardware used in system implementations and the execution
environments and artifacts deployed on the hardware.
UML Deployment Diagram depicts the physical deployment of artifacts on nodes (nodes are the
existing hardware components, artifacts are the software components running on each node);
and how the different pieces are connected.
Use ConceptDraw PRO with UML deployment diagram templates, samples and stencil library
from Rapid UML solution to model the physical deployment of artifacts on nodes of your
software system.
Fig. 3.4 Deployment Diagram
xxxii
4. SCREEN SHOTS
Fig. 4.1 Header section
xxxiii
Fig. 4.2 About us section
Fig. 4.3 Meal picture section
xxxiv
Fig 4.4 How it works section
Fig. 4.5 Location section
xxxv
Fig.4.6 Customer review section
Fig. 4.7 Meal order section
xxxvi
Fig. 4.8 Newsletter section
Fig. 4.9 Footer section
xxxvii
6. Conclusion
The aim of this thesis was to develop an website for customers to make a more user
friendly menu in which the customer can look through and tab the menu on a tablet. And
also to collect more accurate data on the ordered foods in a more efficient and effective
way. The application is implemented on tablet devices, so the text size and design is
adjustable to devices with large screen to make it more easier to read and look through
the menu items. The Restaurant Management System helps to quickly & easily manage
restaurant inventory information. The manager can easily get reports based on the date of
profits and sales depending on the period which they want the report on.
xxxviii

21EJCCS207 Jaikakumari

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

21EJCCS207 Jaikakumari

Uploaded by

Copyright:

Available Formats

Jaipur Engineering College and Research

Centre, Shri Ram ki Nangal, via Sitapura Academic Year- 2021-2022

“Web Development with Python Django”

Submitted in partial fulfillment for the award of degree of

Computer Science & Engineering

Department of Computer Science & Engineering

Date: 7 December, 2023 Jasika kumari

i) Embodies the work of the candidate.

Dr. Sanjay Gaur Mr. Pradeep

Bachelor of Technology in Computer Science & Engineering is the Rajasthan Technical

Name of Guide: Mr. Pradeep kumar sharma

VISION OF CSE DEPARTMENT

MISSION OF CSE DEPARTMENT

PROGRAM OUTCOMES (POs)

1. Engineering knowledge: Apply the knowledge of mathematics, science, engineering

3. Design/development of solutions: Design solutions for complex Computer Science and

4. Conduct investigations of complex problems: Use research-based knowledge and research

7. Environment and sustainability: Understand the impact of the professional Computer

10. Communication: Communicate effectively on complex Computer Science and Engineering

PROGRAM EDUCATIONAL OBJECTIVES (PEOs)

The PEOs of the B.Tech (CSE) program are:

PROGRAM SPECIFIC OUTCOMES (PSOs)

COURSE OUTCOMES (COs)

On completion of Industrial Training Graduates will be able to-

MAPPING: CO’s & PO’s

Fig. 2.3 Use Diagram for WCRS……………………………………………21

Fig. 3. System Design……………………………………………………...22

Fig. 3.1.1 Sale Person User Case Diagram…………………………………..23

Fig. 3.1.2 Member User Case Diagram……………………………………...25

Fig. 3.2 Online food ordering system database design………………………26

Fig. 3.3.1 Sequence Diagram………………………………………………...27

Fig. 3.3.2 Activity Diagram………………………………………………….28

Fig. 3.4 Deployment Diagram……………………………………………….28

Fig: 4.1 Header section.....................................................................................29

Fig: 4.2 About us section........................................……………………….….29

Fig: 4.3 Meal pictures section.................................………………………..…30

Fig: 4.4 How it works section............................... …………………………..31

Fig: 4.5 Location section..................................................................................31

Fig: 4.6 Customer review section..............................………………………...32

Fig: 4.7 Meal order section...............................................................................32

Fig: 4.8 Newsletter section...............................................................................33

Fig: 4.9 Footer section..................................................................................... 33

Step1: MySQL Database Tables. ...

Step2: List Food Items. ...

Step3: Manage Food Items Cart. ...

Step4: Process Order.

• Your working hours

1.2 Project Scope

1.3 Document Convention

• allow the reader to specify personal style sheets

Document language elements and attributes

Value: Possible constant values or value types

Initial: The initial value

Applies to: Elements this property applies to

Inherited: Whether the property is inherited

Percentage values: How percentage values should be interpreted

The five categories have the following meanings:

• Classification and organization of requirements, involves grouping related requirements

2.1 Hardware Requirements

• Processor: Minimum 1 GHz; Recommended 2GHz or more

2.2 Software Requirement

The following are the software required for Web development:

1. Operating System: Fedora or Ubuntu (Linux Distro)