VEER NARMAD SOUTH GUJARAT UNIVERSITY, SURAT

VIMAL TORMAL PODDAR BCA COLLEGE

PROJECT REPORT

ON

FLOWER SHOP
AS A PARTIAL REQUIREMENT FOR THE DEGREE OF

BACHELOR OF COMPUTER APPLICATION (B.C.A.)

2024-2025

GUIDED BY: SUBMITTED BY:

KATVE AMAN.
SHRIMALI FALGUNI.
TIWARI SANTOSH.

1|Page
 ACKNOWLEDGEMENT

When we reach on completion of the project, giving credit

becomes a must, without the support of so many people’s help
and guidance this project couldn’t be completed successfully.

First, we would like to thank our parents with their great

support we can reach at the stage. Then our humble thanks to all
professors and all staff members of our college “Vimal Tormal
Poddar BCA College”, For the Co-operation & interest extended
by them, throughout our degree course. It is a base that they have
built, which sustains such good jobs.

We would like to thank Dr. Chetan Rathod I/C Principal of

Vimal Tormal Poddar BCA College for granting us an opportunity
to work on this project. We would also like to thank to our guide
for their valued guidance and encouragement towards the
completion of our project.

2|Page
 INDEX
Sr. No Description Page No.
1 Introduction 04
1.1 Project description 05
1.2 Project Profile 06
2 Environment Description 08
2.1 Hardware and Software Requirements 09
2.2 Technologies Used 10
3 System Analysis and Planning 13
3.1 Existing System and its Drawbacks 14
3.2 Feasibility Study 15
3.3 Requirement Gathering and Analysis 18
4 Proposed System 19
4.1 Scope 20
4.2 Project modules & functionalities Constraints 20
5 Detail Planning 22
5.1 Data Flow Diagram / UML 23
5.2 Process Specification / Activity Flow Diagram 38
5.3 Data Dictionary 39
5.4 Entity-Relationship Diagram / Class Diagram 43
6 System Design 44
6.1 Database Design 45
6.2 Directory Structure 50
6.3 Input Design 51
6.4 Output Design 51
7 Software Testing 73
7.1 Unit Testing 74
7.2 Integration Testing 76
7.3 System Testing 78
8 Limitations and Future Scope of Enhancements 80
9 Bibliography & Reference 84

3|Page
 FLOWER SHOP

INTRODUCTION

4|Page
 FLOWER SHOP

INTRODUCTION :

1.1 Project description :

 The Flower Shop Management System is a comprehensive software solution

designed to streamline the operations of a flower shop, catering to both
administrative and user functionalities.

 This system aims to provide a user-friendly interface for both administrators and
customers, facilitating efficient management of inventory, orders, and customer
interactions.

 Administrators can perform various tasks such as adding, updating, or deleting

products, managing product categories, and handling user orders.

 They have the capability to view and manage customer messages, ratings, and
reviews, enabling them to respond promptly to customer inquiries and feedback.

 Additionally, administrators can generate reports to analyze sales performance,

popular products, and other key metrics to make informed business decisions.

 The User Interface provides a seamless shopping experience for customers

visiting the flower shop's website.

 Users can browse through the catalog of flowers and floral arrangements, search
for specific products, and add them to their cart or wishlist.

 The checkout process is simplified, allowing users to proceed with payments

securely and track the status of their orders.

 Users can also provide feedback by rating products and leaving reviews,
enhancing transparency and trust in the flower shop's offerings.

5|Page
 FLOWER SHOP

PROJECT PROFILE

6|Page
 FLOWER SHOP

1.2 Project Profile :

Fields Descriptions

Project Title FLOWER SHOP MANAGEMENT SYSTEM

The Flower Shop Management System is a

comprehensive software solution designed to streamline
Definition the operations of a flower shop, catering to both
administrative and user functionalities.

Developed For SDJ INTERNATIONAL COLLEGE,VESU

Project Guide PROF, ANKITA SORATHIA

Front End HTML,CSS, JAVASCRIPT , BOOTSTRAP

Back End PHP

Programming PHP
Language

Microsoft Windows 11
Operating System

Submitted By 1. PATEL NIYATI KETANKUMAR

2. PATEL ISHA DIVYESHBHAI
3. PARMAR VIPUL RAJUBHAI
4. PATEL NACHIKET ANANDBHAI

7|Page
 FLOWER SHOP

ENVIRONMENT
DISCRIPTION

8|Page
 FLOWER SHOP

2. Environment Description

2.1 Hardware and Software Requirements:

 Hardware Requirement:

 Intel® Core™ i5-12400F CPU @ 2.70GHz

 Minimum 8.0 GB DDR3 RAM
 64-bit Operating System
 128 GB Hard Disk Drive

 Software Requirement:

 Development Environment: Anaconda

 Code Editor: Jupyter Notebook
 Database: SQLite Database
 Web Server: Localhost server (XAMPP)
 Machine Learning Libraries: Python libraries such as
Scikit-learn, TensorFlow
 Web Development Tools :HTML, CSS, JavaScript
 Working Internet Connection

9|Page
 FLOWER SHOP

2.2 Technologies Used

Front End: PHP

PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-

used open source general-purpose scripting
language that is especially suited for web
development and can be embedded into HTML.
What distinguishes PHP from something like
client-side JavaScript is that the code is
executed on the server, generating HTML
which is then sent to the
client. The client would receive the results of running that script, but would not
know what the underlying code was. You can even configure your web server
to process all your
HTML files with PHP, and then there's really no way that users can tell what
you have up your sleeve. The best things in using PHP are that it is
extremely simple for a newcomer, but offers many advanced features for a
professional programmer.

Back End: MySQL

MySQL runs on virtually all platforms, including Linux,

UNIX, and Windows. Although it can be used in a
wide range of applications, MySQL is most often
associated with web-based applications and online
publishing and is an important component of an open
source enterprise stack called LAMP. LAMP is a Web
development platform that uses Linux as the
operating system, Apache as the Web server,
MySQL as the relational database management
system and PHP as the object oriented scripting language. MySQL
is an essential part of almost every open source PHP application.
Good example for PHP/MySQL-based script are PHPBB.

10 | P a g e
 FLOWER SHOP

XAMPP:

XAMPP stands for Cross-Platform (X), Apache (A), MySQL (M), PHP(P)
and Perl (P). It is a simple, lightweight Apache distribution that
makes it extremely easy for developers to create a local web
server for testing purposes. Everything you need to set up a web
server - server application (Apache), database (MySQL), and
scripting language (PHP) - is included in a simple extractable
file. XAMPP is also cross-platform, which means it works equally
well on Linux, Mac and Windows. Since most actual web server
deployments use same components as
XAMPP, it makes transitioning from a local test server to a live server is
extremely easy as well. XAMPP has four primary components:
PHP: PHP stands for Hypertext Preprocessor. It is a server-side scripting
language that powers some of the most popular websites in the world,
including WordPress and Facebook. It is open source, relatively easy to
learn, and works perfectly with MySQL, making it a popular choice for web
developers.

Bootstrap:

Bootstrap is a free and open-source front-end web

framework for designing websites and web
applications. It contains HTML- and CSS-based
design templates for typography, forms, buttons,
navigation and other interface components, as well as
optional JavaScript extensions. It aims to ease the development of dynamic
website and web application.
Bootstrap is a front end web framework, that is, an interface for the user,
unlike the server side code which resides on the "back end" or server.
Bootstrap provides a set of stylesheets that provide basic style definitions for
all key HTML components. These provide a uniform, modern appearance for
formatting text, tables and form elements.

Ajax:
Ajax is a client-side script that communicates to and from a server/database
without the need for a post back or a complete page refresh. (The method of
exchanging data with a server, and updating parts of a web page - without
reloading the entire page).

11 | P a g e
 FLOWER SHOP

• CSS:
Cascading Style Sheets (CSS) is a style sheet language used for describing
the presentation of a document written in a markup
language. Although most often used to set the visual style
of web pages and user interfaces written in HTML and
XHTML, the language can be applied to any XML
document, including plain XML, SVG and XUL, and is
applicable to rendering in speech, or on other media. Along
with HTML and JavaScript, CSS is a cornerstone
technology used by most websites to create visually
engaging webpages, user interfaces for web applications,
and user interfaces for many mobile applications. Before
CSS, nearly all presentational attributes of HTML documents were contained
within the HTML markup. All font colors, background styles, element
alignments, borders and sizes had to be explicitly described, often
repeatedly, within the HTML. CSS lets authors move much of that information
to another file, the style sheet, resulting in considerably simpler HTML.

JavaScript:
JavaScript is a high-level, dynamic, untyped, and interpreted programming
language. It has been standardized in the ECMAScript
language specification. Alongside HTML and CSS,
JavaScript is one of the three core technologies of World
Wide Web content production; the majority of websites
employ it, and all modern Web browsers support it
without the need for plug-ins. JavaScript is prototype-
based with first-class functions, making it a
multiparadigm language, supporting objectoriented,
imperative, and functional programming styles. It has an
API for working with text, arrays, dates and regular expressions, but does not
include any I/0, such as networking, storage, or graphics facilities, relying for
these upon the host environment in which it is embedded.

MySQL: Every web application, howsoever simple or complicated, requires a

database for storing collected data. MySQL, which is open source, is the
world's most popular database management system. It powers everything
from hobbyist websites to professional platforms like WordPress. You can
learn how to master PHP with this free MySQL database for beginner's
course.

12 | P a g e
 FLOWER SHOP

SYSTEM ANALYSIS
AND PLANNING

13 | P a g e
 FLOWER SHOP

3.System Analysis and Planning

3.1 Existing System and its Drawbacks

The existing system is that the shop must fill up the data manually and must
submit it to the system. It may take a lot of time to process it and to order
place. Therefore, there is wastage of time. Since the data is entered
manually, the probability of error or mistakes is high.

 Cannot Upload and Download the latest updates.

 No use of Web Services and Remoting
 Risk of mismanagement and of data when the project is under
development.
 Less Security.
 Its difficult to update, delete, or view the data due its manual nature.
 The existing system consumes a lot of time causing inconveniencing
to customers and the staff.
 No proper coordination between different Applications and Users.
 Increasing number of passengers leads to difficulty in maintaining and
retrieving detail.
 Fewer Users - Friendly

14 | P a g e
 FLOWER SHOP

3.2 Feasibility Study

1. Technical Feasibility:

Technical feasibility determines whether the work for the project can be
done with the existing equipment, software technology, and available
personnel. Technical feasibility is concerned with specifying equipment
and software that will stratify the user requirement. This project is
feasible on technical remarks also, as the proposed application is more
beneficiary in terms of having a soundproof application with new
technical components installed on the application.
The proposed application can run on any machine supporting Browser
and Internet services and works on the best software and hardware that
had been used while designing the application. So, it would be feasible
in all technical in terms of feasibility.

2. Economic Feasibility:

Economic feasibility determines whether there are sufficient benefits in

creating to make the cost acceptable, or if the cost of the application is
too high, as this signifies costbenefits analysis and savings.
On the behalf of the cost-benefit analysis, the proposed application is
feasible and economical regarding its pre-assumed cost for making an
application.
Economic feasibility has great importance as it can outweigh other
feasibilities because costs affect an organization's decisions.
The concept of Economic Feasibility deals with the fact that an
application that can be developed and will be used on the installation
must be profitable for Organization.
The cost to conduct a full application investigation the cost of hardware
and software, and the benefits in the form of reduced expenditure are
all discussed during the economic feasibility.

15 | P a g e
 FLOWER SHOP

During the economic feasibility test, I maintained the balance between

the Operational and Economical feasibilities, as the two were
conflicting.
For example, the solution that produces the best operational impact for
the end-uses may also be the most expensive and therefore the least
economically feasible.
I classified the costs of the Family Expanse Manager Application
according to the phase in which they occur.
As I know that the application development costs are usually one-time
costs that will not occur after the project has been completed. For
calculating the Development costs, I evaluated certain costs categories-
wise.
• Personnel Costs
• Computer Usage
• Training
• Supply and equipment costs
• Cost of any new computer equipment and software

3. Operation Feasibility:

Operation feasibility is a measure of how people feel about the

application. Operational
Feasibility criteria measure the urgency of the problem or the
acceptability of the solution.
Operational Feasibility is dependent upon determining human
resources for the project.
It refers to projecting whether the application will operate and be used
once it is installed. If the ultimate users are comfortable with the
present application and they see no problem with its Continuance, then
resistance to its operation will be Zero.
Behavioral also the proposed application is feasible.
A particular application may be technical and but may fail to produce
the forecasted benefits because the company is not able to get it to
work.
For the application, it is not necessary that the user must be a computer
expert but any computer operator given a little bit of knowledge and
training can easily operate.

16 | P a g e
 FLOWER SHOP

4. Management Feasibility:

Management feasibility does not come in basic feasibility of the

application, but it arises in the aspect of management views.
Here all levels of management revise all related basic feasibility and
know the requirements of the all after that all manager give their
decision for all those feasibilities to be used or not.

5. Time Feasibility:

Time feasibility describes the time cost for converting the present
application to a new application.
As an aspect of time feasibility, my application took three months to
complete. This application is Developed in the time period of 80 to 90
Days so I can say that this application is time Feasible.

6. Legal Feasibility:

Investigates if the proposed system conflicts with legal requirements

like data protection acts or social media laws.
As such, in our project, we do not collect user confidential information
for any purpose. But we store user’s financial detail as a user data
which is end to end encrypted so it is safe. this data created and stored
by user.
We providing user privacy and our System does not conflict with any
legal requirements of cyber laws.

17 | P a g e
 FLOWER SHOP

3.3 Requirement Gathering and Analysis

The Software Requirements Specification is produced at the culmination of

the analysis task. The function and performance allocated to software as part
of system engineering are refined by establishing a complete information
description, a detailed functional and behavioral description, an indication of
performance requirements and design constraints. appropriate validation
criteria, and other data pertinent to requirements.

Hardware Requirements –

For the hardware requirements like memory restrictions, cache size, the
processor, RAM size etc... those are required for the software to run.

MINIMUM Hardware Requirements

Processor Pentium IV Hard Drive 100 GBRAM 1 Gb

PREFERED HARDWARE REQUIREMENTS

Processor Core i3Hard Disk Drive 500 GB RAM 4 GB

Software Requirements –

Any window based operating system with DOS support are primary
requirements for software development. Windows 7 and up are required. The
system must be connected vie LAN and connection to internet is mandatory.
Performance requirements:

• User Satisfaction: The system is such that it stands up to the user

expectations.
• Response Time: The response of all operations is good.
• Error Handling: Response to user errors and undesired situation has
been taken care of to ensure that the system operates without halting.
• Safety and Robustness: The system is able to avoid or tackle
disastrous action. In other words it should be foul proof.
• Portable: The software should not be architecture specific. It should
be easily transferable to other platforms if needed.
• User Friendliness: The system is easy to learn and understand. A
native user can also use the system effectively, without any difficulties

18 | P a g e
 FLOWER SHOP

PROCESSED SYSTEM

19 | P a g e
 FLOWER SHOP

4.Processed System

4.1 Scope

The flower store website is an application stored in the user server.

The purpose of the website is to resolve the client to allow website users to
perform tasks related to flower shopping.

 The system enables to perform the following functions:

 Flower shopping
 confirmation order
 Cancellation
 Improved and optimized service

4.2 Project modules & functionalities Constraints

• Flower Management Module: Used for managing the Flower details.

• Payment Module: Used for managing the details of Payment
• Feedback Module : Used for managing the details of Feedbacks.
• Booking Module: Used for managing the Booking details.
• Login Module: Used for managing the login details.
• Users Module: Used for managing the users of the system.

20 | P a g e
 FLOWER SHOP

There are a number of factors in the client’s environment that may restrict
the choices of a designer. Such factors include standards that must be
followed, resource limits, operating environment, reliability and security
requirements and policies that may have an impact on the design of the
system.

Standard Compliances:
This specifies the requirement for standards the system must follow. The
standards may include the report format and accounting properties

Hardware Limitations:
Hardware limitations can include the types of machine to be used, operating
system available on the system, languages support and limits on primary
and secondary storage.

Reliability and Fault Tolerance:

Fault tolerance requirement can be place a constraint on how the system is
to be designed. Recovery requirements are often on integral part here,
detailing what the system should do if some failure occurs to ensure certain
properties. Reliability requirements are very important for critical application.

Security:
Security requirements are particularly significant in defense system and
database system. They place restrictions on the use of certain commands,
control access to data, provide different kinds of access requirements for
different people, require the use of passwords and cryptography techniques
and maintain a log of activities in the system.

21 | P a g e
 FLOWER SHOP

DETAIL
PLANNING

22 | P a g e
 FLOWER SHOP

5 .Detail Planning

5.1 Data Flow Diagram / UML

Context-level:

23 | P a g e
 FLOWER SHOP

0 LEVEL DFD FOR TIME ZONE :

24 | P a g e
 FLOWER SHOP

1 LEVEL DFD FOR REGISTRATION :

25 | P a g e
 FLOWER SHOP

1 LEVEL DFD FOR LOGIN :

26 | P a g e
 FLOWER SHOP

1 LEVEL DFD FOR CLIENT :

27 | P a g e
 FLOWER SHOP

1 LEVEL DFD FOR ORDER :

28 | P a g e
 FLOWER SHOP

1 LEVEL DFD FOR PRODUCT :

29 | P a g e
 FLOWER SHOP

1 LEVEL DFD FOR RATING :

30 | P a g e
 FLOWER SHOP

2 LEVEL DFD FOR CLIENT :

31 | P a g e
 FLOWER SHOP

2 LEVEL DFD FOR PRODUCT :

32 | P a g e
 FLOWER SHOP

2 LEVEL DFD FOR ORDER :

33 | P a g e
 FLOWER SHOP

2 LEVEL DFD FOR RATING :

34 | P a g e
 FLOWER SHOP

USE CASE DIAGRAM

USE CASE DIAGRAM OF ADMIN :

35 | P a g e
 FLOWER SHOP

USE CASE DIAGRAM OF CLIENT :

36 | P a g e
 FLOWER SHOP

UML DIAGRAM :

37 | P a g e
 FLOWER SHOP

5.2 Process Specification / Activity Flow Diagram :

38 | P a g e
 FLOWER SHOP

5.3 Data Dictionary :

ADMIN

NAME Admin

ALIAS NAME Admin

SOURCE Web user / Admin

DESTINATION Admin

DESCRIPTION Admin page

USER

NAME User

ALIAS NAME User

SOURCE Web user / User

DESTINATION User

DESCRIPTION User page

CART

NAME Cart

ALIAS NAME Cart

SOURCE Web user / user / car

DESTINATION User

DESCRIPTION User page

39 | P a g e
 FLOWER SHOP

PRODUCT

NAME Product

ALIAS NAME Product

SOURCE Web user / Admin/Product

DESTINATION Product

DESCRIPTION Product page

CATEGORY

NAME Category

ALIAS NAME Category

SOURCE Web user / Admin/Category

DESTINATION Category

DESCRIPTION Category page

ORDER

NAME Order

ALIAS NAME Order

SOURCE Web user / User/Order

DESTINATION Order

DESCRIPTION Order page

40 | P a g e
 FLOWER SHOP

WISHLIST

NAME Wishlist

ALIAS NAME Wishlist

SOURCE Web user / User/Wishlist

DESTINATION Wishlist

DESCRIPTION Wishlist page

RATE

NAME Rate

ALIAS NAME Rate

SOURCE Web user / User/rate

DESTINATION Rate

DESCRIPTION rate page

REVIEW

NAME Review

ALIAS NAME Review

SOURCE Web user / User/Review

DESTINATION Review

DESCRIPTION Review page

41 | P a g e
 FLOWER SHOP

MESSAGE

NAME Message

ALIAS NAME Message

SOURCE Web user / User/Message

DESTINATION Message

DESCRIPTION Contact page

42 | P a g e
 FLOWER SHOP

5.4 Entity-Relationship Diagram / Class Diagram :

43 | P a g e
 FLOWER SHOP

SYSTEM
DESIGN

44 | P a g e
 FLOWER SHOP

6 . SYSTEM DESIGN

6.1 Database Design :

TABLE NAME : ADMIN

FIELD NAME DATA TYPE KEY DESCRIPTION

ADMIN ID INT AUTO ADMIN ID KEY

INCREMENT COLUM
EMAIL VARCHAR NULL ADMIN MAIL

PASSWORD VARCHAR NULL ADMIN

PASSWORD

TABLE NAME : PRODUCTS

FIELD NAME DATA TYPE KEY DESCRIPTION

ID INT AUTO PRODUCT ID KEY

INCREMENT COLUM
CID INT AUTO PRODUCT ID KEY
INCREMENT COLUM
NAME VARCHAR NULL PRODUCT NAME

DETAILS VARCHAR NULL PRODUCT DETAILS

PRICE VARCHAR NULL PRODUCT PRICE

IMAGE VARCHAR NULL PRODUCT IMAGE

45 | P a g e
 FLOWER SHOP

TABLE NAME : CATEGORY

FIELD NAME DATA TYPE KEY DESCRIPTION

CATEGORY_ ID INT AUTO CATEGORY ID KEY

INCREMENT COLUM
CATEGORY_NAME VARCHAR NULL CATEGORY NAME

TABLE NAME : CART

FIELD NAME DATA TYPE KEY DESCRIPTION

ID INT AUTO PRODUCT ID KEY

INCREMENT COLUM
USER_ID INT AUTO PRODUCT ID KEY
INCREMENT COLUM
PID INT NULL PRODUCT ID KEY
COLUM
NAME VARCHAR NULL PRODUCT NAME

PRICE VARCHAR NULL PRODUCT PRICE

QUANTITY VARCHAR NULL PRODUCT

QUANTITY
IMAGE VARCHAR NULL PRODUCT IMAGE

46 | P a g e
 FLOWER SHOP

TABLE NAME : MESSAGE

FIELD NAME DATA TYPE KEY DESCRIPTION

ID INT AUTO MESSAGE ID KEY

INCREMENT COLUM
USER_ID INT AUTO MESSAGEID KEY
INCREMENT COLUM
NAME VARCHAR NULL MESSAGE NAME

EMAIL VARCHAR NULL MESSAGE MAIL

NUMBER VARCHAR NULL MESSAGE

NUMBER
MESSAGE VARCHAR NULL MESSAGE
MESSAGE

TABLE NAME : RATE

FIELD NAME DATA TYPE KEY DESCRIPTION

ID INT AUTO ID KEY COLUM

INCREMENT
RATEDATE VARCHAR NULL RATE DATE

RATING VARCHAR NULL RATING

TABLE NAME : REVIEW

FIELD NAME DATA TYPE KEY DESCRIPTION

ID INT AUTO ID KEY COLUM

INCREMENT
RATEDATE VARCHAR NULL RATE DATE

REVIEW VARCHAR NULL REVIEW

47 | P a g e
 FLOWER SHOP

TABLE NAME : ORDERS

FIELD NAME DATA TYPE KEY DESCRIPTION

ID INT AUTO ID KEY COLUM

INCREMENT
USER_ID INT AUTO ID KEY COLUM
INCREMENT
NAME VARCHAR NULL ORDER NAME

EMAIL VARCHAR NULL ORDER MAIL

NUMBER VARCHAR NULL ORDER NUMBER

METHOD VARCHAR NULL ORDER METHOD

ADDRESS VARCHAR NULL ORDER ADDRESS

TOTAL_PRODUCTS VARCHAR NULL ORDER TOTAL

PRODUCT
TOTAL_PRICE VARCHAR NULL ORDER PRICE

PLACED ON VARCHAR NULL ORDER

PLACED_ON
PAYMENT_STATUS VARCHAR NULL ORDER PAYMENT

48 | P a g e
 FLOWER SHOP

TABLE NAME : USERS

FIELD NAME DATA TYPE KEY DESCRIPTION

ID INT AUTO ID KEY COLUM

INCREMENT
NAME VARCHAR NULL USERS NAME

EMAIL VARCHAR NULL USERS MAIL

PASSWORD VARCHAR NULL USERS PASSWORD

CPASSWORD VARCHAR NULL USERS

CPASSWORD

TABLE NAME : WISHLIST

FIELD NAME DATA TYPE KEY DESCRIPTION

ID INT AUTO ID KEY COLUM

INCREMENT
USER_ID INT AUTO ID KEY COLUM
INCREMENT
PID IN NULL PRODUCT ID

NAME VARCHAR NULL PRODUCT NAME

PRICE VARCHAR NULL PRODUCT PRICE

IMAGE VARCHAR NULL PRODUCT IMAGE

49 | P a g e
 FLOWER SHOP

6.2 Directory Structure :

FLOWER SHOP

50 | P a g e
 FLOWER SHOP

6.3 Input Design :

ADMIN SITE :

ADMIN LOGIN

ADMIN DASHBOARD :

51 | P a g e
 FLOWER SHOP

PRODUCT :

ADD PRODUCT :

52 | P a g e
 FLOWER SHOP

EDIT PRODUCT :

DELETE PRODUCT :

53 | P a g e
 FLOWER SHOP

CATEGORY :

ADD CATEGORY :

EDIT CATEGORY :

54 | P a g e
 FLOWER SHOP

DELETE CATEGORY :

ORDERS :

55 | P a g e
 FLOWER SHOP

PAYMENT :

RATE :

56 | P a g e
 FLOWER SHOP

REVIEW :

MESSAGES:

57 | P a g e
 FLOWER SHOP

USERS:

58 | P a g e
 FLOWER SHOP

CLIENT SITE :

REGISTRATION :

LOGIN :

59 | P a g e
 FLOWER SHOP

HOME PAGE :

60 | P a g e
FLOWER SHOP

61 | P a g e
 FLOWER SHOP

ABOUT US :

62 | P a g e
 FLOWER SHOP

CONTACT US :

63 | P a g e
 FLOWER SHOP

SERVICES :

BLOG :

64 | P a g e
 FLOWER SHOP

BLOG 1 :

65 | P a g e
 FLOWER SHOP

SHOP :

66 | P a g e
 FLOWER SHOP

WISHLIST :

VIEW PAGE:

67 | P a g e
 FLOWER SHOP

CART :

RATE & REVIEW :

68 | P a g e
 FLOWER SHOP

BILL :

69 | P a g e
 FLOWER SHOP

CHECKOUT :

ORDER :

70 | P a g e
 FLOWER SHOP

ACCOUNT :

ADDRESS :

71 | P a g e
 FLOWER SHOP

CHANGE PASSWORD :

SEARCH :

72 | P a g e
 FLOWER SHOP

SOFTWARE
TESTING

73 | P a g e
 FLOWER SHOP

7 . Software Testing

7.1 Unit Testing :

UNIT ID ADMIN SITE /MODULE

TESTED BY AMAN kATVE

TESTED ON FLOWER SHOP ADMIN SITE

ID DESCRIPTION RESULT YES/NO REMARK

1 View all All module yes ok

available appear
module
2 Admin login Successfully yes ok
message
appear &
validation
message also
3 Add , update & Error message yes ok
delete in and validation
product appear
4 Add , update & Error message yes ok
delete in and validation
category appear
5 order Error message yes ok
and validation
appear
6 Message Error message yes ok
and validation
appear

74 | P a g e
 FLOWER SHOP

UNIT ID USER SITE /MODULE

TESTED BY SHRIMALI FALGUNI

TESTED ON FLOWER SHOP USER SITE

ID DESCRIPTION RESULT YES/NO REMARK

1 View all All module yes ok

available appear
module
2 User Successfully yes ok
registration message
appear &
validation
message also
3 User login Error message yes ok
and validation
appear
4 Product add to Error message yes ok
car and validation
appear
5 Product add to Error message yes ok
wishlist and validation
appear
6 Product order Error message yes ok
and validation
appear
7 search Search product yes ok
and validation

payment Validation yes ok

8 appear and
error message
contact Validation yes ok
9 appear and
message
validation

75 | P a g e
 FLOWER SHOP

7.2 Integration Testing :

Integration testing is the process of testing the interface between two

software units or modules. It focuses on determining the correctness of the
interface. The purpose of integration testing is to expose faults in the
interaction between integrated units. Once all the modules have been unit-
tested, integration testing is performed. Integration testing is a software
testing technique that focuses on verifying the interactions and data
exchange between different components or modules of a software
application. The goal of integration testing is to identify any problems or
bugs that arise when different components are combined and interact with
each other. Integration testing is typically performed after unit testing and
before system testing. It helps to identify and resolve integration issues
early in the development cycle, reducing the risk of more severe and costly
problems later on.User Account Create and verified properly.
 Sign in and Sign Out work properly and load user data.
 User Profile update and load properly.
 Change Password and Deleted account function work fine.
 Reminder functions work properly and show notification on reminder
seated time.
 Transaction recodes create, update and delete properly.
 User can export transactions recodes.
 Analysis work well and shows desired result, analysis filtration and char
generation work properly.
 Home analysis feature work properly.
 Searching Truncations in records work as expected.
 All tools work fine and show desired output results.
 Family group created and member can chat with another member
properly.
 Members can add transaction’s and manage it.

76 | P a g e
 FLOWER SHOP

 Members can export transactions and also, we analysis base on those

transactions.
 Group Admin can manage group profile and all members can leave
group properly.

A testing environment is a software and hardware configuration that allows

testing teams to run test cases. In other words, it enables test execution with
properly configured hardware, software, and network.
The test bed or test environment is set up according to the requirements of
the Application Under Test. On rare occasions, a test bed may be a mix of the
test environment and the test data with which it interacts.
Software testing success is ensured by setting up the correct test
environment. Any errors in this procedure may result in the customer incurring
more costs and effort.

 We test our application in many android devices, also it works fine and
smoothly for different devices.
 Family Expense Manager work well on android version 9 and higher. I
develop this app for Android device,
 we build this app in flutter so we can easily deploy this app for iOS
Devices also.
 Testing of application is done on different mobile to check whether
application is working properly on different mobile without any problem.

77 | P a g e
 FLOWER SHOP

7.3 System Testing

System testing is a type of software testing that evaluates the overall

functionality and performance of a complete and fully integrated
software solution. It tests if the system meets the specified
requirements and if it is suitable for delivery to the end-users. This type
of testing is performed after the integration testing and before the
acceptance testing.

System Testing is a type of software testing that is performed on a

complete integrated system to evaluate the compliance of the system
with the corresponding requirements. In system testing, integration
testing passed components are taken as input. The goal of integration
testing is to detect any irregularity between the units that are integrated
together. System testing detects defects within both the integrated units
and the whole system. The result of system testing is the observed
behavior of a component or a system when it is tested. System Testing
is carried out on the whole system in the context of either system
requirement specifications or functional requirement specifications or in
the context of both.

78 | P a g e
 FLOWER SHOP

Test Actual
Test Filed Step Executed Expected Result
id Result

1 Home Empty Direct to Home As Expected

Return To Previous
2 Back Press Back Button As Expected
Activity

Plus, Sign Press on Floating Add Open Transaction Recode

3 As Expected
Floating Button Button Screen

4 Menu Icon Press on Shows Application Drawer. As Expected

5 Menu Item Press on Item Icons Open specific activity screen As Expected

Press on Floating
6 Image Button Open Add Image Activity As Expected
Image Button

Left to Right swipe Show Edit and Delete

7 Swipe left to right As Expected
in Recodes Options

8 Click on Edit Icons Press on Open Data edit screen As Expected

Click on Delete
9 Press on Open delete exist data As Expected
Icons

Tab on sub menu

10 Press on Change Analysis Content As Expected
items of Analysis

11 Tap On Tool Press on Tools Picture Associated Tool As Expected

12 Log out Press on Sign out Form Application As Expected

Plus, Icon in
Open Category Menage
13 Recode Press on Button As Expected
Alert Box
Transaction

79 | P a g e
 FLOWER SHOP

8 .Limitations and Future Scope of Enhancements

Limitations:

Although I have put my best efforts to make the software flexible, easy to
operate but limitations cannot be ruled out even by me. Though the software
presents a broad range of options to its users some intricate options could
not be covered into it; partly because of logistic and partly due to lack of
sophistication. Paucity of time was also major constraint, thus it was not
possible to make the software foolproof and dynamic.
Lack of time also compelled me to ignore some part such as storing old
result of the candidate etc.

Scope:

While the proposed carpooling service offers various benefits, it also has
some limitations that need to be considered:

 Limited Coverage Area: The service may not be available in all

regions, especially in rural or less densely populated areas where there
may be fewer potential users or drivers. This limitation could restrict
accessibility for some individuals who reside outside the service
coverage area.

 Dependence on User Participation: The effectiveness of the

carpooling service heavily relies on user participation. If there are not
enough users or drivers registered on the platform, it may be
challenging for individuals to find suitable matches for carpooling,
leading to underutilization of the service.

80 | P a g e
 FLOWER SHOP

 Scheduling and Coordination Challenges: Coordinating schedules

and travel routes among multiple users can be complex, particularly
when users have varying commuting patterns or time constraints. This
may result in difficulties finding compatible carpooling partners and
require compromises in terms of departure times and routes.

 Reliability and Availability: Users may encounter issues related to

the reliability and availability of carpooling arrangements. Factors such
as last-minute cancellations, changes in travel plans, or unexpected
delays can disrupt scheduled rides, impacting the overall user
experience.

 Safety and Security Concerns: Sharing rides with strangers may

raise concerns about personal safety and security. Despite
implementing safety features such as user verification and ratings,
some individuals may still feel apprehensive about carpooling with
unfamiliar passengers or drivers.

 Environmental and Social Equity Considerations: Carpooling

services may inadvertently exacerbate existing environmental and
social inequalities if certain demographic groups are systematically
excluded or marginalized from participating. Ensuring equitable access
to carpooling opportunities and addressing potential barriers to
participation is essential for promoting inclusivity and fairness within the
carpooling ecosystem.

 Incentive Structure and Cost Sharing: Ensuring fair and equitable

cost sharing among carpooling participants can be complex, especially
when considering factors such as distance traveled, fuel costs, and
vehicle maintenance expenses. Disparities in cost-sharing
arrangements may deter some individuals from participating in
carpooling, particularly if they perceive the cost savings to be minim

81 | P a g e
 FLOWER SHOP

8. Future Scope of Enhancements

Several future enhancements could be considered to further improve and

expand the carpooling service:

 Integration of Advanced Matching Algorithms: Implementing more

sophisticated matching algorithms that consider additional factors such
as user preferences, commuting patterns, and social connections could
enhance the efficiency and effectiveness of ride matching. Machine
learning techniques could be utilized to continuously optimize matching
algorithms based on user feedback and historical data.

 Smart Routing and Dynamic Pickup/Drop-off Points: Introducing

smart routing features that optimize travel routes in real-time based on
traffic conditions, user preferences, and ride requests could minimize
travel time and congestion. Dynamic pickup and drop-off points could
be implemented to accommodate changing user preferences and
optimize route efficiency.

 Enhanced Safety and Security Features: Investing in advanced

safety and security features such as real-time monitoring, emergency
assistance buttons, and AI-powered risk assessment tools could further
enhance user safety and confidence. Integration with emergency
services and third-party safety platforms could provide additional layers
of protection for users.

 Integration with Public Transportation Systems: Partnering with

public transportation agencies to integrate carpooling services with
existing transit networks could provide users with seamless multi-modal
transportation options. Integration features such as synchronized
schedules, combined ticketing, and transit subsidies could encourage
modal shift and reduce reliance on single-occupancy vehicles.

82 | P a g e
 FLOWER SHOP

 Incentive Programs and Gamification: Implementing incentive

programs and gamification elements to encourage participation and
promote sustainable commuting behaviors could increase user
engagement and loyalty. Rewards for eco-friendly commuting, ride
sharing milestones, and community challenges could incentivize users
to choose carpooling over solo driving.

 Expansion to New Markets and Mobility Services: Expanding the

carpooling service to new geographic regions, including underserved
areas and emerging markets, could broaden access to shared mobility
options. Additionally, exploring partnerships with other mobility service
providers such as bike-sharing, scooter-sharing, or microtransit services
could offer users more comprehensive and integrated transportation
solutions.

 Integration of Environmental Impact Metrics: Introducing features

that track and quantify the environmental impact of carpooling trips,
such as carbon emissions saved, fuel consumption reduced, and
vehicle miles traveled (VMT) avoided, could raise awareness and
incentivize users to choose sustainable transportation options.
Integration with environmental monitoring tools and sustainability
certifications could further promote eco-friendly commuting practices.

 Community Engagement and Social Features: Enhancing community

engagement through social features such as user forums, community
events, and peer-to-peer networking could foster a sense of belonging
and encourage users to actively participate in the carpooling
community. User-generated content, carpooling success stories, and
community initiatives could help build a vibrant and supportive user
community.

83 | P a g e
 FLOWER SHOP

9. Bibliography & Reference

 For PHP
 www.php.net
 https://www.w3schools.com/php/

 For CSS
 http://css-tricks.com/

 For Bootstrap
 https://getbootstrap.com/docs/3.3/components/

 For Carpooling Service Functionality

 https://github.com/maihuong99/Flower-Shop-Website /

84 | P a g e