MCA

A Project Report
ON
Flower Shop
GUJARAT TECHNOLOGICAL UNIVERSITY
Chandkheda, Ahmedabad

B. H. Gardi College of Engineering & Technology

Software Project-2 (639404)

SUBMITTED IN PARTILA FULFILLMENT FOR AWARD OF

MASTER OF COMPUTER APPLICATIONS
SEMESTER - III

Submitted By
Sojitra Aeshvi
(235030694081)
Nimbark Roshani
(235030694048)
Ghodasara Anjali
(235030694019)

Submitted To
Gujarat Technological University

Under the Guidance of

Prof. Yash Buhecha

Academic Year (2024-2025)

MCA

B.H.Gardi College of Engineering &Technology

CERTIFICATE
This is to certify that Mr. / Miss. of
semester _branch Enrollment no. has satisfactorily
completed his/her term work in the subject for the term ending in
2024.

Date:

Subject In charge Head of Department

(Prof. Yash Buhecha) Prof. Jalpesh Ghumaliya
 Index

Sr No. Name Page No. Sign

1. Introduction
1.1. Existing System
1.2. Need for the new system
1.3. Objective of the new system
1.4. Problem Definition
1.5. Core Components
1.6. Project Profile
1.7. Assumptions Constraints
1.8. Advantages and Limitations of the
Proposed System
2. Requirement Determination & Analysis
2.1. Requirement Determination
2.2. Targeted Users
3. System Design
3.1. User Case Diagram
3.2. Class Diagram
3.3. Interaction Diagram
3.4. Activity Diagram
3.5. Data Dictionary
4. Development
4.1. Coding Standards
5. Agile Documentation
5.1. Agile Project Charter
5.2. Agile Roadmap/ Schedule
5.3. Agile Project Plan
5.4. Agile User Story (Minimum 3 Tasks)
5.5. Agile Release Plan
5.6. Agile Sprint Backlog
5.7. Agile Test Plan
5.8. Earned-value and burn charts
6. Proposed Enhancements
7. Conclusion
8. Bibliography
MCA

INTRODUCTION

The "Flower Shop" project is a comprehensive venture aimed at creating a unique and
delightful floral shopping experience. This project focuses on establishing an online and/or
physical shop dedicated to offering a wide variety of fresh flowers, creative floral arrangements,
and related services. The Flower Shop will cater to various customer needs, including personal
gifts, corporate events, weddings, and other special occasions.
The primary goal of the Flower Shop is to provide customers with high-quality flowers
and exceptional service, ensuring a memorable and enjoyable shopping experience. By
combining creativity, expertise, and a passion for floriculture, the Flower Shop aims to stand out
as a preferred destination for all floral needs.

Existing System

In the current market landscape, flower shops primarily operate in both physical and
online formats. Traditional brick-and-mortar flower shops offer in-person experiences where
customers can browse, select, and purchase floral arrangements with the guidance of experienced
florists. These shops often rely on walk-in customers, word-of-mouth, and local advertising for
business.
Online flower shops, on the other hand, provide the convenience of browsing and
purchasing flowers from anywhere, often featuring a broader selection and the ability to
customize orders. These platforms typically offer delivery services, allowing customers to send
flowers directly to recipients, making them ideal for special occasions and last-minute purchases.
However, the existing system has some common challenges:
 Limited Personalization: While online shops offer convenience, they often lack the
personalized touch and expert advice that in-store experiences provide.
 Inconsistent Quality: The quality of flowers can vary significantly, with some shops
unable to maintain freshness, especially during transit.
 Lack of Real-Time Availability: Many shops struggle with real-time inventory
management, leading to issues with availability and substitutions.
 Inadequate Customer Service: Customer service can be lacking, particularly in online
settings where personalized assistance is limited.
 Pricing and Delivery Issues: Hidden fees, high delivery charges, and unclear pricing
structures can deter potential customers.
These challenges highlight the need for a more integrated approach that combines the
personal touch of traditional flower shops with the convenience and efficiency of online
platforms, setting the stage for the development of a more robust and customer-friendly flower
shop experience.

1
MCA

Need of the New System

The current market for flower shops faces several challenges that necessitate the
development of a new and improved system:
 Enhanced Customer Experience
 Improved Quality Control
 Efficient Inventory Management
 Seamless Online and Offline Integration.
 Advanced Delivery Options
 Enhanced Personalization and Customization
 Better Customer Support
 Data-Driven Insights

Objective of the New System

 Enhance Customer Experience

 Ensure High-Quality Products

 Improve Inventory Management

 Provide Personalized Services

 Streamline Order and Delivery Processes

 Integrate Online and Offline Channels

 Enhance Customer Support

 Utilize Data Analytics

 Foster Customer Loyalty

 Promote Sustainable Practices

2
MCA

Problem Definition

The flower industry faces several challenges that affect both customers and business
owners, highlighting the need for an improved system that addresses these pain points. The
existing flower shop models, whether traditional brick-and-mortar or online-only platforms, are
often plagued by inefficiencies, inconsistent service quality, and a lack of personalization. The
following are the key problems identified in the current system:

 Inconsistent Product Quality

 Limited Customization and Personalization
 Poor Inventory Management
 Complex Ordering and Delivery Processes
 Lack of Real-Time Availability Information
 Inadequate Customer Support
 Disconnected Online and Offline Experiences
 Limited Use of Data Analytics
 Environmental Concerns
 High Competition with Low Differentiation

3
MCA

Core Component

System Installation Requirements:

Input devices: Keyboards, Mouse

Output devices: CRT/LCD/LED Monitors

2-250 GB hard disk drive

Computer memory(RAM) of > 4 GB and processor speed of 1.6GHz

System Development Requirements:

PHP (Front End Tool)

MYSQL i(Back End Tool)

Project Profile

Project Title Flower Shop

Operating system Microsoft window 11

Front-End Tools PHP

Back-End Tools MYSQL i

Programming PHP
language
Submitted To Gujarat Technological University

Project guide Mr.Yash Buhecha

4
MCA

Assumptions and Constraints

Assumptions:
 The coding should be error free.
 The system should be user-friendly so that is the easy to use for user.
 The valuable data/information can be stored a for longer period with easy accessing and
manipulation of the same.
 The system should have more storage capacity and provides fast access to the database.
 The system should be provides search facilities and support quick transactions.
 Users may access from any computer that has internet browsing capabilities and an
internet connection.

Constraints:
Any update regarding the Item from the flower shop is to be recorded to have update &
correct values, It should be notified as soon as possible and should be correctly calculated.

5
MCA

Advantages and Limitations of the Proposed System

Advantages:
User-friendly: Our website can be used by both admin and the Customers. We have
separate portals for both.
Easy surfing: Items can be searched based on their Id, so it can be easily find out items
etc.
Better customers’ data: This data is valuable since you can use it to send targeted
promotions to your customers and entice them to keep coming back.
Save Time.
Greatly reduce paper use

Limitations:
Does not keep track of stock.
There is no human interaction if users have some enquiry.

6
MCA

REQUIREMENT DETERMINATION &

ANALYSIS

Requirement Determination

 Requirement determination activity is the most difficult part of information gathering.

 Focusing on basic services by collecting the opinions of the customers.

Hardware Requirement

Processor
RAM 4GB
Hard Disk 500 GB

Software Requirement

System
Operating System Windows 11
Front end PHP
Back end My SQL i
Designing Tools HTML, CSS, JavaScript

7
MCA

Targeted Users

The online fruit ordering system has two main user classes. These include the admin, and
customer. This section will explain in detail all the features and the working of those for each
user class.

1).Customer:

 Login:
Customer in the assigned a unique username and password by the
administrator. The username and password is the same as their login successfully.

 Home Page:
After successfully login, the Customer is display detail in your system.
 Add Customers:
Our system will be add in customer. The user interfaces again easy.
 Add Item:
Over system will be add in Items .The user interface is again easy.
 Delete Item:
This system are not use item will be deleted.

2). Admin:
The admin is responsible for adding, updating, deleting and maintaining all the
information, and customer information. All this data is stored in the database in their
respective tables.
This information is stored in the Assign table. The admin also has access to
flower shop of each customer and can modify them.

There are several features in place to ensure that querying the database is quick
and efficient for the admin. As the database has the potential to become huge, there is
a add feature for every table including item list, customer list etc. The search has get a
specific record based on Id of customer. Also, it can filter the record based on flower
shop.

8
 MCA

SYSTEM DESIGN

Data Flow Diagram (DFD)

 Context level- DFD

9
 MCA

 DFD LEVEL -1 (Admin)

10
 MCA

 DFD LEVEL-1 (User)

11
MCA

 E-R Diagram

12
MCA
 Activity Diagram(Admin)

13
MCA
 Activity Diagram(User)

14
MCA

 Interaction Diagram

15
MCA

 Use Case Diagram

16
MCA
 Class Diagram

17
MCA
Data Dictionary

18
MCA

19
MCA

20
MCA
CODING STANDARDS

Admin

21
MCA

22
MCA

23
MCA

24
MCA

25
MCA

26
MCA

Index

27
MCA

View Product

28
MCA

29
MCA

30
MCA

Add Product

31
MCA

Edit Product

32
MCA

33
MCA

Screen Shots

Home Screen

34
MCA

About Us

35
MCA

Contact Us

36
MCA

Registration

37
MCA

Login

38
MCA

Product

39
MCA

Wishlist

40
MCA

Orders

41
MCA

Shopping Cart

42
MCA

Checkout Order

43
MCA

Messages

44
MCA

Admin

Login

45
MCA

46
MCA

AGILE DOCUMENTATION

Agile Project Charter

The product owner identifies the product vision.The product vision is a definition of
what your product is, how it will support your company or organization’s strategy, and who will
use the product. On longer projects, revisit the product vision at least once a year.

Agile Roadmap/schedule

The product owner creates a product roadmap. The product roadmap is a high-level
view of the product requirements, with a loose time frame for when you will develop those
requirements. Identifying product requirements and then prioritizing and roughly estimating the
effort for those requirements are a large part of creating your product roadmap. On longer
projects, revise the product roadmap at least twice a year.

Agile Project Plan

The product owner creates a release plan. The release plan identifies a high-level time
table for the release of working software. An agile project will have many releases , with the
highest-priority features launching first. A typical release includes three-to-five sprints.

47
MCA

Agile User Story(Minimum 3 tasks)

 Inception:

You often create a stack of user stories during Inception as part of your
requirements envisioning activitiesto identify the scope of your system.

 Construction:
During construction iterations you will identify new stories, split existing stories
when you realize that they're too large to be implemented in single iteration, prioritize
existing stories, or remove stories that are no longer considered to be in scope. The point
is that your stories evolve over time just like other types of requirements models evolve.
Furthermore, enhancement requests may be identified by your support staff during the
production phase and then forwarded to a development team as they are working on an
upcoming release. These enhancement requests are effectively new stories (albeit in a
different format).

 Transition:

Sometimes new stories will be identified during the Transition phase, although
this isn't very common as the focus of release is on hardening the system and not on new
functionality. But it does happen, and these stories would be prioritized and placed on the
stack in priority order just as you normally would.

48
MCA

Agile Release Plan

The agenda of a release planning can be :-

 Opening ceremony :Welcome message, review purpose and agenda, organizing tools
and introduction to business sponsors.

 Product Vision, Roadmap :Show the large picture of the product.

 Review previous releases:Discussion on any item which can impact the plan.

 Release name / theme − Inspect the current status of roadmap themes and do the required
adjustments, if any.

 Velocity − Present the velocity for the current release and of previous releases.

 Release schedule − Review key milestones and decision on time boxes for release and
iterations within release.

 Issues and concerns − Check any concerns or issue and record them.

 Review and Update the Definition of Done − Review the definition of done and make
appropriate changes based on technology, skill, or changes in team memberssince the last
iteration / release.

 Stories and items to be considered − Present the user stories and features from the
product backlog to beconsidered for scheduling in the current release.

 Determine sizing values − If the velocity is unknown, then plan the sizing values to be
used in the release planning.

 Coarse the size of stories − The delivery team determines the appropriate size of the
stories underconsideration and splits the stories into multiple iterations if a story is too
large. The product owner and the subject matter experts clarify the doubts, elaborate the
acceptance criteria, and make proper story splits. The scrum master facilitates the
collaboration.

 Map stories to iterations − The delivery team and the product owner move the
stories/defects in the iterations based on the size and velocity. The scrum master
facilitates the collaboration.

 New concerns or issues − Check any new issues based on previous experience and
record the same.

 Dependencies and assumptions − Check anydependencies/assumptions planned during

the release planning.

49
MCA

 Commit − The scrum master calls for the planning. Delivery team and Product owner
signal it as the best plan and then commit to move to the next level ofplanning, that is,
iteration planning.

 Communication and logistics planning − Review/Update the communication and

logistics planning for the release.

 Parking lot − Process parking lot means all items should be either resolved or set as
action items.

 Distribute Action items and action plans − Distribute the action items among their
owners, process the action plan.

 Retrospect − Solicit feedback from participants to make the meeting successful.

 Close − Celebrate the success.

Agile Sprint Backlog

 The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan
for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a
forecast by the Development Team about what functionality will be in the next Increment
and the work needed to deliver that functionality into a “Done” Increment.

 The Sprint Backlog makes visible all the work that the Development Team identifies as
necessary to meet the Sprint Goal. To ensure continuous improvement, it includes at least
one high priority process improvement identified in the previous Retrospective meeting.

 The Sprint Backlog is a plan with enough detail that changes in progress can be understood
in the Daily Scrum.The Development Team modifies the Sprint Backlog throughout the
Sprint. Only the Development Team can change its Sprint Backlog during a Sprint. The
Sprint Backlog is a highly visible, real-time picture of the work that the Development Team
plans to accomplish during the Sprint, and it belongs solely to the Development Team.

50
MCA

Agile Test Plan

 Unlike the waterfall model, in an agile model, a test planis written and updated for every
release. The agile test plan includes types of testing done in that iteration like test data
requirements, infrastructure, test environments, and test results. Typical test plans in
agile includes:
 Testing Scope
 New functionalities which are being tested
 Level or Types of testing based on the features complexity
 Load and Performance Testing
 Infrastructure Consideration
 Mitigation or Risks Plan
 Resourcing
 Deliverable and Milestone

51
MCA

Earned-value and burn charts

Earned Value is a project management monitoring & reporting technique that has been
developed and utilized over the course of the last 100 years in traditional engineering projects. It
relies on an initial task-based base lined plan for measuring progress, and a project with well-
defined scope that evolves in a sequential, linear fashion. In agile, projects evolve in an iterative,
non-linear fashion, with feedback loops that affect the initial plan. Change is expected and
frequent throughout the project life cycle, thus measuring progress relative to the initial plan will
be misleading. While there are issues with attempting to apply Earned Value to Agile projects,
agile project management techniques such as burn charts (indicating the amount of functionality
outstanding vs. completed over time, etc.) provide status & progress information very similar to what
Earned Value attempts to measure. Costs can be added to the charts to view the information together with
rate of feature completion. All of these may be more valuable to the project manager and project
stakeholders in monitoring an agile project, rather than attempting to apply traditional Earned Value.

52
MCA

PROPOSED ENHANCEMENT

This website provides a computerized version of online fruit ordering system

which will benefit the customers.

It makes entire process online wherecustomer can search items.

This project thus making it more interactive more user friendly and project which
fulfills each user need in the best way as possible.

As well as this project save the time of customer and provide fresh and seasonal
fruit as per their requirement.
Admin can easily manage product and offer about fruit. They can also manage
advertisement.

53
MCA

CONCLUSION

 Our project is only a humble venture to satisfythe needs to manage

their project work.

 It is completely open source and can be seen here.

 It useful to fulfill customer requirement.

54
MCA

BIBLIOGRAPHY

 Reference Book:-

1) Node.js Complete reference guide.

2) SAD (System Analysis and Designing) Software Qualityassurance and

Testing.

 Reference Website:-

www.nodejs.org

www.dataflowdiagram.com

www.javatpoint.com

https://www.lucidchart.com

www.w3school.com

55