A Project Report on

“Beyond Books Rental”

By
Diya Soni
Krishi Gandhi
Kashish Patel

ENROLLMEN NO. : 194510307059

ENROLLMEN NO. : 194510307015
ENROLLMEN NO. : 194510307036

Semester : V
Diploma Engineering (Computer Engineering)
Guided By:

Lecturer,
SAL Institute of Diploma Studies

A Project Report Submitted to

Gujrat Technological University in fulfilment of the Requirements for The Degree
of Diploma Engineering in Information Technology

October:2021

SAL EDUCATION
SAL Institute Of Diploma Studies
Opp. Science City, Sola Ahmedabad, Gujarat: 380060
 CERTIFICATE

THIS IS TO CERTIFY THAT PROJECT WORK EMBODIED IN THIS PROJECT

REPORT TITLED “BEYOND BOOK RENTAL” WAS CARRIED OUT BY DIYA SONI,
ENROLLMENT NO. 194510307059 AT SAL INSTITUTE OF DIPLOMA STUDIES (451)
FOR FULLFILLMENT OF DIPLOMA ENGINEERING DEGREE IN COMPUTER
ENGINEERING TO BE AWARDED BY GUJARAT TECHNOLOGICAL UNIVERSITY.
THIS PROJECT WORK HAS BEEN CARRIED OUT UNDER MY GUIDANCE AND
SUPERVISION AND IT IS UP TO MY SATISFACTION.

DATE: SIGNATURE AND NAME OF H.O.D.,

HEAD OF DEPARTMENT (C.E.),

DIPLOMA ENGINEERING
DEPARTMENT,
SIDS (451), AHMEDABAD.
PLACE: SIDS, AHMEDABAD.

SIGNATURE AND NAME OF GUIDE

LECTURER,
COMPUTER ENGINEERING DEPARTMENT,
SIDS (451), AHMEDABAD.

SIGNATURE AND NAME OF PRINCIPAL

DR. MONIKA SWAMI,
SIDS (451), AHMEDABAD.

Page | ii
 CERTIFICATE

THIS IS TO CERTIFY THAT PROJECT WORK EMBODIED IN THIS PROJECT

REPORT TITLED “BEYOND BOOK RENTAL” WAS CARRIED OUT BY KRISHI
GANDHI, ENROLLMENT NO. 194510307015 AT SAL INSTITUTE OF DIPLOMA
STUDIES (451) FOR FULLFILLMENT OF DIPLOMA ENGINEERING DEGREE IN
COMPUTER ENGINEERING TO BE AWARDED BY GUJARAT TECHNOLOGICAL
UNIVERSITY. THIS PROJECT WORK HAS BEEN CARRIED OUT UNDER MY
GUIDANCE AND SUPERVISION AND IT IS UP TO MY SATISFACTION.

DATE: SIGNATURE AND NAME OF H.O.D.,

HEAD OF DEPARTMENT (C.E.),

DIPLOMA ENGINEERING
DEPARTMENT,
SIDS (451), AHMEDABAD.
PLACE: SIDS, AHMEDABAD.

SIGNATURE AND NAME OF GUIDE

DRUSHTI BHAVSAR

LECTURER,
COMPUTER ENGINEERING DEPARTMENT,
SIDS (451), AHMEDABAD.

.SIGNATURE AND NAME OF PRINCIPAL

DR. MONIKA SWAMI,
SIDS (451), AHMEDABAD.

Page | iii
 CERTIFICATE

THIS IS TO CERTIFY THAT PROJECT WORK EMBODIED IN THIS PROJECT

REPORT TITLED “BEYOND BOOK RENTAL” WAS CARRIED OUT BY KASHISH
PATE, ENROLLMENT NO. 194510307036 AT SAL INSTITUTE OF DIPLOMA
STUDIES (451) FOR FULLFILLMENT OF DIPLOMA ENGINEERING DEGREE IN
COMPUTER ENGINEERING TO BE AWARDED BY GUJARAT TECHNOLOGICAL
UNIVERSITY. THIS PROJECT WORK HAS BEEN CARRIED OUT UNDER MY
GUIDANCE AND SUPERVISION AND IT IS UP TO MY SATISFACTION.

DATE: SIGNATURE AND NAME OF H.O.D.,

HEAD OF DEPARTMENT (C.E.),

DIPLOMA ENGINEERING
DEPARTMENT,
SIDS (451), AHMEDABAD.
PLACE: SIDS, AHMEDABAD.

SIGNATURE AND NAME OF GUIDE

LECTURER,
COMPUTER ENGINEERING DEPARTMENT,
SIDS (451), AHMEDABAD.

.
SIGNATURE AND NAME OF PRINCIPAL
DR. MONIKA SWAMI,
SIDS (451), AHMEDABAD.

Page | iv
 ACKNOWLEDGEMENT

We are grateful to give us this opportunity and groom ourselves from this project.
the completion of this undertaking could not possible without people who may put
their all efforts in this which is absolutely commendable their contribution is
sincerely appreciated and gratefully acknowledged. However, the group would like
to express their deep appreciation and indebtedness particularly to the following:
our guide MS Drashti Bhavsar and SAL institute of diploma studies.
we are overwhelmed and grateful to acknowledge our depth to all those who have
helped me to put these idea, well above the level of simplicity and intro something
concrete.

Your Sincerely,
Diya Soni ( 194510307059)
Krishi Gandhi (1945103070)
Kashish Patel (194510307036)

ABSTRACT

Page | v
 (“Beyond Book Rental”)

The project entitles "Beyond Book Rental" is a very effective, feasible online
portal which facilities the readers to read the books, magazines, journals on a very,
much reliable rent. If a reader wants to read a book he/she has to purchase the
book, where he/she has to give much money or he/she can go to library to lend a
book where firstly he/she has to be a member and he/she has to follow the library
rules and regulations like he has to return the book at specified date. So, lot of time
and money gets wasted in these. But with our portal situation becomes very easy.
The person which is having the book can give the book on rent for some days at a
reasonable rent and can gain money and on the contrary those who want to rent a
book can communicate with the book giver through our portal.

Page | vi
 Chapter:1
INTRODUCTION

Page | 1
1.1 Introduction to System
1.1.1 Definition
The project is to search and rent a book based on title and author. ... The selected books are
displayed in a tabular format and the user can order their books online through cash on delivery
and online payment.
1.1.2 Functionalities
 Login / sign up
 OTP verification
 Track of ordered book
 Online payment methods
 Rewards

1.1.3 Benefits
 Convenient for users
 No need to keep stuff in house
 Ordered book will come on doorstep
1.1.4 Tools -if applicable
 Figma Tool
 Android Studio,
 Firebase,
 Map Integration

1.1.5 Applications (Uses)

1.1.6 Scope
Users of this portal first of all will register their details. They will see the list which they want
take on rent. if user want to give book on rent they can upload the book details like Book title,
author name etc. if user want to take book on rent and in case it is not available then they can
generate a request for their demanded book and their request will be displayed on the home page
of the portal.

1.1.7 Characteristics
Book rental system help you to manage your book rental business with great ease.

User: If a user want to give a book on rent he/she give it on rent and he/she want to take book
on rent they can take. The user who want to give book on rent he/she must be give information of
books which they want to give on rent.

1.2 Purpose of Project

 The Purpose of this application is that

Page | 2
  Defining and describing the functions and specifications of the Book Rental System is the
primary goal of this Software Requirements Specification.
1.1.2 Future trends
 In future if the application get success and if there is grow in users then we can increase
the reward to the users who is taking more and more books on rent.

1.3 Function Requirements

Functional Requirement After analysing the problem domain and concluding the solution,
the function requirements that will satisfy the need are following:

 The system should provide a registration page for users.

 User and admin must be verified using login module.
 System should provide a search book mechanism.
 The system should provide complete details of books along with cover page.
 The customer should be able to rent book.
 Rent should be calculated on the basis of period of rent and market price of book.
 Order id and user id must be given to customer by system.
 Customer should be able to return book.
 Admin should be able to add, update and delete books. Admin should be able to view the
registered users and remove them if required.
 System should provide a way to add books to cart.
 System should display total rent of books.
 System should provide mechanism to logout.

1.4 Problems in existing system

used for describing something that exists now, especially when it might be changed or replaced.
The existing system needs to be changed.

Page | 3
 CHAPTER:2
SYSTEM REQUIREMENTS

Page | 4
2.1 Hardware & Software Requirements
 Hardware Requirements:
 Mobile Phone
 API Level above 30
 RAM: 3GB minimum
 Camera 16MPx
 Software Requirements:
 Android Studio
 Figma
2.1.1 Server-Side Requirements
 Windows 7
 Windows 8 or 8.1
 Windows 10
 Internet explorer
2.1.2 Developer Side Requirements
 Windows requirements
 Microsoft Windows 7/8/10 (32-bit and Above).
 3 GB RAM minimum.
 2 GB of available disk space minimum, 4 GB recommended
 Stable internet is required
 Android Studios is required.
 Figma is required.

2.1.3 User Side Requirements

 Smart mobile phone is required
 internet is required
 Mobile number is required for verification
 User want to give book on rent information of the book is required.

Page | 5
 CHAPTER 3
SYSTEM ANALYSIS AND
DESIGN

Page | 6
3.1 System Analysis and Design
Systems Analysis and Design (SAD) is a broad term for describing methodologies for
developing high quality Information System which combines Information Technology, people
and Data to support business requirement.

3.2 System Development Life Cycle (SDLC)

Software Development Life Cycle (SDLC) is a process used by the software industry to design,
develop and test high quality software.
 Identification
Identification is a process used by the software industry to design, develop and test high
quality software. The SDLC aims to produce a high-quality software that meets or exceeds
customer expectations, reaches completion within times and cost estimates.
System Development Life Cycle (SDLC) is a conceptual model which includes policies and
procedures for developing or altering systems throughout their life cycles. The Design phase
starts with the conceptual design in the baseline spiral and involves architectural design,
logical design of modules, physical product design and the final design in the subsequent
spirals.
 Construct or Build
The Construct phase refers to production of the actual software product at every spiral. In the
baseline spiral, when the product is just thought of and the design is being developed a POC
(Proof of Concept) is developed in this phase to get customer feedback.
Then in the subsequent spirals with higher clarity on requirements and design details a
working model of the software called build is produced with a version number. These builds
are sent to the customer for feedback.
3.2.1 Needs of SDLC
 It is important to have an SDLC in place as it helps to transform the idea of a project into a
functional and completely operational structure. In addition to covering the technical aspects
of system development, SDLC helps with process development, change management, user
experience, and policies.
 SDLC sets the series of stages to follow that not only complete the development properly but
also consume less time in the development process. It provides a quality software solution
within specified time and expense. Use of System Requirement Specification (SRS)
document as a guideline of the project leads to client satisfaction.
 The next phase that the systems analyst undertakes involves analysing system needs. Again,
special tools and techniques help the analyst make requirement determination.
3.2.2 SDLC Cycle
 Software Development Life Cycle (SDLC) is a process used by the software industry to
design, develop and test high quality software. The SDLC aims to produce a high-quality
software that meets or exceeds customer expectations, reaches completion within times and
cost estimates.

Page | 7
 SDLC is the acronym of Software Development Life Cycle.
 It is also called as Software Development Process.
 SDLC is a framework defining tasks performed at each step in the software development
process.
 ISO/IEC 12207 is an international standard for software life-cycle processes. It aims to be
the standard that defines all the tasks required for developing and maintaining software.

Fig.3.2.2: SDLC Cycle

3.3 Spiral Model

 It was originally proposed by Berry Bohen, the spiral model is an evolutionary software
process model that couples the iterative nature of prototyping with the controlled and
systematic aspects of the waterfall model.

Fig3.2: Spiral Model

Page | 8
 It provides the potential for rapid development of increasingly more complete versions of the
software.
 The spiral development model is a risk-driven process model generator that is used to guide
multi-stakeholder concurrent engineering of software intensive systems.
 The spiral model has four phases. A software project repeatedly passes through these phases
in iterations called Spirals.

3.4 Feasibility Study

Feasibility is the measure of how gainful the advancement of data framework will be to an
association. The feasibility analysis is categorized under four different types.
1. Operational Feasibility
2. Technical Feasibility
3. Schedule Feasibility
4. Economic Feasibility
Operational Feasibility
 The operational feasibility is based on the human factors and political aspects
 Factors describing the society
 High cost of books
 Books not required for larger period of time
 More Books, more paper more deterioration of forest
 Change brought by system V Reuse of books by leading to saving environment
 Renting books for required period Low rent cost
 Website development and designing skills are required
Technical Feasibility
 This conceded with the specifying equipment and software that will successfully satisfy
the requirements. the proposed system is technically feasible as it can be developed easily
with the help of available technology these may be different technical needs but on
broader aspect it will include the following: Better GUI on platforms such as windows 7
and above
 Producing outputs in less time
 User friendly website not much technical knowledge required

Schedule Feasibility
 Schedule feasibility corresponds to whether sufficient time is available to complete the
project.
 Factor considered:
 Schedule of the project
 Time by which project has to be completed
 Reporting period

Economic feasibility
 This kind of feasibility study is done for cost or benefit analysis. In this study the benefit
of proposed system are identified and the corresponding costs are determined. in this

Page | 9
website the books are provided at rent so multiple books can be rented by a user. This
will prove beneficial for user as well as owner as:
 User need not buy book
 Same book can be rented many times generating profit for owner
 Specifying particulars
 75% of money will be given back if book rented for one month
 60% of money will be given back if book rented for Three month
 50% of money will be given back if book rented for Six month

Page | 10
 CHAPTER 4
FRONT END OF SYSTEM

Page | 11
 CHAPTER:5
BACK END OF SYSTEM

Page | 12
5.1 About MySQL
 MySQL creates a database for storing and manipulating data, defining the relationship of
each table.
 Clients can make requests by typing specific SQL statements on MySQL.
 The server application will respond with the requested information and it will appear on
the clients’ side.
5.1.1 How MySQL Works
 MySQL creates a database for storing and manipulating data, defining the relationship of
each table.
 When any query reaches SQL Server, the first place it goes to is the relational engine.
 MySQL Workbench gives you a statistical view of the server performance.

5.1.2 MySQL Features

 Can contain SQL Procedural Language statements and features which support the
implementation of control-flow logic around traditional static and dynamic SQL statements.
 Are easy to implement, because they use a simple high-level, strongly typed language.
 SQL functions are more reliable than equivalent external functions.
 Support input parameters.
 SQL scalar functions return a scalar value.
 SQL table functions return a table result set.
 Support a simple, but powerful condition and error-handling model.
 Allow you to easily access the SQLSTATE and SQLCODE values as special variables.
 Reside in the database and are automatically backed up and restored as part of backup and
restore operations.
 Can be invoked wherever expressions in an SQL statement are supported.
 Support nested functions calls to other SQL functions or functions implemented in other
languages.
 Support recursion (when dynamic SQL is used in compiled functions).
 Can be invoked from triggers.
 Many SQL statements can be included within SQL functions, however there are exceptions.
For the complete list of SQL statements that can included and executed in SQL functions,
5.1.3 Why use MySQL
 Security: Whenever a database is created, the very next step is to identify and formulate a
security policy before giving access to the database users.

Page | 13
 CHAPTER 6
SYSTEM DESIGN

Page | 14
 CHAPTER 7
DATA DICTONARY

Page | 15
7.1 Introduction
Data dictionaries store and communicate metadata about data in a database, a system, or data
used by applications. A useful introduction to data dictionaries is provided in this video. Data
dictionary contents can vary but typically include some or all of the following:

 A listing of data objects (names and definitions)

 Detailed properties of data elements (data type, size, nullability, optionality, indexes)
 Entity-relationship (ER) and other system-level diagrams
 Reference data (classification and descriptive domains)
 Missing data and quality-indicator codes
 Business rules, such as for validation of a schema or data quality

7.2 List of Table

Table 1: table_cart
Column Data Type Null Constrain Key Constrain
Cart_id int(11) No Primary Key
userId varchar(255) No Foreign Key
productId varchar(255) No Foreign Key
qty varchar(255) No
orderId varchar(255) No 0
created_date timestamp No CURRENT_TIMESTAMP
Table 2: table category
Column Data Type Null Constrain Key Constrain
Category_id int(11) No Primary Key
name varchar(255) No
image varchar(255) No
created_date timestamp No CURRENT_TIMESTAMP
Table 3: table product
Column Data Type Null Constrain Key Constrain
Product_id int(11) No Primary Key
categoryId varchar(255) No Foreign Key
subCategoryId varchar(255) No Foreign Key
name varchar(255) No
image varchar(255) No
price varchar(255) No
qty varchar(255) No
description longtext No
created_date timestamp No CURRENT_TIMESTAMP
Table 4: table shipping

Page | 16
 Column Data Type Null Constrain Key Constrain
Shipping_id int(11) No Primary Key
userId varchar(255) No Foreign Key
name varchar(255) No
contact varchar(255) No
address longtext No
city varchar(255) No
state varchar(255) No
pincode varchar(255) No
orderId varchar(255) No Foreign Key
created_date timestamp No CURRENT_TIMESTAMP
Table 5: sub_category
Column Data Type Null Constrain Key Constrain
Sub_category_id int(11) No Primary Key
categoryId varchar(255) No
name varchar(255) No
image varchar(255) No
created_date timestamp No CURRENT_TIMESTAMP
Table 6: tbl_order
Column Data Type Null Constrain Key Constrain
Order_id int(11) No Primary Key
userId varchar(255) No Foreign Key
shippingId varchar(255) No Foreign Key
status varchar(255) No
created_date timestamp No CURRENT_TIMESTAMP
Table 7: user
Column Data Type Null Constrain Key Constrain
User_id int(11) No Primary Key
name varchar(255) No
email varchar(100) No
contact bigint(10) No
password varchar(20) No
created_date timestamp No CURRENT_TIMESTAMP
Table 8: wishlist
Column Data Type Null Constrain Key Constrain
Whishlist_id int(11) No Primary Key
userId varchar(255) No Foreign Key
productId varchar(255) No Foreign Key

Page | 17
created_date timestamp No CURRENT_TIMESTAMP
Table 9: change_password
Column Data Type Null Constrain Key Constrain
userId int(11) No Foreign Key
oldPassword varchar(20) No
newPassword varchar(20) No
Table 10: forgotpassword
Column Data Type Null Constrain Key Constrain
userId int(11) No Foreign Key
email_contact varchar(100) No
newPassword varchar(20) No
Table 11: login
Column Data Type Null Constrain Key Constrain
userId int(11) No Foreign Key
email_contact varchar(100) No
password varchar(20) No
Table 12: profile
Column Data Type Null Constrain Key Constrain
userId int(11) No Foreign Key
name varchar(100) No
contactNo varchar(10) No
email varchar(100) No
password varchar(20) No
Table 13: updateprofile
Column Data Type Null Constrain Key Constrain
userId int(11) No Foreign Key
name varchar(255) No
contactNo varchar(10) No
email varchar(100) No
password varchar(20) No

Page | 18