INTRODUCTION

The project “Restaurant Billing System” is a basic program used in restaurants.

The main aim is to perform the process of ordering and billing of a “Restaurant”.

This system is named as Restaurant Billing System. This is designed especially for
a restaurant which wants to attend their customers in a very well manner. This
system has the capability to give the receipt, in which GST is also included, to the
customers.

The program is easily executable and can be easily accessed by a user. It is great
software for saves time and decreases the work of the owner of the restaurants.

OBJECTIVES
 To provide a computer-based billing system for an accurate computation of
bills.
 To reduce the time, energy, and resources that was being consumed when
performing a billing for the customer.
 To generate a receipt when performing a service.
 To provides a convenient solution of billing pattern.

1
 FEASIBILITY STUDY
This is the measure of how beneficial or practical the development of an
information system will be to an organization. It is aimed at establishing whether it
is worthwhile developing the new system. The area introduces the system in terms
of research into why it is more viable than the existing system. Three main areas of
feasibility study are identified: Operational Feasibility,
Technical Feasibility, Economic Feasibility. The following study was carried out
to establish whether the system development will carry on to the next stage:

OPERATIONAL FEASIBILITY:

The Billing system will save time for workers of restaurant. By use of their
computer systems, workers of restaurant give bills to the customers. By the help of
this software, paper work is reduced.

This saves both time and money.

TECHNICAL FEASIBILITY:

Technical feasibility centers on the existing computer system (Hardware, Software,

etc.) and to what extent it can support the proposed system.

ECONOMIC FEASIBILITY:

The procedure is to determine the benefits and savings that are expected from a
user system and compare it with the costs. If a benefit outweighs costs, then the
decision is made to design and implement the system. Otherwise further alterations
are made in the proposed system

 Manpower cost
 Hardware and software cost

2
DATA FLOW DIAGRAM

3
ER- DIAGRAM

4
 HARDWARE & SOFTWARE REQUIREMENTS

 HARDWARE:

CPU Configuration
RAM

OPERATING SYSTEM:

Windows 8

 SOFTWARE:

Language Used: C
CodeBlock (For Compiling and executing the program)

5
 MODULES

 Bills Management Module: Used for managing the Bills details.

 Payment Module: Used for managing the payment details.
 Receipt Module: Used for managing the Receipt information.
 Users Module: Used for managing the users of the system.

REPORTS OF FOOD BILLING SYSTEM

 It generates the report on bills, customer
 Provide filter reports on Payment, Receipt

SCOPE
 This project will help the user in fast billing.
 It will generate receipt on every transaction inputted to the system.
 The software will display view of calculations of every transaction.

6
SRS

7
 SYSTEM REQUIREMENT PHASE
 Project Title:

Restaurant Billing System

 Technology:

Front End: C

 Modules:

 Bills Management Module: Used for managing the Bills details.

 Payment Module: Used for managing the payment details.
 Receipt Module: Used for managing the Receipt information.
 Users Module: Used for managing the users of the system.

8
 Hardware and software requirement

 HARDWARE:

CPU Configuration
RAM

OPERATING SYSTEM:

Windows 8

 SOFTWARE:

Language Used: C
CodeBlock (For Compiling and executing the program)

9
 SYSTEM ANALYSIS PHASE
Information gathering
Information gathering is done by interviewing the users and reviewing the
existing documents. For the development of Restaurant Billing system a lot of
research and important input from various website and application user was
needed. Hence the following questionnaires were provided to them and hence
need for our website arises

User Requirement
 Need for an application that makes communicating easy and comfortable.
 An application that enables user to calculate the bill of the customers.
 Need for an application that is easy to use and widely available and hence a
web application.
 Handling all functions done with organization in a computerized manner.

Functional Requirement
 Admin need to insert all details about customer.
 Admin must generate a bill with GST.

Non-functional Requirement
 Usability: This website has appropriate user interface and adequate
information to guide the user in order to use the website.
 Portability: The website is portable as it is online website running across the
net
 Flexibility: It is very flexible
 Security: This website provide user and authentication so that only the
legitimate user are allowed to use the website
 Maintainability: This website is capable to secure the data and easily retrieve
the data.
 Scalability: This system can further modified in future.

10
 SYSTEM PLANNING PHASE
Feasibility Study

This is the measure of how beneficial or practical the development of an

information system will be to an organization. It is aimed at establishing whether it
is worthwhile developing the new system. The area introduces the system in terms
of research into why it is more viable than the existing system. Three main areas of
feasibility study are identified: Operational Feasibility,
Technical Feasibility, Economic Feasibility. The following study was carried out
to establish whether the system development will carry on to the next stage:

 OPERATIONAL FEASIBILITY:

The Billing system will save time for workers of restaurant. By use of their
computer systems, workers of restaurant give bills to the customers. By the help of
this software, paper work is reduced.

This saves both time and money.

 TECHNICAL FEASIBILITY:

Technical feasibility centers on the existing computer system (Hardware, Software,

etc.) and to what extent it can support the proposed system.

 ECONOMIC FEASIBILITY:

The procedure is to determine the benefits and savings that are expected from a
user system and compare it with the costs. If a benefit outweighs costs, then the
decision is made to design and implement the system. Otherwise further alterations
are made in the proposed system

 Manpower cost
 Hardware and software cost

11
 SYSTEM IMPLEMENTATION
PHASE

Cost Benefit Analysis:

Cost benefit analysis (CBA) estimates and total up the equivalent money value of
the benefits and the cost invested to for implementation the software .Cost benefit
analysis (CBA) is the weighing scale approach to decision-making. All the plus
points (such as cash flow and other intangible benefits) are put on one side all the
minus points (the cost and disadvantages) are put on the other side. Both sides
should be weighed and benefits should be evaluated.

Cost Estimation:

A cost estimate is the approximation of the cost of a program, project, or

operation. The cost estimate is the product of the cost estimating process. The
cost estimate has a single total value and may have identifiable component values.

For a given set of requirements, it is desirable to know how much it will cost to
develop the software to satisfy a given requirement, and how much time
development will take. The cost of a project is a function of many parameters.
Foremost among them is the size of the project. Other factors that effects the cost
are programmer ability, experience of the developers in the area , complexity of the
project, and reliability requirements of the software, hardware and human
resources

Benefits:

 Improves business processes leading to annual cost decrease.

 Due to availability of information, better decision making is possible
leading to additional cash flows.

12
 SYSTEM MAINTENANCE
System Maintenance and Evaluation:

System Maintenance is a modification of the software product after delivery to

accomplish one of the following objectives:

 Correct faults.
 Improve the performance or other attributes
 Adapt the product to the change environment

The term support and maintenance describes activity that occur after a system is
made operational. Support activities assist users in realizing the full benefits of the
system. It ensures that the system function at peak efficiency and the needed
changes are implemented with minimal disruption to the organization.

The performance of the system can be measured by two factors, viz. the efficiency
and effectiveness. The efficiency indicates the manner in which the inputs are used
by the system .If the input-output ratios is adverse, we say that the system is
inefficient though it produces the desired output or not .When the system is
ineffective, the system is out of control and it needs a major correction. A system
has to be effectiveness is a measure of the productivity i.e. the measure of the
output against the input.

Throughout the Lifecycle of the project it is put through test against efficiency and
effectiveness quite frequently. The stronger the system is, the lesser maintenance
the system requires. As of now ,there is no significant maintenance policy adopted
or proposed for the system.

13
Security:

The system security problem can be divided into four relates issues: security,
integrity, privacy and confidentiality. They determine the file structure, data
structure and access procedures.

System security an (operating) system is responsible for controlling access to

system resources, which will include sensitive data. The system must therefore
include a certain amount of protection for such data, and must in turn control
access to those parts of the system that administer this protection. System security
is concerned with all aspects of these arrangements.

System Integrity

State of a system where it is performing its intended functions without being

degraded or impaired by changes or disruptions in its internal or external
environments.

That condition of a system wherein its mandated operational and technical

parameters are within the prescribed limits.
The state that exists when there is complete assurance that under all conditions an
IT system is based on the logical correctness and reliability of the operating
system, the logical completeness of the hardware and software that implement the
protection mechanisms, and data integrity.

Confidentiality, integrity and availability, also known as the CIA triad, is a model
designed to guide policies for information security within an organization. The
model is also sometimes referred to as the AIC triad (availability, integrity and
confidentiality) to avoid confusion with the Central Intelligence Agency.

14
 SYSTEM TESTING PHASE
Testing Process
Testing is a process to show the correctness of the program. Testing is needed to
show completeness, it improve the quality of the software and to provide the
maintenance aid. Some testing standards are therefore necessary reduce the testing
costs and operation time. Testing software extends throughout the coding phase
and it represents the ultimate review of configurations, design and coding. Based
on the way the software reacts to these testing, we can decide whether the
configuration that has been built is study or not. All components of an application
are tested, as the failure to do so many results in a series of bugs after the software
is put to use.

 Black box Testing

Black box testing, also called behavioral testing, focuses on the functional
requirements of software. This testing approach enables the software engineer to
derive the input conditions that will fully exercise all requirements for a program.
Black box testing attempts to find the errors like

 Incorrect or missing functions

 Interface errors
 Errors in data structures or external database access
 Behavior or performance errors
 Initialization and termination errors

In Black box testing software is exercised over a full range of inputs and outputs
are observed for correctness.

 White box Testing

White box testing is also called Glass box testing is a test case design control;
structure of the procedural design to derive test cases using White box testing
method, the software engineer can derive the test cases that guarantee that all
independent paths within the module have been exercised at least once. Exercise
all logic decisions on their true or false sides. Execute all loops at their boundaries
and within their operational bounds. Exercise internal data structure to ensure their
validity.

15
  Software Testing Strategies
Testing involves

 Unit testing
 Integration testing
 Acceptance testing

The first level of test is unit testing. The purpose of unit testing is to ensure
that each program is fully tested.

The second step is integration testing. In this individual program units or

programs are integrated and tested as a complete system to ensure that the software
requirements are met.
Acceptance Testing involves planning and the execution of various types of tests in
order to demonstrate that the implemented software system satisfies the
requirements. Finally our project meets the requirements after going through all the
levels of testing.

16
 SYSTEM TEST REPORT
Test Cases

Test Cases are good in revealing the presence of faults. Successful in

implementation of test cases implies that there is no error in program. Test cases
should be minimum as they are expensive in case of money & efforts. Primary
objectives of test cases are to ensure that if there is an error or fault in program it is
exercise by the test cases. An ideal test case set is one that succeeds only if there
are no errors in the program. One possible ideal set of test case is one that includes
all possible I/P to the program and is called exhaustive testing. A test case is good
if it detect in undiscovered error in program.

CONCLUSION
This Project is minimizing the task of billing an order by paying. In this the billing
is safe and secure. This project is done as Efficient as possible

Hereby I, the Student of MCA 5th Semester conclude that the project was
completely and slowly developed by me. I would be glad to enhance and promote
this project if given chance and help ourselves and society in the near future

The developed application is tested with sample inputs and outputs obtained in
according to the requirement. Even though I have tried our level best to make it a
dream project. Due to time constraints I could not add more facilities to it.

The efficiency of the developed system can be enhanced with some minor
modifications. Future development can be made in proposed system by integration
more services like:

 It can be implemented through web pages.

 New effectives modules can be added time to time

17
 SCOPE
 This project will help the user in fast billing.
 It will generate receipt on every transaction inputted to the system.
 The software will display view of calculations of every transaction.

18
19