INDIRA GANDHI NATIONAL OPEN

UNIVERSITY

A Project Proposal on

“RESTAURANT AND FAST FOOD BILLING SYSTEM”

Name :-Priyanka Kumari

Enrolment Number: -178062907

IGNOU

BCA

NEW HORIZON STUDY CENTER

VIP ROAD, ALLALPATI (DARBHANGA)

1
 INDEX
1. Introduction
2. Objectives
3. Module Description
4. SRS

1. Introduction
1.1. Purpose
1.2. Scope
1.3. Definitions, Acronyms, Abbreviation
1.3. Reference
1.4. Overview
2. General Description
2.1. Product Prospective
2.1.1 System Interface
2.1.2. User Interface
2.1.3. Software Interface
2.1.4. Hardware Interface
2.1.5. Communication interface
2.1.6. Operations
2.2 Product function
2.3. User Characteristics
2.4. General Constraints
2.5. Assumption and Dependencies
3. Specific Requirement
3.1. External Interface Requirement
3.2. Functional Requirement
3.3. Performance Requirement
3.4. Design Constraints
3.4.1. Standard Compliance

2
 3.5. Logical Database Requirement
` 3.6. Software System Attributes
3.6.1. Reliability
3.6.2. Availability
3.6.3. Security
3.6.4. Maintainability
4. DFD

5. ERD

1. Introduction
Restaurant and fast food billing system is windows application software. This is designed
especially for a restaurant which wants to attend their customers in a very well manner.
This system has the capability to take the order from the customer. This software is run on
desktop-computer and laptop. It generates unique transaction of the mode of payment.

This system has the capability of calculating the bill according to the total number of the
item ordered and taxes are also added accordingly then shown to the customer in a proper
bill.

Fast food billing system software basically the software that facilitates the add item,
delete, save and update item list, make payment via credit/debit card, and also print
the bill. This application helps the restaurant to do all functionalities more accurately
and faster way. Food billing system reduces manual works and improve efficiency of
restaurant. This system is use to maintain the stock and cash flows and there are many
more functionalities are: -

 To store records.
 Control order and services.
 Billings.
 Control staff and their shifting.
 Control multiple branches.
 Helps manager to control each part of the restaurant.

3
 Objective
This project will serve the following objectives: -
1. Add and maintain records of available products.
2. Add and maintain Customers details.
3. Add and maintain description of new products.
4. Add and maintain new entered category of products.
5. Provide economical/financial to the owner monthly or weekly.
6. Provide a convenient solution of billing system.

Modules Description
Option

Creation Master Transaction Purchase Report Account Utility Exit

1. Creation: - In this creation module we can change password, add company

information, create user rights and user master.

2. Master: - In this master section we can create table, create service person, create
category, create items/menu, create customer and supplies entry.

3. Transaction: - We can create transaction part for the purpose of print bill, billing
touch screen, and also edit the bills.

4
4. Purchase: - In this module master enter the purchase entry, purchase return, and can
save purchase list for the future use, and save the daily purchase.

5. Report: - The main purpose of report module is, it can store bill wise sale report, bill
item wise sale, daily sale, monthly sale, daily item wise sale, item wise sale, monthly
item wise sale, service man wise sale, category wise sale and stock report.

6. Account: - In this account section user payment bill by debit or credit card via ATM.

7. Utility: - In this utility section, in case if we lose some important data then we can
recover the data by using recovery, and it also use

8. Exit: - In this section we can exit the program.

Data Dictionary
Table name: R_Table

Field name Data type Allow null?

T_name Int Yes

T_type Char(30) Yes

T_size Int No

Table name: E_table

5
 Field name Field type Allow null?

Name Char(20) Yes

Address Char(30) Yes

Phone Int Yes

Code Int Yes

Table name: S_table

Field name Datatype Allow null?

CAT id Int Yes

Name Char(20) Yes

Code Int No

Table name: T_table

Field name Data type Allow null?

Item code Char(10) Yes

Type Char Yes

Name Char(20) Yes

Sale tax Float Yes

Sale rate Float Yes

Cost rate Float Yes

Remarks Varchar Yes

Table name: A_table

6
Field name Datatype Allow null?

Mobile no. Int Yes

Name Char(30) Yes

Email Varchar(20) No

Flat no. Varchar(20) No

Road no. Varchar(20) No

Area Char Yes

City Char(20) Yes

Table name: U_table

Field name Data type Allow null?

Name Char(30) Yes

Address Char(30) No

Code Int Yes

Discount Varchar(30) Yes

VAT Int No

Phone Int Yes

Fax No

Email Varchar(25) No

Table name: N_table

Field name Data type Allow null?

Code Char(25) Yes

7
Rate Float Yes

Tax account Int No

Search Varchar Yes

Tax disc

Table name: B_table

Field name Data type Allow null?

Mobile no. Int Yes

Name Char(25) Yes

Email Varchar(30) No

Flat no. Varchar No

Road no. Varchar No

Area Char No

City Char Yes

Subtotal Int Yes

Disc rate No

Other charges Int Yes

Credit Int Yes

Debit Int Yes

Balance Int Yes

8
Table name: C_table

Field name Data type Allow null?

Memo no. Int No

Date Int Yes

Order time int Yes

Mobile no. Int Yes

Customer Char Yes

Bill amount Float Yes

Cash amount Int Yes

Card amount Int Yes

Table name:C_table

Field name Data type Allow null?

Bill no. Int Yes

Gross Varchar Yes

Good ret No

Discount Int Yes

Net amount Int Yes

Cash Int Yes

Credit Int Yes

Name Char(30) Yes

Address Char(30) No

9
Table name:F_Name

Field name Data type Allow null?

Name Char(25) Yes

Quantity Int Yes

Rate Int Yes

Total Int Yes

Testing level
Why do we test software systems?
To gain the confidence by providing them a quality product. Software testers are the
main enforcers of quality. Hence, Software testing is the entire process of verifying a
system with the purpose of identifying any missing errors, gaps or requirement versus
the actual necessities

There are three types of testing that are following: -

1. Unit testing: - Unit Testing is a level of software testing where individual units/
components of a Software are tested. The purpose is to validate that each unit of the
software performs as designed. A unit is the smallest testable part of any software. It
usually has one or a few inputs and usually a single output. The main purpose of using
unit testing is to segregate each part of the program and test that the individual parts
are working correctly.
2. Integration testing: - INTEGRATION TESTING is a level of software testing where
individual units are combined and tested as a group. The purpose of this level of testing is to
expose faults in the interaction between integrated units. Test drivers and test stubs are
used to assist in Integration Testing. Integration tests catch system-level issues, such as a
broken database schema, mistaken cache integration, and so on.

3. System testing: - System Testing (ST) is a black box testing technique performed to
evaluate the complete system the system's compliance against specified requirements.
In System testing, the functionalities of the system are tested from an end-to-end
perspective.

10
 4. User acceptance testing (UAT): - User acceptance testing (UAT) is the last phase of the
software testing process. The goal of User Acceptance Testing is to assess if the system can
support day-to-day business and user scenarios and ensure the system is sufficient and correct
for business usage.

SRS
1. Introduction
Purpose

The purpose of developing restaurant and fast food billing software is to provide all works
related to restaurant and fast food billing software performed on Computer system. It is
enable to maintain all fast food detail and customer detail related task, payment related
task, sending information about payment, notice etc.

Scope

Benefits

This software reduces the manual work, maintaining accuracy, increasing efficiency and
saving time.

Overview

This system provide easy to solution staff’s to maintain and also customer to take message
and receipt.

General Description
1.1. Product Perspective
1.1.1. System Interface

The software fast food billing software interact with system using Windows 7 and above
operating system. System contain at least 1 GB RAM and 50 GB space on hard disk for
running the application.

11
1.1.2. Hardware interface

We can operate software fast food billing system using mouse, keyboard, monitor, and
printer. Screen resolution of at list 800*600 is required for proper and complete viewing of
screens. Higher resolution will be accepted.

1.1.3. Software Interface

In development of the software fast food billing following software are use:

 Any windows based operating system.

 Text editor such as notepad.
 SQL database.
 Visual studio
 Software written in PHP language.
1.1.4. Communication Interface

The software written in English so user must know English language. User can
communicate with software in English language.

12