Project Report

On
Online cake Shop Management Shop (Floweraura)
By
Deepak Pawar
MCA 2nd Year Sem IV

Under the guidance of

Prof. Ashok Deokar Sir

SAVITRIBAI PHULE PUNE UNIVERSITY

MASTER OF COMPUTER APPLICATION

Dr. D.Y. Patil School of MCA

Charholi (BK), PUNE-412105
Academic Year 2021-2022
 CERTIFICATE

This is to certify that Mr. Deepak Balasaheb Pawar has successfully/partially completed his
Project work entitled Online Cake Shop Management System (Floweraura) from “Dr. D Y
nd
Patil School of MCA” in partial fulfilment of MCA-2 Year SEM-IV Mini Project for the

year 2021-2022. He has worked under our guidance and direction.

Prof. Ashok Deokar Prof. Ashok Deokar Dr. E. B. Khedkar

Project Guide, DYPSOMCA HOD, DYPSOMCA Director, DYPSOMCA

Examiner 1 Examiner 2

Date:

Place: Pune
 INDEX

Sr No. Title

1. College Certificate and Company Certificate

2. Acknowledgement
3. Problem Definition
4. Existing System and Need for The New System
5. Scope of The Work
6. Limitation of Existing System
7. Feasibility Study
• Technical Feasibility
• Economical Feasibility
• Operational Feasibility
8. Requirement Analysis
9. System Requirement
• Hardware
• Software
10. Analysis and Design
• DFD
• ER Diagram
11. UML Diagrams
• Use-Case Diagram
• Activity Diagram
• Collaboration Diagram
• Class Diagram
• Object Diagram
• Component Diagram
• Deployment Diagram
12. Data Dictionary
13. Screen Design
14. Testing Method Used
15. Future Enhancement
16. Conclusion
17. Bibliography
 Project Progress Report

Roll NO & Name of the student Deepak Balasaeb Pawar

Title of the Project GTL Software PVT LTD

Project Guidance Name Prof Ashok Devkar Sir

Head
Dept. of Computer Science
 Acknowledgment
Any attempt at any level cannot be satisfactorily completed without the
proper support and guidance of learned people who share their knowledge
and experience in order to improve our work. In completing this project, I
was fortunate to get help, support and an encouragement from many
people. I would like to acknowledge them for their cooperation.
I would like to appreciate all teachers for their guidance to work on
project in accomplishing the project.
I am pleasured to thank Prof Ashok Deokar Sir, head of the
department of computer science, for his valuable help and support.
We also thank all the staff members of our college for their help in
making this project a successful one.

Thanking you all,

 Problem Definition
1. This project aims to develop an online shopping system for customers
with the goal so that it is very easy to shop your loved things from an
extensive number of online shopping sites available on the web.
2. With the help of this you can carry out an online shopping from your
home.
3. Here is no compelling reason to go to the crowed stores or shopping
centres during festival seasons.
4. You simply require a PC or a laptop and one important payment
sending option to shop online.
5. Online Shopping System is also designed for to overcome those
problems using manual system such as the possibility the paper order is
high.
6. Many shops use conventional system, which is on paper-based, for
purchasing product.
7. Customer can login to the system to maintain his account information,
such as changing phone number, address, and check the status of his
orders.
8. Therefore, Online Shopping developed to enhance the efficiency and
accuracy of taking order. Besides that, conventional system cannot see
the sales history therefore Online Shopping designed to view the sales
history.
9. Online Shop System Problem Statement Customer can browse through
the product catalogue and add the items to shopping cart.
10. Hence, an efficient system is required to eliminate such problems
after a structural analysis of the existing system.
 Existing System
1. The present scenario for shopping is to visit the shops and market
manually and then from the available product list one needs to choose
the item he or she wants and then pay for the same item mainly in cash
mode is done, as not every society is well educated and aware to use net
banking or card modes or wallets etc.

2. This system is not much user-friendly as one needs to go to the market

physically and then select items only from the available list. So mostly
it is difficult to get the product as per our desire. Description About the
products is less available and are mostly verbal only. For gifts, this type
of shopping, one needs to have an ample amount of free time.

3. Also, not really good markets exist everywhere, so many times good
markets become out of reach for certain people. In the proposed system
customers need not go to the shops for purchasing the products. He/she
can order the product he/she wishes to buy through the use of this
system. The shop owner can be the admin of the system.

4. The shop owner can appoint officials particularly to handle this, who
will help the owner in managing the customers and product orders. The
system also endorses a home delivery system for delivering the
purchased products.

5. In existing system for giving any orders, users should visit product shop
to know about product, give them order, and pay advance.
6. In this method, time and manual work is required.
7. Maintaining critical information in the files and manuals is full of risk
and a tedious process.
8. The existing system serves a major drawback to the realization of
efficiency and customer satisfaction.
9. The experience of ordering in most shop is not pleasant for the
customers.
 Need for the New System
1. There is always a need of a system that will perform to ordering of
flowers, cakes, personalized gift products online
2. This system will reduce the manual operation required to maintain all
the records.
3. This online shopping application enables the end users to register
online, select the product from the Catalog, and view the product or
search.
4. The product and order product online by just selecting product which
user wants.
5. By using this application, Easy to solve customer query, any record is
easy to store and manage, Easy to purchase product, Give the Discount
Offer for Customer, and provide shipping method
 Scope of the Work
1. The main purpose to develop this project Online Shopping System is to
sell the flower, cake, and flower pot, gift of birthday, anniversary etc.
items online. This project is basically developed for India for focus on
locally.
2. Purchasing and selling products and services over the internet without
the need of going physically to the market is what online shopping all
about. Online shopping stores offer product description, pictures,
comparisons, price and much more.
3. Few examples of these are Amazon.com, ebay.com and the benefits of
online shopping is that by having direct access to customer, the online
stores can offer special products to the customer, cookies can used for
tracking the customer selection over the internet or what is of their
interest when they visit the site again.
4. Online shopping makes use of digital technology for managing the flow
of information, products, and payment between customer, site owners
and suppliers.
5. shopping cart is one of the important facilities provided in online
shopping, this lets customer to browse different types of product and
services and once they select an item to purchase, they can place the
item in shopping cart, and continue browsing till the final selection.
6. Customers can even remove the items from shopping cart that selected
earlier before they place the final order.
Module Specifications:
Admin:
• Admin can manage user and customer account.
• Admin can manage product.
• Manage product category.
• Admin can manage the orders of customers.
• Generate bill.
• View the feedback.

Customer:

• Customer Registration.
• Update the details.
• Search the products as per there requirements.
• Customer can view the product.
• Customer can buy the products or give the order.
• Pay the bill cash on delivery.
• Give Feedback.

Employee/Delivery boy:

• View order details.

• Deliver order.
• Give bill & Receive payment

Login Module:
• User name.
• Password.
Feedback:
• Customer Give feedback.
• Admin View Feedback.
• Delivery boy feedback

Inventory
• List Item
• List of Supplier
• Payment
Online Shopping System Modules: -

1. Login Module:
In this module, the DBA or the customer will have to
authorize his access to the modules of the online software system.

2. Customer Module:
In this module, there is two types of users one is registered and
second is unregister user. Registered user create account and buy the
product. This module helps the customer to edit his/her profile
details, view the orders.

3. Admin Module:
In this module, the work of admin can be proceeded with i.e.
maintenance of the website, review customer’s feedback and
queries, bill maintenance.

4. Product:
In this module, we can add, edit and delete the products.

5. Search Module:
In this module, product search using high-performance search
system with an option to search by selected attributes.

6. Feedback:
In this module, the customer can give some valuable feedback
or ask a query pertaining to a product.
 Limitations of Existing System
Due to manual system has following limitations:
• In the existing system all transactions of product, purchasing product
which is done manually which is time consuming.

• There is no computer system for handling payments. All calculations

performed manually, which may not be accurate always maintaining
the record is really a tedious task.

• To buy product user has to collect information about it either by

visiting the shop or by asking people, which is the better one.
 Feasibility Study
Feasibility study carried out whether there is complex problem. A
feasibility study is undertaken to determine the possibility or probability of
either improving the existing system or developing completely new
system. Feasibility study evaluates the cost and benefits of the proposed
system.
There are three aspects of feasibility study, which should be check.
Following are the types of Feasibility Study:
1. Technical Feasibility
2. Economic Feasibility
3. Operational Feasibility

➢ Technical Feasibility:
Definition: “Technical feasibility is carried out to determine
whether the company has the capability, in terms of software,
hardware, personnel and expertise, to handle the completion of the
project.”
Technical feasibility determines whether it is possible to develop
the project with available equipment, available software technology and
the workers. If there is any kind of need in order to develop software in
this case the cost of hardware, software and technical equipment are
considered.
Our system used hardware, software which are we used the
Windows 10 operating system, processor Intel® Core™ i3 CPU, RAM
4 GB, Hard Disk 500 GB, Front end and back end are PHP and MySQL
respectively. Therefore, we do not require costly hardware.
There is lot of security, accuracy and reliability in system by
considering the above reason the system is technically feasible.
➢ Economic Feasibility:
Definition: “Economic analysis is the most frequently used method
for evaluating the effectiveness of a new system. Most commonly
called as cost or benefit analysis, the procedure is to determine the
benefits and saving that are expected from a candidate system and
compare them with costs.”
It is the study of economic benefits of this software. More
commonly known as cost/benefit analysis, the procedure is to determine
the benefits and savings that are expected from a candidate system and
compare them with costs. If benefits outweigh costs, then the decision
is made to design and implement the system. An entrepreneur must
accurately weigh the cost versus benefits before taking an action. These
websites save our money and time.

➢ Operational Feasibility:
Definition: “Operational feasibility in a measure of how well a
proposed system solves the problem and takes advantages of the
opportunities identified during scope definition and how it satisfies
the requirements identified in the requirements analysis phase of
system development.”
Operational feasibility is a measure of how well a proposed
system solves the problems, and takes advantage of the opportunities
identified during scope definition and how it satisfies the requirements
identified in the requirements analysis phase of system development .
After implementing the system, the system-training program are
arranged for the users. The people who are familiar with information
system as well as the techniques carry this out. They are experienced
persons like system analyst or managers. The cost of the training
program as well as space requirement for implementation of the system
and the other assets are considered. Therefore, our system is
operationally feasible.
1. It is user-friendly system.
2. Does not require special training.
3. Provide better security.
4. Any user having technical knowledge or not can operate system.
 Requirement Analysis
The requirements can be defined as "A complete understanding of the
software development effort. No matter how well designed or well coded,
a poorly analysed and specified program will disappoint the user and bring
grief to the developer."
❖ Requirements may be either:
✓ Functional, describing the facilities of the system.
✓ Non-functional, describing constraints which may impact later
development phases.

➢ Functional Requirements:
After careful analysis the system has been identified to have the
following functional modules:
1. Registration -
If customer wants to order flower, cake, and flower pot, gift of birthday,
anniversary etc. items then he/she must be register. Unregister customer
cannot buy the product.

2. Login -
Customer logins to the system by entering valid user id and password
for order the products online.

3. Changes to Cart -
Changes to cart means the customer after login or registration can make
order or cancel order of the item from the cart.

5. Logout -
After the payment or searching, the product the customer will logged out.
6. Report Generation -
After all transaction, the system can generate the portable document file
(.pdf) and then sent one copy to the system database to calculate the
monthly transaction.

➢ Non-Functional Requirements:
1. Security -
The system uses SSL (secured socket layer) in all transactions that
include any confidential customer information. The system
must automatically log out all customers after a period of inactivity.
The system should not leave any cookies on the customer’s
computer containing the user’s password. The system’s back-end servers
shall only be accessible to authenticated administrators.
Sensitive data will be encrypted before sent over insecure
connections like the internet.

2. Reliability -
The system provides storage of all databases on redundant
computers with automatic switch over. The reliability of the overall
program depends on the reliability of the separate components.
The system has a backup of the database, which is continuously
maintained and updated to reflect the most recent changes.
Thus, the overall stability of the system depends on the stability of
container and its underlying operating system.

3. Availability -
 The system should be available at all times, meaning the user can
access it using a web browser, only restricted by the down time of the
server on which the system runs. In case of a hardware failure or database
corruption, a replacement page will show. Also, in case of a hardware
failure or database corruption, backups of the database should be retrieved
from the server and saved by the administrator. Then the service will be
restarted. It means 24 X 7 availability.

4. Maintainability -
A commercial database used for maintaining the database and the
application server takes care of the site. In case of a failure, a re-
initialization of the program will be done. In addition, the software design
done with modularity in mind so that maintainability done efficiently.

5. Portability -
The application is HTML and scripting language based. Therefore,
the end-user part is fully portable and any system using any web browser
should be able to use the features of the system, including any hardware
platform that is available or will be available in the future.
An end-user is using this system on any OS; it is either Windows or
Linux. The system shall run on PC, Laptops, and PDA etc.
 System Requirements
➢ Hardware Requirements:
System should have the internet connection.
Processor Pentium 4 Intel core i3 and 1GHz Minimum
RAM Minimum of 512 MB. The recommended amount can
vary depending on the number of users connected and
other factors.
Hard Disk 3 GB of available hard-disk space for installation,
additional free space is required during installation.

➢ Software Requirements:
Operating System Windows 10
Browser Chrome, Internet Explorer or any compatible
web browser
Database MySQL
Web Server Apache
Language/Technology PHP, HTML5, CSS3, jQuery, Bootstrap,
JavaScript.
 Analysis and Design

➢ Data Flow Diagram (DFD):

➢ Entity Relationship Diagram (ERD):
 UML (Unified Modeling Language) Diagrams:

➢ Use Case Diagram for Admin:

➢ Use Case Diagram for Customer:
➢ Activity Diagram for Customer:
➢ Activity Diagram for Admin:
➢ Sequence Diagram:
➢ Class Diagram:
➢ Object Diagram:
➢ Component Diagram:

ProductDeliver.exe
DBProduct.mdb Order.mdb

Delivery.dll floweraura.com.ppt Help.pdf

➢ Deployment Diagram:
 Data Dictionary

Table Name: Customer

Description: Information of Customer
Sr. Field Name Field Size Constrain Description
No Type t
1. CustId Int 10 Primary Customer ID
Key
2. FirstName Varchar 50 Not Null Customer
First Name
3. LastName Varchar 50 Not Null Customer
Last Name
4. Email varchar 50 Not Null Mail Id
5. Password varchar 30 Not Null Password

6. MobileNumbe Int 20 Not Null Mobile Number

r
7. Gender Varchar 10 Not Null Customer Gender
8. DateOfBirth Varchar 30 Not Null Date of Birth

9. Address Varchar 50 Not Null Customer Address

10. Country Varchar 20 Not Null Customer Country

11. State Varchar 20 Not Null Customer State

12. City Varchar 20 Not Null Customer City

13 ZipCode Varchar 10 Not Null Customer Zip

code
Table Name: Staff
Description: Information of Admin
Sr. Field Name Field Size Constraint Description
No Type
1. sid Int 10 Primary Admin ID
Key
2. SName Varchar 50 Not Null Admin Name

3. SAddress Varchar 50 Not Null Admin Address

4. SEmailId Varchar 50 Not Null Admin Email ID

5 Password Varchar 30 Not Null Admin Password

6. Sphno Int 20 Not Null Phone number

Table Name: Product

Description: Information of Product
Sr. No Field Name Field Size Constraint Description
Type
1. PId Int 10 Primary Product ID
Key
2. CaId Int 10 Foreign Product Category
Key ID
3. PName Varchar 50 Not Null Product Name
4. Price Int 20 Not Null Price of Product
5 Product Desc. Varchar 50 Not Null Product
Description
6 Unit Int 30 Not Null Product Size
7 Gst Int 20 Not Null Gst

8 SPid Int 10 Fk Supplier id

Table Name: Order

Description: Information of Order
Sr. No Field Name Field Size Constraint Description
Type
1. Order_Id Int 10 Primary Order ID
Key
2. PId Int 10 Foreign Product ID
Key
3. CustId Int 10 Foreign Customer ID
Key
3. Quantity Int 20 Not Null Product Quantity

5. Total Int 30 Not Null Product Amount

Amount
6. Order_Date Varchar 30 Not Null Date of order

Table Name: Product Category

Description: Information of Product Category
Sr. No Field Name Field Size Constraint Description
Type
1. CaId Int 10 Primary Category ID
Key.
2. CaName Varchar 20 Not Null Category Name

Table Name: Delivery

Description: Information of Delivery Boy
Sr. No Field Name Field Size Constraint Description
Type
1. Did Int 10 Primary Delivery Boy ID
Key
2 CustId Int 10 Foreign Customer Id
Key
3. DName Varchar 20 Not Null Delivery Boy
Name
4. DAddress Varchar 40 Not Null Address
5. DEmailId Varchar 50 Not Null Email ID

6. Dphno Int 13 Not Null Phone number

7 Order_id Int 10 Foreign Order Id
Key

Table Name: Feedback

Description: Information of Feedback
Sr. Field Name Field Size Constrain Description
No Type t
1. Fid Int 10 Primary Feedback ID
Key
4 CId Int 10 Foreign Customer
key
5 Feedback varchar 50 Not Null Feedback/comme
nt

Table Name: order_status

Description: Information of Order Status
Sr. Field Name Field Size Constrain Description
No Type t
1. Id Int 10 Primary Order Status ID
Key
 2 Email-id varchar 10 Not Null Customer Email

3 Cid date Foreign Expected

key departure of order
4 Order_date date Not Null Date of Order

Table Name: Payment:

Supplier Table
Sr.no Field Name Field Type Size Constraint

1 Spid Int 10

2 Sname Varchar 50 Not null

3 Spno Int 10 Not null

 Screen Design

➢ Home Page:
➢ Product Category:

➢ Product(Gift) Category:
➢ Product List:

➢ Product Detail Page:

➢ Delivery City:

➢ Customer Login:
➢ Customer Registration:

➢ Customer Registration:
➢ My Account:
➢ Customer Update Profile:
➢ Cart:

➢ Checkout Page:
➢ Payment Page:

➢ Gift Finder:
➢ Track your order:

➢ Admin Login:
➢ Admin Dashboard:

➢ Add Products:
➢ Category:
 Testing Method Used

1. Unit Testing

Unit testing concentrates verification on the smallest element of the

program – the module. Using the detailed design description important
control paths are tested establish errors within the bounds of the module.In
the system each sub module is tested individually as per the unit testing
such as campaign, lead, contact etc. are tested individually. Their input
field validations are tested

2. Integration testing

Once all the individual units have been tested there is a need to test how
they were put together to ensure no data is lost across interface, one
module does not have an adverse impact on another and a function is not
performed correctly. After unit, testing each sub module is tested with
integrating each other.

System testing for the current system:

In this level of testing, we are testing the system as a whole after

integrating all the main modules of the project. We are testing whether
system is giving correct output or not. All the modules were integrated
and the flow of information among different modules was checked. It
was also checked that whether the flow of data is as per the requirements
or not. It was also checked that whether any particular module is non-
 functioning or not i.e., once the integration is over each and every
module is functioning in its entirety or not.

In this level of testing, we tested the following: -

• Whether all the forms are properly working or not.

• Whether all the forms are properly linked or not.
• Whether all the images are properly displayed or not.
• Whether data retrieval is proper or not

Specific knowledge of the application's code/internal structure and

programming knowledge in general is not required. The tester is aware of
what the software is supposed to do but is not aware of how it does it. For
instance, the tester is aware that a particular input returns a certain,
invariable output but is not aware of how the software produces the output
in the first place.

Test Cases

Test cases are built around specifications and requirements, i.e., what the
application is supposed to do. Test cases are generally derived from
external descriptions of the software, including specifications,
requirements and design parameters. Although the tests used are primarily
functional in nature, non-functional tests may also be used. The test
designer selects both valid and invalid inputs and determines the correct
output without any knowledge of the test object's internal structure.

Test Design Techniques

Typical black-box test design techniques include:

• Decision table testing

• All-pairs testing
• State transition Analysis
• Equivalence partitioning
• Boundary value analysis
• Cause–effect graph
• Error guessing

Advantages

• Efficient when used on large systems.

• Since the tester and developer are independent of each other, testing
is balanced and unprejudiced.
• Tester can be non-technical.
• There is no need for the tester to have detailed functional knowledge
of system.
• Tests will be done from an end user's point of view, because the end
user should accept the system. (This testing technique is sometimes
also called Acceptance testing.)
• Testing helps to identify vagueness and contradictions in functional
specifications.
• Test cases can be designed as soon as the functional specifications
are complete.

Disadvantages
 • Test cases are challenging to design without having clear functional
specifications.
• It is difficult to identify tricky inputs if the test cases are not
developed based on specifications.
• It is difficult to identify all possible inputs in limited testing time. As
a result, writing test cases may be slow and difficult.
• There are chances of having unidentified paths during the testing
process.
• There is a high probability of repeating tests already performed by
the programmer.

1] Test case For Admin Login Page:

Project Name: floweraura.com (online Shopping)

Prepared Date: - 24-04-2022 Prepared By: - Mr. Polkar
Akash
Module Name: Login. Reviewed Date: - 24-04-
2022
Project Code: OJS

Total no of test Cases: -04

Total no of test Cases Passed: -04
Total no of test Cases failed: -00
Total no of test Cases executed: -04
Total no of test Cases pending: -00
Test Test Case Input Expected Actual Test
Case ID Procedure Data Output Output Status
OJS- Checking the 1.Enter valid Admin Admin Pass
LG-01 functionality Usernames in Panel Panel
of Admin textbox should be should be
LOGIN 2. Enter valid displayed displayed
Button Password in
textbox
3. Click on
Admin
LOGIN
Button
OJS - Checking the 1.Enter Admin Admin Pass
LG-02 functionality invalid User Panel Panel
of Admin Name in text should not should not
LOGIN box be be
Button 2. Enter valid displayed displayed
Password in
password
textbox
3. Click on
Admin
LOGIN
Button

2] Test case for customer Login Page:

Project Name: floweraura.com (online Shopping)
 Prepared Date: - 24-04-2022 Prepared By: - Mr.
Polkar Akash
Module Name: customer login. Reviewed Date: - 24-04-
2022
Project Code: OJS

Test Test Case Input Expected Actual Test

Case ID Procedure Data Output Output Status
OJS- Checking Enter The email The email pass
CL-01 the invalid address that address that
functionality email and you entered you entered
of customer any phone doesn’t match doesn’t match
login Button number any account any account
and hit sing up for an sing up for an
login account account
button
OJS- Checking Enter The phone The phone pass
CL-02 the valid number that number that
functionality email and you’ve entered you’ve entered
of customer incorrect is incorrect is incorrect
login Button phone
number
password
OJS- Checking Enter Successful sucessfull pass
CL-03 the valid
functionality email and
of customer phone
login Button number
3] Test case For add cart Login Page:

Test Test Case Input Expected Actual Test

Case Procedure Data Output Output Status
ID
OJS- Checking the Click on Product is Product is pass
AC-01 functionality product added to the added to the
of add cart and cart cart
Button product
is added
OJS- Checking the Keep the Message will Message did pass
AC-02 functionality cart display not displayed
of add cart empty Nothing in cart
Button
 Future Enhancement
There are many places where we can improve. The following are the
features that we are about to implement in near future.
1. In future, we provide search facilities like category wise searching or
price wise searching.
1. Provide notifications to user about offers and discounts.
2. We can develop mobile application for most of the users who uses smart
phones rather than browsers.
3. In the future, I want to Enhanced my project with thee admin part of
online flowers, cakes etc shopping.
4. Add more product types in web site.
 Conclusion
In the fast-moving life where people do not have time to shop
manually, online shopping has emerged as a time saving and convenient
way of shopping. The increase trend of online shopping will only grow
and expand in the future. It concludes that people have substituted their
needs to shop at local stores by shopping online. Customer is the king for
every business and nobody wants to lose the profitable customers. The
online shopping system provides various features to your customers to
keep in the list of your 'regular customers’. Customers can enjoy the
convenience of ordering Product online while sitting at their
homes/offices.
The Online shopping System upload their product online so that they
can be easily managed or changed and customers can order online.
Customer can add products to shopping cart or order the product online.
Discount can be given to product in online system and we can purchase the
new fashion of the product.
 Bibliography
1. www.scribd.com
2.www.w3school.com
3. www.htmltutorial.com
4.www.csstutorial.com
5.www.caratlane.com
6. www.stackoverflow.com