Coffee shop management system

Coffee Shop
Management System

Coffee s
hopsds
Prepared By:
Herina Kalathiya
Juli Patel

Guided By:
Mr. Rajen Trivedi

Prepared By: Juli & Herina Page 1

 Coffee shop management system

INDEX
CHAPTER NO CONTENT PAGE NO

Chapter 1 Introduction
1.1 Background 7
1.2 Objective 8
1.3 Purpose 9
1.4 Scope 10
1.5 APPlicablity 10

Chapter 2 Requirement And Analysis

2.1 Study of the system 12
2.2 Problem Defination 14
2.3 Requirement Specification 15
2.4 Hardware Requirement 16
2.5 Software Requirement 16
2.6 Planning and Sceduling 17

Chapter 3 System design

3.1 Over all System design using designing tools 19

3.2 Data Dictionary 30

3.3 Input/Output Design 36

Chapter 4 Testing And Implemention

4.1 Testing Approach Used 53
4.2 Test Case 58
4.3 Implemention Approches 59

Chapter 5 Conclusion
5.1 Limitation Of System 64
5.2 Future Scop Of System 64
5.3 Bibliography 65

Prepared By: Juli & Herina Page 2

 Coffee shop management system

ACKNOWlEGEMENT

 We would like to express our special thanks to gratitude to our guidance

Mr.Rajan Trivedi Sir, as well as our principal Mr.Vijay sir, who gave us
golden opportunity to do this wonderful project on the topic Coffee Shop
Management System,which also helped us in doning lot of research and we
came to know about so many new things, we are really thankful to them.

 Secondly ,we would like to thanks our parents and friends and all faculty
member of BCA department who helped us a lot in finalizing this project
within the limitation time frame.

 We have taken effort in this project. However,it would not possible without
the kind support and helping of many inndividuals and organization.we would
like to extend our sincere thanks to all of them.

With sincere regards,

 Juli Patel
 Herina Kalathiya

Prepared By: Juli & Herina Page 3

 Coffee shop management system

PROJECT PROFILE
Project Title Coffee shop Management system

Front End Asp.Net

Back End SQl Server

Operating System Windows 10

Project Guide Mr.Rajen Trivedi

Submitted by Miss.Patel Juli

Miss. Kalathiya Herina

Submitted To Shree Adarsh BCA College

Botad-364710

Prepared By: Juli & Herina Page 4

 Coffee shop management system

Chapter:-1

INTRODUCTION

1.1 Background
1.2 Objective
1.3 Purpose
1.4 Scope
1.5 Applicability

Prepared By: Juli & Herina Page 5

 Coffee shop management system

INTRODUCTION

 “Coffee Shop Management System” is a web application. This system is developed to

automatic day to day activity of shop.

 Coffee shop management system is the system for managing the coffee shop business.
After successful login the customer can access the menu with the item listed according to
desired time. The main point of developing this system is to help coffee shop
administrator.

 The coffee shop management system helps the shop manager to manage coffee shop
effective and efficiently by computerizing meal ordering and billing.

 It is a complete solution, beginning with taking orders from customer and ending with
billing. By standardizing the entire process, this system radically improves serving speed.
It’s easy to install and to use.

Prepared By: Juli & Herina Page 6

 Coffee shop management system

1.1 BACKGROUND

 Operating system: windows 10,windows 8.1,windows 7,windows XP

 Technology used:
Front End: ASP.NET
Back End: SQL Server Database

 Microsoft visual studio is an integrated development Environment (IDE) from Microsoft.

It can be used to develop console and graphical user interface application along with
windows forms application, web sites, web application and web services.

ASP.NET

 Asp.net is a web application framework designed and developed by Microsoft.

 Asp.net is an open-source server-side web application to designed for web development to

produce dynamic web pages.

 Asp.net is only used to create web application and web services.

 It provides the easy way to build, deploy & run the web application on any browser. Web
forms are pages that your user request using their browser.

SQL SERVER DATABASE

 SQL Server is a relational database model produced by Microsoft.

 SQL Server 2008, also support for structured and semi structured data, including digital
media and multimedia data.

 SQL Server includes better compression features, which is also helps in improving
scalability.

Prepared By: Juli & Herina Page 7

 Coffee shop management system

1.2 OBJECTIVE

 It is designed to avoid Paper work. It is designed to increase operational efficiency, saving

our money and time, provide more security.

 This project to provide ecofriendly environment in various activity such as updating,

searching etc.

 This online software is increasing sales by 30% in a year.

 This software is developed to manage the coffee shop more effectively and efficiently by
computerizing ordering and billing.

 The main objective is to attract coffee lovers and teenagers to spending time over coffee
and to attract business meeting over coffee.

Prepared By: Juli & Herina Page 8

 Coffee shop management system

1.3 PURPOSE

 The main purpose of coffee shop management system is to reach the wider range of
customers and to educate them about existing and new packages and discount offered for
special day and occasion by coffee shop.

 Allows user to pay bill online.

 This project helps manager to know customers order details in few second and it helps to
knows customer choice and manager change items according to customer requirement.

 This system reduces the time consumption.

Prepared By: Juli & Herina Page 9

 Coffee shop management system

1.4 SCOPE

 This system is help to manage and run the shop systematically.

 All the required information’s about customers will be saved in the system which can be
only accessed by the system admin.
 To store the database of coffee shop.
 To have faster, easier, to search a detail.
 All the registration details are stored in files on stable storage.

1.5 APPLICABILITY

 This type of website is used in any kind of shop and restaurant like Bar, Bakery shop, Cake
shop, Pizzeria, Steak house, Deli, Buffet, Hotel restaurant and more.

 This website is give benefit to customer and user to purchase item 24 * 7. In this type of
website the item are available like, Cake, Sandwich, Pastry, Tea, Desert, Drinks, Fast food,
cookies etc.

 The customer is also ordering and Purchase any above item form the menu list.

Prepared By: Juli & Herina Page 10

 Coffee shop management system

Chapter:-2

REQUIREMENT AND ANALYSIS

2.1 Study of the system

2.2 Problem definition
2.3 Requirement specification
2.4 Hardware requirement
2.5 Software requirement
2.6 Planning and scheduling

Prepared By: Juli & Herina Page 11

 Coffee shop management system

2.1 STUDY OF THE SYSTEM

 Modules of the system

 The System after analysis has been identified to be presented with the following modules:
1. Administration user interface
2. Generic user interface

 Modules of the project

 The structure of the system is described by the figure as shown:

Coffee shop
management

Admin User

Prepared By: Juli & Herina Page 12

 Coffee shop management system

 User Management
User management is a critical part of maintaining a secure system. It is important that you
understand how you can protect your system through simple and effective user account
management techniques.

 Menu Management
Menu management system improve the customer experience, streamlines your ordering
process and increase efficiency in your coffee shop. A good coffee shop menu design is a key to
any shop’s marketing plan. It expresses your personality, focuses your overall operation and
keeps your brand fresh in your customer’s mind.

Menu management is done by using following features-

 Add Menu Item:-

In this we add item in a menu by assigning a unique item code to each item. When we add
any item; we have given name, price, and category for any item. The access of adding the item is
given to administrator.

 View Full Menu:-

As the name indicates, in this we display the full information of all the items in a menu.
Only outlook of all the items is displayed, no editing is performed.

 Edit Item :-
If any information about the menu items is changed or incorrect then editing can be
performed. After editing we can save the item again, the new changes are updated automatically.

 Delete Item:-
By using this feature, we can delete any item from the menu.

 Customer Management
The customer management system is an application, which allows the users to store,
manage, and exchange customer information for efficient and effective management.

Prepared By: Juli & Herina Page 13

 Coffee shop management system
Customer Management is done by using following features-

 Add Customer:-
In this customer can make a new account which provides full information about the
customer like customer Name, Address, E-mail, etc.

 Bill Management
The process of sending a bill to customer for goods or services is called Billing. It is
complete solution starting from taking orders from clients in producing and closing bills with
different payment option.

2.2 PROBLEM DEFINATION

We are going to build software Coffee Shop Management System that will have several
features such as:

 Online Ordering
 Customer Management
 Billing
 Convenient way of Shopping
 Available 24 *7

We tried to make the problem more obvious Because of the fact that the project is in abstract
state now. we tried to concertize the project .To achieve that, we tried to think about the similar
software examples that are used in real life, like restaurant .One of the reasons to do that was to
draw the borders of the problem, how much we can achieve. After drawing the borders of
problem we divided the solution into several parts, which may change during the development of
the project.

Prepared By: Juli & Herina Page 14

 Coffee shop management system

2.3 REQUIREMENT SPECIFICATION

 System requirement are expressed in a software requirement document. The SOFTWARE
REQUIREMENT SPECIFICATION is the official statement of what is required of the
system developers. This requirement document includes the requirement definition and the
requirement specification.

 The software requirement document is not a design document. It should set out what the
system should do without specifying how it should be done. The requirement set out in this
document is complete and consistent.

 A software requirement specification (SRS) a document that captures complete description

about how the system is expected to perform. It is usually signed off at the end of
requirement engineering phase.

 It defines the features and functionality that the product requires to satisfy all stakeholders
(business, users) needs.

 A standard SRS includes:

 A goal/purpose
 A summary of the whole process
 Specific requirement

Prepared By: Juli & Herina Page 15

 Coffee shop management system

2.4 HAEDWARE REQUIREMENT

Processer Intel

RAM 1GB and above

Disk Space 8GB and above

2.5 SOFTWARE REQUIREMENT

Operating System Windows

Tool Visual Studio 2008 or Latest

Web-Technology Asp.net

Front-End Asp.net

Back-End SOL Server

Prepared By: Juli & Herina Page 16

 Coffee shop management system

2.5 PLANNING AND SHEDULING

MONTHS/WEEKS WEEK1 WEEK2 WEEK3 WEEK4

1st Month Retrieving project Selection of Designing Implementation

definition. front-end and of master of administrator
back-end. page and module.
Introduction of creating
project. Designing of forms.
database and
Understanding tables.
project.

2ndMonth Implement the first Implement Implement Designing

and second chapter the coding of the coding diagrams such as
of documentation all admin of all UML diagrams.
forms. customer
forms.

3rd Month Complete the Third Testing each Create the Completing
and Forth chapter and every exam and Documentation.
of documentation. algorithm result
with all types project. Complete the
of query and project.
improve the Complete
performance the design
of website of project.

Prepared By: Juli & Herina Page 17

 Coffee shop management system

Chapter:-3

SYSTEM DESIGN

3.1 Overall System design using designing tools

3.2 Data Dictionary
3.3 Input/ Output Design

Prepared By: Juli & Herina Page 18

 Coffee shop management system

3.1 OVERALL SYSTEM DESIGN USING DESIGNING

TOOLS
 System Design is the Process of defining the architecture, modules, interfaces, and data for a
system to satisfy specified requirement.

 System design is provide the overview of the project.

 System Design=system + design

System: Assembly of different components for the specified requirements.

Design: How efficiently the assembly of different components is done.

 For example, if we have to build large application like Facebook, Instagram, Youtube, etc.
First we note down all the requirements.

 System design is a way by which the required amount of reliability, scalability performance,
security and consistency are satisfied in any real-world application.

 System design is a high-level design identifying the system processes, functional components
and their interface. System design is derived from system requirement.

 We need it because we want our whole system designed in such a way so that we used
system design.

Advantages:

 It reduces the cost of designing.

 It eliminates inconsistencies.

 It speeds up the process.

 It provides a lot of resources.

 It makes the life of the customer easier and simpler.

Prepared By: Juli & Herina Page 19

 Coffee shop management system

 Reduce development time.

 UML DIAGRAM

 UML is stands for Unified Modeling Language.

 UML is a graphical language for visualizing, specifying, constructing and documenting the
system.

 UML provides the blue-print for business process, system function, programing language
statement reusable component.

 UML is different from the other common programming languages like C++, JAVA, etc.

 UML is may be used in variety of ways to support a software development methodology but
in itself it does not specify that methodology or process.

 All the elements, relationships are used to make a complete UML diagram and the diagram
represents the system.

 Here are various kinds of methods in software design. They are as follow:
 Use Case Diagram
 Class Diagram
 Activity Diagram

Prepared By: Juli & Herina Page 20

 Coffee shop management system

 Use Case Diagram

 A use case diagram is a dynamic or behavior diagram in UML. Use case diagram model the
functionality of system using actors and use cases.

 Use cases are a set of actions, services, and functions the system need to perform.

 In this context a “system” is something being developed or operated, such as a web site. The
“actors” are people or entities operating under defined roles within the system.

 Use case diagrams are valuable for visualizing the functional requirement of a system that
will translate into design choice and development priorities.

 They also help identify any internal or external factors that may influence the system and
should be taken into consideration.

 They provide a good high level analysis from outside system. Use case diagrams specify how
the system interacts with actors without worrying about the details of how that functionality
is implemented.

 A use case is a description of set of sequence of actions .It is association between the use
cases and actors. An actor represents a real world object.

 Primary Actor – Sender, Secondary Actor - Receiver

Prepared By: Juli & Herina Page 21

 Coffee shop management system
 Following are different elements that are used in use case diagram.

 Use Case :-

 Actor :-

 Communication :-

 Include :-

 Exclude :-

 System Boundary :-

Prepared By: Juli & Herina Page 22

 Coffee shop management system

Login

Get Registered

Change Password

Item Ordering

Pay Bill

Access Database

User Admin
Add Item

Manage Menu

Manage Ordering

Manage Payment

Prepared By: Juli & Herina Page 23

 Coffee shop management system

 Activity Diagram

 An Activity diagram is essentially a flowchart, showing flow of control from activity to

activity.

 In UML, activity diagrams can be used to describe the business and operational step-by-
step workflows of components in a system.

 An Activity diagram is a behavioral diagram it depicts the behavior of a system.

 Activity diagram is typically used for business processing model. It gives the detail view of
system.

 An activity diagram is show the overall flow of control.

 So, the purpose can be described as to:

 Draw the activity flow of a system.
 Describe the sequence from one activity to another.
 Describe the parallel, branched and concurrent flow of the system.

Prepared By: Juli & Herina Page 24

 Coffee shop management system
 Following are different elements that are used in activity diagrams:

 Start/Begin

 Action

 Decision

 Action/Control flow

 Stop

 Join

 Transaction(Fork)

Prepared By: Juli & Herina Page 25

 Coffee shop management system

 Customer :-

Customer
Registration

Not Valid Valid

Login

View Menu

Item Ordering

Pay Bill

Prepared By: Juli & Herina Page 26

 Coffee shop management system

 Admin :-

Login

In Valid
Valid

Manage Menu Manage Manage Manage

Item Customer Ordering Payment

Logout

Prepared By: Juli & Herina Page 27

 Coffee shop management system

 Class Diagram

 Class diagram are the most common diagram used in UML.

 Class is nothing but a structure that contains both variables and
methods.
 The class diagram shows a set of classes, interface, association,
collaboration and their relationship.
 Class diagram basically represent the object oriented view of system,
which is static in nature.
 Class diagram represent the object orientation of a system. Hence, it
is generally used for development purpose.
 This is the most widely used diagram at the time of system
construction.
 Following are class notation and symbol:

Class name
Attributes
Operation ()
Responsibility

 Top section is show the name of the class.

 The second section is describing the attribute of class.
 The third section is show the operation that performed by the class.
 The forth section is optional to show any additional component.

Prepared By: Juli & Herina Page 28

 Coffee shop management system

Customer
Admin
Id : varchar2
Username : Varchar2
+1 Username : varchar2
Password : varchar2
Password : varchar2
Email : varchar2
+ Login ()
Mobile no : varchar2
+ Add Item()
# Login ()
+View Item()
# Registration ()
+ Update Item()
# View Menu()
+ Delete Item () 1 # Buy Item()
+ Change password ()
# Payment()
+

New User
1 1

+View Product() + 1 1
+Get Register() Shop
Id: Varchar2
Name: Varchar2
Category: Varchar2
Price: Varchar2
+Add Item()
+Delete Item()
+Update Item()

Prepared By: Juli & Herina Page 29

 Coffee shop management system

3.2 DATA DICTIONARY

 A Data dictionary is a file or a set of files that contains a database’s metadata.

 The data dictionary contains records about other objects in the database, such as data
ownership, data relationship to other objects, and other data.

 A data dictionary is a place in the database that holds information.

 A data dictionary Provides information about each attribute also referred to as fields, of a
data model.

 Benefits of data dictionary are mainly due to the fact that it is a central store of
information about database.

 Benefits includes:
 Improved documentation and control
 Easier data analysis
 Simpler programming
 Better means of estimating the effect of change
 Reduce the redundancy

Prepared By: Juli & Herina Page 30

 Coffee shop management system

Admin Login:-

Table Name :- Login

Use :- It stores the username and password.

Filed Name Data Type Size Description

Username Varchar 50 Store the username

Password Varchar 50 Store the password

Menu:-
Table Name:- Menu

Use: - Add the item in shop.

Primary Key :- Id

Filed Name Data Type Size Description

Id Int 50 It Store Item Number

Name Varchar 50 It store the name of item

About Varchar 500 It store the detail of item

Price Int 50 It store the price of item

Category Varchar 50 It Store the category of item

Image Varchar 50 It store the image of item

Prepared By: Juli & Herina Page 31

 Coffee shop management system

User Register:-
Table Name:-URegis

Use: - It Use to register new user for the shop.

Filed Name Data Type Size Description

User Id Varchar 50 It store the user id number

First Name Varchar 50 It store the first name of user

Last Name Varchar 50 It store the last name of user

username Varchar 50 Store the username

Email Varchar 50 Store the email

Password Varchar 50 Store the password

Confirm Varchar 50 Store the confirm password

password

Phone no Varchar 50 Store the phone number

City Varchar 50 Store the city

Gender Varchar 50 Store the gender

Prepared By: Juli & Herina Page 32

 Coffee shop management system

Feedback:-
Table Name:- Feedback

Use: - It stores the user feedback.

Filed Name Data Type Size Description

Feedback Type Varchar 50 It store the type of feedback

Full name Varchar 50 It store the name of user

Email Varchar 50 It store the email

Message Varchar 500 It store the message

Order:-
Table name:- Order

Use: - It store order detail.

Primary Key:- Oid

Field Name Data Type Size Description

Oid Int 50 It store order id

Odate Datetime 50 It store date time of order

Ostatus Varchar 50 Store order status

Username Varchar 50 Store username

Id Int 50 Store item id

Qty Int 50 Store quantity of item

Prepared By: Juli & Herina Page 33

 Coffee shop management system

Add To Cart:-
Table Name:- Ucart

Use:- It use to add item on the cart.

Primary Key :- Cart id

Filed Name Data type Size Description

Username Varchar 50 It store the name of user

Id Int 20 It store the item id

Name Varchar 50 Store the name of item

Qty Int 20 Store the quantity of item

Price Int 50 Store the price of item

Total Int 100 Store the total of item

Image Varchar 500 Store the item image

Cart Id Int 20 Store the cart id

Prepared By: Juli & Herina Page 34

 Coffee shop management system

Payment:
Table Name:-Payment1

Use: - It display payment detail.

Field Name Data type Size Description

Payment -Type Varchar 50 It stores the type of

payment.

Username Varchar 50 Store the username

Total Int 50 Store the total of item

First-name Varchar 50 Store the first name

Last-name Varchar 50 Store the last name

Ac-no Int 50 Store the user account

number

Conf-ac-no Int 50 store confirm account

number

Bank-name Varchar 50 Store the bank name

Prepared By: Juli & Herina Page 35

 Coffee shop management system

3.3 INPUT/OUTPUT DESIGN

Admin :-
 Admin Login:-

 This is admin login page. This page contains two fields Username and
Password.

Prepared By: Juli & Herina Page 36

 Coffee shop management system
 Add Item Details:-

 This page is for adding item details. Item details can be inserted by choosing
category.

Prepared By: Juli & Herina Page 37

 Coffee shop management system
 Update Item Details:-

 This page is for delete item by click delete button and update item by select
button which can redirect than selected item details to following page.

Prepared By: Juli & Herina Page 38

 Coffee shop management system

 The above page selected item details redirect here in this page which details
are update.

Prepared By: Juli & Herina Page 39

 Coffee shop management system

 Change Password:-

 This page is used by admin to change their password.

Prepared By: Juli & Herina Page 40

 Coffee shop management system

 Customer Details:-

 This page shows all the customer registration details which only admin can see.

Prepared By: Juli & Herina Page 41

 Coffee shop management system

 View Orders:-

 In this page it shows all the order that is given by customer with their
username.

Prepared By: Juli & Herina Page 42

 Coffee shop management system

User:-
 User login:-

 This is a user login page. This page contains three filed Username, E-mail and
Password.

Prepared By: Juli & Herina Page 43

 Coffee shop management system
 Forget Password:-

 If the user forgets their password then this page take Username and E-mail id
from user and give the Password.

Prepared By: Juli & Herina Page 44

 Coffee shop management system
 User Home:-

Prepared By: Juli & Herina Page 45

 Coffee shop management system

 This is user Home Page and Food Gallery.

Prepared By: Juli & Herina Page 46

 Coffee shop management system
 User Registration:-

 This is user registration page which contains Username, Password, E-mail,

Phone number, Address etc.

Prepared By: Juli & Herina Page 47

 Coffee shop management system
 Change Password:-

 This is change password page. If user changes their password then user can
change their password using this page.

Prepared By: Juli & Herina Page 48

 Coffee shop management system

 View Menu:-

 This page shows all the details of item which also can be categories that are
selected by user.

Prepared By: Juli & Herina Page 49

 Coffee shop management system

 My Cart:-

 Customer can only view their own cart details in this page.

Prepared By: Juli & Herina Page 50

 Coffee shop management system
 User Logout:-

 If payment process can be successful then payment page redirect this page.

Prepared By: Juli & Herina Page 51

 Coffee shop management system

Chapter:-4

TESTING & IMPLEMENTION

4.1 Testing Approach Used

4.2 Test Case
4.3 Implementation Approaches

Prepared By: Juli & Herina Page 52

 Coffee shop management system

4.1 TESTING APPROCH USE

A test approach is the test strategy implementation of a project would be carried out.

 Test approach has two techniques

1. Protective:-
 An approach inn which the test design process is initiated as early as possible in order to
find and fix the defects before the build is created.
2. Reactive:-
 An approach in which the testing is not started until after design and coding are
completed.

 Testing:-
 System testing is a label of software testing where complete or integrated software is
tested.
 It is also verify of that is need specify requirement of user.
 System testing is carried out by specialist tester or independent tester.
 System testing should investigate both functional and non-functional requirement.
 System testing is an expensive and critical process that can take as much as 50% of the
budget for program development.
 The common view of the testing held by user is that it is perform to prove there are no
errors in program.
 In software testing it is trying to make the program fail and find an error.
 Testing program does not guaranty system readability.

Prepared By: Juli & Herina Page 53

 Coffee shop management system
 Types of testing methods

Black Box Testing

White Box Testing

Gray Box Testing

Testing GUI testing

Usability testing

Performance Testing

Procedure Testing

Prepared By: Juli & Herina Page 54

 Coffee shop management system
1) Black Box Testing:-

 Black box testing is a technique that ignores internal mechanism of the system and focus in
input and output.

 It is also called functional testing because the tester is only concern with functionality of
the system.

 Black box testing performs without planning and documentation.

 The tester is oblivious to the system architecture and does not have access to the source
code.

 When performing a black box test, a tester will interact with the system user interface by
providing inputs and examining outputs without knowing how and where the inputs are
worked upon.

2) White Box Testing:-

 White box testing is a testing technique that focuses on internal mechanism of the system.

 White box testing is a testing of internal working of code of software application.

Prepared By: Juli & Herina Page 55

 Coffee shop management system

 It is also called Structure testing and Glass box testing.

 White box testing is the detailed investigation of internal logic and structure of the code.

 In order to perform white box testing of an application, the tester needs to process
knowledge of the internal working of the code.

3) Gray Box Testing:-

 Grey box testing is a combination of black box and white box testing.

 The aim of this testing is to search for the defects if any due to improper usage of
application.

 Grey box testing is also knows as translucent testing.

Prepared By: Juli & Herina Page 56

 Coffee shop management system

 Gray box testing is beneficial because it takes the straightforward techniques of black box
testing and combines it with the code targeted system in white box testing.

4) Performance Testing:-

 Performance testing is a type of testing to ensure software application with performs under
user specification.

 It is mostly used identify any bottleneck or performance issue rather than finding bugs.

 The focus on performance testing is checking a software program speed, scalability and
stability.

 If system goes live without doing performance testing many causes the error like, running
the system low while several user access system.

5) GUI Testing

 These test GUI (Graphical user interface) characteristics like text, formatting, textbox,
buttons, layouts, colors, fonts, font size.

 GUI testing is time consuming and this is test by client instead of developers.

6) Usability Testing

 Usability testing focus on the user easy to use the application system flexibility and
ability of the system to meets the objective.

7) Procedure Testing

 This method determine clarity of documentation check on operation and use of the
system it check system that is same in documentation.

Prepared By: Juli & Herina Page 57

 Coffee shop management system

4.2 TEST CASE

Common Tests:

SR NO. TEST CASE EXPECTED RESULT ACTUAL

RESULT
1 Check Text box for Text, with all validations is inserted PASS
validation

2 Check tab order It should be in proper logical order and it PASS

should move through all the fields.

3 Check field’s name, It should be as per program specs. PASS

type, size, screen
layout etc. against
program

4 Check field’s name, Fields name, type and size should be PASS
type and size for each consistent throughout the database for a
database table and particular field.
against database
design

5 Check heading/titles There should be no grammatical mistake or PASS

of all the forms and spelling mistake. All heading and titles
pages should be consistent throughout the
system.

6 Field validation Proper validation should be placed PASS

according to the program specification to
validation the required fields and to check
the type of allowed character.
7 Select value from the The dynamic values from the database PASS
dropdown should be filled in the drop down

8 Delete record and try Record must be deleted from the database PASS
to find it in the and should not be available there
database

Prepared By: Juli & Herina Page 58

 Coffee shop management system

4.3 IMPLEMENTATION APPROCH

Implementation can be defined as putting (a decision, plan, agreement, etc.) into effect.
System implementation is the delivery of that system into production (that is, the day-to-day
business or organization operations.

It is important to understand that this topic is not about building or programming a

system, but rather making the system live. There are following four common methods is
implement system.

 Parallel

 When the new system is used at the sometime as the old system the two system are said to
be running in parallel.

 User can compare the output of the old system with the output of the new system, to ensure
correction

 The disadvantage of parallel system is that took more time to enter data into two different
systems.

 For example, in our system we can compare of the new system with the old system.

 Phased

 When small parts of the new system gradually replace small parts of the old system, the
implementation methods is said to be phased.

Prepared By: Juli & Herina Page 59

 Coffee shop management system

 A failure of the implementation method takes more time to get the new system fully online
then other methods.

 For example, the old system in which it allows only to book service but in new system it
will allow book service as well as add service providers.

 Pilot

 When a small group of users within an organization uses a new system prior to wide use,
the system is said to be piloted.

 In this implementation approach training can be supported by pilot group failure or

problem can be identified and addressed without widespread impact to the organization.

 For example, the system is implementing by some of the customer and books the service
online and asks them to try new system, and provide feedback.

Prepared By: Juli & Herina Page 60

 Coffee shop management system
 Direct

 When a new system is implemented without any phased or pilot implementation, it is said
to be direct.

 The old system is retried and new system goes live.

 If the system is not critical, this can be good method for implementation.

 For example, new system will be directly implementation. There is no existing system.

Prepared By: Juli & Herina Page 61

 Coffee shop management system

Chapter:-5

CONCLUSION

5.1 Limitation of system

5.2 Future scope of system
5.3 Bibliography

Prepared By: Juli & Herina Page 62

 Coffee shop management system

 Conclusion

 In our project entitled “COFFEE SHOP MANAGEMENT SYSTEM” we have tried our best
to fulfill all the requirements of coffee shop.

 The project being simple and flexible is running successfully. The main advantage of our
project is that its simplicity attracts a lot of user.

 It can easily run by a novice user. Our software can be used in any kind of shop (Bar,
Restaurant, Pizzeria and more).

 The coffee shop management helps the café manager to manage the coffee shop more
effectively and efficiently by computerizing item ordering, and billing control.

 The system processes transaction and stores the resulting data. Reports will be generated
from these data which help the manager to make appropriate business decision for the
coffee shop.

 Therefore, our software will definitely prove to be a successful stepping stone in replacing
the outdated manual method of maintaining secure records.

 The work plan also includes detailed features of the technology used in the project defining
the front end and back end. The objectives and scope of the project in future have been
elaborated.

Prepared By: Juli & Herina Page 63

 Coffee shop management system

5.1 LIMITATION OF SYSTEM

 The limitation of the project is that it runs on a single server within the education institute
or corporate world not over internet. An internet application can provide much better
security.

 Only registered user can use this website.

 Users can not use the other information.

 This system will not be able to send some notification about my report or any delivery
system to owner or customer.

 We cannot send any types of email to the system user.

5.2 FETURE SCOPES OF THE SYSTEM

 Customize orders: allow customers to customize item order.

 Payment options: add different payment options such as a pay pal, Gifts cards, etc. allows
to save payment details for future use.

 Also return order functionality.

 The GUI of the website will be modified to improve its performance on a slow connection
terminal also.

 The capability of server will be increased.

Prepared By: Juli & Herina Page 64

 Coffee shop management system

5.3 WIBLIOGRAPHY

 Hariti study hub-Easy learn–YouTube

 www.youtube.com

 www.google.com

 www.onlineproject.com

 WWW.freeprojectz.com

5.4 BIBLIOGRAPHY

 SQL notes

 Software testing techniques book-Boris Beizer

Prepared By: Juli & Herina Page 65