Cafe Management Report
Cafe Management Report
SUBMITTED BY:
HEMANTH U : 201NSB7012
PAVAN H : 201NSB7022
Center of Examination: G T I M S R
Internal Examiner
External Examiner
ACKNOWLEDGEMENT
It is not exaggerated to say that the emergence of this book was outcome of
observing project. It not only involved number of days of efforts but also extensive
consultation, case study, analysis, programming and much more. In fact, this
project work enjoyed the creation and innovative support from the concerned
guide.
I also like to thank our Principal, Lecturers, my parents and all our class mates,
who have contributed directly or indirectly in our efforts to complete this project
successfully.
With Gratitude
HEMANTH U [201NSB7012]
PAVAN H [201NSB7022]
ABSTRACT
Introduction:
Objectives:
Functionality:
Menu management:
Cafe owners will be able to manage their menu offerings, including the creation
and modification of menu items, pricing.
Order management:
Inventory management:
The system will provide a range of reports and analysis tools to help cafe owners to
make informed decisions about their business. This will include reports on sales,
customer behaviour, inventory usage, and other critical metrics.
Technical Description:
The cafe management system will be developed using a modern and flexible
architecture that will allow for easy customization and future growth. The system
will be developed using a range of open-source technologies.
Conclusion:
In conclusion, the cafe management system project will provide cafe owners with a
modern and efficient system to manage their businesses effectively. By automating
many of the manual tasks currently performed by staff and providing valuable
insights into customer behavior, the system will improve the efficiency and
profitability of cafe operations. The system will be developed using open-source
technologies, providing cafe owners with a flexible and cost-effective solution to
their management needs.
TABLE OF CONTENTS
SI.NO NAME OF THE CHAPTERS Page
No
1. INRODUCTION
1.1. Features of Café Management System
1.2. Existing System
1.3. Proposed System
4. MODULES
4.1. Manager login Module
4.2. Cashier login Module
4.3. Items Module
4.4. Orders Module
4.5. View Orders Module
4.6. Bill Module
5. FEASIBILITY STUDY
7. SYSTEM DESIGN
9. SNAPSHOTS
9.1. Manager login Form
9.2. Cashier login Form
9.3. Items Form
9.4. Orders Form
9.5. View Orders Form
9.6. Bill Form
10. CODING
10.1. Data Base Connectivity
10.2. Manager login Form
10.3. Cashier login Form
10.4. Items Form
10.5. Orders Form
10.6. View Orders Form
10.7. Bill Form
11. TESTING
11.1. Unit Testing
12. CONCLUSION
13. FUTURE ENHANCEMENT
14. BIBLIOGRAPHY
14.1 References
14.2 Websites
CHAPTER 1
INTODUCTION
Cafe Management System is the application to automate all kinds of operations in
a cafe shop. The purpose of this software is to manage the items in the cafe. It
includes the Order Processing, Stock Management and Accounts Management.
We developed this software to maintain record of sales, purchase records. This
project has been developed using VB.NET as front end and SQL Server as Back
end. Here we are trying to develop such type of system which provide the
automation on the any type of a café store. That means a store that has the type
of system which provides the facility to the customers of the store to purchase
food and snacks from the store without any complexity.
At the start of the business, the café store owner buys the raw materials from the
dealers. All the name of the items is noted down in the software along with rate.
In the present system user must do all work manually and during the issue, order
of more stock, the product register is required to check the availability of stock in
hand. And it takes time to check records.
In present café store management system, to generate the reports based on the
management requirement, will require extensive searching of records. In case of
item Record Management, the registers need to be updated time to time as
information changes frequently. The stock section gives the total number of item
stocks available in the store. When a customer buys an item from the store, a bill
is generated. The bill contains the name of the item purchased, rate per item,
quantity, total rate, and the total amount. And then purchase it by paying price on
café store cash counter and receives its invoice.
For the next month, the owner will get estimation as to which item to purchase
more and which item to purchase less and which item has to be stopped for
purchasing. In present café management system, in each process whether it is
Product Management, Payment Management, Report Generation, manager must
pay attention to a greater extent while performing the tasks. In proposed system
all records are saved in the database for report generation. Depending upon the
number of items purchased, the number of items from the stock will be deducted.
Therefore, we get the total number of items sold from the stock. In present
system user has to maintain stock Records manually.
• Cashier can enter the details of items being purchased and give the client receipt
for purchasing
• Manager can track all the information of Receipts, Sales, Stocks ETC
• Manager can edit, add, delete and update the records of Inventory.
• It also maintains management of all incoming and outgoing finance from the
store account section.
At present, the stores are working under manual management. The client uses MS
Excel, all records related to Products, Sales, Suppliers, Orders, Payment are stored
in excel files. there is lot of duplicate work, and chance of mistake. When the
records are changed, they need to update each and every excel file
Drawbacks:
• To manage the whole data, the person maintaining records has to take great pain.
• There is no security, anybody can access any report and sensitive data.
This Café Management System is used to overcome the entire problem which they
are facing currently, and making manual system to computerized system.
Proposed Café management system should help the customers query whether an
item is in stock. The user can query the availability of an item either by using the
item name or by using the item category. The objective and scope of my Project
Café Management System is to record the details various activities of user. It
simplifies the task and reduce the paper work. Café management system should
generate sales statistics for any period.
In proposed system, as soon as customer asks for an item to purchase, the cashier
would enter the item name in the system. Café management system should update
the stock and generate the sales receipt for the item. The Café management system
make sure to save both in and out of the stocks. Hence, it is less time consumable
than compare to MS excel.
To reduce the headache of maintaining the record of book keepers and customer
related documents.
It will eliminate the delays in making the payments, where people use to stand for
a long time in the queue to pay and get their food.
Searching will become more efficient and fast in comparison to manual searching.
It will also provide assurance that we have a proper record of the selling of the
items so that we can limit our items stock according to that.
Overall, it will reduce the cost and time of the manager who will take care of the
store.
CHAPTER 2
SOFTWARE REQUIREMENTS AND
SPECIFACATIONS (SRS)
2.1. Software Requirement Analysis
Analysis is the process of breaking a complex topic or substance into smaller parts
to gain a better understanding of it. Analysis in the field of engineering look at
requirements, structures, mechanisms and systems dimensions. Analysis is an
exploratory activity.
Café management system shall handle expected and non-excepted errors in ways
that prevent loss in information and long downtime period.
➢ PERFORMANCE REQUIREMENTS
The system shall accommodate high number of items and category without any
fault.
➢ SAFETY REQUIREMENTS
➢ SECURITY REQUIREMENTS
• Normal users can just read information but they cannot edit or modify anything
except some information of billing.
• System will have different many users but only managers can give authorization
to users to enter the system.
CHAPTER 3
HARDWARE AND SOFTWARE REQUIREMENTS
3.1. Hardware Requirements
• Processor - Intel Core i3
• IDE-Visual Studio.
CHAPTER 4
MODULES
4.1. Cashier login Module
The cashier login Module is a portal module that allows users to type a username
and password to log in to the café management system. We can add this module on
any module tab to allow users to log in to the system.
Manager login module acts same as login module but in this module only manager
can login to the system where manager can check stock details and maintain the
entire system. Through this module manager gives access to users to login to café
management system via by providing username and password to users.
Items module is used by the manager to store the data of any items are being added
or removed from the store. In Items module we can also change the price of the
item and update the changed data into the system so that we can keep the records
of the items in store upgraded.
In this module, the people who work in store are given username and password by
the admin to log in to café management system. The people who work in that café
are called as users. The manager gives the authorization to users so that they can
store all the transaction done in the store.
View Orders module is very useful module. Using this module, we can easily get
the idea of stocks present and sold. Because this module shows the number of
items sold. It is used to display the amount of money got by selling the items.
Module is used by users to print bills. If any customers purchase items from the
store, then the users will enter the item name, category name, quantity and price of
the book and generate a bill to give it to customer and when the users print the bill
the data will be updated automatically in the system.
CHAPTER 4
FEASIBILITY STUDY
Feasibility is defined as the practical extent to which a project can be performed
successfully. To evaluate feasibility, a feasibility study is performed, which
determines whether the solution considered to accomplish the requirements is
practical and workable in the software.
Consequently, costs and benefits are described with greater accuracy at this stage.
It consists of the following:
A list of the major findings and recommendations of the study. It is ideal for the
user who requires quick access to the results of the analysis of the system under
study. Conclusion are stated , followed by a list of the recommendation and a
justification for them.
* Details of findings:
Technical feasibility:
* Analyzes the technical skills and capabilities of the software development team
members.
* Ascertains that the technology chosen for software development has a large
number of users so that they can be consulted when problems arise or
improvements are required.
Operational feasibility:
Operational feasibility assesses the extent to which the required software performs
a series of steps to solve business problems and user requirements. This feasibility
is dependent on human resources (software development team) and involves
visualizing whether the software will operate after it is developed and be operative
once it is installed.
Economic feasibility:
It involves the cost incurred on the software development team, estimated cost of
hardware and software, cost of performing feasibility study, and so on. For this, it
is essential to consider expenses made on purchases (such as hardware purchase)
CHAPTER 6
After designing input and output, the analyst must concentrate on database design
or how data should be organized around user requirements.
The general objective is to make information access, easy quick, inexpensive and
flexible for other users.
* Controlled Redundancy
* Data independence
* Performance
Database design activity deals with the design of the physical database. The
designer begins to concentrate on file design or how data should be organized
around user requirements.
How data are organized depends on the data and response requirements that
determine hardware configurations. An integrated approach to file design is the
database.
The objectives of data base are accuracy and integrity, privacy and security of data
etc.
CHAPTER 7
SYSTEM DESIGN
INTRODUCTION TO SYSTEM DESIGN
The design phase is the life cycle phase in which the detailed design of the selected
system in the study phase is accomplished. In the design phase, the technical
specifications are prepared for the performance of all allocated tasks. It also
includes the construction of programs and program testing. In the design phase, the
first step is to determine the output is to be produced and in what format. Second,
input data and master files have to be designed to meet the requirements of
proposed output. The system analyst has to define the methods of capturing and
input programs and format of the output and its use by the users.
CODE DESIGN
Codes can provide brief identification of data items and replace longer descriptions
that would be more awkward to store and to manipulate.
INPUT DESIGN
3. The format in which data fields are entered for example, filling out the data field
is required through the edited format mm/dd/yy.
When we approach input data design, we design source documents that capture the
data and then selected the media use to enter them into the computer.
There are different ways in which data can be introduced into the system such as:
a. The data is converted into a machine sensible from by some realistic source
document and types in the relevant items using a keyboard connected to the
system.
b. The document can be read directly by a machine and this converts information
held in the human sensible form into a machine-readable form without need for
human investigations.
c. Data entered into a system through a keyboard. This is done interactively by the
person using the system.
e. The data entry in the system has been designed so as to make to user friendly
and also to incorporate certain validation checks. The field name must be
documented. The field name must be known to data entry operator or users so that
the data entry will not exceed the allocated space. Our system contains the
following inputs.
OUTPUT DESIGN
PROCEDURE DESIGN
When program become very long, they are divided into smaller programs or
modules. These smaller programs can be written, tested and debugged separately.
This technique of programming is known as modular programming.
2. Generally the modules of common nature are prepared, which can be used at
many places.
CHAPTER 8
A data flow diagram is a graphical tool used to describe and analyze movement of
data through a system. They are the central tool and forms the basis from which the
other components are developed. The transformation of data from input to output
may be described logically and independently of physical components associated
with the system. These are known as the logical data flow diagrams. The physical
data flow diagrams show the actual implements and movements of data between
people, departments and workstations. A full description of a system actually
consists of a set of data flow diagrams. Using two familiar notations Yourdon,
Ganev and Sarson notation develops the data flow diagram. Each component in a
DFD is labelled with a descriptive name. Process is further identified with a
number that will be used for identification purpose. The development of DFD’s is
done in several levels. Each process in lower-level diagrams can be broken down
into a more detailed DFD in the next level. The top-level diagram is often called
context diagram. It consists a single process bit, which plays vital role in studying
the current system. The process in the context level diagram is exploded into other
process at the first level DFD.
The idea behind the explosion of a process into more process is that understanding
at one level of detail is exploded into greater detail at the next level. This is done
until further explosion is necessary and an adequate amount of detail is described
for analyst to understand the process. Larry Constantine first developed the DFD as
a way of expressing system requirements in a graphical form, this led to the
modular design.
A DFD is also known as a “bubble Chart” has the purpose of clarifying system
requirements and identifying major transformations that will become programs in
system design. So, it is the starting point of the design to the lowest level of detail.
A DFD consists of a series of bubbles joined by data flows in the system.
DFD SYMBOLS
*An arrow defines data flow. It is the pipeline through which the information
flows.
*A circle or a bubble represents a process that transforms incoming data flow into
outgoing data flows.
*An open rectangle is a data store, data at rest or a temporary repository of data.
CONSTRUCTING A DFD
There are several rules of thumb that are used in drawing DFD’s. They are:
* Process should be named and numbered for an easy reference. Each name should
be representative of the process.
* The direction of flow is from top to bottom and from left to right. Data
traditionally flow from source to the destination although they may flow back to
the source. One way to indicate this is to draw long flow line back to a source. An
alternative way is to repeat the source symbol as a destination. Since it is used
more than once in the DFD, it is marked with a short diagonal.
* No process can have only inputs. If an object has only inputs, then it must be a
sink.
DATA STORE
* Data cannot move directly from one data store to another data store, a process
must move data.
* Data cannot move directly from an outside source to a data store. Data must be
moved by a process that receives data from the source and places the data into the
data store.
* Data cannot move directly to an outside sink from a data store. Data must be
moved by a process.
SOURCE OR SINK
DATA FLOW
* A data flow has only one direction of flow between symbols. It may flow in both
directions between a process and a data store to show a read before an update.
* A fork in a data flow means that exactly the same data goes from a common
location to two or more different processes, data stores, or source/sinks.
* A join in a data flow means that exactly the same data come from any of two or
more different processes, data stores, or source/sinks to a common location.
CHAPTER 9
SNAPSHOTS
CHAPTER 10
CODING
10.2. Manager login Code
Public Class ManagerLogin
MsgBox("Enter Username")
MsgBox("Enter Password")
Obj.Show()
Me.Hide()
Else
TextBox1.Text = ""
TextBox2.Text = ""
End If
End Sub
Obj.Show()
Me.Hide()
End Sub
End Class
End Sub
Obj.Show()
Me.Hide()
End Sub
MsgBox("Enter Username")
MsgBox("Enter Password")
Obj.Show()
Me.Hide()
Else
TextBox1.Text = ""
TextBox2.Text = ""
End If
End Sub
End Class
If key = 0 Then
Else
Con.Open()
Dim query = "delete from ItemTbl where Id = " & key & ""
cmd.ExecuteNonQuery()
Con.Close()
Reset()
DisplayItem()
MsgBox("Item Deleted!!")
End If
End Sub
Obj.Show()
Me.Hide()
End Sub
MsgBox("Enter Category")
Else
Con.Open()
Dim query = "insert into CategoryTbl values('" & TextBox1.Text & "')"
cmd.ExecuteNonQuery()
MsgBox("Category Added")
Con.Close()
TextBox1.Text = ""
FillCategory()
End If
End Sub
TextBox4.Text = ""
ComboBox1.SelectedIndex = 0
TextBox3.Text = ""
TextBox2.Text = ""
End Sub
Con.Open()
adapter.Fill(Tbl)
ComboBox1.DataSource = Tbl
ComboBox1.DisplayMember = "Name"
ComboBox1.ValueMember = "Name"
Con.Close()
End Sub
Reset()
End Sub
FillCategory()
DisplayItem()
End Sub
Con.Open()
adapter.Fill(ds)
DataGridView1.DataSource = ds.Tables(0)
Con.Close()
End Sub
MsgBox("Missing Information!")
Else
Con.Open()
Dim query = "insert into ItemTbl values('" & TextBox4.Text & "','" &
ComboBox1.SelectedValue.ToString() & "'," & TextBox3.Text & "," &
TextBox2.Text & ")"
cmd.ExecuteNonQuery()
MsgBox("Item Added")
Con.Close()
Reset()
DisplayItem()
End If
End Sub
Dim key = 0
TextBox4.Text = row.Cells(1).Value.ToString
ComboBox1.SelectedValue = row.Cells(2).Value.ToString
TextBox3.Text = row.Cells(3).Value.ToString
TextBox2.Text = row.Cells(4).Value.ToString
key = 0
Else
key = Convert.ToInt32(row.Cells(0).Value.ToString)
End If
End Sub
If key = 0 Then
Else
Try
Con.Open()
Dim query = "update ItemTbl set Name = '" & TextBox4.Text & "',
Category = '" & ComboBox1.SelectedValue.ToString() & "', Price = " &
TextBox3.Text & ", Quantity = " & TextBox2.Text & " where Id = " & key & ""
cmd.ExecuteNonQuery()
Con.Close()
Reset()
DisplayItem()
MsgBox("Item Edited!!")
Catch ex As Exception
MsgBox(ex.Message)
End Try
End If
End Sub
End Class
Try
Con.Open()
Dim query = "update ItemTbl set Quantity = " & newQty & " where Id = "
& key & ""
cmd.ExecuteNonQuery()
Con.Close()
DisplayItem()
MsgBox("Item Added!!")
Catch ex As Exception
MsgBox(ex.Message)
End Try
End Sub
If key = 0 Then
MsgBox("Select an Item!")
Else
i=i+1
DataGridView2.Rows.Item(rnum).Cells("Column1").Value = i
DataGridView2.Rows.Item(rnum).Cells("Column2").Value = ProdName
DataGridView2.Rows.Item(rnum).Cells("Column4").Value =
TextBox2.Text
DataGridView2.Rows.Item(rnum).Cells("Column3").Value = price
DataGridView2.Rows.Item(rnum).Cells("Column5").Value = total
UpdateItem()
TextBox2.Text = ""
key = 0
End If
End Sub
Con.Open()
adapter.Fill(Tbl)
ComboBox1.DataSource = Tbl
ComboBox1.DisplayMember = "Name"
ComboBox1.ValueMember = "Name"
Con.Close()
End Sub
Con.Open()
adapter.Fill(ds)
DataGridView3.DataSource = ds.Tables(0)
Con.Close()
End Sub
Con.Open()
adapter.Fill(ds)
DataGridView3.DataSource = ds.Tables(0)
Con.Close()
End Sub
Obj.Show()
Me.Hide()
End Sub
DisplayItem()
FillCategory()
End Sub
FillterByCategory()
End Sub
DisplayItem()
End Sub
Con.Open()
Dim query = "insert into OrderTbl values('" & DateTime.Today.Date & "'," &
GrdTotal & ")"
cmd.ExecuteNonQuery()
MsgBox("Bill Added")
Con.Close()
End Sub
AddBill()
PrintPreviewDialog1.Show()
End Sub
Obj.Show()
Me.Hide()
End Sub
e.Graphics.DrawImage(bm, 0, 90)
e.Graphics.DrawString("-------------------------THANK YOU---------------------
-", New Font("Georgia", 15), Brushes.Crimson, 130, 600)
End Sub
ProdName = row.Cells(1).Value.ToString
key = 0
stock = 0
Else
key = Convert.ToInt32(row.Cells(0).Value.ToString)
stock = Convert.ToInt32(row.Cells(4).Value.ToString)
price = Convert.ToInt32(row.Cells(3).Value.ToString)
End If
End Sub
End Class
Con.Open()
adapter.Fill(ds)
DataGridView3.DataSource = ds.Tables(0)
Con.Close()
End Sub
DisplayBill()
End Sub
Obj.Show()
Me.Hide()
End Sub
End Class
CHAPTER 11
TESTING
Types of Testing
The various types of testing done on the system are:
•Unit Testing
•Integration Testing
•Validation Testing
•System Testing
•Acceptance Testing
TEST CASE
1. Run the project
=> Message Box appears indicating that correct Username and Password must be
entered.
4. Adding a category
7. Deleting an item
8. Clear
9. Logout
=> The manager account gets logged out and the manager login page gets loaded.
=> Entering the wrong username and password message box appears indicating
that correct Username and Password must be entered.
13. Refresh
=> Choosing an item from List of Items and entering the quantity and then click on
Add to bill. The selected items will appear on your orders table.
15. Total
=> The total price of the selected items is calculated and displayed on the specified
place.
16. Print
=> The Bill with selected item and the total amount gets displayed with the help of
preview dialog.
17. Vieworders
=> The Bills which are generated are displayed on this form with the date at when
the bill was generated and also the total amount of that bill.
18. Back
=> When the button is clicked it gets back to the previous form i.e., Orders form.
19. Logout
=> The Cashier Login account gets logged out and the Cashier Login page gets
loaded.
CHAPTER 12
CONCLUSION
The cafe management system project has successfully addressed the needs of cafe
owners by providing a comprehensive solution to manage their businesses
efficiently. The system has been designed to streamline operations, improve
customer satisfaction, and increase profits. The system has a range of
functionalities that allow cafe owners to manage their menu offerings, customer
orders, customer information, inventory, and reporting and analysis. The system
has been developed using open-source technologies that provide a flexible and
cost-effective solution to the management needs of cafe owners.
CHAPTER 13
FUTURE ENHANCEMENT
The cafe management system has been designed with future enhancements in mind
and there are several areas where the system can be further improved. Some
potential future enhancements include:
In conclusion, the cafe management system project has been a success and has
provided cafe owners with a comprehensive solution to manage their businesses.
The system has the potential for further enhancements that will provide additional
benefits to cafe owners and improve the overall customer experience.
CHAPTER 14
BIBLIOGRAPHY
References:
1. YouTube Tutorials
2. Connecting Data Base to SQL Server
3. MS Visual Studio 2019
Websites:
1. https://www.w3schools.com
2. https://www.geekforgeeks.com
3. https://www.google.com