A Project Report on

Cafe Management System

By
Rushikesh Ramchandra Kutal
&
Patil Rajiv Ashok
MCA – I, SEM – I
2023-24

To
Savitribai Phule Pune University,Pune

In Partial Fulfillment of the Degree of

Master in Computer Application (M. C. A.)

Under The Guidance Of

Dr. Rupali Dahake

Suryadatta Group of Institutes, Pune

Suryadatta Institute of Management and Mass Communication (SIMMC)
 Date:-

CERTIFICATE

This is to certify that Mr. / Ms. _________________________________, has successfully completed his/her
project work entitled “________________________” in partial fulfillment of MCA – I Semester-I program
for the year A.Y. 2023-24 . He / She have worked under our guidance and direction.

Prof.(Name of Project Guide)

(Dr. Rupali Dahake ) HoD-MCA,SGI

Examiner 1 Examiner 2

Date :
Place :
 Acknowledgment
We are the student of MCA first year. Here by we express our thanks to our project guide for allowing us to do the
project on Cafe Managemwnt System. This project work has been the most exciting part of our learning
experience which would be an asset for our future carrier. We would especially like to thank our guide and
mentor Dr. Rupali Dahake, who constantly guided us in developing, pushing us to search for more answers to her
numerous questions. Also I would like to thank our project coordinators Dr. Rupali Dahake & Prof. Apurva Patil,
for their support. As a building block of MCA Department, I thank Dr. Manisha Kumbhar, HOD, MCA
Department for her continuous support and help. We are grateful to many classmates who contributed their
suggestions. Their hard work and examples push us to limits of our capability and encourage us daily.

Thank You

Rushikesh Ramchandra Kutal

Patil Rajiv Ashok
 Index
Chapter Page number
CHAPTER 1 : INTRODUCTION
1.1 Existing System
1.2 Need for System
1.3 Operating Environment Hardware and Software
CHAPTER 2 : PROPOSED SYSTEM
2.1 Proposed System (Introduction of system)
2.2 Module specifications (Scope)
2.3 Objectives of System
CHAPTER 3 : ANALYSIS & DESIGN
3.1 Use Case Diagrams
3.2 Activity Diagram
3.3. Sequence Diagram
3.4 Class Diagram
3.5 Module Hierarchy Diagram
3.6 Table specifications (Database design)
3.7 Data dictionary
CHAPTER 4 : USER MANUAL
4.1 User Interface Screens (Input)
4.2 Output Screens with data
4.3 Data Reports
4.4 Testing

4.5 Sample program code

4.6 Limitations and Bibliography
 INTRODUCTION

Cafe owner has to maintain records of daily billing, which will be used to manage sale report. There will be many
items available in the cafe, many customers will be coming at different time for having food, they will be selecting
items from the displayed menu and their bills will be generated. This system will save time and will be easy to use
when compared to manual work that was done in paper. Cafe Management System is an application, which will
help cafes to optimize and control over their cafes menu. This application helps the cafes to do all functionalities
more accurately and efficiently. Cafe Management system reduces manual work and improves efficiency and rate
of work. It is specifically designed for cafe billing management and order taking management system. This
software helps to take food orders and display them. Also, help to maintain records in system and display total sale
report. It is keeping a proper record of the bills. The aim of this document is to gather and analyse and give an in
depth insight of the complete Cafe Shop Management. This system will help to automate the work and make it
easier for the manager to manage the cafe.

In the bustling world of cafes and restaurants, efficient management is key to success. A Cafe Management System
plays a pivotal role in streamlining operations, enhancing customer experience, and optimizing overall business
performance. This system leverages technology to automate various aspects of cafe management, from order
processing to inventory control and customer relationship management.
 Key Features:

1.Order Management:

Efficient order processing through a user-friendly interface.Quick order entry, modification, and cancellation.
Order tracking and status updates in real-time.

2.Menu Management:

Easy creation, modification, and categorization of menu items.Integration of images and descriptions for each item.
Seasonal or promotional item highlighting.

3.Inventory Control:

Real-time monitoring of stock levels.Automatic alerts for low inventory or expiring items.
Streamlined reordering processes.

4.Employee Management:

Staff scheduling and attendance tracking.Role-based access control for security.

Performance monitoring and payroll integration.

5.Customer Relationship Management (CRM):

Customer database for personalized service.Loyalty programs and rewards management.

Feedback collection and analysis.

6.Table Management:

Efficient table allocation and reservation system.Integration with order processing for a seamless dining
experience.
Visual representation of table occupancy.

7.Billing and Payments:

Automated invoicing and billing.Multiple payment options, including cash, card, and digital wallets.
Integration with accounting systems for financial management.

8.Analytics and Reporting:

Comprehensive reporting on sales, inventory, and employee performance.Data-driven insights for business
decision-making.
Trend analysis for menu optimization and marketing strategies.

9.Security and Data Protection:

Robust security measures to protect customer and business data.Regular data backups and secure storage practices.
Compliance with data protection regulations.
 1.1Existing System

At present traders maintain their day-to-day transactions where a waiter has to go at each table and takes the order.
And give to the chef and they must be passed to the cashier. During this process it takes lots of time and customer
must wait till the process only single system is used during this process. This management system will be designed
to minimize the manual work in maintaining Managing Customer details, working of Token system, working with
Offers to be applied in Cafe, generating Reports according to the working of system and Menu Card for Cafe and
other managements in Cafe.

 Key Components of the Existing System:

1.Manual Order Processing:

Orders are manually recorded using pen and paper or basic order forms.Communication of orders to the kitchen
relies on physical tickets or verbal communication.

2.Limited Menu Management:

Menu updates and modifications are time-consuming, involving manual changes to physical menus.Visuals and
descriptions for menu items are limited or absent.

3.Inventory Control Challenges:

Inventory levels are monitored manually, and reorder decisions are based on periodic physical checks.Lack of real-
time visibility into stock levels may lead to stockouts or overstocking.

4.Basic Employee Management:

Employee scheduling and attendance tracking are manual processes.Limited role-based access control and security
measures.

5.Simple Customer Relationship Management (CRM):

Customer information is recorded manually, with ad-hoc loyalty programs and feedback collection.
6.Table Management Challenges:

Table allocation and reservation systems may be paper-based or rely on memory.Inefficient integration with order
processing can lead to delays and errors.

7.Manual Billing and Payments:

Invoicing and billing are manual processes, with limited payment options.Accounting integration may involve
manual data entry.

8.Limited Analytics and Reporting:

Reporting on sales, inventory, and employee performance is manual and time-consuming.Lack of data-driven
insights hinders strategic decision-making.

9.Security Concerns:

Limited security measures for protecting customer and business data.Irregular data backups pose a risk of data loss.

10.Non-compliance with Data Protection:

Inadequate measures to comply with data protection regulations.

1.2 Need of system

 Cafe management system is used for maintaining the details, Sales,

 billing maintains an inventory for the Cafe.
 The Cafe management system is a system which help cafeteria to manage their cafeteria daily process such as
order & bill.
 This project also gives the interface for the bill printing purpose in instant time.
1.3 Operating Environment Hardware and Software

 Hardware Specification:

Server Hardware:

The Cafe Management System will require a dedicated server to host the database and manage application logic.
Recommended Specifications:
Processor: Dual-core or higher
RAM: 8GB or higher
Storage: 256GB SSD or higher
Network: Ethernet connectivity

Client Hardware:

Client machines are devices where users, such as cafe staff, interact with the Cafe Management System.
Recommended Specifications:
Processor: Intel Core i3 or equivalent
RAM: 4GB or higher
Storage: 128GB SSD or higher
Display: Minimum 15-inch monitor with a resolution of 1366x768
Network: Ethernet or Wi-Fi connectivity

 Hardware Specification:

 Processor : core i3 and above

 RAM : 512MB to 1GB
 Hard disk : 128GB
 Software Specification:

1.Programming Language:

Java: Choose Java as the primary programming language for its platform independence, scalability, and extensive
libraries.

2.Database Management System (DBMS):

MySQL : Select a reliable relational database management system to store and manage data efficiently. MySQL
are popular choices for Java applications.

3.Web Technologies :

HTML5, CSS3, JavaScript: If the Cafe Management System includes a web-based interface, use standard web
technologies for front-end development to ensure compatibility across browsers.

 Software Specification:

 Front End : Html, Java

 Back End : MySQL
 2. PROPOESD SYSTEM

 2.1 Proposed system

The proposed system provides user friendly interface and also provides powerful and efficient database
management system. The aim of proposed system is to develop a system of improved facilities. The existing
system work is done manually thus hampering its accuracy and effectiveness. The proposed system can overcome
the limitations of the existing system. The system provides proper security and reduces the manual work. The
existing system has several disadvantages and many more difficulties to work. The proposed system tries to
eliminate or reduce these difficulties up to some extent. The proposed system will help the user to reduce the
workload and mental conflict. Through this system it is possible to print various reports and bills for the
organization. The aim of the proposed system is to develop a system of improved facilities.
 Security of data.
 Ensure data accuracy.
 Proposed control of the Higher Authority.
 Minimum time needed for the various processing.
 Greater efficiency. Better services.
 User friendliness and interactive.
 Minimum time required.

 Key Objectives:
1. User-Friendly Interface:
 The proposed system prioritizes an intuitive and user-friendly interface for both cafe staff and customers. This
ensures smooth navigation and quick adoption, enhancing overall usability.

2. Efficient Order Processing:

 A streamlined order processing system will be implemented, allowing for quick and accurate order entry,
modification, and cancellation. Real-time order tracking and status updates will be available to both staff and
customers.
3. Dynamic Menu Management:

 Our system introduces a dynamic menu management feature, empowering cafe owners to easily create,
modify, and categorize menu items. Integration of images and descriptions enriches the customer experience,
with the ability to highlight seasonal or promotional items.

4. Real-time Inventory Control:

 Say goodbye to inventory woes with a real-time monitoring system. Automatic alerts for low inventory or
expiring items, coupled with efficient reordering processes, ensure that cafes maintain optimal stock levels at
all times.

5. Comprehensive Employee Management:

 The proposed system includes a comprehensive employee management module, covering staff scheduling,
attendance tracking, role-based access control for security, and integrated performance monitoring with payroll
functionalities.
 2.2 Module Specification (Scope)

It aims to maximize the productivity and provide improved managed System. This System will be easy to
understand and use. More specifically, this system is designed to allow an admin to manage the employee records,
Customer records, Products records and other managements in Cafe. Whereas, it maintains the relationship
between customer and the admin in the technical way with the help of cafe management software. The software
will facilitate creation of different Reports such as Customer report & Product report

 Cafe management system is used for maintaining the details, sales, billing and maintains an inventory for the
cafe. This project developed using java and database.

 It reduce manual work and provide efficiency rate of the work.

 Its application help to the maintain the record of this application.

 Display total sale report and keeping proper record of the billing.

 At the home are easily ordering food and correct place of the order And proper order list as well as proper
billing it is the possible.
 2.3 Objectives Of System

Order Management: Streamlining the process of taking and managing customer orders efficiently.

Inventory Control: Tracking and managing inventory levels of food, beverages, and other supplies to prevent
stockouts or overstock.

Billing and Payment: Automating the billing process and providing various payment options for customers.

Employee Management: Managing employee schedules, roles, and performance to ensure smooth cafe
operations.

Customer Relationship Management (CRM): Building a database of customer information, preferences, and
feedback to enhance customer experience and loyalty.

Menu Management: Easily updating and customizing the menu, including pricing and item availability.

Reporting and Analytics: Generating reports on sales, inventory, and other key metrics to aid in decision-making
and business analysis.

Table Reservations: Allowing customers to reserve tables in advance for better planning and customer
satisfaction.

Integration with POS Systems: Integrating with Point of Sale (POS) systems for accurate and real-time
transaction processing.

Security: Implementing robust security measures to protect customer and business data.

User-Friendly Interface: Developing an intuitive and user-friendly interface for both customers and staff.

Scalability: Designing the system to accommodate the potential growth of the cafe business.

Mobile Accessibility: Ensuring the system is accessible via mobile devices for on-the-go management.
Promotions and Loyalty Programs: Implementing features for running promotions and loyalty programs to
attract and retain custom

 3 . ANALYSIS & DESIGN

 Entity Relationship Diagram

ER Diagram stands for Entity Relationship Diagram, also known as ERD is a diagram that displays the relationship
of entity sets stored in a database. In other words, ER diagrams help to explain the logical structure of databases.
ER diagrams are created based on three basic concepts: entities, attributes and relationships.ER Diagrams contain
different symbols that use rectangles to represent entities, ovato define attributes and diamond shapes to represent
relationships.

Entity Relationship Diagram

ER Diagram in DBMS An Entity–relationship model (ER model) describes the structure of a database with the
help of a diagram, which is known as Entity Relationship Diagram (ER Diagram). An ER model is a design or
blueprint of a database that can later be implemented as a database. The main

Components of E-R model are:

Entity set and relationship set. What is an Entity Relationship Diagram (ER Diagram)? An ER diagram shows the
relationship among entity sets. An entity set is a group of similar entities and these entities can have attributes.

In terms of DBMS, an entity is a table or attribute of a table in database, so by showing relationship among tables
and their attributes, ER diagram shows the complete logical structure of a database. Lets have a look at a simple
ER diagram to understand this concept

Facts about ER Diagram Model:

ER model allows you to draw Database Design It is an easy to use graphical tool for modeling data Widely used in
Database Design It is a GUI representation of the logical structure of a Database It helps you to identifies the
entities which exist in a system and the relationships between those entitie
Why use ER Diagrams?

Here, are prime reasons for using the ER Diagram Helps you to define terms related to entity relationship modeling
Provide a preview of how all your tables should connect, what fields are going to be on each table Helps to
describe entities, attributes, relationships ER diagrams are translatable into relational tables which allows you to
build databases quickly ER diagrams can be used by database designers as a blueprint for implementing data in
specific software applications.

A simple ER Diagram:

In the following diagram we have two entities Student and College and their relationship. The relationship between
Student and College is many to one as a college can have many students however a student cannot study in
multiple colleges at the same time. Student entity has attributes such as Stu_Id, Stu_Name & Stu_Addr and
College entity has attributes such as Col_ID & Col_Name

Here are the geometric shapes and their meaning in an E-R Diagram

We will discuss these terms in detail in the next section (Components of a ER Diagram) of this guide so don’t
worry too much about these terms now, just go through them once.

Rectangle: Represents Entity sets. Ellipses: Attributes

Diamonds: Relationship Set

Lines: They link attributes to Entity Sets and Entity sets to Relationship Set Double Ellipses: Multivalued
Attributes
Dashed Ellipses: Derived Attributes Double Rectangles: Weak Entity Sets
Double Lines: Total participation of an entity in a relationship set
 3.2 Class Diagram

In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their attributes, operations (or
methods), and the relationships among objects.
The class diagram is the main building block of object-oriented modeling. It is used for general conceptual
modeling of the structure of the application, and for detailed modeling, translating the models into programming
code. Class diagrams can also be used for data modeling.[1] The classes in a class diagram represent both the main
elements, interactions in the application, and the classes to be programmed.

In the diagram, classes are represented with boxes that contain three compartments:

 The top compartment contains the name of the class. It is printed in bold and centered, and the first letter is
capitalized.

 The middle compartment contains the attributes of the class. They are left-aligned and the first letter is
lowercase.

 The bottom compartment contains the operations the class can execute. They are also left-aligned and the first
letter is lowercase.

In the design of a system, a number of classes are identified and grouped together in a class diagram that helps to
determine the static relations between them. In detailed modeling, the classes of the conceptual design are often
split into subclasses.

In order to further describe the behavior of systems, these class diagrams can be complemented by a state diagram
or UML state machine.
 3.3 Use Case

To model a system, the most important aspect is to capture the dynamic behavior.

Dynamic behavior means the behavior of the system when it is running/operating.

Only static behavior is not sufficient to model a system rather dynamic behavior is more important than static
behavior. In UML, there are five diagrams available to model the dynamic nature and use case diagram is one of
them. Now as we have to discuss that the use case diagram is dynamic in nature, there should be some internal or
external factors for making the interaction.

These internal and external agents are known as actors. Use case diagrams consists of actors, use cases and their
relationships. The diagram is used to model the system/subsystem of an application. A single use case diagram
captures a particular functionality of a system.

Hence to model the entire system, a number of use case diagrams are used.
 Purpose of use case diagram

The purpose of use case diagram is to capture the dynamic aspect of a system. However, this definition is too
generic to describe the purpose, as other four diagrams (activity, sequence, collaboration, and Statechart) also have
the same purpose. We will look into some specific purpose, which will distinguish it from other four diagrams.

Use case diagrams are used to gather the requirements of a system including internal and external influences. These
requirements are mostly design requirements. Hence, when a system is analyzed to gather its functionalities, use
cases are prepared and actors are identified.

When the initial task is complete, use case diagrams are modelled to present the outside view.

In brief, the purposes of use case diagrams can be said to be as follows

 Used to gather the requirements of a system.

 Used to get an outside view of a system.
 Identify the external and internal factors influencing the system.
 Show the interaction among the requirements are actors.
 3.4 Activity Diagram :

An activity diagram is a type of Unified Modeling Language (UML) flowchart that shows the flow from one
activity to another in a system or process. It's used to describe the different dynamic aspects of a system and is
referred to as a 'behavior diagram' because it describes what should happen in the modeled system.
Even very complex systems can be visualized by activity diagrams. As a result, activity diagrams are often used in
business process modeling or to describe the steps of a use case diagram within organizations. They show the
individual steps in an activity and the order in which they are presented. They can also show the flow of data
between activities.
Activity diagrams show the process from the start (the initial state) to the end (the final state). Each activity
diagram includes an action, decision node, control flows, start node, and end node.

Benefits of activity diagrams :

 Here are some of the key benefits of using activity diagrams to show the flow of activities in a system or
process within your organization:
Shows the progress of workflow amongst the users, and the system

 Activity diagrams clearly show the progress of workflow between the users. This makes it easier for managers
to see what's working well and where the bottlenecks are within the system to make relevant changes.
Demonstrates the logic of an algorithm

 Activity diagrams provide a clear visualization of the logic of an algorithm. This provides a clear view of
what's happening behind the scenes and makes it easy to identify what's working well and needs improvement.
Vividly shows the steps taken when performing a UML use case.

 A use case diagram is designed to show the different ways a user may interact with a system. An activity
diagram vividly shows every single step taken within this use case diagram. This helps business managers to
visualize business processes within the organization fully.

 Models the software architecture elements, including the method, operation, and function

 Activity diagrams can be used to model software architecture elements within a system by showing the
relationships between the components and the constraints for assembling these components. This can provide a
better understanding of how the system works.

 Simplifies the majority of the UML processes by clarifying complicated use cases

 Use cases can either be sequential or concurrent. Concurrent use cases can be tough to describe, as many
different processes are happening simultaneously. Activity diagrams provide a clear visualization of these
processes, making them easier to understand.
Activity Diagram For Admin
Activity Diagram For User
3.5 Sequence Diagram :

To understand what a sequence diagram is, it's important to know the role of the Unified Modeling Language,
better known as UML.

UML is a modeling toolkit that guides the creation and notation of many types of diagrams, including behavior
diagrams, interaction diagrams, and structure diagrams.

A sequence diagram is a type of interaction diagram because it describes how and in what order—a group of
objects works together.

These diagrams are used by software developers and business professionals to understand requirements for a new
system or to document an existing process. Sequence diagrams are sometimes known as event diagrams or event
scenarios.

Note that there are two types of sequence diagrams: UML diagrams and code-based diagrams. The latter is sourced
from programming code and will not be covered in this guide.

Lucid chart’s UML diagramming software is equipped with all the shapes and features you will need to model
both.

Benefits of sequence diagrams

Sequence diagrams can be useful references for businesses and other organizations. Try drawing a sequence
diagram to:

Represent the details of a UML use case.

Model the logic of a sophisticated procedure, function, or operation.

See how objects and components interact with each other to complete a process.

Plan and understand the detailed functionality of an existing or future scenario.

Use cases for sequence diagrams

The following scenarios are ideal for using a sequence diagram:

Usage scenario: A usage scenario is a diagram of how your system could potentially be used. It's a great way to
make sure that you have worked through the logic of every usage scenario for the system.

Method logic: Just as you might use a UML sequence diagram to explore the logic of a use case, you can use it to
explore the logic of any function, procedure, or complex process.

Service logic: If you consider a service to be a high-level method used by different clients, a sequence diagram is
an ideal way to map that out.

Sequence diagram Visio - Any sequence diagram that you create with Visio can also be uploaded into Lucidchart.
Lucidchart supports .vsd and .vdx file import and is a great Microsoft Visio alternative. Almost all of the images
you see in the UML section of this site were generated using Lucidchart.
Admin Sequence Diagarm
User Sequence Diagarm
Admin Manage Customer Record
 Module Hierarchy Diagram

The hierarchy chart is a graphical representation that is used to represent the relationship between various modules
or systems in an organization. In programming, a hierarchy chart is used for representing an organizational
framework. The hierarchy charts can also be utilized to show an organization’s reporting structure.

In such a hierarchy chart, the President is at the top, the Vice Presidents are on the next level which is lower than
its predecessor, and so forth. Within the context of a software program, it indicates the relationship among modules
(or capabilities).

The design team members create hierarchy charts to represent the relationship between modules in an application.

Concept of the hierarchy chart

The hierarchy chart is a structure chart that is used to represent the control information and data that gets
exchanged between the modules. In a hierarchy chart, a rectangular symbol is used to represent each module. An
arrow sign with an open circle at the source end is used to represent each data pair or flow of data.

The workflow, code selection and logical structures of the code are not shown in the structure chart. However,
some creators and designers include transaction hubs in a control module by identifying high-level case structures.

Designers create a program using a hierarchy chart in the same way that an architect creates a plan for a house.
Each of the functions or modules are placed at their correct positions and also the flow of data between the various
modules is also listed.

An example of the hierarchy chart for a software application is discussed in the last section of this article.

How to create Hierarchy chart to represent an organization's structure?

Find the most essential entity of the system. For example, the CEO is in the highest position in an organization.

Choose the components for the second level, third level, fourth level, and so on. List them down.

Once you list them down in the hierarchy chart, connect them to show the relationship between entities and their
parts.

If one wants to add some more information, one can add them to the chart. Use themes available to color the chart
in order to make it visually attractive.

Download the hierarchy chart in an available format like png, jpg, etc., in order to use it in presentations and
documents.
Components of a Hierarchy chart

1.Module - It represents a task or a process.

Sub Module: It is a module that is actually a part of another module.
Control Module: It is a module responsible for coordinating several sub-modules. Library Module: It is a module
that can be called and reused by other modules.

2.Conditional Call - denotes a control module that has the ability to select any sub Module based on a set of
circumstances.

3.Loop - The loop refers to the repeated execution of a set of modules.

4.Data Flow - The flow of data between modules is represented by data flow. A directed Arrow with an empty
circle at the end represents it.

5.Control Flow - It depicts the control flow between the modules. A directed arrow with a filled circle at the end is
also used to express it.

6. Physical Storage- It is a storage space for all of the information.

Module Hierarchy Diagram For Admin
Module Hierarchy Diagram for User
3.6 Table specifications (Database design)
Table 1 : Billing Table
Field Name Data Type Description Constraints Size
ID Int bill Id PRIMARY KEY 25
Name String bill name 10
Mobile No varChar(200) User mobile no 35
Email varChar(200) User email 25
Date varChar(200) Bill date 10
Total varChar(200) Total bill 20
category varChar(200) bill category 50

Table 2 : Category
Field Name Data Type Description Constraints Size
Id Int categoryId PRIMARY KEY 25
Name Varchar(200 categoryname 10
Table 3 : Product
Field Name Data Type Description Constraints Size
Id Int Product id PRIMARY KEY 25
Name Varchar(200) Product name 10
category Varchar(200) Product category 30
Price Varchar(200) Poduct price 20
Table 4 : User
Field Name Data Type Description Constraints Size
ID Int User id PRIMARY KEY 25
Name String User name 10
Mobile No varChar(200) User mobile no 35
Email varChar(200) User email 25
adress varChar(200) User address 10
password varChar(200) Userv password 20
Security question varChar(200) User security 50
question
answer Varchar(200) User answer 100
status Varchar(50) User status 100
 4. USER MANUAL
 4.1 User Interface Screens (Input)

 Login :
 Sign Up :
 Forgot Password :
 Menu :
Category :
Change Password
Change Security Questions :
4.2 Output Screens with data :
4.3 Data Report :
 4.4 TESTING
Unit Test Plan
➢ A unit is the smallest testable part of software.
➢ It usually has one or a few inputs and usually a single input.
➢ In procedural programming a unit may be an individual program, function, procedure, etc.
➢ In object-oriented programming, the smallest unit is a method which to a base/super class, abstract class or
derived/child class.
➢ Some treat a module of an application as a unit.
➢ This is to be discouraged as there will probably be many individual units within that module.
➢ Unit testing is the first level of testing and is performed prior to Integration Testing

Acceptance Test Plan

➢ Functional Testing is a type of software testing where, the system is tested against the functional
requirements/specifications.
➢ Functions are tested by feeding them input & examining the output.
➢ Functional testing ensures that the requirements are properly satisfied by the application. This type of testing is
not concerned with how processing occurs, but rather, with the results of processing.
➢ During functional testing, Black Box Testing technique is used in which the internal logic of the system being
tested is not known to the tester.
➢ User Registration: Process has been properly working and all fields are validated through various validation
checks.
➢ Login & password validation process has been co-operated properly.
➢ Payment gateway has been done properly & accurately.
➢ Contents are playing safely.
➢ Admin side handling & dynamic & real-time data integration module is implemented successfully.
 4.5 Sample program code
 Login :
 Connection Provider Code
 DB Oparations Code
 Open pdf Code
 Product Dao Code
 Add New Product
 Tables code
 Bill Dao code
 Category Dao Code
 User Dao code
4.6 Limitations and Bibliography

Every system has some limitations or drawbacks, some of the limitations of Cafe Management system are:

 It is a Stand-Alone System.
 It can be used by a Single Person.
 As it is machine dependent, machine failure may result in data loss.
 Some manual data entry required
Bibliography

 https://www.stackoverflow.com
 https://developer.android.com
 https://youtube.com
 https://www.visual-paradigm.com