LIFE SAVER QR

A project report submitted to

Rajiv Gandhi Proudyogiki Vishwavidhyalaya, Bhopal
in partial fulfillment for the award of
the degree of
Bachelor of Technology
in
Computer Science & Engineering

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

SUSHILA DEVI BANSAL COLLEGE OF TECHNOLOGY
INDORE- 453331
Jul-Dec 2024
 LIFE SAVER QR

A project report submitted to

Rajiv Gandhi Proudyogiki Vishwavidhyalaya, Bhopal
in partial fulfillment for the award of
the degree of
Bachelor of Technology
in
Computer Science & Engineering

PROJECT GUIDE SUBMITTED BY

Prof. Shraddha kumari Pratik Rathod(0829CS221145)
Prof. Ayesha Akhtar Parth Gupta(0829CS221135)
. Prachi Solanki(0829CS22140)

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

SUSHILA DEVI BANSAL COLLEGE OF TECHNOLOGY
INDORE- 453331
Jul-Dec 2024
 ACKNOWLEDGEMENT

The successful completion of any significant task is the outcome of

invaluable aggregate combination of different people in radial
direction explicitly and implicitly. We would therefore take
opportunity to thank and express our gratitude to all those without
whom the completion of project would not be possible.
We express our sincere gratitude to Prof. Shraddha kumari Mam,
Head of the Department, Computer Science and Engineering for her
support and guidance and provided all the facilities that helped us in
timely completion of this project report
We would like to thanks Prof. Shraddha kumari and Prof.Ayesha
Akhtar mam project guide of Sushila Devi Bansal College of
Technology, Indore for her support and encouragement
I express my sincere gratitude to our institution and management for
providing us with good infrastructure, laboratory facilities, qualified
and inspiring staffs, and whose guidance was of immense help in
completion of this seminar successfully.

Pratik Rathod (0829CS221145)

Parth Gupta (0829CS221135)
Prachi Solanki (0829CS221140)
SUSHILA DEVI BANSAL COLLEGE OF TECHNOLOGY
INDORE, 453331

CERTIFICATE
This is to certify that Pratik Rathod (0829CS221145), Parth
Gupta (0829CS221135), Prachi Solanki (0829CS221140) have
completed their project work, titled “LIFE SAVER QR” as per
the syllabus and have submitted a satisfactory report on this
project as a part of fulfillment towards the degree of “Bachelor
of Technology” (Computer Science & Engineering) from Rajiv
Gandhi Proudyogiki VIshwavidhyalaya, Bhopal.

HEAD OF THE DEPARTMENT DIRECTOR PROJECT GUIDE

SUSHILA DEVI BANSAL COLLEGE OF TECHNOLOGY
INDORE, 453331

CERTIFICATE
This is to certify that Pratik Rathod (0829CS221145), Parth
Gupta (0829CS221135), Prachi Solanki (0829CS221140) have
completed their project work, titled “LIFE SAVER QR” as per
the syllabus and have submitted a satisfactory report on this
project as a part of fulfillment towards the degree of “Bachelor
of Technology” (Computer Science & Engineering) from Rajiv
Gandhi Proudyogiki VIshwavidhyalaya, Bhopal.

INTERNAL EXAMINER EXTERNAL EXAMINER

CHAPTER TITLE PAGE NO.
ABSTRACT i
LIST OF TABLES ii
LIST OF FIGURES iii
LIST OF SYMBOLS iv

1. Introduction 1
1.1. Purpose 1
1.2. Scope 2
1.3. Problem in existing system 2
1.4. Statement of Problem 3

2. System Requirement Analysis

2.1 Introduction
2.1.1 Purpose
2.1.2 Document Conventions
2.1.3 Intended Audience and Reading Suggestions
2.1.4 Product Scope
2.1.5 References of SRS

2.2 Overall Description

2.2.1 Product Perspective
2.2.2 Product Functions
2.2.3 User Classes and Characteristics
2.2.4 Operating Environment
2.2.5 Design and Implementation Constraints
2.2.6 User Documentation
2.2.7 Assumptions and Dependencies

2.3 External Interface Requirements

 2.3.1 User Interfaces
2.3.2 Hardware Interfaces
2.3.3 Software Interfaces
2.3.4 Communications Interfaces
2.4 Functional Requirement
2.4.1 System Feature 1
2.4.2 System Feature 2 (and so on)
2.5 Nonfunctional Requirements
2.5.1 Performance Requirements
2.5.2 Safety Requirements
2.5.3 Security Requirements
2.5.4 Software Quality Attributes
2.6 Project Plan
2.6.1 Team Members
2.6.2 Division of Work
2.6.3 Time Schedule
3. Analysis
3.1 Methodology Used (If Object Oriented)
3.2 Use Case Diagrams (Also include use case specifications)
3.3 Activity Diagram
3.4 Sequence Diagram
3.5 Class Diagram
3.5.1. Identified Classes
3.5.2. Identified Attributes
 3.5.3. Identified Methods
3.5.4. Identified Relationships
4. Design
4.1 Architectural Design
4.1.1. System Architecture Diagram
4.1.2. Description Of Architectural Design
4.2 Database Design
4.2.1. Data Dictionary
4.2.2. Normalization
4.3 Component Design
4.3.1. Packages, Component Diagrams and Deployment Diagram
4.4 Interface Design
4.4.1. Screenshots
5. Implementation
5.1 Language and database system used for the implementation
5.2 Features of language and database used for the project
5.3 Description of third party tools used (If any)
6. Testing (Theory of testing is not required. Only write how u have tested the system)
6.1 White Box Testing <<with Test Cases and results using Basis Path Testing Method>>
6.2 Black Box Testing <<with Test Cases and results using Interface Testing Method>>
7. Future Scope and Limitations.
8. Conclusion
9. Reference <<include references of the project in IEEE format>>
 ABSTRACT
Title: LIFE SAVER QR
Team- member: PRATIK RATHOD,PARTH GUPTA ,PRACHI SOLANKI
Description:

In emergency situations, quick access to an individual's personal and contact

information can be crucial. This project aims to develop a website that enables users
to input their basic details, including name, address, contact number, and emergency
contact number.
The website generates a QR code based on this information, which can be scanned by
first responders or concerned individuals in case of emergencies such as accidents.
The generated QR code provides immediate access to vital data, helping emergency
personnel make timely decisions. The project is developed using a simple, user-
friendly interface with technologies such as HTML, CSS, JavaScript, and a QR code
generation library.
It emphasizes ease of use and data security, ensuring the privacy of the user’s
information.
The project's primary objective is to provide a practical solution that can assist in
emergency scenarios, reducing the time taken to retrieve essential information and
potentially saving lives. Future improvements include adding medical information and
enhancing data security
 CHAPTER-1

INTRODUCTION

1. Introduction

1.1 Purpose

The primary purpose of this project is to develop a web-based application that

generates a personalized QR code containing essential personal and contact
information. This QR code can be easily scanned by emergency responders or
concerned individuals in case of accidents or other emergencies. The quick access to
vital information can significantly reduce response time and potentially save lives.

1.2 Scope

This project focuses on:

• User Interface: Designing a simple and intuitive interface for users to input
their personal details.
• QR Code Generation: Implementing a robust QR code generation algorithm
to encode the user's information.
• Data Security: Ensuring the privacy and security of user data through
appropriate measures.
• Deployment: Deploying the web application to a suitable platform for public
access.

1.3 Problem in Existing System

In traditional emergency situations, first responders often face challenges in quickly

obtaining accurate and up-to-date information about the victim. This can delay critical
medical attention and decision-making.

1.4 Statement of Problem

To address this issue, this project aims to develop a user-friendly web application that
empowers individuals to create personalized QR codes containing essential
information. By simply scanning the QR code, emergency responders can instantly
access vital details, streamlining the response process and potentially saving lives.
 CHAPTER-2

System Requirement Analysis

2. System Requirement Analysis

2.1 Introduction

This section outlines the functional and non-functional requirements of the QR code
generation system.

2.1.1 Purpose

The purpose of this document is to specify the requirements for the QR code
generation system, ensuring a clear understanding between the development team and
the stakeholders.

2.1.2 Document Conventions

• Bold: Used for keywords and important terms.

• Italics: Used for emphasis and references.
• Code: Used for code snippets and technical specifications.

2.1.3 Intended Audience and Reading Suggestions

This document is intended for:

• Development Team: To understand the system requirements and design the

application accordingly.
• Project Manager: To track progress and allocate resources.
• Stakeholders: To review the system requirements and provide feedback.

2.1.4 Product Scope

The QR code generation system will:

• Allow users to input their personal information (name, address, phone number,
emergency contact).
• Generate a unique QR code containing the user's information.
• Provide a user-friendly interface for input and QR code display.
• Ensure the security and privacy of user data.

2.1.5 References of SRS

• QR Code Standard: ISO/IEC 18004

 • HTML5 Specification
• CSS3 Specification
• JavaScript Standard
• QR Code Generation Library Documentation

2.2 Overall Description

2.2.1 Product Perspective

This project aims to develop a web-based application that allows users to input their
personal and emergency contact information. This information is then encoded into a
QR code, which can be scanned by first responders or concerned individuals in case of
emergencies.

2.2.2 Product Functions

1. User Registration: Users can create accounts and input their personal
information.
2. QR Code Generation: The system generates a unique QR code for each user,
encoding their information.
3. QR Code Display: The generated QR code is displayed on the screen and can
be downloaded.
4. Data Security: The system ensures the security of user data through
appropriate measures.

2.2.3 User Classes and Characteristics

• Primary Users: Individuals who wish to generate emergency QR codes for

themselves or their loved ones.
• Secondary Users: First responders and medical professionals who can scan the
QR code to access vital information.

2.2.4 Operating Environment

The system will be deployed on a web server and accessed through web browsers on
various devices (desktops, laptops, smartphones, and tablets).

2.2.5 Design and Implementation Constraints

• Security: Strong security measures must be implemented to protect user data.

• Accessibility: The system should be accessible to users with disabilities.
• Performance: The system should have fast response times and efficient
resource usage.
• Scalability: The system should be able to handle a growing number of users.

2.2.6 User Documentation A user manual will be provided to guide users through the
registration process, QR code generation, and how to share the QR code.
2.2.7 Assumptions and Dependencies

• Users will have access to the internet and a device capable of accessing the
website.
• The QR code scanning technology will be widely available and supported by
devices.
• The underlying infrastructure (web server, database) will be reliable and
secure.

2.3 External Interface Requirements

2.3.1 User Interfaces

• A web-based interface for user registration and QR code generation.

• A mobile-friendly interface for easy access on smartphones.

2.3.2 Hardware Interfaces

• Web servers
• Databases
• QR code scanners

2.3.3 Software Interfaces

• Web development frameworks (e.g., React, Angular)

• Database management systems (e.g., MySQL, PostgreSQL)
• QR code generation libraries

2.3.4 Communications Interfaces

• HTTP protocol for communication between the client and server.

2.4 Functional Requirements

2.4.1 User Registration

• Users can create accounts with a unique username and password.

• Users can provide personal information (name, address, phone number,
emergency contact information, medical conditions, etc.).

2.4.2 QR Code Generation

• The system generates a QR code that encodes the user's information.

• The QR code can be downloaded or shared digitally.

2.5 Nonfunctional Requirements

2.5.1 Performance Requirements

• The system should have a response time of less than 2 seconds for most
operations.
• The system should be able to handle a large number of concurrent users.

2.5.2 Safety Requirements

• The system should not pose any physical or psychological harm to users.

2.5.3 Security Requirements

• User data should be encrypted and stored securely.

• Strong authentication and authorization mechanisms should be implemented.

2.5.4 Software Quality Attributes

• Reliability: The system should be reliable and have minimal downtime.

• Usability: The system should be easy to use and intuitive.
• Maintainability: The system should be easy to maintain and update.

2.6 Project Plan

2.6.1 Team Members

PRATIK RATHOD

PARTH GUPTA

PRACHI SOLANKI

2.6.2 Division of Work

• Frontend Development: PRACHI SOLANKI

• Backend Development: PRATIK RATHOD
• Backend Development: PARTH GUPTA
3. Analysis

3.1 Methodology Used (If Object Oriented)

For this project, we'll employ an object-oriented approach. This paradigm allows us to model
the real-world entities (users, QR codes, etc.) as objects with their attributes and behaviors.

3.2 Use Case Diagrams

• Use Case: Generate QR Code

o Basic Flow:
1. User logs in or registers.
2. User enters personal information.
3. System generates a unique QR code.
4. System displays the QR code.
o Alternate Flow:
1. If user information is invalid, the system prompts the user to correct
the input.
• Use Case: Scan QR Code
o Basic Flow:
1. Scanner scans the QR code.
2. System decodes the QR code and retrieves user information.
3. System displays the user's information.

3.3 Activity Diagram

[Insert an activity diagram visualizing the flow of activities involved in generating and
scanning QR codes]

3.4 Sequence Diagram

[Insert a sequence diagram illustrating the interactions between actors (user, system) and the
objects involved in the process]

3.5 Class Diagram

3.5.1 Identified Classes

• User
• QRCode
• Database

3.5.2 Identified Attributes

• User: userID, name, address, phone number, emergency contact, medical conditions
• QRCode: QRCodeID, userID, QRCodeData
• Database: databaseName, connectionString

3.5.3 Identified Methods

 • User: register, login, updateInfo
• QRCode: generateQRCode, scanQRCode
• Database: connect, insert, update, delete, retrieve

3.5.4 Identified Relationships

• A User has many QRCodes.

• A QRCode belongs to one User.
• The system interacts with the Database.

4. Design

4.1 Architectural Design

4.1.1 System Architecture Diagram

[Insert a system architecture diagram showing the components (frontend, backend, database)
and their interactions]

4.1.2 Description of Architectural Design The system will follow a three-tier architecture:

• Presentation Layer: Handles user interaction (web interface).

• Business Logic Layer: Implements the core business logic (QR code generation, data
storage).
• Data Access Layer: Interacts with the database.

4.2 Database Design [Insert an ER diagram or a detailed database schema]

4.3 Component Design

4.3.1 Packages, Component Diagrams, and Deployment Diagram [Insert component

diagrams and deployment diagrams showing the components and their dependencies]

4.4 Interface Design [Insert screenshots of the user interface]

5. Implementation

5.1 Language and Database System Used

• Frontend: HTML, CSS, JavaScript

• Backend: Python (with frameworks like Django or Flask)
• Database: MySQL or PostgreSQL

5.2 Features of Language and Database [Describe the specific features of the chosen
technologies]

5.3 Description of Third-Party Tools [List any third-party tools used, such as QR code
generation libraries or testing frameworks]

6. Testing
 • Unit Testing: Test individual components (e.g., QR code generation, database
operations).
• Integration Testing: Test the interaction between components.
• System Testing: Test the entire system as a whole.
• User Acceptance Testing: Test the system with real users to ensure it meets their
needs.

7. Future Scope and Limitations

• Future Scope:
o Add features like biometric authentication, location tracking, and emergency
alerts.
o Integrate with wearable devices.
o Explore blockchain technology for enhanced security.
• Limitations:
o Relies on internet connectivity for QR code scanning and data retrieval.
o QR code may be damaged or obscured, affecting readability.
o Data privacy concerns need to be addressed.

8. Conclusion

This project aims to provide a practical solution for emergency situations by leveraging QR
code technology. By following the proposed design and implementation steps, we can
develop a robust and user-friendly system that can potentially save lives.

9. References [List of references used]