0% found this document useful (0 votes)
61 views49 pages

Cafe Billing

The document describes a cafe billing system created to automate the billing process for restaurants. It was developed using the waterfall model and allows users to manage employee and menu items, take customer orders, generate bills, and view reservation and billing history. The system aims to increase efficiency by reducing paperwork and speeding up tasks like billing compared to a manual process. It has functions for staff management, order placement, menu management, reservations, and accessing order histories. The technical requirements include a Windows OS, .NET framework, and SQL database to store information.

Uploaded by

Vaibhav Jajodiya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
61 views49 pages

Cafe Billing

The document describes a cafe billing system created to automate the billing process for restaurants. It was developed using the waterfall model and allows users to manage employee and menu items, take customer orders, generate bills, and view reservation and billing history. The system aims to increase efficiency by reducing paperwork and speeding up tasks like billing compared to a manual process. It has functions for staff management, order placement, menu management, reservations, and accessing order histories. The technical requirements include a Windows OS, .NET framework, and SQL database to store information.

Uploaded by

Vaibhav Jajodiya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 49

INTRODUCTION

The “Cafe Billing System” is an application to automate the process of information


recording and billing of a restaurant. This desktop based application is designed to
administer its users and customers. RBS is a billing system, made for the effective
utilization of modern technology in the organization. It is an automated software
that can handle a lot of information about the restaurant’s employees, order
history, reservation data.

It has the capability to process bills and gather information about its employees
and billing history. It is designed for the sole purpose of efficiency, speed and
accuracy. Waterfall Model is used to develop this software where different
requirements are identified at first, analyze the requirements then design the
software using various tools and techniques and using the development language
the software is developed. Different testing like unit testing and integration
testing are done during the development process.

BACKGROUND
A restaurant is a business which prepares and serves food and drinks to
customers in exchange for money, either paid before the meal, after the meal, or
with an open account. Meals are generally served and eaten on premises.
Restaurants vary greatly in appearance and offerings, including a wide variety of
cuisines and service models ranging from inexpensive fast food restaurants to
high-priced luxury establishments.
Restaurants are one of the growing business in recent times. In Nepal, many
restaurants are doing very well by providing quality service to its customers. It has
to deal with a lot of information about its client and employees, all of which are
kept and recorded manually and physically in a drawer or a room. Due to this
situation, finding any reliable data when required and in time is not possible.
Objective of Project
The main objective of this software is a computerized working environment. This
system is made on the assumption that the organization is fully requires manual
work for any task.
This project will serve the following objectives:
 To add and maintain records of available menu.
 To add and maintain employee details.
 To add and maintain description of new menu.
 To provide view of transaction to the owner.
 To provide a convenient solution of billing pattern.
 To make an easy to use environment for users.
 Easy to use system.

Problem Definition

The billing process is done manually by manpower. It results in delayed time for
the consumer and to the organization while the bill is being processed. So, there
is a room for improvement here. A certain computer based billing system could
aid the organization to utilize its resources better. Computerized Billing System
provide capabilities for entering client, employee and payment information,
building a record and managing other related data needs in the organization.
The currently used system contains the following problems which are listed
below:
 Inability of modification of data
 Manual operator control
 Lots of paperwork

Project Overview
Cafe Billing System is a computer based billing system with user friendly interface
which automatically manages the billing process of the customer very easily
taking only a short period of time. The system can large amount of data and also
generates bill for the customer. Billing history, reservation information and staff
information can also be obtained with the use of café billing. It is an automated
desktop based software which has a simple design and very easy to use also. This
project’s main focus is on proper management of information regarding the staffs,
billing and reservation records. It is also specialized in automatically processing
the customer bills and discounts. The proposed system either does not require
paper work or very few paper works are required. All the data is fetched into the
computer immediately and various bills can be generated through computers.
Since all the data is kept in a database, no data of the organization can be
destroyed. Moreover works become very easy because there is no need to keep
data on papers.

Scopes and Limitations


The software has a lot of features and advantages over the paper based billing
system.

It has the following scopes:

 This project will help the employee in fast billing.


 The project will enable to see free reservation available.
 Quality and faster service can be given to the customers. 5
 Easy to maintain in future prospect.
 This project enable employees to maintain a great database of information
regarding the billing and reservation.
The limitations of this system are as follows:
 It is a desktop based software. A wider reach of customers cannot be obtained.
 Insufficient time for development.
 Need further more improvements for high class restaurants.
 Employees/staffs should be trained at first to use this system.

FUNCTIONAL REQUIREMENTS

A functional requirement defines a function of a system and its components. This


subsection presents the identified functional requirements for Cafe which are
listed below.
 Staff management –
The admin has the full power to manage (add, delete, update, view) the staffs’
records. RBS provides an easy view of the staff records from which the
management of the staffs can be done.
 Make order –
The staffs can record orders by simply selecting the category and type of the item
or meal. The order will be added to database.
 Billing –
The orders made can be billed as well. The staffs as well as the admin can make
bills of the orders made by the customers easily.
 Menu management –
The admin can manage the menu of the restaurant. He/she can add, delete,
update or view the menu of the restaurant.
 Reservation –
Table can also be reserved by the customers by phone. The customer will get a
unique reservation number.
 Order history –
History of the billing or transaction can be viewed easily.
 To-do list –
Users can add tasks to be done as well as clear the task from the list after its
completion.

Non-functional requirements
The following are the non-functional requirements of cafe:
Consistency- This system provides consistency user interface design to the user.
The designs of the screen are standardize and consistent that make the user feel
comfortable to use it.
 Convenience –
The system gives convenience to the user to perform different activities like
making order, menu managing, staff management, etc.
 Usability –
The software is ready to use system. The users will feel easy to use the system
without much technical expertise.
 Security –
This system provides the password security access control to avoid unauthorized
user to login to the system. The system also authenticates the staff level to access
to some of the admin part.
 Reliability –
The restaurant billing system provides effective method to maintain the back-end
of the system. All the orders are managed by this system effectively.
 Scalability –
It has the capacity to handle a growing amount of work and its potential to be
enlarged in order to accommodate that growth.

Technical feasibility
Technical feasibility canters on the existing computer system (hardware,
software) and to what extent it can support the proposed system.
The technologies used in this project are:
Software:
Front End
 Language used: .net
 SQL Operating System:
 Windows XP and higher.
Our system requires window operating system which is easily available.

Hardware:
 Intel based processor run computer system, which have keyboard and mouse as
input devices.
 This has been decided for the case of availability and up-gradation.
Economic feasibility

This feasibility study is to determine the benefits and savings that are
expected from a system and compare it with its 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.
Some of the costs to be considered are:
• Manpower cost
• Hardware and software cost

Operational feasibility

People are inherently resistant to change and software or applications


have been known to facilitate change. In this project, a technical team is
required to configure the software. Technical background on Java,
database is important.

For users/customers, a short seminar or demo can be given so that they


will be familiar with the software. They do not require much technical
expertise to use Cafe software.

GENERAL ARCHITECTURE

The general architecture of the application is shown in the figure below.


Figure 1: General Architecture of the system
1.1 Use case diagram

A use case diagram is a graphical representation of the interaction


among the elements of a system. A use case is a methodology used in a
system analysis to identify, clarify and organize system requirements.
Figure 2: Admin Function
Figure 3: Employee Function

1.2 Class Diagram

A class diagram is an illustration of the relationship and source code


dependencies among the classes in the Unified Modelling Language
(UML). In this context, a class defines the methods and variables in an
object, which is specific entity in a program or the unit code representing
the entity.

Restaurant Reservation Customer


- reservation + addReservation() - cId
- menu + releaseReservation() - cName
- customer - cOrder
+ addReservation() + giveOrder()
+ releaseReservation()
+ genertateBill()
+ addCustomer()

Menu
Menu : List<item>
+ giveMenu()
+ display()
Order
- oId
+ addOrder()

< issue >

Item ItemOrder
- ItemId - iItem
- ItemName - inumberOfPlates
- ItemPrice -memberName
+ getItemId() + getItem()
+ setItemId(ItemId) : void + setItem(item) : void
+ getItemName() + getNumberOfPlates()
+ setItemName(ItemName) : void + getNumberOfPlates(): void
+ getItemPrice()
+ setItemPrice(ItemPrice) : void

Bill
- Order
- BillId
+ calculateTotal()

Figure 4: Class Diagram


1.3 Sequence Diagram

Sequence diagram is an user friendly representation of an use case


diagram which provides the sequential steps used in making the
application. It helps to understand the different process that happens
inside the system. There are several sequence diagram in this project
which are given below:

1.4 Admin Login

This sequence diagram shows the different steps how admin


can log in, first admin input his / her username and password
then it checks whether the entered values are right or wrong if
the data are in database and are for admin login then it will
open admin dashboard otherwise it will give an error message.
Figure 5 shows the process.
Figure 5: Admin Login

1.5 Add User

This sequence diagram shows the different steps how admin can add
new user, after admin login to the application he /she clicks on the add
user option which opens add new user page. Then admin can add new
user by filling up the necessary details like (Name, Gender, Contact,
Address, Salary, username, password) and click add employee button.
Then the request is sent to the database ,here the entered parameters
are checked to make sure that the entered data are correct. If all the
entered data are correct then new user is created in the database
otherwise error message is displayed.
Figure 6: Add User

1.6 Edit User

This sequence diagram shows the different steps how admin can edit or
update the user information, after admin login to the application he /she
clicks on the staff option in the dashboard which opens edit user page.
Then admin can make all the necessary changes to the staff information
and click edit employee button. Then the request is sent to the
database ,here the entered parameters are checked to make sure that
the entered data are correct. If all the entered data are correct then new
user is created in the database otherwise error message is displayed.
Figure 7: Edit user

1.7 Delete User

This sequence diagram shows the different steps how admin can delete
the user account, after admin login to the application he /she clicks on
the staff option in the dashboard which opens delete user page. Then
admin can simply click on the employee to be deleted and click on
delete employee button. Then the request is sent to the database and
returns the success message.
Figure 8: Delete user

1.8 User Login

This sequence diagram explains the various steps that are needed for the
user to log in the application. First user enters his / her username and
password, for the very first login they must enter user name and
password assigned by the admin. Once the login details are entered and
clicked on login button, the request goes on to validate user which
checks in the database. If the entered details are found in the database,
the user can view dashboard otherwise the application will show an
error message.

Figure 9: User Login

1.9 User Password Change

This sequence diagram shows the step by step process how user can
change their password. First user log in with their old password once
they are logged in they can click change password option from menu and
enter their old password and new password they want to update and
click on Ok button.

Figure 10: User Password Change

1.10 Reservation

This sequence diagram show how the reservations are made. First the
booking request is made by the customer then employee checks if there
is any free table if there is one then booking is confirmed if not then the
customer waits in line. Figure 11 below shows this process.

Figure 11: Reservation

1.11 Billing

This sequence diagram show step by step process of how billing is done
once the customer is done with the meal, he/she ask for the bill and staff
first click on the billing page and enters all the item's the customer had
then the application shows the total amount include service tax and VAT
and the user click on print bill option which prints the bill and all the
items ordered by the customer are stored in the database. Figure 11
shows the process in detail.

Figure 12: Billing

2 DATA MODELING

Data modelling is often the first step in database design and object-
oriented programming as the designers first create a conceptual model
of how data items relate to each other. Data modelling involves a
progression from conceptual model to logical model to physical schema.
2.1 Database

In this we design and configure the database for the applications. Since the
application is desktop application, we setup database in the local host server.

2.2 Design of the Database

The MySQL database is used to design the database. The database name
is café it is in the local computer.

2.3 ER Diagram

An entity relationship diagram (E-R diagram) is a graphical


representation of an information system that shows the relationship
between people, objects, concepts or events within that system. An E-R
diagram is a data modeling technique that helps define business process
and can be used as the foundation of the relational database.
Figure 13: ER Diagram

The ER diagram describes the relationship between the different tables


in the database.

Admin: This table is only for admin, admin username and password are in
this table.

Employee: This table consists of details of all the employees like name,
address, contact info, salary.

Category: This table consists of all the different type of food category available.

Menu: This table consists of all the menu available.


Reservation: This table shows all the tables that are reserved for now and
also for the future.

Billing history: This table consists of bill achieve, admin can view this table
to know how the business have been progressing so far.

Figure 14: Database tables of the application


3 CODING TOOLS

There are various tools available for the development of a project. Our
Restaurant Billing System software has been developed using the front
end java and back end MySQL. Following tools are used for the RBS
project.

Java is general purpose programming language that is class-based, object-


oriented specifically designed to have few complexity as possible.
Together is a diagramming and vector graphics application that has been used
to design system models like, Use-Case Diagram, Sequence Diagrams and so
on.

• Windows launcher generator, that is included for free when you


purchase j. exe is useful if you want to create a Java launcher without
an installer.

3.1 User Interface

This part provides a detail description of the user interface for the application.
There are two user interfaces.

Admin’s Interface and

User's Interface

3.2 Login Page

The login page allows the manager to log in to a dashboard/home page


using username and password. The manager can log in using the user
name and password created while developing this application and once
he/she successfully log in then he/she can create other user's as well as
admin users.
Scope Of The Project

It may help collecting perfect management in details. In a very short time, the
collection will be obvious, simple and sensible. It will help a person to know
the management of passed year perfectly and vividly. It also helps in current
all works relative to Inventory. It will be also reduced the cost of collecting the
management & collection procedure will go on smoothly.

The present project has been developed to meet the aspirations indicated in
the modern age. An attempt has been made through this project to do all
work ease & fast. It provide current add, Update, Move Next, Move
Previous , Move Last, Find & Delete all facilities to accomplish the desired
objectives. The facility Include in this project and the suggested activities have
been organized to impart knowledge & develop skill & attitude in the Service
official works.

(i) System Design (Introduction):

The systems objectives outlined during the feasibility study serve as


the basic from which the work of system design is initiated. Much of the
activities involved at this stage is of technical nature requiring a certain degree
of experience in designing systems, sound knowledge of computer related
technology and through understanding of computers available in the market
and the various facilities provided by the vendors. Nevertheless, a system
cannot be designed in isolation without the active involvement of the user.
The user has a vital role to play at this stage too. As we know that data
collected during feasibility study wills we utilized systematically during the
system design. It should, however be kept in mind that detailed study of the
existing system is not necessarily over with the completion of the feasibility
study. Depending on the plan of feasibility study, the level of detailed study
will vary and the system design stage will also vary in the amount of
investigation that still needs to be done. This investigation is generally an
urgent activity during the system. Sometimes, but rarely, this investigation
may form a separate stage between feasibility study and computer system
design. Designing a new system is a creative process, which calls for logical as
well as lateral thinking. The logical approach involves systematic moves
towards the end product keeping in mind the capabilities of the personnel and
the equipment at each decision making step. Lateral thought implies
encompassing of ideas

Beyond the usual functions and equipment. This is to ensure that no efforts
are being made to fit previous solutions into new situations.

ii) Considerations: System Design

The system design process is not a step-by-step adherence of clear procedures


and guidelines. Though, certain clear procedures and guidelines have emerged
in recent days , But still much of design work depends on knowledge and
experience of the designer. When designer starts working on system design,
he will face different type of problems. Many of these will be due to
constraints imposed by the user or limitations of the hardware and software
available in the market. Sometimes, it is difficult to enumerate the complexity
of the problems and solutions thereof since the variety of likely problems is so
great and no solutions are exactly similar.

iii)Design Objectives:

The primary objective of the design of course, is to deliver the requirements as


specified in the feasibility reports. In general the following design objectives
should be kept in mind.

Practicality

The system must be stable and can be operated by people with average.

Efficiency

This involves accuracy, timeliness and comprehensiveness to the system


output.

Cost

It is desirable to aim for a system with a minimum cost subject to the


condition that it must satisfy all the requirements.

Flexibility

The system should be modifiable depending on the changing needs of the


user. Such modifications should not entail extensive reconstructing or
recreation of software. It should also be portable to different computer
systems.

Security
This is very important aspect of the design and should cover areas of hardware
reliability, fall back procedures, physical security of data and provision for
detection of fraud and abuse.
System design involves first logical design and then physical construction of
the system. The logical design describes the structure and characteristics of
features, like the outputs, inputs, files, database and procedures. The physical
construction, which follows the logical design, produces actual program
software, files and a working system.

System Configuration
i) HARDWARE CONFIGURATION:

CPU TYPE : Dual Core


CPU CLOCK MEMORY : 2.66 GHz Extend
RAM DDR II : 2 GB
Disk drive : DVD Writer
Keyboard : Any
Display type : LCD monitor
Printer type : laser print
Speed : 1.1 GHz
Hard Disk : 500 GB
Mouse : optical

ii) SOFTWARE CONFIGURATION:

Operating System : Windows 7


Front End : .net
Back End : Ms Access
Software Selection

OPERATING SYSTEM

Operating system software is a class of program which manages the


resources of the computer processing command and control program execution
as the translation of all computer operations. It is most complex program
executed on the complex yet must also be the most reliable. An operating
system irrespective of whether it is being used on a microcomputer,
minicomputer or mainframe computer. An operating system plays three basic
roles as a manager, as a command processor and as a controller. An operating
system can be a single user, a multiuser, a multitasking in this project we have
used Window 7 and MS Dos as operating system.

M.S.WORD
Microsoft word was first released in 1983 under the name multi-tool
word for system versions were later written for several other platforms. It
became part of the suite, in which it is referred to as Microsoft office word,
although it is still also sold as a standalone product or bundled with a full
featured word processing program for windows and the Macintosh from
Microsoft, it is sophisticated program with rudimentary desktop publishing
capabilities that has become the most widely used word processing applications
on the market the first various of word come out under dos and provided both
graphics-based and text-based interfaces for working with a document.

WINDOW 7
The difference being that the server Versions are designed to be dedicated
servers. The clients versions of windows may also share data over the network
and can be configured to grant access to all are specific files only. Windows
PC’s are used to access a verify of servers on the networks, including windows
servers, UNIX, Linux and network servers and mainframes. The most widely
used operating system for desktop and Laptop computer developed by the
Microsoft window primarily runs on the x 86-based CPU windows provide a
graphical user interface and desktop environment in application displayed in
resizable movable windows on screen. Window comes in both client and server
various, all of which support networking Windows 95 was the first 32-bit
windows operating system and a major upgrade from windows 3.1 it used an
entirely different user interface that incorporated the now common start menu
and taskbar. It was also the first time the computer booted directly into
windows, rather than being loaded after booting up in dos. Windows 98 was an
upgrade to Windows 95 that tightly integrated the internet explorer, web
browser with the O/S. In 1999 windows 98 second edition fixed numerous bugs
and upgraded its applications.

MS-DOS

Ms-dos (for micro soft disk operating system) is a commercialized by


Microsoft. It was the most widely used member of the family of operating
system and was the dominant .The operating system for during the 1980’s it has
gradually been replaced on customer desktop computers with various
generation of the operating system.dos commonly refers to the family of
closely related a single user operating system from Microsoft for the PC. It was
the first O/S for windows 3.1, 95, 98 , Window NT 2000, XP and 7 emulate dos
in order to support existing dos application.
VB.Net2010

Visual Basic.NET is the next generation of Microsoft's popular Visual Basic


programming languages. Some programmers refer to the new incarnation as
VB.net, but this is incorrect. VB.net is actually not backwards-compatible with
VB6, meaning that code written in the old version will not compile under
VB.net. In fact, the languages are sufficiently different that many programmers
consider them independent. As a language, VB.net has the following traits:

Object-Oriented:-

VB.NET included limited support for object-oriented design.


Encapsulation was supported with Public and Private Data types in Classes, as
well as special accessory /matador Pairs called Properties (a feature unique to
Visual Basic). Polymorphism received crude Support through the Implements
keyword, which would require that one class implement all of the methods in
another, skeleton class. Inheritance was neglected completely. As of VB.NET,
all of this has changed. As with all 2013 languages, concepts, VB.NET includes
full-Blown support for object-oriented

Including simple inheritance. Unlike most other OOP languages, everything in


VB.net is an object, including all of the primitives (Short, Integer, Long, String,
Boolean, etc.) as well as types, events, and even assemblies. Everything inherits
from the Object base class.

Event-Driven:-

All previous versions of Visual Basic.net were event-driven, but this feature is
heavily enhanced under the vb.net framework. Events are no longer recognized
because they use certain naming convention (Object Name Event Name), but
now are declared with a Handles Object Name. Event Name clause. Event
handlers can also be declared at runtime using the Add Handler command.

System Analysis

The system analysis part is done by the following six steps

I. Preliminary Investigation
II. Feasibility Study
III. Fact Finding Techniques
IV. Cost Benefit Analysis
V. Entity Relationship Model
VI. Data Flow Diagram
VII. Normalization
i) Preliminary Investigation

   Here in the project Hotel Management System, a detailed study of existing


system is carried along with all the steps in system analysis. An idea for
creating a better project was carried and the next steps were followed. A
detailed study of the process must be made by various techniques like
interviews, questionnaires etc. The data collected by these sources must be
scrutinized to arrive to a conclusion. The conclusion is an understanding of
how the system functions. This system is called the existing system. Now the
existing system is subjected to close study and problem areas are identified.
The designer now functions as a problem solver and tries to sort out the
difficulties that the enterprise faces. The solutions are given as proposals. The
proposal is then weighed with the existing system analytically and the best
one is selected. The proposal is presented to the user for an endorsement by
the user. The proposal is reviewed on user request and suitable changes are
made. This is loop that ends as soon as the user is satisfied with
proposal.  Preliminary study is the process of gathering and interpreting facts,
using the information for further studies on the system. Preliminary study is
problem solving activity that requires intensive communication between the
system users and system developers. It does various feasibility studies. In
these studies a rough figure of the system activities can be obtained, from
which the decision about the strategies to be followed for effective system
study and analysis .

ii) Feasibility Study

An important outcome of the preliminary investigation is the


determination the at the system requested is feasible. Feasibility study is
carried out to select the best system that meets the performance
requirements.

Feasibility study is both necessary and prudent to evaluate the feasibility of


the project at the earliest possible time. It involves preliminary investigation of
the project and examines whether the designed system will be useful to the
organization. Months or years of effort, thousand for millions of money and
untold professional embarrassment can be averted if an in-conceived system
is recognized early in the definition phase.

The different types of feasibility are: Technical feasibility, Operational


feasibility, Economical feasibility.
Technical Feasibility

Technical Feasibility deals with the hardware as well as software


requirements. Technology is not a constraint to type system development. We
have to find out whether the necessary technology, the proposed equipments
have the capacity to hold the data, which is used in the project, should be
checked to carry out this technical feasibility.

The technical feasibility issues usually raised during the feasibility stage
of investigation includes these

 This software is running in windows 2000 Operating


System, which can be easily installed.

 The hardware required is Pentium based server.


 The system can be expanded.

Behavioral Feasibility

This feasibility test asks if the system will work when it is developed and
installed Operational feasibility in this project:

 The proposed system offers greater level of user-


The proposed system produces best results and gives

high performance. It can be implemented easily .So this

project is operationally feasible.


Economical feasibility

Economical Feasibility deals about the economical impact faced by the


organization to implement a new system. Financial benefits must equal or
exceed the costs. The cost of conducting a full system, including software and
hardware cost for the class of application being considered should be
evaluated. Economic Feasibility in this project:

The cost to conduct a full system investigation is possible.

iii) Fact Finding Techniques

The various document of the office was studied and after a short interview
the fact finding was finished and certain

questions were arising that:

1. Whether there is any problem of retrieval.

2. Whether there is any extra Guide needed.

3. Whether you want the proposed system of Hardware detailing.

4. Whether the office member is benefited or not.

5. Whether they are ready to accept the changes or not.


And afterwards it was found that:

1. No problem of retrieval.

2. There is no extra Guide is needed.

3. Yes they want the proposed system of Hardware Detailing.

4. Yes office member is benefited.

5. Yes they are ready to accept the changes.

iv) Cost Benefit Analysis

A system is also expected to provide benefits. The first task is to identify and
then assign a monetary value to it for cost / benefit analysis.

The two major benefits are improving performance and minimizing the
cost of processing. The performance category emphasize in the accuracy of
the result or access to information and easier access to the system by
authorized users.

Our software has fulfilled all the benefits very well. Our software are
improving and minimizing the cost of processing. Our software has controlled
error and caused reduction of staff.

Tangible or Intangible cost and benefits:-


An outlay of case for a special file item or activity is referred to as a
tangible cost. The purchase of hardware or software, personal training and
employees salaries are examples of tangible cost in our software we have
included training and employee salaries approx 300 /- to be paid for
training and we have saved the salary of 3 employees but training cost is
one time cost and hence we have saved 3 x 5000 = 15000 /- per month.

V) Data Flow Diagram

Data flow oriented techniques advocate that the major data items
handled by a system must be first identified and then the processing required
on these data items to produce the desired outputs should be determined.
The DFD (also called as bubble chart) is a simple graphical formalism that can
be used to represent a system in terms of input data to the system, various
processing carried out on these data, and the output generated by the system.
It was introduced by De Macro (1978) , Gane and Sarson (1979).The primitive
symbols used for constructing DFD’s are:

Symbols used in DFD :

A circle represents a process.

A rectangle represents external entity


A square defines a source or destination of the system data.

An arrow identifies dataflow.

Double line with one end closed indicates data store

vi) Normalization

Normalization is a data analysis technique that organizes the data such


that they are grouped to form non-redundant, stable, flexible and adaptive
entities. Normalization is a three stem technique that places the data moved
in 3N forms.

We can easily change the database without rewriting many or the entire
program that used those databases.

We can make our data model as application independent as possible to


encourage the Database structure that can be extended to modify without
impact to current program.
I. Simply stated entity in 1NF if there are no attributes that can have more than
one value for single instance of the entity any attribute that can have multiple
values actually describe a separate entity possibly an entity and relationship.

II. An entity is in 2NF if it is already in 1NF and if the value of all non primary
key attributes that are dependent on only part of primary key should be
moved to any entity where that partial key is actually the full key. That may
require creating a new entity and relationship of model.

III. An entity is in 3NF if it is already in 2NF and if the value of it non primary key
attributes that are not dependent on another non primary key attributes. Any
non primary key attributes that are dependent on other non primary key
attributes must be moved or deleted. Again new entities and relationship may
have to be added to the data model. For our convenience we have not taken
the concept of Normalization in consideration in our project.
Implementation

Implementation is the stage of the project when the theoretical design is


turned out into a working system. Thus it can be considered to be the most
critical stage in achieving a successful new system and in giving the user,
confidence that the new system will work and be effective.

The implementation stage involves careful planning, investigation of the


existing system and it’s constraints on implementation, designing of methods
to achieve changeover and evaluation of changeover methods.

Implementation Review:
After the system is implemented and conversion is complete, user usually
conducts a review of the system. User usually conducts a review of the system.
 In this system all Requirements are fulfills.
 The user can easily insert, update and delete the
record in Efficient way.
 This system is user-friendly and easily understands.
 User can view the Purchase Report and Sales Report So,
user can speedily work in this system .
 The performance level of users has improved.
 Data record can be easily stored.
DATA DICTIONARY

Field type Appropriate Uses Storage Space

Text Data containing text, a Based on what’s


combination of text and actually stored in
numbers, or numbers the field; ranges
that don’t need to be from 0 to 255
included in calculations. bytes
Examples are name,
addresses, department
codes, and phone
numbers.

Memo Long text and numeric Ranges from 0 to


strings Example are 65,536 bytes.
notes and description
Number Data that’s included in 1, 2, 4 or 8
calculation (excluding bytes,depending
money). on the field size
selected (or 16
Examples are ages, codes
(such as employee Bytes for
IDs),and payment Replication ID).
methods
Date/Time Dates and times ex. Are 8 bytes
Date ordered ,birth date
Auto number Unique sequential or 4 bytes (16 bytes
random numbers ex. for replication ID).
invoice number and
project number

DATABASE –DESIGN

A database is an organized mechanism that has the capability of storing


information through which a user can retrieve stored information in an
effective and efficient manner. The data is the purpose of any database and
must be protected.

The database design is a two level process. In the first step, user requirements
are gathered together and a database is designed which will meet these
requirements as clearly as possible. This step is called Information Level
Design and it is taken independent of any individual Database Management
System (DBMS).

Organization of the data in the database is aimed to achieve. In the second


step, this Information level design is transferred into a design for the specific
DBMS that will be used to implement the system in question. This step is
called Physical Level Design, concerned with the characteristics of the specific
DBMS that will be used. A database design runs parallel with the system
design. The following two major objectives.
 Data Integrity
 Data independence
CONCLUSION

The documentation includes all necessary information on the structure


and the coding of the program created for Café Billing system. Creating the
program was an overwhelming task that required a lot of analyzing,
research work and personal skills. Creating this report has been a great
experience and numerous facts have been learned since the required tasks
were very challenging. Tasks such as creating a system to a restaurant,
needed research work as well as personal skills. Creating proper design and
smooth flow of operation was a very tiring task that consumed a lot of time.
The program has been created successfully with proper design and working
flow of operation.

The billing part was the most important and difficult part of this project.
Retrieving data from database for the billing purpose was quite a tough
task. Making changes on multiple data base using SQL queries was also a bit
time consuming and though provoking task. In conclusion, many
experiences have been gained specially in coding.

Time management and teamwork is very important in the development


system.

3.1 Future Enhancement

Café billing software software offers various functionalities needed to


effectively manage restaurant operations such as staff management,
making orders, billing, menu management, reservation, viewing order
history, to-do list and many more.

In the future, many enhancements/upgrades can be made to the existing


software. Various enhancements such as inventory management and
control, wireless table side ordering and payment, real-time alerts,
online ordering, mobile management capabilities can help increase
revenue and cut cost.

You might also like