ABSTRACT

The bakery shop management system is being developed for shop owners so
that they can manage their shop easily form any part of world .This application
takes information form admin through filling their stock details.

A admin being login on the website has facility to billing , stock update , sales
report managed. The proposed system is completely integrated online systems.

It automates manual procedure in an effective and efficient way. This

automated system facilitates admin & cashier to fill up.

The details according to their requirements. It includes type of bakery products.

The main purpose of this system is to develop a web site for the owner/admin of
the respective bakery shop.

The objective and essence of any Records Management system is the right
information in the right place in the right order, at the right time for the right
person at the lowest cost.”Bakery Management System is a computerized
system designed and programmed to deal with daily operations taking place in
the bakery. It is only built to facilitate and makes every things in the record. The
program can manage products, employees, suppliers, customers and orders. It
also keeps check on Bakery items life by storing its manufacturing and expiry
information.

The purpose of the project is to computerize the management of Bakery to

develop software which is user friendly, simple, fast, and cost–effective. It deals
with the collection of products information, Quantity details, etc. Traditionally,
it was done manually.

The project outlines all the process followed to come up with the software that
is from analysis to testing the system.

Table of Contents
CHAPTER I:
INTRODUCTION……………………………………………………….….……. 9

1.1 BACKGROUND………………………...………………………..…….…… 9

1.2 OBJECTIVES………………………………………….…………………..…10

Page 1
1.3 PURPOSE, SCOPE ……………………………………………....……. …...11

1.3.1 Purpose
1.3.2 Scope
1.4 APPLICABILITY…………………………………………….………….….11

1.5 ACHIEVEMENTS. …………………………………………………..……12

1.6 ORGANIZATION OF REPORT…………………………………………. 12

CHAPTER 2: SURVEY OF TECHNOLOGIES……………………..…….…...13

CHAPTER 3: REQUIREMENTS AND ANALYSIS………………………..... 15

3.1 PROBLEM DEFINITION …………………………………...…………… 15

3.2 REQUIREMENTS SPECIFICATION…………………………………….. 15

3.2.1 NON FUNCTIONAL REQUIREMENTS
3.2.2 FUNCTIONAL REQUIREMENTS

3.3 SOFTWARE AND HARDWARE REQUIREMENTS. ………….…... 15-16

3.3.1 SOFTWARE REQUIREMENTS
3.3.2 HARDWARE REQUIREMENTS

3.4 CONCEPTUAL MODELS………………………………………………… 16

3.4.1 CLASS DIAGRAM
3.4.2 USE CASE DIAGRAM

CHAPTER 4: SYSTEM DESIGN. ……………………………………………..19

4.1 Basic Modules…………………………….…………………………………19

4.2 Algorithm Design .…………………………………………………………..20

4.3 User Interface Design………………………………………………………..22

Chapter 5: Implementation and Testing ……………………..……………..…...23

5.1 Implementation Approaches………………………………………………....25

5.2 Testing……………………………………………………….…………. ….25

Page 2
5.2.1 Unit Testing…………………………………………………………....25-26

5.2.2 Integration Testing…………………………………………...……………26

Chapter 6: Result And Discussion ……………………………………...……... 27

Chapter 7: Conclusion And Future Scope ….…………………………………. 31

7.1 Conclusion .……………………..………………………………………….31

7.2 Limitations of the system………………..…………………………………. 31

7.3 Future Scope……………………………..…………………………………. 32

REFERENCE

Chapter 1
Introduction
In this project, the topic and implementation is about creating a bakery shop
website. In this project we will studying that how the given website actually
works in frontend and backend and database server and what output it will
generate to the user respectively. This project will gave you the breif description
of how the website is created and how its interface is reliable, easy and simple
for the users.

1.1 Background
1.Now a days everybody have a very busy schedule, they don’t know what they
are eating, the Bakery Products they are eating It is healthy or not, how much
calorie the Bakery produces have ,the fat which is present in bakery Products.

2.So I plan on building a Bakery shop websites that will contain many bakery
products and cakes so it is very easy to purchase bakery products from the
websites. From the website User will see many different type of bakery products
are there to purchase.

3.It will also help to eat healthy bakery Products and also time saving it will
also help to choose different variety of products in our daily life.

4.Ordering cakes online is in trend now a days as there are many benefits in
ordering online. So, people prefer to get the online delivery at their all special
moments.

Page 3
5.More Variety At the online portals user can get various varieties to choose
Products. customer can get the cakes according to your choice in different sizes,
designs and flavours.

6. Online delivery also offers their customers to get their cake customized
according to their choices. For eg customer want any designs on the cake so
user can get customized.

7. Affordable Prices customer can get their favorite cake at the very affordable
price that every user can Shop the Product. Customer have to pay more at the
normal bakery store as compared to the online stores.

8. Costomer can get discounts also at many festival or first birthday.

9. Home Delivery Order the favourite cake of your friend and family and it will
be delivered to your friend at his doorstep. This home delivery helps you to
save your time and energy by which you can enjoy more at the party. And the
best thing is that you can also get all the cakes for home delivery also like
chocolate cake, pineapple cake, black forest cake, fruit cake or any cake.

1.2 Objectives:
1. It will help to purchase bakery products easily and also healthy for people

2. It will help to save customer time because they don’t need to Visit shop for
purchase bakery shop.

3. The user will know what exactly they have to eat on next meal because the
user will already have planned so the user will also not get confused what he
or she have to eat next.

4. It will also customer time because there is no need to go on shop for

Purchasing.

5. The user will also get decoration products like candles balloons etc.

Object
Modules:-

User Registration: User can register on the system and get his online account
on site.

User Login: User can login to system and check various bakery items.

Page 4
 Product Categories: The bakery products are arranged and can be viewed in
categories.

Add to cart: Users can add new items to cart.

1.3 Purpose and scope:

1.3.1 Purpose:-
1. The purpose of the given project is to create a user friendly website. The
website saves the time and effort of the customer.

2. The purpose of creating website is also to save the time because when we
go to bakery shop for shopping it take more time to purchase bakery products.

3. when we order products online through website it save lot of time of user
and from that time user can do some important work for eg. office works
college work etc.

1.3.2 Scope:
The main issue of today generation is they want everything online

1. Payment Method: In the payment method the user can pay cash on delivery
method at their doorstep.

2. User Login: user can login to system and check various bakery item.

3. Home page: Include various new varieties etc.

4. Bakery Items: Include various types of items.

5. Biscuit: Include various types of biscuit.

6.Snacks: Include various snacks.

1.4 Applicability:-
1. The website will be available on any web browser such as google chrome , mozilla
firefox , Microsoft edge, Opera etc.
2. As well as website will be responsive in any devices such as Pc’s, Tablets, laptop,
Mobile Etc.
3. The user can be available to use this website at any location and would be very easy
for every user.

Page 5
4. These were the applications of the project.

1.5 Achievements:
1. We have gained a some knowledge about how the website is created , and how it
works upon servers.
2. Such as frontend, backend and database server.
3. We have get some knowledge on how the projects are done on the industrial level.
4. From Creating this website we Got some improvisation in communication skill.

1.6 Organization of report:

In the following report we have studied and researched about four chapters such as
Introduction, survey of technologies, requirements and analysis and system design. So
in the first chapter there is a brief and theoretical description of the introduction. In the
introduction there is background of bakery shop website project as well as the
purpose, scope and applications of the project. Then in the second chapter there is
information or survey of technologies through which we are going to implement the
project. There is information about languages, software, frontend, backend and
database servers. Coming to the third chapter the project gives us information about
the requirements of hardware as well as software and gives the graphical
representation of how the project was scheduled with the help of Gantt chart. Also
there are some conceptual models. In chapter 4 there is brief idea about modules and
the system design. These 4 chapters cover the study and research of the project report.

Chapter 2: Survey of Technologies

The following technologies will be used in creating the website.

Front End: HTML, CSS, Bootstrap.

Backend: PHP, MySQL.

Page 6
The programming/scripting languages used in the project are HTML, CSS, and
Bootstrap for the frontend. For the backend purpose we will be using Bootstrap v5
framework. The last is for database we will be implementing xampp server. xampp
required to Run the Server and Execute the Program.
HTML: Hypertext Markup Language (HTML) is the standard markup language for
documents designed to be displayed in a web browser. It can be assisted by
technologies such as Cascading Style Sheets (CSS) and scripting languages such as
JavaScript.
Web browsers receive HTML documents from a web server or from local storage and
render the documents into multimedia web pages. HTML describes the structure of a
web page semantically and originally included cues for the appearance of the
document. HTML elements are the building blocks of HTML pages. With HTML
constructs, images and other objects such as interactive forms may be embedded into
the rendered page. HTML provides a means to create structured documents by
denoting structural semantics for text such as headings, paragraphs, lists, links, quotes
and other items. HTML elements are delineated by tags, written using angle brackets.
HTML can embed programs written in a scripting language such as JavaScript, which
affects the behavior and content of web pages. Inclusion of CSS defines the look and
layout of content.
CSS: Cascading Style Sheets (CSS) is a style sheet language used for describing the
presentation of a document written in a markup language such as HTML CSS is a
cornerstone technology of the World Wide Web, alongside HTML and JavaScript.
JavaScript: JavaScript often abbreviated as JS, is a programming language that
conforms to the ECMAScript specification. JavaScript is high-level, often just-intime
compiled, and multi-paradigm. It has curly-bracket syntax, dynamic typing,
prototypebased object-orientation, and firstclass functions.
MySQL: XAMPP is a free and open-source cross-platform web server solution stack
package developed by Apache Friends, consisting mainly of the Apache HTTP
Server, MySQLDB database, and interpreters for scripts written in the PHP
programming languages. Since most actual web server deployments use the same
components as XAMPP, it makes transitioning from a local test server to a live server
possible. XAMPP's ease of deployment means a WAMP stack can be installed
quickly and simply on an operating system by a developer, with the advantage that
common add-in applications such as WordPress can also be installed with similar ease
using Bitnami.
MySQL Server: MySQL is an open-source relational database management system
(RDBMS). Its name is a combination of "My", the name of co-founder Michael
Widenius's daughter and "SQL", the abbreviation for Structured Query Language. A
relational database organizes data into one or more data tables in which data types

Page 7
may be related to each other; these relations help structure the data. SQL is a language
programmers use to create, modify and extract data from the relational database, as
well as control user access to the database. In addition to relational databases and
SQL, an RDBMS like MySQL works with an operating system to implement a
relational database in a computer's storage system, manages users, allows for network
access and facilitates testing database integrity and creation of backups. MySQL is
free and open-source software under the terms of the GNU General Public License,
and is also available under a variety of proprietary licenses. MySQL was owned and
sponsored by the Swedish company MySQL AB, which was bought by Sun
Microsystems (now Oracle Corporation). In 2010, when Oracle acquired Sun,
Widenius forked the open-source MySQL project to create MySQLDB. MySQL has
stand-alone clients that allow users to interact directly with a MySQL database using
SQL, but more often MySQL is used with other programs to implement applications
that need relational database capability. MySQL is a component of the LAMP web
application software stack (and others), which is an acronym for Linux, Apache,
MySQL, Perl/PHP/Python. MySQL is also used by many popular websites, including
Facebook, Flickr, MediaWiki, Twitter, and YouTube.

Chapter 3: Requirements and Analysis

3.1 Problem defination: The problem we have seen and studied in this project is to
expand the Bakery Products services door to door in less than one hour. Also many of
the people are unaware of the cashless transaction so there will Epayment in this
website. Precise the website will be responsive and user friendly for the users. These
were the problem defination of the project. 3.2 Requirement Specification
3.2.1 Non functional requirements: A non-functional requirement (NFR) is a
requirement that specifies criteria that can be used to judge the operation of a system,
rather than specific behaviors. They are contrasted with functional requirements that
define specific behavior or functions. The plan for implementing functional
requirements is detailed in the system design. The plan for implementing
nonfunctional requirements is detailed in the system architecture, because they are
usually architecturally significant requirements. In our project we are mainly focusing
on the feedback section such that the user will not be able to face glitches or bugs, late
delivery, transaction failure in our project respectively.

Page 8
3.2.2 Functional Requirements: Functional requirements may involve calculations,
technical details, data manipulation and processing, and other specific functionality
that define what a system is supposed to accomplish. Behavioral requirements
describe all the cases where the system uses the functional requirements, these are
captured in use cases. Functional requirements are supported by non-functional
requirements (also known as "quality requirements"), which impose constraints on the
design or implementation (such as performance requirements, security, or reliability).
Here in this case we will mainly focus on the customers basic Bakery Products
requirements that is they can choose any type of Bakery item available in the website.
After purchasing the Bakery Products, the customer will be able to see their order on
cart So that they would be sure and hence it makes the website more reliable.

3.3.1 Software Requirements:

1. PHP2.11.4
2.MYSQL 5.0.45
3.Apache 2.0.55
4.Visual studio code 2013
5.XAMPP 8.1.6
3.3.2 Hardware requirements:

1. Processor: Intel(R) Core(TM) i5-3360M

2.Physical memory 4100Mb
3. Expandable Memory: 8GB
4. Display Size: 14.0-inch LED HD (1366 x 768) anti-glare

5. Storage: 1TB

3.5 Conceptual Models:

3.5.1 Class Diagram: The class diagram is the main building block of
objectoriented 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. The classes in a class diagram represent both the main
elements, interactions in the application, and the classes to be
programmed.

Page 9
 3.5.2 Activity Diagram

For User

Page 10
 3.5.3 Use Case Diagram:

A use case diagram at its simplest is a representation of a user's interaction with the
system that shows the relationship between the user and the different use cases in
which the user is involved. A use case diagram can identify the different types of
users of a system and the different use cases and will often be accompanied by other
types of diagrams as well. The use cases are represented by either circles or ellipses.

Page 11
 Chapter 4: System Design

4.1 Basic Modules

There are several modules are studied and created in this project such as:
1. Login module
2. Home module
3. Point of Sale
4. Generate Printable Receipt
5. Manage User List
6. Manage Account Credentials

1. Login Module: It is the first module of the project. In this module we are
distinguished it into two parts such as SignUp and SignIn. In SignUp if the user

Page 12
 is using the website for the first time then he/she will have to fill the form
containing username, emailid, password, address. In SignIn the user can
directly access the page simply giving the emailid and password.

2. Home Module: It is the main page of the website. In this page the user will
be able to buy the latest Bskery items or can get the new offers in the page.

3. Point of sale: In this module the customer which selects the Bakery item can
purchase it. We have made form where customer have to give his personal
details such as name, contact number, address, city name etc. After that there is
option for a Cash On Delivery (COD) option.

4. Manage User List: User management describes the ability for administrators
to manage devices, systems, applications, storage systems, networks, and user
access to other various resources.
5. Manage Account Credentials: Account Credentials means the login and
password of the Client, which are required so as to have access on and use the
Platform(s).

4.2 Algorithm Design

Admin-Side
▪ Login Page
▪ Home Page
▪ Summary
▪ Inventory/Available Stocks List
▪ Restock Products
▪ Maintenance
▪ Add New Category
▪ List All Categories
▪ View Category Details
▪ Update Category Details
▪ Update Category Status
▪ Delete Category
▪ Manage Product
▪ Add New Product
▪ List All Products
▪ View Product Details
▪ Update Product Details
▪ Delete Product

Page 13
 ▪ Manage Stocks
▪ Add New Stock
▪ List All Stocks
▪ View Stock Details
▪ Update Stock Details
▪ Delete Stock
▪ Point of Sale
▪ Generate Printable Receipt
▪ Generate Printable Date-wise Sales Report
▪ Manage User List (CRUD)
▪ Manage Account Credentials

4.3Test Case Design

Admin:

Sr. No Test Cases Description Result

1 Admin enters Display

wrong username incorrec
t username
2 Admin enters Display
wrong password incorrec
t password
3 Admin leaves any field blank Error message displayed
at required field

User :
For Login
Sr no Test Cases Description Result

Page 14
 1 Username or password Display incorrect
entered incorrectly username or password

2 Username or password Display error message at

field left blank required field

4.4 User Interface Design

Login Page:

Home Page:

Page 15
 Chapter 5: Implementation and Testing
5.1 Implementation Approaches
Implementation refers to the second last phase of the Software Development
Lifecycle. There are many different approaches which can be used for development of
software such as waterfall model, spiral model, big bang approach etc. Each of these
approaches have their own advantages and disadvantages.
For developing this project we have used the waterfall model approach. We
started with requirement gathering and analysis in which we analyzed the type of the
project and decided on the requirements such as hardware requirements, software
requirements, programming languages to be used etc. Then we moved on to design
phase in which we designed the basic structure of the website such as user interface,
different modules involved etc. After designing the basic skeleton of the project, we
moved on to coding in which individual module were coded and implemented using
the programming languages decided. After implementing all the modules, we tested
the modules individually through unit testing and then tested the whole project
through integration and system testing. Finally, the project was implemented and any
errors solved through maintenance.

Coding:

Page 16
Page 17
 5.2 Testing Approach
5.2.1 Unit testing:
Unit tests are typically automated tests written and run by software developers to
ensure that a section of an application (known as the "unit") meets its design and
behaves as intended. In procedural programming, a unit could be an entire module,
but it is more commonly an individual function or procedure. In object-oriented
programming, a unit is often an entire interface, such as a class, but could be an
individual method. By writing tests first for the smallest testable units, then the
compound behaviors between those, one can build up comprehensive tests for
complex applications.
To isolate issues that may arise, each test case should be tested independently.
Substitutes such as method stubs, mock objects, fakes, and test harnesses can be used
to assist testing a module in isolation. During development, a software developer may
code criteria, or results that are known to be good, into the test to verify the unit's
correctness.
During test case execution, frameworks log tests that fail any criterion and report them
in a summary. For this, the most commonly used approach is test - function - expected
value.
Writing and maintaining unit tests can be made faster by using parameterized tests.
These allow the execution of one test multiple times with different input sets, thus

Page 18
reducing test code duplication. Unlike traditional unit tests, which are usually closed
methods and test invariant conditions, parameterized tests take any set of parameters.
Parameterized tests are supported by TestNG, JUnit and its .Net counterpart, XUnit.
Suitable parameters for the unit tests may be supplied manually or in some cases are
automatically generated by the test framework. In recent years support was added for
writing more powerful (unit) tests, leveraging the concept of theories, test cases that
execute the same steps, but using test data generated at runtime, unlike regular
parameterized tests that use the same execution steps with input sets that are pre-
defined.

5.2.2 Integration Testing:

Integration testing (sometimes called integration and testing, abbreviated I&T) is the
phase in software testing in which individual software modules are combined and
tested as a group. Integration testing is conducted to evaluate the compliance of a
system or component with specified functional requirements.It occurs after unit
testing and before validation testing. Integration testing takes as its input modules that
have been unit tested, groups them in larger aggregates, applies tests defined in an
integration test plan to those aggregates, and delivers as its output the integrated
system ready for system testing.
Some different types of integration testing are big-bang, mixed (sandwich), risky-
hardest, top-down, and bottom-up. Other Integration Patterns are: collaboration
integration, backbone integration, layer integration, client-server integration,
distributed services integration and high-frequency integration.

In the big-bang approach, most of the developed modules are coupled together to form
a complete software system or major part of the system and then used for integration
testing. This method is very effective for saving time in the integration testing process.
However, if the test cases and their results are not recorded properly, the entire
integration process will be more complicated and may prevent the testing team from
achieving the goal of integration testing.
Bottom-up testing is an approach to integrated testing where the lowest level
components are tested first, then used to facilitate the testing of higher level
components. The process is repeated until the component at the top of the hierarchy is
tested. All the bottom or lowlevel modules, procedures or functions are integrated and
then tested. After the integration testing of lower level integrated modules, the next
level of modules will be formed and can be used for integration testing. This approach
is helpful only when all or most of the modules of the same development level are
ready. This method also helps to determine the levels of software developed and
makes it easier to report testing progress in the form of a percentage.

Page 19
Top-down testing is an approach to integrated testing where the top integrated
modules are tested and the branch of the module is tested step by step until the end of
the related module.
Sandwich testing is an approach to combine top down testing with bottom up testing.
One limitation to this sort of testing is that any conditions not stated in specified
integration tests, outside of the confirmation of the execution of design items, will
generally not be tested.

Chapter 6: Results and Discussion

Page 20
Page 21
Page 22
Page 23
 Chapter 7: Conclusions

7.1 Conclusion
Website for Bakery Corner shopping is a user-friendly website which allows users to
buy Cake from the comfort of their home. The system was tested and was found to
function properly. But it can still be improved for higher use.

The website for grocery shopping is developed using HTML and CSS. MySQL server
was used as the database and hosting the website locally.
The following final conclusions were derived from the project:
• It allows users to order groceries remotely.
• User interface is minimalistic and user friendly.
• Appropriate messages displayed for easy understanding of user.
• Navigation through the application is easy through navigation bar.
• Appropriate access given to users depending on permissions such as user and
admin.
• Application can be modified and improved for further use.

7.2 Limitations of the system

• User verification is not done using email or OTP.

Page 24
• Payment gateway is not implemented.
• Limited number of products.
• There is no discount on any products.

7.3Future scope of project

Greater number of products can be added to the site. Additional features such as
search option can be implemented. Discount and gift voucher schemes can be used.
Chatbot can be used for automated handling of customer’s queries. Wishlist can also
be implemented so customer can simply catalog the products.

REFERENCES
Made by Amey Pravin Bhobaskar.
Reference Website:

1. https://www.google.co.in/

2. https://www.youtube.com/

Page 25