Atmanand Saraswati Science College

Bachelor of Computer Application

Programme

Project Report
T.Y.B.C.A. SEMESTER – VI
AY 2023-24

The FireGuard
By

Exam No. Name of Student

6708 Shruti savani T.
6709 Zeel Savani V.

Guided By:
Ms. Chitra Gohil
 Atmanand Saraswati Science College

CERTIFICATE

This is to certify that Ms. Savani Shruti Tulshibhai

examination number 6708 has satisfactorily completed his /
her minor project work entitled The fireguard as partial
fulfilment of requirements for T.Y.B.C.A. Semester – VI, during the
academic year 2023-24.

Date: 02/04/2024
Place: Surat

Guided by Head of department

Ms. Chitra Gohil Ms. Eeva Sheladiya

 Atmanand Saraswati Science College

CERTIFICATE

This is to certify that Mr Savani Zeel Vithalbhai

examination number 6709 has satisfactorily completed his / her minor
project work entitled _The fireguard as partial fulfilment of
requirements for T.Y.B.C.A. Semester – VI, during the academic year
2023-24.

Date: 02/04/2024
Place: Surat

Guided by Head of department

Ms. Chitra Gohil Ms. Eeva Sheladiya

 ACKNOWLEDGEMENT

I would like to express my gratitude and appreciation to all those

who gave me the possibility to complete this project. Special thanks are to
my mentor Ms. Chitra Gohil whose help, stimulating suggestions and
encouragement helped me in all time of fabrication process and in writing
this report. I also sincerely thanks for the time spent proofreading and
correcting my many mistakes.
I would also like to acknowledge with much appreciation the
crucial role of the staff in B.C.A. Laboratory, who gave me a permission
to use the lab equipment and also the machine and to design the drawing
and giving a permission to use all the necessary tools in the laboratory.
Many thanks go to the all lecturers who have given their full effort
in guiding me in achieving the goal as well as their encouragement to
maintain our progress in track. My profound thanks go to all classmates,
especially to my friends for spending their time in helping and giving
support whenever I need it in fabricating my project.
 ABSTRACT

The FireGuard: A Comprehensive Fire Safety Mobile App with Fire

Awareness and Fire Tools Buying Portal

Fire incidents continue to pose significant risks to lives and property

worldwide. In response, there is a growing need for innovative solutions
that promote fire safety awareness and facilitate access to essential fire
tools and equipment. This project presents "FireGuard," a comprehensive
mobile application designed to enhance fire safety awareness among users
while providing a convenient platform for purchasing fire tools. The fire
awareness component aims to educate and inform users about fire safety
measures, precautions, and emergency protocols. interactive content, users
can access a wealth of fire safety information. The second feature of the
FireGuard app is a dedicated fire tools buying portal. This portal offers a
seamless and secure platform for users to browse and purchase a wide
range of fire safety equipment, including fire extinguishers, smoke
detectors, fire blankets, escape ladders. the fire tools buying portal offers a
convenient solution for users to access and purchase fire safety equipment
with ease.
 INDEX

Sr No Description Page No.

1 Introduction
1.1 Project Summary 1
1.2 Project Technical Profile 2
2 Scopes & Planning
2.1 Requirement Analysis 3
2.2 Feasibility Study 5
2.3 Timeline Chart 7
2.4 Future Development 8
2.5 Technology Details 9
3 Designing
3.1 Data Flow Diagram 14
3.2 Use Case Diagram 22
3.3 ER Diagram 23
3.4 Database Design 24
3.5 User interface 28
4 Testing
4.1 Unit Testing 47
4.2 Navigation Testing 50
4.3 Functional Testing 52
4.4 Environment Testing 53
5 Conclusion 54
6 References 55
 1. Introduction

1.1 Project summery

 Our application has two sides seller and buyer.

 This system also allows to quickly and easily manage different different plants
category which customers browse and use to place orders with just flew
clicks.
 Our system presents an interactive an up to date our product category menu
with all available options in an easy to use manner.
 Customers can view all fire product like smoke detector, fire Suppression
system, fire pump, fire extinguisher equipment, fire bucket etc type of item.
 Customers can also view all types of product related information and also
show how to use a product as its required.
 At the end customer place order and get order conformation details.
 User can see that how to use the fire product and how it use.
 User can manage his/her profile.
 In our application seller can add multiple product categories and their images
also add product information. Seller can remove and update a category of
product.

 Admin
 Buyer

1|Page
2|Page
 Admin

 Add Product
 Update Product
 Delete Product
 Manage Category
 Manage Price

Buyer

 Mange Profile
 Change Password
 Change Address
 View Product
 Purchase Product
 Chat
 Search product
 Contact seller

3|Page
 1.2 Project Technical Profile

Project Title
The Fireguard
Project Definition project presents "FireGuard," a comprehensive mobile
application designed to enhance fire safety awareness
among users while providing a convenient platform for
purchasing fire tools.

Framework Open source

Type Of Application Mobile Application

Duration 3 Months

Internal Guide Ms. Chitra Gohil

Front End Flutter

Back End Firebase

Language Dart

Operating System Windows 10

Shruti Savani
Submitted By T. Zeel Savani
V.

4|Page
 2. Scopes & Planning

2.1 Requirement Analysis

The requirement analysis and gathering processes are critical for the
successes of any project. To develop any web application system, it is most
important to identity the user requirement in very specific manner, also to
function properly; all interfaces of proposed system with surrounding
system must be identified. Technical requirements are the technical issues
that must be considered to successfully complete a project. These can
include aspects such as performance, reliability, and availability. In
software projects, technical requirements typically refer to how the
software is built.
It's a process of identifying, analyzing, and managing project requirements
to determine what the project should accomplish and eliminate any
ambiguities or conflicting requirements in your project plan. The system is
the one that satisfied all requirements. Which helped us to have a clear idea
about the expected system?

Functional Requirements:
• Reporting requirement
• External interfaces
• regulatory requirements
• Business rules
• Articles
• Historical data
• Authorization

Non-Functional Requirements:
• Documentation
• Portability
• Quality
• Reliability
• Response time
• Scalability
• Stability

5|Page
6|Page
2.2 Feasibility Study

A feasibility study phase provides the analyst with a more thorough

understanding of the problems, opportunities related to personnel. A feasibility
study should be conducted to determine the viability of an idea before
proceeding with the development of human resource. A feasibility study contains
a detailed analysis of what's needed to complete the proposed project. The report
may include a description of the new product or venture, a market analysis, the
technology and labor needed, as well as the sources of financing and capital.
Information has been collected by reference to sources, written references
and information published in scientific, research and literary sites on the
Internet.

 Feasibility is an important phase in the software development process it

enables the developers to have an assessment of the product begin
developed .It refers to the feasibility study of the product in terms of outcomes
of the product, Operational required for implementing it. Feasibility study
should be performed on the basic of various criteria and parameters. The
various feasibilities are :-
o Economic Feasibility
o Technical Feasibility
o Operational Feasibility
o
1) Economical Feasibility :

 for flawless working of a Planty fast Internet connection is required. along

with an Internet connection a costly server is required with max RAM and
Processing power to handle the maximum possible traffic on the site. It
would require a cloudinary subscription to fetch the images and logos of
products. These are feasible economically.
7|Page
8|Page
2) Technical Feasibility:

 The system must be evaluated from the technical point of view first. This
Application does require that much of higher & advanced technology. It
requires database interaction and it also requires to be accessed via web or
internet. This can be easily done. Also these should be a facility of online
Order for the particular Customers on line. It must be developed within
the period of Time excluding the time period for the testing and
validation, verification. Thus it seems that the project is technically
feasible to do.

3) Operational Feasibility:
 The new system can be beneficial only if it satisfies the organization
requirements in such a way that resource utilization and optimum outcome is
justified. A new system should not only be robust but should also be able to
work simultaneously with other systems. Operational feasibility means that
new system should not affect any existing system during the development
phase.

9|Page
10 | P a g
e
2.3 Timeline Chart

11 | P a g
e
2.4 Future Development

 Machine learning will be used to provide appropriate products to our users

for their convenience. User’s preferences, price range and product brands will
be analayzed to extract information of specific user to show them affordable,
suitable and long lasting items.
 In future updates shopkeepers will be able to register their shops and sell
their products through us.
 We will be improving our security to protect the privacy and data of our users.
 Known bugs and error will be fixed.
 We can add coupon’s functionality.

12 | P a g
e
2.5 Technology Details

Hardware Requirements:

Hardware Configuration
8 GB RAM , Intel core i7 or Higher
Development Time processor
8 GB RAM, Intel core i7 or Higher
Run Time processor

Software Requirements:

Software Configuration
Browser Chrome
Operating System Windows 11
Front End Flutter, dart
Back End Dart, firebase
Other Tools Figma, image

13 | P a g
e
  Flutter Information:

Flutter is an open-source UI toolkit created by Google for building natively

compiled applications for mobile, web, and desktop platforms from a single
codebase. Flutter uses the Dart programming language, which was also created by
Google, to build high-performance, visually attractive, and customizable mobile, and
web applications.

Flutter provides a rich set of pre-built widgets and tools for building user
interfaces, which can be customized to match the specific design requirements of the
application. Flutter's widgets are designed to be compassable and can be combined
to create complex layouts and animations.

Flutter also provides a hot-reload feature, which allows developers to see the
changes they make to the code in real-time, without having to rebuild the entire
application. This speeds up the development process and makes it easier to iterate on
designs and fix bugs.

Flutter has gained popularity among developers because of its ease of use,
performance, and ability to build high-quality applications for multiple platforms
using a single codebase. It has been used by various companies, including Alibaba,
Google, and Tangent, to build their mobile and web applications.

10 | P a g e
  Why Flutter?

1. Fast development and testing: Flutter's hot-reload feature allows developers to see
the changes they make to the code in real-time, without having to restart the
application. This speeds up the development process and makes it easier to iterate on
designs and fix bugs.

2. Cross-platform development: Flutter allows developers to build applications for

multiple platforms, including mobile, web, and desktop, from a single codebase. This
reduces the time and effort required to develop and maintain applications for
different platforms.

3. High-performance applications: Flutter uses a compiled programming language

(Dart) and provides its own set of pre-built widgets, which makes it easy to create
high-performance applications that are visually attractive and responsive.

4. Large community and ecosystem: Flutter has a large and growing community of
developers and enthusiasts who contribute to its development and share their
knowledge and experience. There are also numerous packages and libraries
available in the Flutter ecosystem that can be used to add additional functionality to
applications.

5. Open-source and free: Flutter is open-source software, which means that anyone
can use, modify, and distribute it freely. This makes it an affordable and accessible
option for developers who are just starting out or working on a budget.

11 | P a g e
  Dart:

Dart is a general-purpose, object-oriented programming language developed by

Google. It was first announced in 2011 and is used for building web, mobile, and
desktop applications. Dart is a statically typed language, which means that
variable types are known at compile time, and it supports both just-in-time (JIT)
and ahead- of-time (AOT) compilation.

Dart was created to address some of the shortcomings of existing

programming languages, such as JavaScript. It includes features such as optional
typing, garbage collection, and a simpler syntax, which make it easier to learn and
use than some other languages.

Backend Tools:

 FireBase:

Firebase is a Backend-as-a-Service (BaaS) app development platform that provides

hosted backend services such as a real time database, cloud storage, authentication,
crash reporting, machine learning, remote configuration, and hosting for your
static files.

12 | P a g e
 What is Firebase Plunging?

You access Firebase in your Flutter app through the various Firebase Flutter Plugins,
one for each Firebase product (for example: Cloud Firestore, Authentication, Analytics,
etc.).
Since Flutter is a multi-platform framework, each Firebase plugin is applicable for
Apple, Android, and web platforms. So, if you add any Firebase plugin to your Flutter
app, it will be.

13 | P a g e
 3. Designing

3.1 Data Flow Diagram

A data flow diagram (DFD) illustrates how data is processed by a system in terms of
inputs and Outputs. As its name indicates its focus is on the flow of information,
where data comes from, where it goes and how it gets stored.

Strict landing page policy:

 A data flow diagram needs to be simple because user has to go through it,
understand suggest correction or changes.
 External entity
 Data flow
 Process
 Data stores

Symbols used in DFD:

1. process

14 | P a g e
  Flow of data is transformed.
 A Process represents some amount of work u.
 sing behaviour of data.
 Transformation of data from one form to another.
 A circle represents a process.
 The area of the circle is divided into two parts.
 The process number is written in the top portion and process name is written
the bottom portion.
 E.g. verify credits, update inventory file, etc.

2. External Entity:

 A source or destination of data which is external to the system.

 As the name suggest it line outside the context of the system. It represented by
solid squares.
 The people/department that will be giving the data and/or receiving information.
 It can be referred to as external entities as they do not accomplish any word
done by the system.
 The data coming in and the report produced are referred as the input and
Output of the system respectively.

15 | P a g e
 3. Data Flow:

 Line is packet of data. it may be of form of documentation, letter etc.

 A data flow portrays an interface among different components in the flow
diagram. It represents the data of the data as it flows through a system. An
arrow represents it.
 The arrow head point in the direction in which the data moves.

4. Data Stores:

 Any stores data but no reference to the physical method of storing.

 If there is a logical requirement for the data to be stored, it is held in a data store.
 A data store there for, is a repository of the data.

16 | P a g e
  Context level for fireguard

 Context level DFD of FireGuard

17 | P a g e
  First level DFD(admin)

18 | P a g e
  First level DFD(buyer)

 Second level DFD(admin)

 Second level DFD(buyer)

19 | P a g e
  second level DFD(Admin)

20 | P a g e
  second level DFD(buyer)

21 | P a g e
3.2 Use Case Diagram

22 | P a g e
 3.3 ER Diagram

23 | P a g e
 3.4 Data Design

1. Admin Login:

SR NO FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION

1 Email String Primary Key Email id of admin

2 Password String Not Null Password

2. buyer Login:

SR NO FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION

1 Email String Primary Key Email id of buyer

2 Password String Not Null Password

3. Forget Password:

SR NO FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION

1 Email String Primary Key Email id of

buyer
2 New Password String Not Null Password

3 Confirm String Not Null Confirm

Password Password

24 | P a g e
4. Buyer Registration:

SR NO FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION

1 Email String Primary Key Email id of buyer

2 Name String Not Null Buyer Name

3 Mobile No String Not Null Buyer mobile

number
4 password String Not Null password

5 Confirm String Not Null Confirm password

password
6 address String Not Null Home Address of
buyer
7 office String Not Null Office address

5. product category:

SR NO FIELD DATATYPE CONSTRAINTS DESCRIPTION

NAME
1 Product id String Primary Key Product id

2 name String Not Null category name

6. Add product:

SR NO FIELD DATATYPE CONSTRAINTS DESCRIPTION

NAME
1 Product id String Primary Key Id of product
2 Product name String Not Null Product name

3 category String Not Null Category of product

4 price String Not Null Price of product

25 | P a g e
 5 description String Not Null Description of
product.
6 link String Not Null Youtube vedio
link of
Product
7 Admin id String Foreign Key Admin id

7. Cart:

SR FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION

NO
1 Cart Id String Primary Key Uniqe indentification
of cart
2 Product Id String Foreign Key Product id of product

3 Buyer Id String Foreign Key Buyer id of buyer

4 Quantity String Not Null Quantity of product

5 main Total String Not Null Main total You

have Purchase.
6 Product name String Not Null Product name

7 price String Not Null Product price

8. Payment:

SR NO FIELD DATATYPE CONSTRAINTS DESCRIPTION

NAME
1 Product Id String Foreign Key Product id

2 Card owner String Not Null Card Owner

3 Card String Not Null Cart number

number
4 Expire date Date Not Null Card date

5 Cvv String Not Null Cvv number

number
26 | P a g e
9. Orders:

SR NO FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION

1 Order Id String Primary Key Order id for

unique
identification
2 Product Id String Foreign Key Plant id

3 Quantity String Not Null Quantity of product

4 Total Price String Not Null Total price

of Product
5 Status String Not Null Status of order

6 Time String Not Null Time of order

9. Review:

SR NO FIELD NAME DATATYPE CONSTRAINTS DESCRIPTION

1 Review id String Primary Key Review id

2 Rating String Not Null Rating of Product

3 Email id String Not Null Email id for

buyer

10. Wishlist:

SR NO FIELD DATATYPE CONSTRAINTS DESCRIPTION

NAME
1 Product Id String Foreign Key product id

2 Product String Not Null Name of product

Name which is liked

27 | P a g e
 3.5 User interface

Splash Screen Seller buyer

28 | P a g e
 Admin_side:

Admin_login_screen Category_screen

29 | P a g e
 Add_product Product_update/delete

30 | P a g e
 Admin_dashboard Product_update/delete

31 | P a g e
 Product_detail_page All_product

32 | P a g e
 All_product show_rate_review

33 | P a g e
 Privacy_policy admin_profile

34 | P a g e
 Buyer side:

Buyer_registration Buyer_login

35 | P a g e
 Send_otp screen Verify otp

36 | P a g e
 location screen buyer_home_screen

37 | P a g e
 Search_screen chat screen

38 | P a g e
 Category_screen category_wise_product

39 | P a g e
 buyer_drawer favourite screen

40 | P a g e
 Cart screen user address

41 | P a g e
 Payment screen profile screen

42 | P a g e
 order screen buyer order

43 | P a g e
 Continue shopping product_detail screen

44 | P a g e
 Customer care add rate_review

45 | P a g e
 Tracking order help center screen

46 | P a g e
 4. Testing

4.1 Unit Testing

[Link] Case for Admin Login

Test Id Test field Step Executed Result Actual Result

Execute
1 email Empty Msg. given string As Expected
is empty or null
2 password Empty Msg. password is As Expected
invalid

2. Test Case for buyer Login

Test Id Test field Step Executed Result Actual Result

Execute

1 email Empty Msg. given string As Expected

is empty or null
2 password Empty Msg. password is As Expected
invalid

47 | P a g e
3. Test Case of Add product Details

Test Id Test field Step Executed Actual Result

Execute Result
1 Product name Empty Msg. please fill As Expected
record
2 price Only Msg. please fill As Expected
number record
3 link Empty Msg. please fill As Expected
record
4 description Empty Msg. please fill As Expected
record
5 image Empty - Not expected

4. Test Case of Add buyer detail

Test Id Test field Step Executed Result Actual Result

Execute
1 name Empty Msg. please enter As Expected
your Name
2 email Empty Msg. please enter As
your password Expecte
d
3 Mobile number Only Msg. please enter As
numb your mobile Expecte
er number d

48 | P a g e
 4 password Empt Msg. password is As
y/ required Expecte
patter d
n Msg. password
contain Lowercase,
upper case, special
symbol and digit.

5 Confirm Empt Msg. please enter As

passwor y/ password and Expecte
d patter confirm password d
n same!!

Msg. password is
required

5. Test Case of forgot password

Test Id Test field Step Execute Executed Result Actual

Result
1 email Empty Msg. please enter As
your email Expected

49 | P a g e
4.2 Navigation Testing

• Admin

Sr no Link Expected Page Result of Page

1 login Admin Dashboard Admin Dashboard

2 Add product Add product screen Add product screen

3 Manage product All product screen All product screen

4 order admin order screen admin order screen

5 Edit product Update product screen Update product

screen
6 Manage profile Profile screen Profile screen

7 Review/rating Product rating screen Product rating screen

8 Product Product detail screen Product detail screen

9 Log out Admin login screen Admin login screen

• buyer

Sr no Link Expected Page Result of Page

50 | P a g e
 1 login Add Location screen Add Location screen

2 location Buyer dashboard Buyer dashboard

screen screen
3 Forgot password Forgot password Forgot password screen
screen
4 register Add Location screen Add Location screen

5 Search Search product screen Search product screen

6 chat Chat screen Chat screen

7 category Product category Product category

screen screen
8 wishlist Favourite product Favourite product page
page
9 cart Add to cart screen Add to cart screen

10 popular Product detail screen Product detail screen

11 All product Product detail screen Product detail screen

12 Place order Buyer address screen Buyer address screen

13 Save address Payment screen Payment screen

14 Confirm order Buyer dashboard Buyer dashboard

15 profile Buyer Profile screen Buyer Profile screen

16 All order Buyer all order screen Buyer all order screen

17 Manage account Edit profile screen Edit profile screen

18 privacy policy screen policy screen

19 Help center Help center screen Help center screen

20 Rating/review Review screen Review screen

21 My order Track order Track order

51 | P a g e
 22 Contact us Contact screen Contact screen

23 Log out login screen login screen

4.3 Functional Testing

• Login Modules are Working properly with validation.

• New buyers are been added successfully.

• All Modules are working properly.

• New products are added successfully by admin.

• Validations are working properly.

• Log out modules are being successfully.

52 | P a g e
4.4 Environment Testing

Database – Fire Base

OS – Windows

Browser – Firefox/Internet/Explorer/Chrome

Device – Android

53 | P a g e
 5. Conclusion

 Application can able to manage the buyer and their details.

 Application is also good at the security level means that the user or
other unauthorized user will not be able to get all details of the users.
 Application gives the best way for the registration of new members and
joins the portal.
 Authorized login, highly secure.
 User friendly.
 This project satisfies the customer’s need.
 Admin can be able to manage various user information.
 fire safety awareness among users while providing a convenient platform for
purchasing fire tools.

54 | P a g e
 6. Refrences

All the needed information related to Our project “Do & Be” was being clumped
from the following sources:

[Link]

[Link]

[Link]

55 | P a g e