“BILLING SLIPS FOR FOOD CORRIDORS”

PROJECT PROPOSAL

SUBMITTED TO:

Ms. AFSAH IMTIAZ ELAHI

SUBMITTED BY:

HAIDER ABBAS
(S21BINFT1M01156)

SADAQAT ALI
(S21BINFT1M01136)

M.USMAN
(S21BINFT1M01098)

SANA BATOOL
(S21BINFT1M01157)

DEPARTMENT OF INFORMATION TECHNOLOGY,

THE ISLAMIA UNIVERSITY OF BAHAWALPUR
RE-VISION HISTORY:

DATE TOPIC SUBMITTED SIGNATURE

18-10-2022 INTRO, DOMAIN, SCOPE, PROCESS MODEL

INTRODUCTION:

The Introduction of the software requirements specification (SRS) and providing an overview of
the entire SRS with purpose , project , scope , definition ; acronyms and abbreviation.

The aim of this document is to gather & analyze and give in depth insight of the complete issues
about mess .

The details of the requirement of the mess issues are provided in this document .

DOMAIN:
This project is for Hostel Mess Administration to bill and collects money from their customers
remotely.

SCOPE:
This app is designed especially for Mess.
It is designed to provide a platform for Mess to
better way.

Our App is to provide several facilities such as:

➢ Free advertising by demonstration of Mess.
➢ Sharing experience of Mess owner by images, comments & rating
➢ A chance to enhance the performance of Mess

PURPOSE:
The purpose of the document is to collect and analyze all assorted ideas that have come
up to define the system, its requirements with respect to consumers.
in short, the purpose of this SRS document is to provide a detailed overview of our
software product, its parameters and goals.

This document describes the project's target audience and its Functional requirements,
hardware requirements and software requirements.
Nonetheless, it helps designers and developers to assist in software product development.
PROJECT PROCESS MODEL:

In "The Waterfall" approach, the whole process of software development is divided into
separate phases. In this Waterfall model, typically, the outcome of one phase acts as the input for the
next phase sequentially.

The sequential phases in Waterfall model are −

● 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.
● System 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.
● Implementation − With inputs from the system design, the system is first developed in
small programs called units, which are integrated in the next phase. Each unit is developed
and tested for its functionality, which is referred to as Unit Testing.
● Integration and Testing − All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system is
tested for any faults and failures.
● Deployment of system − Once the functional and non-functional testing is done; the
product is deployed in the customer environment or released into the market.
● 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.
PROCESS MODEL JUSTIFICATION:
We select the waterfall model because our requirements are very well documented, clear and
fixed, the Project definition is stable. A schedule can be set with deadlines for each Development stage
and a product can proceed through the development process model phases one by one.
Development moves from concept, through design, implementation, testing, installation, and
troubleshooting, and ends up with operation and maintenance. Each phase of development proceeds in
strict order.

● Simple and easy to understand and use easy to manage due to the rigidity of the model.
● Each phase has specific deliverables and a review process.
● Phases are processed and completed one at a time.
● Works well for smaller projects where requirements are very well understood.
● Clearly defined stages.
● Well-understood milestones.
● Easy to arrange tasks.
● Process and results are well documented.

TOOLS & TECHNIQUE:

1. JavaScript
2. MySQL
3. React
4. HTML/CSS
5. TAILWIND CSS