Title of the Project

“Online Bakery Shop System”

1
 TABLE OF CONTENTS

1 Introduction 3

2 Objective 4

3 Project category 4

4 Existing System 5

5 Proposed system 5

6 Module description 6

7 Data flow diagram(DFD) 8

8 Use Case Diagram 11

9 Data tables 12

9 System testing 14

10 Hardware and software requirements 17

11 Scope 18

12 Conclusion 19

2
 INTRODUCTION

The main aim of this Online Bakery Shop project is to establish online system for bakery

where people can buy various bakery products online.

Bakery products are very much essential for our daily usage. Though people likes are

different, food habits are different, life styles are different still everybody likes bakery

products. Online bakery system, where people can stay indoors and order the items they

need is a very convenient and friendly process which can be fitted around busy lines. In

this fast lifestyle this project aims to make life style of people more convenient. People

can pamper state buds by ordering the items they required in few minutes of time. They

can also send sweets (gift) to relatives and friends on occasion without leaving the

comfort of their sofa.

This Online Bakery Shop project has mainly two types of users, customer and admin.

The admin is responsible to add all bakery items to the portal and user can check and

order various bakery products available online. This delightful, cost effective, time-

saving project is developed using PHP and MySQL.

3
 OBJECTIVE

The main objective of the project on Online Bakery Shop System is to manage the

bakery details, ordering and maintaining the bakery items.

 This will minimize the number of employees at the back of the counter.

 The system will help to reduce the cost of labor

 The system will be less probable to make mistake, since it’s a machine

 This will avoid long queues at the counter due to the speed of execution and

number of optimum screens to accommodate the maximum throughput

 It saves their time and efforts.

 Helps Bakery shops to automate bakery selling online.

PROJECT CATEGORY

This is an RDBMS web based project which is currently using MYSQL for all the

transaction statements and PHP as the front end. This project also uses Javascript and

CSS for the user friendly view.

MYSQL is an open source RDBMS system. PHP (recursive acronym for PHP:

Hypertext Preprocessor) is a widely-used open source general-purpose scripting

4
language that is especially suited for web development and can be embedded into

HTML.

EXISTING SYSTEM

In this busy schedule the existing Online Bakery Shop system is very inconvenient. It is

very difficult to go to the bakery shop and face the hassle of packing and the crowd

formed in front of the items displayed and the long queue at the billing counter.

PROPOSED SYSTEM

The proposed Online Bakery Shop system is more convenient and time saving. Admin

adds list of various bakery products of different categories in to the web site. The

customer can visit the web site and check the products. If the customer likes a product he

may place the order online by paying the amount through cards or net banking, even

COD facility is available. The system should cover the following functions in order to

support the bakery business process for achieving the objectives:

 To provide interface that allows promotion and menu

 To prevent interface that shows customers’ orders detail to front-end

 A tool that allows the management to modify the bakery information such as

price, add a new bakery items and many others as well as tools for managing user,

system menu and promotion records.

5
 MODULE DESCRIPTION

For the optimum use of practical time it is necessary that every session is planned.

Planning of this project will include the following things:

 Topic Understanding.

 Modular Break – Up of the System.

 Process Logic for Each Module.

 Database Requirements.

The project is modularized on the basis of users who use this portal.

1. Administrator
2. Customer

 Process Logic for Each Module:

1. Administrator

Admin can add list of items to the portal based on the categories. Also he can

view list of orders placed by the customers. The functionalities of admin are;

 Change password

 Add, edit and delete the bakery items

 List the order details

 Approve or disapprove the status of order

6
  Logout

2. Customer

New user has to register first. After registration he can log in to the system and

view all the available bakery products. Customer can search the product based on

different categories and price range. He can select and add list of products to his

shopping cart. Once shopping is completed he can make the payment online and

wait for the items to be delivered to his address. The functionalities of customer

are;

 Change password

 View the bakery items

 Add it to cart

 Order the menu

 Logout

7
 DATA FLOW DIAGRAM (DFD)

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an

information system, modeling its process aspects. A DFD is often used as a preliminary

step to create an overview of the system without going into great detail, which can later

be elaborated. DFDs can also be used for the visualization of data processing (structured

design).

Symbol meaning

An entity. A source of data or destination

for data

A process or task that is performed by the

system

A database store, a place where data is

held between processes

A data flow

8
 Level0: Data Flow Diagram

Level1 Data Flow Diagram : Admin

9
Level 1 Data Flow Diagram: Customer

10
USE CASE DIAGRAM

11
 DATA TABLES

1. UserDetails
Field Type Constraint
UserId INTEGER Primary Key
EmailId VARCHAR(50) NOT NULL
Password VARCHAR(50) NOT NULL
UserName VARCHAR(50) NOT NULL

2. AdminDetails
Field Type Constraint
Id INTEGER Primary Key
UserName VARCHAR(50) NOT NULL
Password VARCHAR(50) NOT NULL
UpdationDate TIMESTAMP

3. BakeryDetails
Field Type Constraint
BakeryId INTEGER Primary Key
BakeryName VARCHAR(50) NOT NULL
BakeryDescription VARCHAR(100) NOT NULL
BakeryPrice INTEGER NOT NULL
BakeryPhoto VARCHAR(50) NOT NULL
BakeryCategoryId INTEGER NOT NULL

12
4. CategoryDetails
Field Type Constraint
Id INTEGER Primary Key
CategoryName VARCHAR(50) NOT NULL

5. CartDetails
Field Type Constraint
Id INTEGER Primary Key
UserId INTEGER NOT NULL
BakeryId INTEGER NOT NULL
QuantityId INTEGER NOT NULL
Total INTEGER NOT NULL
Status INTEGER NOT NULL

6. OrderDetails
Field Type Constraint
Id INTEGER Primary Key
UserId INTEGER NOT NULL
CartId INTEGER NOT NULL
Status INTEGER NOT NULL

13
 SYSTEM TESTING

Testing is a set activity that can be planned and conducted systematically. Testing begins

at the module level and work towards the integration of entire computers based system.

Nothing is complete without testing, as it is vital success of the system.

There are several rules that can serve as testing objectives, they are

1. Testing is a process of executing a program with the intent of finding an error

2. A good test case is one that has high probability of finding an undiscovered error.

3. A successful test is one that uncovers an undiscovered error.

If testing is conducted successfully according to the objectives as stated above, it would

uncover errors in the software. Also testing demonstrates that software functions appear

to the working according to the specification, that performance requirements appear to

have been met. There are three ways to test a program

1. For Correctness

2. For Implementation efficiency

3. For Computational Complexity

Tests for correctness are supposed to verify that a program does exactly what it was

designed to do. This is much more difficult than it may at first appear, especially for

large programs. Tests for implementation efficiency, attempt to find ways to make a

14
correct program faster or use less storage. It is a code-refining process, which

reexamines the implementation phase of algorithm development.

Tests for computational complexity amount to an experimental analysis of the

complexity of an algorithm or an experimental comparison of two or more algorithms,

which solve the same problem.

The following ideas should be a part of any testing plan:

1. Preventive Measures

2. Spot checks

3. Testing all parts of the program

4. Test Data

5. Looking for trouble

6. Time for testing

7. Re Testing

The data is entered in all forms separately and whenever an error occurred, it is corrected

immediately. A quality team deputed by the management verified all the necessary

documents and tested the Software while entering the data at all levels. The entire testing

process can be divided into 3 phases.

1. Unit Testing

2. Integrated Testing

15
 3. Final/ System testing

Unit testing

As this system was partially GUI based WINDOWS application, the following were

tested in this phase

1. Tab Order

2. Reverse Tab Order

3. Field length

4. Front end validations

In our system, Unit testing has been successfully handled. The test data was given to

each and every module in all respects and got the desired output. Each module has been

tested found working properly.

Integration testing

Test data should be prepared carefully since the data only determines the efficiency and

accuracy of the system. Artificial data are prepared solely for testing. Every program

validates the input data.

Validation testing

In this, all the Code Modules were tested individually one after the other. The following

were tested in all the modules

1. Loop testing

2. Boundary Value analysis

16
 3. Equivalence Partitioning Testing

In our case all the modules were combined and given the test data. The combined

module works successfully without any side effect on other programs. Everything was

found fine working.

Output testing

This is the final step in testing. In this the entire system was tested as a whole with all

forms, code, modules and class modules. This form of testing is popularly known as

Black Box testing or system tests.

Black Box testing methods focus on the functional requirement of the software. That is,

Black Box testing enables the software engineer to derive sets of input conditions that

will fully exercise all functional requirements for a program. Black Box testing attempts

to find errors in the following categories; incorrect or missing functions, interface errors,

errors in data structures or external database access, performance errors and initialization

errors and termination errors.

HARDWARE AND SOFTWARE REQUIREMENTS

PROCESSOR : INTEL CORE 2 DUO

SYSTEM TYPE : 32 BIT

RAM : 2GB DDR2

OPERATING SYSTEM : MICROSOFT WINDOWS 7

17
 FRONT END : PHP

BACKEND : MY SQL

SCOPE

This application can be easily implemented under various situations. We can add new

features as and when we require. Reusability is possible as and when require in this

application. There is flexibility in all the modules.

Extensibility: This software is extendable in ways that its original developers may not

expect. The following principles enhance extensibility like hide data structure, avoid

traversing multiple links or methods, avoid case statements on object type and

distinguish public and private operations.

Reusability: Reusability is possible as and when require in this application. We can

update it next version. Reusable software reduces design, coding and testing cost by

amortizing effort over several designs. Reducing the amount of code also simplifies

understanding, which increases the likelihood that the code is correct. We follow up both

types of reusability: Sharing of newly written code within a project and reuse of

previously written code on new projects.

18
Understandability: A method is understandable if someone other than the creator of the

method can understand the code (as well as the creator after a time lapse). We use the

method, which small and coherent helps to accomplish this.

Cost-effectiveness: Its cost is under the budget and make within given time period. It is

desirable to aim for a system with a minimum cost subject to the condition that it must

satisfy the entire requirement.

Scope of this document is to put down the requirements, clearly identifying the

information needed by the user, the source of the information and outputs expected from

the system.

CONCLUSION

The project Online Bakery Shop System provides user with many facilities. It

provides an elegant management of bakery items ordering online. The system can

also be used as software to promote various bakeries. The system limits human

interaction. In future linking and integration of Payment Gateway and SMS and

Email notification for booking can be implemented. It will be hosted on the internet

server which will be accessed by all people in the world and can view the site.

19