0% found this document useful (0 votes)
1K views

Coffee Shop Management System Documentation-Final

Coffee Shop Management System Documentation

Uploaded by

Aniket Gawari
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)
1K views

Coffee Shop Management System Documentation-Final

Coffee Shop Management System Documentation

Uploaded by

Aniket Gawari
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/ 43

COFFEE SHOP MANAGEMENT

A Project Report
Submitted in partial fulfilment of the
Requirements for the award of the Degree
of

BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY

Aniket Gawari –53003205135


Ramesh Poojari – 53003205165

Under the esteemed guidance of


Dr. Neelam Naik
Assistant Professor BSc.IT

DEPARTMENT OF INFORMATION TECHNOLOGY


Shri Vileparle Kelavani Mandal’s
USHA PRAVIN GANDHI COLLEGE OF ARTS, SCIENCE &
COMMERCE
(Affiliated to University of
Mumbai) MUMBAI, 400056
MAHARASHTRA
2022-2023

i
PROFORMA FOR THE APPROVAL PROJECT PROPOSAL

PRN No: …………………… Roll No: ___________

1. Name of the Student

__________________________________________________________________

2. Title of the Project

__________________________________________________________________

3. Name of the Guide

__________________________________________________________________

4. Teaching experience of the Guide ____________________________________

5. Is this your first submission? Yes No

Signature of the Student Signature of the Guide

Date: ………………… Date: …………………….

Signature of the Coordinator


Date: …………………

ii
PROFORMA FOR THE APPROVAL PROJECT PROPOSAL

PRN No.: …………………… Roll No: ___________

1. Name of the Student

__________________________________________________________________

2. Title of the Project

__________________________________________________________________

3. Name of the Guide

__________________________________________________________________

4. Teaching experience of the Guide ____________________________________

5. Is this your first submission? Yes No

Signature of the Student Signature of the Guide

Date: ………………… Date: …………………….

Signature of the Coordinator


Date: …………………

iii
SHRI VILE PARLE KELAVANI MANDAL’S
USHA PRAVIN GANDHI COLLEGE OF ARTS, SCIENCE AND COMMERCE
(Affiliated to University of Mumbai)
Bhaktivedanta Swami Marg, Juhu Scheme, Vile Parle (West), Mumbai – 400 056. Tel.: 42332071 /
42332041- 44 ● Website: www.upgcm.ac.in ● Email: [email protected]
NAAC ACCREDITED ” A ” GRADE WITH CGPA 3.04

CERTIFICATE
This is to certify that this is a bonafide Project
Report on

carried out by the following student of final year


B.Sc. (I.T.), Semester V

Bachelors of Science in Information Technology


Submitted by

Name of the Student :-

Exam Seat Number :-

In partial fulfilment of the award of degree of B.Sc.(I.T.) from the


University of Mumbai and is a bonafide record of the work done during the
Academic Year 2022–2023.

Internal Examiner External Examiner


Name: Name:
Date: Date:

Course Co-ordinator Principal

iv
SHRI VILE PARLE KELAVANI MANDAL’S
USHA PRAVIN GANDHI COLLEGE OF ARTS, SCIENCE AND COMMERCE
(Affiliated to University of Mumbai)
Bhaktivedanta Swami Marg, Juhu Scheme, Vile Parle (West), Mumbai – 400 056. Tel.: 42332071 /
42332041- 44 ● Website: www.upgcm.ac.in ● Email: [email protected]
NAAC ACCREDITED ” A ” GRADE WITH CGPA 3.04

CERTIFICATE
This is to certify that this is a bonafide Project
Report on

carried out by the following student of final year


B.Sc. (I.T.), Semester V

Bachelors of Science in Information Technology


Submitted by

Name of the Student :-

Exam Seat Number :-

In partial fulfilment of the award of degree of B.Sc.(I.T.) from the


University of Mumbai and is a bonafide record of the work done during the
Academic Year 2022–2023.

Internal Examiner External Examiner


Name: Name:
Date: Date:

Course Co-ordinator Principal

v
Abstract
The main purpose of coffee shop management system is to automate the existing manual
system with the help of advance computerized software so that valuable data can be stored
for a long time with easy access and manipulation of the same data. A registered user can
access the account with valid details. The user can order coffee items by category, add coffee
items to the cart, view cart items and check payment details etc are available to the user. The
user can track their orders with coffee details.

In Coffee Shop Management System, the admin can handle tasks such as adding new Coffee
items, editing / removing Coffee items. The administrator has the authority to view order
details. Payment function and user details are also visible to the administrator. This coffee
shop management system allows end users to register online, read and select coffee from the
e-menu and order coffee by selecting the coffee the user wants to have. The results after
selecting the coffee on the E-menu card will appear directly on the screen next to the chef.
The app is based on a web application.

vi
Acknowledgement

For the success of this project, we would like to appreciate the assistance of everyone who
has been a part of the development or who has been the source of motivation for us.

To start with we would love to appreciate the efforts put up by our teacher in charge Dr.
Neelam Naik. Without your guidance and key element, we do not think it was possible to
build the project. She always mentoring us and guiding us with all the affections and care.

Not to forget we would like to thank our teaching and non-teaching staff of the college
without whose support it was not even possible to think this big. We would like to thank our
fellow students and our friends for helping us carry out the testing procedures.

Lastly not to forget but maybe above all we would love to thank our parents for allowing us
to do this for being there as a backbone to us. It was really an unimaginable task without your
support.

vii
DECLARATION

I hereby declare that the project entitled, "COFFEE SHOP MANAGEMENT" done at Mumbai,
has not been in any case duplicated to submit to any other university for the award of any degree.
To the best of my knowledge other than me, no one has submitted to any other university. The project
is done in partial fulfilment of the requirements for the award of degree of BACHELOR OF
SCIENCE (INFORMATION TECHNOLOGY) to be submitted as final semester project as part of
our curriculum.

Aniket Gawari

viii
DECLARATION

I hereby declare that the project entitled, "COFFEE SHOP MANAGEMENT" done at Mumbai,
has not been in any case duplicated to submit to any other university for the award of any degree.
To the best of my knowledge other than me, no one has submitted to any other university. The project
is done in partial fulfilment of the requirements for the award of degree of BACHELOR OF
SCIENCE (INFORMATION TECHNOLOGY) to be submitted as final semester project as part of
our curriculum.

Ramesh Poojari

ix
Table of Contents

Sr. No Title Page


No.
1 Title Page i

2 Original Copy of Approved Proforma of the Project Proposal ii

3 Certificate Page iv

4 Abstract vi

5 Acknowledgement vii

6 Declaration viii

Chapter 1: Introduction 1

1 1.1 Background 1

1.2 Objectives 1

1.3 Purpose & Scope 2

1.3.1 Purpose 2

1.3.2 Scope 3

1.4 Applicability & Limitations 4

1.4.1 Applicability 4

1.4.2 Limitations 4

1.5 Organisation of Report 4

Chapter 2: Survey of Technologies 6

2 2.1 Front End 6

2.2 Back End 8

2.3 Technology Used 9

Chapter 3: Requirement and Analysis 10


3 3.1 Problem definition 10

3.1.1 Problem in existing system 10

x
3.1.1 Problem Statement 10
3.1.2 Solution to overcome Problems 10
3.2 Requirement’s specification 11

3.3 Planning and scheduling 11


3.3.1 Water Fall Model 12
3.3.2 Scheduling Using Gantt Chart 13
3.4 Software & Hardware Requirement 15
3.5 Preliminary Product Description 15
3.6 Conceptual Diagrams 17
3.6.1 ER Diagram 17
3.6.2 Use Case Diagram 18

Chapter 4: System Design 19


4.1 Basic Modules 19
4.2 Data Design 21
4.2.1 Schema design 21
4.2.2 Data Integrity and Constraints 22
4.3 Procedural Design 22
4.3.1 Data Flow Diagram 23
4.3.2 Sequence Diagram 26
4.4 User Interface Design 27
4.5 Security Issues 30
4.6 Test Case Design 31

xi
LIST OF TABLES
Section No. Table Name Page No.

4.2 Table 1 (Feature Table) 15

4.2 Table 2 (Data Design Customer Table) 21

4.2 Table 3 (Data Design Coffee Table) 21

4.2 Table 4 (Data Design Employee Table) 21

4.2 Table 5 (Data Design Order Table) 22

4.6 Table 6 (Test Cases Design) 31

LIST OF FIGURES
Section No. Figure Name Page No.

3.3.1 Figure 1 (waterfall model) 12

3.3.2 Figure 2 (Gantt Chart) 14

3.6.1 Figure 3 (ER Diagram) 17

3.6.2 Figure 4 (Use case Diagram) 18

4.1 Figure 5 (Basic Modules) 19

4.3.1 Figure 6 (DFD Level 0 Diagram) 23

4.3.1 Figure 7 (DFD Level 1 Diagram) 24

4.3.1 Figure 8 (DFD Level 2 Diagram) 25

4.3.2 Figure 9 (Sequence Diagram) 26

4.4 Figure 10 (UI Login Page) 27

4.4 Figure 11 (UI Products Page) 28

xii
4.4 Figure 12 (UI Products Page) 29

xiii
1. Introduction

Coffee Shop Management involves different processes like managing employee & customer
details, working with offers to be applied in coffee shop, generating reports according to the
working of system and menu card for coffee shop and several other tasks.
Performing all these tasks manually becomes too complex and time consuming.

Features:

1. Ordering System
2. Login System
3. Admin Panel
4. Displays total Cash and Card Transactions
5. Add and Delete Coffee Items
6. Item Counter
7. Instant Order Preview

Coffee Shop Management software is the need and necessity of every organization and its
human resource systems. With Coffee Shop Management System. The employee information
and their details are efficiently managed to satisfy the needs of both the employees and the
administrator

1.1 BACKGROUND

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 the must be passed to the cashier. During
this process it takes lots of time and customer must wait till the process. Only single system it
used during this process. Cafe owners face a business environment with unique challenges. The
tightrope balance between providing the right quality, pricing and ambience, managing with
minimal staff and carving a unique identity for one's brand in a crowded market.

1
1.2 OBJECTIVES

The usage of Coffee Shop Management System would ultimately reduce the overall management
costs thus ensuring greater profits and reduced burdens.

1. Help full for Admin (manager) to manage the cafe.

2. Customer Records.

3. Employee Records.

4. Transaction Details.

5. Payroll Management.

The aim of this project is to gather and analyse and give an in- depth insight of the complete
Coffee Shop Management. This system will help to automate the work and make it easier for the
manager to manage the café.

1.3 Purpose, Scope, Applicability

1.3.1 Purpose
The main purpose preparing these project is to give a general insight into the analysis and
requirements of the existing system or situation and for determining the operating characteristics
of the system. The proposed software will solve all the problem they are facing now. This
software is designed such way that it will generate the bill automatically every order in time. So
there not much worries. This software also equipped with to enter the details of each employee in
the organization, it helps them to track each employee. This being a Desktop based application is
very easy to access. Data and Records are managed in centralized database. Data is secure and
easy to retrieve, store, and analysis, so chances of miscalculations and occurrence of error are
very less.

1.3.2 Scope
2
Scope of the System This management system will be designed to minimize the manual
work in maintaining Managing Employee & Customer details, working of Token system,
working with Offers to be applied in coffee shop, generating Reports according to the working of
system and Menu Card for coffee shop and other managements in coffee shop. 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 coffee shop.
Whereas, it maintains the relationship between customer and the admin in the technical way with
the help of coffee shop management software. The software will facilitate creation of different
Reports such as Customer report & Product report.

1.3.3 Applicability

Coffee Shop Management software system is an system that is use to Maintain the Whole
Record of Coffee Shop link to add Customer Name, Address, Coffee With Detail, Coffee Types.
This system automates and simplifies all the functions of shop and it will also help owner to
handle all the operations.

3
1.4 Achievements
1) Learn to generate project documentation.
2) Learn new technology and implementation of it.
3) Learn debugging and testing the software.

1.5 Organization of Report

Chapter 1- Introduction
This chapter gives the knowledge about what is the objective of the project, what are the scope
and purpose of the project, to whom the project is applicable and the achievements of the project.
It gives the brief information about the introduction of project.

Chapter 2- Survey of Technology

In this chapter, we discuss about the available technologies to develop software, and explain why
we selected the one technology for the completion of the objectives of the project.

Chapter 3- Requirements and Analysis

In this chapter we define the problem on which we are working in the project. And specifies the
requirements of the project related to software and hardware.

Chapter 4- System Design

Describes desired features and operations in detail, including screen layouts, business rules,
process diagrams and other documentation.

4
2. Survey of Technologies

The coffee shop management system is developed using a combination of frontend and
backend technologies.
2.1 Frontend: The part of a website that the user interacts with directly is termed the front
end. Front-end web development is the development of the graphical user interface of a
website, through the use of HTML, CSS, and JavaScript, so that users can view and interact
with that website. It is also referred to as the ‘client side’ of the application.

Frontend technologies
Description

HTML
Hyper Text Markup Language (HTML) is the backbone of any website development process,
without which a web page does not exist.
It will be used to design frontend portion of web pages using markup language. Since it is the
combination of hypertext and markup language, the hypertext will define the link between web
pages. When a user clicks on a word or a phrase that has a hyperlink, it will bring another
web- page. A markup language indicates text can be turned into images, tables, links, and other
representations. It is the HTML code that provides an overall framework of how the site will
look.

CSS
Cascading Style Sheets (CSS) controls the presentation aspect of the site and allows your site to
have its own unique look. It will allow to apply stylesheets to web pages (inline, internal,
external). It will simplify the process of making web pages presentable. The CSS can be added
externally, internally, or embedded in the HTML tags.

JavaScript

5
JavaScript is an event-based imperative programming language that is used to transform a static
HTML page into a dynamic interface. Dynamic describes content that is susceptible to change,
whereas static content is immovable. Before the emergence of JavaScript, the web as a whole
was static in nature. A web page was simply a block of text. Then JavaScript came about,
enabling interactivity, like scrolling, clicking, and much more.

React
React, or ReactJS, is a front-end JavaScript library for building UIs and UI components. React
was developed and is maintained by a small team of developers at Facebook. Today, React is
one of the most popular JavaScript libraries for web development. React uses the classic model-
view- controller (MVC) architecture. In an MVC pattern, there is a separation of concerns
between the presentation layer and the data access layer.

Angular
Angular is a Typescript web application framework, and a reliable component of the
MEAN tech stack — or MongoDB, Express.js, Angular, And Node.js. Typescript is a superset
of JavaScript which extends static typing, permitting stronger type safety for detecting errors
quickly. Instead of MVC, Angular uses a model-view-view model (MVVM) design pattern. An
MVVM pattern also distinguishes the graphical UI from the business logic.

React Native
React Native is a mobile application framework, also the offspring of Facebook. Through React
Native, mobile developers can build applications for Android, Ios, and a variety of other
platforms from macOS to Android TV. This means that React Native is a hybrid app
development platform. To be sure, the primary objective of React Native is to enable native
features on multiple platforms. Other notable feature of React Native are code reusability.

6
2.2 BACKEND
TECHNOLOGY
Description
Backend

The backend is the server-side of the website. The backend (or “server-side”) is the portion of
the website you don’t see. It’s responsible for storing and organizing data, and ensuring
everything on the client-side actually works. The backend communicates with the frontend,
sending and receiving information to be displayed as a web page. There are many different
databases that are widely used, such as MySQL, SQL Server, PostgreSQL, and Oracle.
System will still contain frontend code, but it also has to be built using a language that a
database can recognize. Some common backend languages are Ruby, PHP, Java, .Net, and
Python, C#.

MySQL

It will be used to add, access and manage content in database. (here, maintaining customer
records, availability of coffee prices, employees detail, etc.)

Python

Python is an object-oriented language that focuses on manipulating objects that contain data, is a
straightforward language with a simple syntax that makes it easy to read and debug. With
Python, programmers can use the open-source framework Django to create scalable, or easily
upgraded or side- graded, software for the web more quickly with web development-specific tools and
functions.

C#

C# is a high-level language that can operate on various types of computers easily. Programmers use
this powerful language with frameworks like .NET to design the internal structure of webpages and
connect client interactions with server interactions for a fully functioning program. C# is similar to C
and C++, both useful back-end programming languages.
7
Java

Java is a popular language for developers who want to create large, dependable web applications
that require high-security measures to keep data safe. It's a versatile language that you can use
with many digital platforms, including mobile devices and computers, to create web, mobile and
desktop applications and tools. This versatility and dependability are because Java runs on the
Java Virtual Machine (JVM), which standardizes the machine on which programmers run code
rather than allowing it to run on each programmer's individual machine.

PHP

PHP is the acronym for hypertext pre-processor and is a scripting language, which means the code
you write in this language goes through an interpreter to be read directly by the computer rather
than a compiler, where it would translate into machine-readable code. PHP is best used for
server-side functionality and makes deploying, or submitting and confirming, your code much
easier with deployment tools and capabilities.

2.3 Technology used for project


Coffee Shop Management System will be developed using Java, Jframe, Netbeans , Mysql Database.

8
3. Requirements and Analysis

3.1: Problem Definitions: -


Coffee Shop can be found on seemingly every corner, it’s important for coffee shop owner to establish
an identity for their establishment. This means identifying types of customers you want to attract.

3.1.1 Problems in existing system

1. The existing system requires more time for searching old files and details of the products
2. It is difficult to remember prices for small-small products.
3. It is also difficult to maintain the sales record by owner or manager.
4. It is less Secured.
5. Difficulties in checking the available stock of items.
6. Difficulty to generate sales reports.
7. Managing Customer records is difficult in the existing system.

3.1.2 Problem Statement:


This project will make available different types of coffees for the purchasing purpose, where
customer can purchase coffees on the spot.

3.1.3 Solutions to overcome the problems in existing system:

1. Because this is an automated system, so there are no chances of calculation problem.


2. To store records admin will using separate database.
3. It provides most secured way for purchasing the coffees.
4. Admin can generate daily sales reports.
5. It is easy for admin to check and maintain the stock report.
6. UI (user interface) is user friendly and provides various options for customers.

9
3.2 Requirements Specifications
Requirement specification plays an important part in the analysis of a system. Only when the
requirement specifications are properly given, it is possible to design a system, which will fit
into required environment.

1. Admin can able to generate sales report where he can see daily sale of coffee shop.
2. Admin can easily maintain the stock reports.
3. Software will be able to develop the customer details.
4. Customer can purchase and pay online.
5. The system should be better than the existing system

3.3Planning and Scheduling

System Development Life Cycle (SDLC) describes the data design applications design. SDLC
is an interactive rather than a sequential process. Thus, SDLC might help to refine feasibility
study to the user requirements. Here we are using the Waterfall Model for our system

3.3.1 Waterfall Model

The waterfall model is a classical model used in system development life cycle to create a system
with a linear and sequential approach. It is termed as waterfall because the model develops
systematically from one phase to another in a downward fashion.

10
Figure 1:Waterfall model

11
3.3.2 Scheduling Using Gantt chart

Planning is done for improving the scope and quality of system.


Planning is done for time schedule of each activity.
Planning also done for budget i.e. how much cost required each task or activity.
Planning is done for allocating and sharing resources between projects.
Risk management plan should be there to remove the future risks in project.
To summarize, a Gantt chart shows you what has to be done (the activities) and when (the schedule).
A Gantt chart is a timeline view that makes it easy to see how a project is tracking. You can visualize
project tasks and see how they relate to each other as projects progress over time. Use this tool to
simplify your tasks and details with a visual project timeline by transforming task names, start dates,
durations, and end dates into cascading horizontal bar charts. With a Gantt you can plan out all of
your tasks, so complex projects are manageable and easy to tackle. We can use a Gantt to figure
out the minimum delivery time for your project to get our project finished efficiently.

12
Figure 2 : GANTT CHART

13
3.4 Software and Hardware Requirements
o Software requirements:

• Java - Net Beans


• Operating System (Windows 7 or above)
• Database (MySQL server)

o Hardware requirements:

• Laptop/Desktop
• Minimum 4GB RAM
• Processor 1 GHz or higher
• Hard disk
• Ethernet Connection or wireless connection (Wi-Fi)

3.5 Preliminary Product Description


Following is a list of functions and operations performed by the system, for registered and
non-registered users.

Table 1: Features Table


Features Owner Customer Employee
Registering And Yes Yes Yes
Login

Searching for Yes Yes No


different varieties of
Coffees
Accessing Tokens NO Yes NO

Sale Report Yes No No

14
Payroll Yes No Yes

Transaction Details Yes Yes No

Feedback No Yes No

15
3.6 Conceptual Models:
A conceptual model is a representation of a system, made of the composition of concepts which
are used to help people know, understand, or simulate a subject the model represents. It is also
a set of concepts.

3.6.1 ER Diagram

Figure 3: ER Diagram

16
3.6.2 Use Case Diagram

Figure 4 : Use Diagram

17
4. System Design

4.1 Basic Modules

Figure 5:Basic Modules

Registration / Login Module:


Login Page: These page will allow you to login as an owner or employee or customer if
you have registered.
Register: In these page you will register yourself to the website if you are a new to it by
giving required details.
Admin Module: In this module, owner will manage entire coffee shop. By generating reports
of sale, stock, employee details and payroll, customer details and transaction details.
Employee Module: In this module, employee will be able to register or login themselves by
entering correct username and password. And the employee details access will be given to the
owner.
Customer Module: In this module, customer will be able to register or login themselves by
entering correct username and password. Customer will be able to search the different variety of
coffee, and can order the coffee by paying online. They can also avail different offers that are
currently available. All the access of customer detail will be given to the owner.
18
Generating/Managing Reports: Here owner will be able to generate daily sales report,
Stock report.
Online Payment: Customer will be ordering the coffee in the shop but they can pay online.
Payroll Management: Owner will manage the payroll of the employees under this module.

19
4.2 Data Design

4.2.1 Schema Design

a) Customer Table

Table 2: Customer Table

Attributes Data Type Constraints


Cust_id int Primary Key
Cust_name Varchar(30) Unique ,Not Null
Email Varchar(30) Unique , Not Null
Password Varchar(30) Not Null
First Name Varchar(30) Not Null
Last Name Varchar(30) Not Null
Gender Char(1) Not Null
Contact Number Int Unique ,Not Null
Signup_Date timestamp

b) Coffee Table

Table 3: Coffee Table


Attributes Data Type Constraints
Coffee_name Varchar(30) Not Null
Coffee_price int

c) Employee Table:
Table 4: Employee Table
Attributes Data Type Constraints
Emp_id int Primary Key
Emp_name Varchar(30) Unique ,Not Null
Email Varchar(30) Unique , Not Null
Password Varchar(30) Not Null
First Name Varchar(30) Not Null
Last Name Varchar(30) Not Null
Gender Char(1) Not Null
Contact Number Int Unique ,Not Null

20
d) Order Detail Table:

Table 5: Order Detail Table


Attributes Data Type Constraints
Order_id int Primery key
Order_amt inr Not Null
Quantity int Not Null
Cust_Id int Not Null

In registration & login module


This module is applicable for owner, employee and customer too.
 Password should consist of 6-8 characters.
 Username should be unique and valid
 Email-id entered by user should be a valid email-id
 If username and password combination matches, then only login access should be
given.
In Order module
 User should be register or login successfully before ordering the coffee.
 Name of the coffee should not be empty, i.e. null.
 Quantity of the coffee should not be empty.

4.3 Procedural Design


21
4.3.1 Data Flow Diagram
Level 0

Figure 6 : DFD Level 0 Diagram

22
Level 1

Figure 7: DFD Level 1 Diagram

23
Level 2

Figure 8: DFD Level 2 Diagram

24
4.3.2 Sequence Diagram

Figure 9: Sequence Diagram

25
4.4 User Interface Design

Figure 10: User Interface Login Page

26
Figure 11: User Interface Products Page

27
Figure 12: User Interface Products Page

28
4.5 Security Issues
Password encryption: Passwords are encrypted and stored securely into the
database. Even though there is attack of hacker’s data is not leaked and it is
completely safe into database.
Authentication: Authentication ensures that each entity involved in using a Web
service—the owner, the employee, and the customer (if there is one)—is
what it actually claims to be. Authentication involves accepting credentials
from the entity and validating them against an authority.

29
4.6 Test Cases
Table 6: Test Cases

Sr. Descriptions Possible Expected Result


no. Input
1 Incorrect username or User-1234 Invalid Credentials.
wrong password. Pass_26 Incorrect username or
password
2 Correct username User$1234 Logged in Successfully.
and password Pass$6
3 Invalid Email Ram123.gmail.com Invalid Email.
Please enter a valid Email-Id.
4 Valid Email [email protected] Logged in Successfully.
5 Quantity 0 Please Enter Quantity.
6 Quantity 1,2,3 Items added to cart.
7 Search for coffee Green Tea Invalid Coffee Name. Please
enter valid name.
8 Search for coffee Latte Enter Quantity.

9 Generate sale report with 01-02-2022 - Please enter valid date


starting and end date 30-02-2022
10 Generate sale report with 01-08-2022 - Report Generate Successfully
starting and end date 30-09-2022

30

You might also like