Designing and Implementing a Project Based Learning on

“ blood bank system ”

Submitted to the

Savitribai Phule Pune University

In partial fulfillment for the award of the Degree of

Bachelor of Engineering
in

Information Technology
by

Gaurish Mundada(I2210)
Sarvesh Pabitwar(I2215)
Rugved Patil(I2220)
Ajinkya Palve(I2216)
Sakshi Patare(I2219)
Under the guidance of

Prof. Lalit Patil

Department Of Information Technology

SMT. Kashibai Navale College of Engineering
Vadgaon, Pune - 41.
 CERTIFICATE

This is to certify that the mini project report entitled Online Food App being submitted by
Gaurish ,Sarvesh , Rugved , Ajinkya, Sakshi (Roll no-I2210,I2215,I2220,I2216,I2219)
of div-2 is a record of bonafide work carried out by him/her under the supervision and
guidance of Prof. Lalit Patil partial fulfillment of the requirement for SE (Information
Technology Engineering) – 2019 course of Savitribai Phule Pune University, Pune in the
academic year 2020-2021.

Date: 31/05/2023

Place: Pune

Guide Subject Coordinator Head of the Department

Principal

This Mini Project report has been examined by us as per the Savitribai Phule Pune
University, Pune requirements at [Link] Navale College of
Engineering,Vadgaon,Pune-41 on . . . . . . . . . . .

Internal Examiner External Examiner

 Assigment -1
Software Requirement Specification(SRS) for
Food Delivery App
1. Introduction

1.1 Purpose:
The purpose of introducing a food delivery app is to provide a convenient and efficient way
for people to order food from their favorite restaurants and have it delivered to their
doorstep. In today's fast-paced world, where time is often limited, many individuals prefer
the convenience of ordering food online rather than going out or cooking themselves. A
food delivery app streamlines this process by bringing together a wide variety of restaurants
and cuisines, allowing users to browse menus, place orders, and track deliveries all from the
comfort of their own homes or offices.

1 .2 Scope:
The scope of developing a food delivery app can be quite extensive, as it
involves various components and features. Here are some key aspects to
consider when envisioning the scope of a food delivery app.

1 .3 Definitions:
OSS- Online shopping System (for electronics item shop)
SRS- Software Requirement Specification
GUI- Graphical User Interface
Stackholder- The person who will participate in system
Ex. Customer, Administrator, Visitor etc.
1.4 References:
[Link]

[Link]
%20objective%20of%20this,them%20into%20their%20potential%20customers

1.5 Overview:
Developing a food delivery app involves conceptualization, UI/UX design, essential
features like menu browsing, ordering, payment integration, order tracking, and
 ratings. Development includes front-end and back-end programming, payment
gateway integration, and testing. Launching requires deployment on app stores,
marketing to attract users, and continuous improvement based on
feedback and analytics.
[Link] Description:
Developing a food delivery app involves creating an intuitive user interface with
features like menu browsing, ordering, and tracking. It includes designing a backend system
for order management, integrating secure payment gateways, and ensuring smooth
functionality. Launching the app involves publishing it on app stores, marketing to attract
users, and gathering feedback for continuous improvement. The goal is to provide a
seamless and convenient platform for customers to order food and for restaurants to
manage their deliveries efficiently.
2.1 Product Perspective:
From a product perspective, developing a food delivery app aims to provide a
convenient and efficient platform for users to order food from a variety of restaurants. The
app focuses on enhancing the user experience by offering intuitive menu browsing, easy
order placement, and real-time order tracking. It includes features like secure payment
integration, customer reviews and ratings, and a robust backend system for order
management. The app aims to streamline the food delivery process, ensuring timely and
accurate deliveries while providing a user-friendly interface for both customers and
restaurant owners.
2.2 Product Functions:
use case:
 2.3 User Characeristics:
User should be familiar with the terms like login,register,order system etc.

2.4 Principle Actors:

2 Principle Actors are Customer and Administrator.

2.5 General Constraints:

A full internet connection is required for APP.

2.6 Assumptions and Dependencies :

Working of APP need Internet Connection.

3. Specific Requirements:

3.1 Functional Requirements:

[Link] Registration: Allow users to create accounts and login securely.
[Link] and Ordering: Provide a comprehensive menu with food options,
prices, and descriptions. Allow users to customize their orders and add
items to the cart.
[Link] Integration: Enable secure and convenient online payment
options, including credit/debit cards, digital wallets, or cash on delivery.
3.1 Description:
3.1.1 Registration
If customer wants to buy the product then he/she must be
registered, unregistered user can’t go to the shopping cart.
3.1.2 Login
Customer logins to the system by entering valid user id
and password for the shopping.
3.1.3 Changes to Cart
Changes to cart means the customer after login or
registration can make order or cancel order of the
product from the shopping cart.
3.1.4 Payment
In this system we are dealing the mode of payment by [Link] will
extend this to credit card,debit card etc in the future.

3.1.5 Logout
 After ordering or surfing for the product
customer has to logout.

3.1.6 Report Generation

After ordering for the product,the system will sent one
copy of the bill to the customer’s Email-address and
another one for the system data base.

3.2 Non-Functional Requirements:

1. Performance: The app should have fast and responsive performance, ensuring quick
loading times, smooth navigation, and minimal latency.
[Link]: The app should be designed to handle a large user base and accommodate
increasing demands without compromising performance.
[Link]: Implement robust security measures to protect user data, transactions, and
prevent unauthorized access.
[Link]: The app should have an intuitive and user-friendly interface, making it easy
for users to navigate, place orders, and track deliveries.

Performance Requirements:
In order to maintain an acceptable speed at maximum number of uploads allowed
from a particular customer as any number of users can access to the system at any time.
Also the connections to the servers will be based on the attributes of the user like his
location and server will be working 24X7 times.

3.3 Technical Issues:

This system will work on client-server architecture.
It will require an internet server and which will be
able to run PHP application. The system should
support some commonly used browser such as IE,
mozzila firefox,chrome etc.

4. Interface
Requirement:
Various interfaces for the product could be-
1). Login Page
2). Registration Form
3). There will be a screen displaying information about
product that the shop having. 4). If the customers select
 the buy button then another screen of shopping cart will
be opened.
5). After ordering for the product,the system will sent one copyof
the bill to the customer’s Emailaddress

Software Interface:
[Link] System:Windows7 Ultimate which supports networking.
[Link] development toolkit.

Hardware Interface:
Hardware requirements for insurance on internet will be same
for both parties which are as follows:
Processor:Dual Core
RAM:2 GB
Hard Disk:320 GB
NIC:For each party
Payment terminals
Push notifications
GPS/Location services
Communication Interfaces:
The two parties should be connected by LAN or WAN for the
communication purpose.

SENDER SENDER Communication channel RECEIVER

5 .System Design Specification:

5.1 Architecture Design:
5.1.1 Data Flow Diagram(DFD):
It is a way of representing system requirements in graphical form;this
led to modular design.A DFD describes a data flow(logical) rather
than how they are [Link] they do not depend upon
software,hardware,data structure or file [Link] is also known
as ‘bubble sort’.
A DFD is a structured analysis and a design tool that can be used for
flowcharting in place of ,or in association with ,information-oriented
and processoriented system flowcharts.
A DFD is considered as an abstract of the logic of information-
oriented or process-oriented system [Link] four basic symbols
used to construct data flow diagrams are-

A rectangle represents a data source or destination.

A directed line represents flow of data.

An Oval represents a process that transforms into

streams.

An Open ended rectangle represents storage.

The points at which data is transformed are called as [Link]

principle processes that take place at nodes are:

[Link] data streams

[Link] data streams
[Link] data streams
Data Flow Diagram (DFD)

[Link] 0 DFD –

[Link] 1 DFD –
 Assigment 4 – ER Diagram

In the Online Food Ordering System we have the following

entities

 User
 Site Information
 Payment
 Order
 Order Details
 Customer
 Rating
 Menu
 Menu Type

Our design of Online Food Ordering System consists of 9

entities; the specified entities will be our database tables in the
design and implementation of Online Food Ordering database
schema.
After we have specified our entities, it is time now to connect or
establish a relationship among the entities.

 The users manage/update the site information (1 to 1

relationship).
 The user processes the orders of the customers (1 to
many relationship).
 The user processes the payment of the customers (1 to
many relationship).
 The customer places their orders (1 to many relationship).
 Order information can contain 1 or more items (1 to many
relationship).
 An order detail contains 1 or more menu (1 to many
relationship).
 The order information will be linked to the payment
module (1 to 1 relationship).
 The customer gives their rating on a menu (1 to 1
relationship).
 A menu has multiple ratings from the customers (1 to
many relationship).
 A menu belongs to a specific menu type (1 to 1
relationship).

This ER Diagram for Online Food Ordering System depicts a

web and mobile-based application that allows a company to
post their menus/foods and accept orders from customers via
this platform. This is similar to an eCommerce platform but is
specifically designed for food ordering. The first step in
developing the Online Food Ordering System is to create the ER
diagram, which will later serve as the foundation for creating
the actual database. The rectangle shape represents the entity.
Later on, the entity will be our Online Food Ordering System
database table. The oval shape represents an attribute. Each
table's columns or fields in the Online Food Ordering will be
listed.
 Assigment 4 – Use Case Diagram

The Use case diagram for online food delivery

system shows the sample behavior of the software. It
includes the project functions using use cases, actors, and
their connections.

Moreover, the diagram assists you to define and organize

project needs. This also provides a clear picture of the
user and system relationships. Therefore, this diagram
depicts the complex functions of a system including how
the user reacts to it.

Use Case Diagram for Online Food

Delivery System using Include and Extend

The use case Diagram using Include and Extend is used to

elaborate the proceeding diagrams. The terms include and
extend are known as indicators.

The label include indicates that the sub-processes of the

main processes must be included to complete the task.
Extend, on the other hand, declares that the sub-
processes can only be performed when needed.
Manage Customers’ Information and Status Use
Case Diagram

This process enables the admin to manage and monitor

customers’ information and status. They were able to
track the customers’ basic information such as contact
numbers and addresses as references for food deliveries.

Manage Food Offered Information Use Case

Diagram

Its process includes the encoding of food information

offered by the restaurant. This process also monitors all
of the transactions related to food such as the count of
the food orders and the remaining available for order.

Manage Deliveries and Payments Use Case

Diagram

This is the process where the admin manages every

transaction made by their customers. It shows the
delivery date, place, and payment for the order. All the
processes said were connected in this main process of the
system.

As a result, this process makes the personnel’s job and

services more manageable and fast.
j
Assigment 4 – Class Diagram
List of classes
1. User
2. Food
3. Payment
4. Driver
Class (User)
Attributes/Variables of the class (User)
Private Attributes/Variables:
There are following private attributes in the mentioned class diagram.
-user_id: int
-user-name: string
-user-address: string
-user-email: string
-user-contact: double

Public Attirbutes/Variables:
There are following public attributes in the mentioned class diagram.
Nil
Functions of the class (User)
There are following functions in the mentioned class diagram.
+register ()
+login ()
+booking ()
+payment ()
+feedback ()
Class (Food)
Attributes/Variables of the class (Food)
Private Attributes/Variables:
There are following private attributes in the mentioned class diagram.
-food_type: string
-food_name: string
-food_id : sting
-food_price : int
Public Attributes/Variables:
There are following public attributes in the mentioned class diagram.
Nil
Functions of the class (Food)
There are following functions in the mentioned class diagram.
+food_type ()
+food_name ()
+food_id ()
+food_price ()
Class (Payment)
Attributes/Variables of the class (Payment)
Private Attributes/Variables:
There are following private attributes in the mentioned class diagram.
-payment_id: int
-amount: int
-payment_details: string
-payment_type: string

Public Attirbutes/Variables:
There are following public attributes in the mentioned class diagram.
Nil
Functions of the class (Payment)
There are following functions in the mentioned class diagram.
+payment_id ()
+payment_info ()
Class (Driver)
Attributes/Variables of the class (Driver)
Private Attributes/Variables:
There are following private attributes in the mentioned class diagram.
-driver_id: int
-driver-name: string
-driver-address: string
-driver-email: string
-driver-contact: double
Public Attirbutes/Variables:
There are following public attributes in the mentioned class diagram.
Nil
Functions of the class (Driver)
There are following functions in the mentioned class diagram.
+driver_details ()
+booking_details ()
+ride_details ()
+payment_details ()
This meta description provides an overview of an Online Food Ordering
System Class Diagram. It explains how this diagram is used to model entities
and their relationships in software development. It also shows how it
visualizes the structural, behavioral and functional aspects of web or mobile
applications, allowing developers to understand and design the software in
an easy and efficient way. The class diagram illustrates the classes,
attributes, operations and the relationships between them such as
inheritance, aggregation, realization, and association. It helps developers
visualize the system for better analysis and implementation.
 Assigment 5 – DFD Diagram

1. Level 0 DFD

Food Ordering System has the following input :

Food order is input as the customer’s order for food.

Food Ordering System has the following output:

Receipt of the order.

For further processing the order, the food order is passed to the kitchen.
The restaurant manager gets the report of Bill and Management.
[Link] 1 DFD –

For processing the order, process 1.0 is responsible. For food, the
housekeeping activities involved are represented by processes 2.0, 3.0, and
4.0. The detailed information about daily sold items should be available to
create and report management and the list of items that are available ‘in-stock’
should be kept by maintaining the inventory data (describes the records of
datasets such as their name, their content, source, many useful information,
etc.) at the same time.
Hence, two data stores are used in this level of DFD given below :
-Database of Sold items
-Inventory database
In the end, with the use of the amount of daily sold items and daily inventory
depletion, it is easy to prepare a report of management. Further, the
restaurant manager gets this report of management.
[Link] 2 DFD –
Detailed information about “Processing of an Order” is shown below :
[Link] 3 DFD –
More detailed information about the activity of the “Generate Management
Report” is given at this level of DFD. Having access to data of sold items and
data of inventory should be available for generating the report of
management. Then, both data of solid items and data of inventory need to be
aggregated after which the restaurant manager should get the report of
management that is prepared from the above calculations.
The above details are shown below: