1.

INTRODUCTION

1.1 Project Description

This project is designed so as to be used by BICYCLE Rental Company specializing in renting

BICYCLEs to customers. It is an online system through which customers can view available
cycle, register, view profile and book cycle.
1.2 Objective

The advancement in Information Technology and internet penetration has greatly

enhanced various business processes and communication between companies services
provider and their customers of which bicycle rental industry is not left out. This E-BICYCLE
Rental system is developed to provide the following services

• Enhance Business Processes To be able to use internet technology to project the rental
company to the global world instead of limiting their services to their local domain alone,
thus increase their return on investment
2. SYSTEM ANALYSIS

2.1 Existing System & Proposed System

2.1 Existing System

BICYCLE Rental System service will help users to book a cycle for some fee specified. Till
now there was no clear web based UI to help the users to rent the vehicle. They had to
manually rent the vehicle through their offices. It was a difficult task to manage rental
vehicles. Keeping track of all the rental cycle was a problem.

2.1 Proposed System

This BICYCLE Rental System project will enable the user to rent a vehicle. The user shall
login to the system and check for availability of cycle. The user specifies a type of cycle
and the journey date and time. The BICYCLE Rental System shall check for the availability of
the cycle and rent the cycle to the customer. The user can make payment online. The tool is
designed using PHP. All the data regarding the rental bicycle are stored in MySQL
database. The user has to enter his name, address, phone details and check for the c y c l e
available for rent. The UI is very simple and the connectivity to back end is robust. The
main advantage is that the user shall be able to choose a cycle depending on his budget.

2.2 Feasibility Study

Preliminary investigation examine project feasibility, the likelihood the system will be
useful to the organization. The main objective of the feasibility study is to test the
Technical, Operational and Economical feasibility for adding new modules and
debugging old running system. All system is feasible if they are unlimited resources and
infinite time. The objective of a feasibility study is to find out if an information system
project can be done and to suggest possible alternative solutions.
There are aspects in the feasibility study portion of the preliminary investigation:

• Technical Feasibility

• Operational Feasibility

• Economical Feasibility

2.2.1 Technical

It refers to whether the software that is available in the market fully supports the
present application. It studies the pros and cons of using particular software for the
development and its feasibility. It also studies the additional training needed to be given
to the people to make the application work. The technical requirements are then compared
to the technical capability of the organization. The systems project is considered
technically feasible if the internal technical capability is sufficient to support the project
requirements. The analyst must find out whether current technical resources can be
upgraded or added to in a manner that fulfils the request under consideration.
2.2.2 Operational

It refers to the feasibility of the product to be operational. Some products may

work very well at design and implementation but may fail in the real time environment. It
includes the study of additional human resource required and their Technical expertise. It
dependent on human resources available for the project and involves projecting whether
the system will be used if it is developed and implemented. It measure of how well a
proposed system solves the problems, and takes advantage of the opportunities identified
during scope definition and how it satisfies the requirements identified in the analysis
phase of system development. It reviews the willingness of the organization to support the
proposed system.
2.2.3 Economical

It refers to the benefits or outcomes we are deriving from the product as compared to the
total cost we are spending for developing the project. It the more or less same as the older
system, then it is not feasible to develop the product. Economic analysis could also be
referred to as cost/benefit analysis. It is the most frequently used method for evaluating
the effectiveness of a new system. In economic analysis the procedure is to determine the
benefits and savings that are expected from a candidate system and compare them with
costs. If benefits outweigh costs, then the decision is made to design and implement the
system. An entrepreneur must accurately weigh the cost versus benefits before taking an
action.
2.3 TOOLS AND TECHNOLOGIES USED

A graphical user interface (GUI) is an interface for the user to communicate with a
computer application using graphical symbols rather than typing the instructions in.
The GUI of the proposed BICYCLE Rental system will be developed using
HTML5, CSS and PHP (PHP Hypertext Processor).

Hypertext Markup Language (HTML) is the standard markup language for creating
web pages and web applications. HTML elements are the building blocks of HTML
pages. With HTML constructs, images and other objects, such as interactive forms,
may be embedded into the rendered page. It provides a means to create structured
documents by denoting structural semantics for text such as headings, paragraphs,
lists, links, quotes and other items. HTML elements are delineated by tags,written
using angle brackets. The BICYCLE Rental system uses HTML as the building
blocks for creating UI elements.

Cascading Style Sheets (CSS) is a style sheet language used for describing the
presentation of a document written in a markup language. CSS is used to format the
pages to make it appealing to the user. CSS is designed primarily to enable the
separation of presentation and content, including aspects such as the layout, colours
and fonts. The BICYCLE Rental system application uses Bootstrap 4.1 a boilerplate
designed with CSS to reduce development times on the GUI design.

PHP (PHP Hypertext Processor) is a server-side scripting language used to

dynamically create webpages. PHP code may be embedded into HTML code, or it
can be used in combination with various web template systems, web content
management systems, and web frameworks. PHP code is usually processed by a
PHP interpreter implemented as a module in the web server or as a Common
Gateway Interface (CGI) executable. The web server combines the results of the
interpreted and executed PHP code, which may be any type of data, including
images, with the generated web page. PHP code may also be executed with a
command-line interface (CLI) and can be used to implement standalone graphical
applications. The BICYCLE Rental system uses PHP for interacting with the
database using MySQL and to display dynamic content on the webpage based on the
users queries.
2.4 HARDWARE AND SOFTWARE REQUIREMENTS

2.4.1 Hardware Requirements

➢ Processor : Pentium Duel Core or above

➢ RAM : 4GB
➢ Hard Disk : 100 GB hard disk or above
➢ Monitor : 15 inch Color Monitor
➢ Keyboard : 102/104 Keys
➢ Mouse : Optical Mouse

2.4.2Software Requirements

➢ Operating System :Windows 7/8/10 or Linux distribution

➢ Browser :Chrome or Firefox or any browser
➢ Front-end :HTML/CSS/PHP
➢ Backend :PHP
3. SOFTWARE REQUIREMENTS SPECIFICATION

3.1 FUNCTIONAL REQUIREMENTS

• Usability: The interface should use terms and concepts, which are drawn
from the experience of the people who will make most of the system.
• Efficiency: The system must provide easy and fast access without
consuming more cost
• Reliability: User should never be surprised by the behaviour of the system
and it's easy to use to stored data and easy to used transfer voice data (only
way files)

3.2 NON – FUNCTIONAL REQUIREMENTS

It describes aspects of the system that are concerned with how the system provides the
functional requirements. They are:

• Security: The subsystem should provide a high level of security and integrity of
the data held by the system, only authorized persons of the company can gain
access to the company’s.

• Performance and Response time: The system should have high performance rate
when executing user’s input and should be able to provide feedback or response
within a short time span usually 50 seconds for highly complicated task and 20 to
25 seconds for less complicated task.

• Error handling: Error should be considerably minimized and an appropriate error

message that guides the user to recover from an error should be provided.
Validation of user’s input is highly essential.

• Availability: This system should always be available for access at 24 hours,7days

a week. Also in the occurrence of any major system malfunctioning, the system
should be available in 1 to 2 working days.
4. SYSTEM DESIGN

System designs the process of defining the architecture, modules, interfaces and data for a
system to satisfy specific requirements. System design could be seen as the application of
system theory to product development. There is some overlap with the disciplines of
systems analysis, systems architecture and systems engineering.

4.1 Module Description

BICYCLE:

This is one of the most important modules. This module helps the customers to take any
Cycle on rent from any cycle seller. The status of cycle can be updated as soon as it gets
free or it gets booked so that no other customer tries to book the same cycle. The
informationthat is added to a cycle is its model no, vehicle no, and owner name.

Login:

After registration, one can log in to the system either as the event manager or the
customer. The option to register either an employee or customer is given when the user is
registering. The interface of this system depends upon the registration. If the user has
registered as an employee, then it will have options like arranging all the things as asked
by a customer for an event.

For the customer, the interface includes the option to check all the available event
managers and can select anyone for this event.

Admin:

This module is present only for one account. That is, no one can register as an admin after
one account is created. The admin account has all the privileges, to check about any
particular bicycle seller or customer. To block any account, to calculate the salary of the
employees after deducting their leaves, to update the status about any event, to calculate
the payment, to make changes into accounts of users, etc.
User:

As explained in the login section, the user can be of two types and both the users will
have different interfaces and after the user has registered and login then the features
provided can be used by the user. A user who has registered as the seller can update about
the BICYCLEs that are free card can be given on rent. If the user is a customer, then he can
see all the available bicycle that he can take on rent.

About us:

WE ARE THE BICYCLE RENTAL. The only 100% dedicated cycle rental booking
website. The first BICYCLE Rental shop was our own c y c l e shop. Ever Since it has been
our aim to make bicycle rental easier for everyone, everywhere.We focus on making cycle
rentals easier for you.Your rental business has a unique set of challenges.
4.2. CONTEXT DIAGRAM

Data flow diagram is graphical representation of flow of data in an information

system. It is capable of depicting incoming data flow, outgoing data flow and stored
data. The DFD does not mention anything about how data flows through the system.

There is a prominent difference between DFD and Flowchart. The flowchart

depicts flow of control in program modules. DFDs depict flow of data in the system at
various levels. DFD does not contain any control or branch elements.

Types of DFD

Data Flow Diagrams are either Logical or Physical.

• Logical DFD - This type of DFD concentrates on the system process and flow of
data in the system. For example in a Banking software system, how data is moved
between different entities.

• Physical DFD - This type of DFD shows how the data flow is actually
implemented in the system. It is more specific and close to the implementation.

DFD Components

DFD can represent Source, destination, storage and flow of data using the following set
of components -

• Entities - Entities are source and destination of information data. Entities are
represented by rectangles with their respective names.

• Process - Activities and action taken on the data are represented by Circle or
Round-edged rectangles.

• Data Storage - There are two variants of data storage - it can either be represented
as a rectangle with absence of both smaller sides or as an open-sided rectangle
with only one side missing.

2 0
 • Data Flow - Movement of data is shown by pointed arrows. Data movement is
shown from the base of arrow as its source towards head of the arrow as
destination.

Levels of DFD

• Level 0 - Highest abstraction level DFD is known as Level 0 DFD, which depicts
the entire information system as one diagram concealing all the underlying details.
Level 0 DFDs are also known as context level DFDs

Fig: level 0
 Fig: level 01 DFD

• Level 1 - The Level 0 DFD is broken down into more specific, Level 1 DFD.
Level 1 DFD depicts basic modules in the system and flow of data among various
modules. Level 1 DFD also mentions basic processes and sources of information.

Change
5. DETAILED DESIGN

5.1 Class Diagram

Class diagram is a static diagram. It represents the static view of an application.

Class diagram is not only used for visualizing, describing, and documenting different
aspects of a system but also for constructing executable code of the software application.

Class diagram describes the attributes and operations of a class and also the
constraints imposed on the system. The class diagrams are widely used in the modelling
of object oriented systems because they are the only UML diagrams, which can be
mapped directly with object-oriented languages.

Class diagram shows a collection of classes, interfaces, associations, collaborations, and

constraints. It is also known as a structural diagram.

Purpose of Class Diagrams

The purpose of class diagram is to model the static view of an application. Class
diagrams are the only diagrams which can be directly mapped with object-oriented
languages and thus widely used at the time of construction.UML diagrams like activity
diagram; sequence diagram can only give the sequence flow of the application; however
class diagram is a bit different. It is the most popular UML diagram in the coder
community.

The purpose of the class diagram can be summarized as −

• Analysis and design of the static view of an application.

• Describe responsibilities of a system.

• Base for component and deployment diagrams.

2 0
 How to Draw a Class Diagram?

Class diagrams are the most popular UML diagrams used for construction of
software applications. It is very important to learn the drawing procedure of class
diagram.Class diagrams have a lot of properties to consider while drawing but here the
diagram will be considered from a top level view.

Class diagram is basically a graphical representation of the static view of the

system and represents different aspects of the application. A collection of class diagrams
represent the whole system.
The following points should be remembered while drawing a class diagram −

• The name of the class diagram should be meaningful to describe the aspect of the
system.

• Each element and their relationships should be identified in advance.

• Responsibility (attributes and methods) of each class should be clearly identified

• For each class, minimum number of properties should be specified, as

unnecessary properties will make the diagram complicated.

• Use notes whenever required to describe some aspect of the diagram. At the end
of the drawing it should be understandable to the developer/coder.

• Finally, before making the final version, the diagram should be drawn on plain
paper and reworked as many times as possible to make it correct.

The following diagram is an example of an Order System of an application. It describes

a particular aspect of the entire application.

• First of all, Order and Customer are identified as the two elements of the system.
They have a one-to-many relationship because a customer can have multiple
orders.

• Order class is an abstract class and it has two concrete classes (inheritance
relationship) Special Order and Normal Order.

• The two inherited classes have all the properties as the Order class. In addition,
they have additional functions like dispatch () and receive ().

2 0
 Where to Use Class Diagrams?

Class diagram is a static diagram and it is used to model the static view of a
system. The static view describes the vocabulary of the system.

Class diagram is also considered as the foundation for component and

deployment diagrams. Class diagrams are not only used to visualize the static view of
the system but they are also used to construct the executable code for forward and
reverse engineering of any system.
Generally, UML diagrams are not directly mapped with any object-oriented programming languages but the class
diagram is an exception.
Class diagram clearly shows the mapping with object-oriented languages such as
Java, C++, etc. From practical experience, class diagram is generally used for
construction purpose.

In a nutshell it can be said, class diagrams are used for −

• Describing the static view of the system.

• Showing the collaboration among the elements of the static view.

• Describing the functionalities performed by the system.

2 0
 5.2 Use Case Diagram

To model a system, the most important aspect is to capture the dynamic

behaviour. Dynamic behaviour means the behaviour of the system when it is
running/operating.

Only static behaviour is not sufficient to model a system rather dynamic

behaviour is more important than static behaviour. In UML, there are five diagrams
available to model the dynamic nature and use case diagram is one of them.

Now as we have to discuss that the use case diagram is dynamic in nature, there
should be some internal or external factors for making the interaction.

These internal and external agents are known as actors. Use case diagrams consist
of actors, use cases and their relationships. The diagram is used to model the
system/subsystem of an application. A single use case diagram captures a particular
functionality of a system. Hence to model the entire system, a number of use case
diagrams are used.
Purpose of Use Case Diagrams

The purpose of use case diagram is to capture the dynamic aspect of a system.
However, this definition is too generic to describe the purpose, as other four diagrams
(activity, sequence, collaboration, and State chart) also have the same purpose. We will look into some specific
purpose, which will distinguish it from other four diagrams. when a system is analysed to gather its
functionalities, use cases are prepared and actors are identified. When the initial task is complete, use case
diagrams are modelled to present the outside view.

In brief, the purposes of use case diagrams can be said to be as follows –

• Used to gather the requirements of a system.

• Used to get an outside view of a system.

• Identify the external and internal factors influencing the system.

• Show the interaction among the requirements is actors.

2 0
 How to Draw a Use Case Diagram?

Use case diagrams are considered for high level requirement analysis of a system.
When the requirements of a system are analysed, the functionalities are captured in use
cases.

We can say that use cases are nothing but the system functionalities written in an
organized manner. The second thing which is relevant to use cases is the actors. Actors
can be defined as something that interacts with the system.

• Functionalities to be represented as use case

• Relationships among the use cases and actors.

Use case diagrams are drawn to capture the functional requirements of a system. After
identifying the above items, we have to use the following guidelines to draw an efficient
use case diagram

• The name of a use case is very important. The name should be chosen in such a
way so that it can identify the functionalities performed.

• Give a suitable name for actors.

• Show relationships and dependencies clearly in the diagram.

Do not try to include all types of relationships, as the main purpose of thediagram is to identify the
requirements.
• Use notes whenever required to clarify some important points.

Following is a sample use case diagram representing the order management system.
Hence, if we look into the diagram then we will find three use cases (Order, Special
Order, and Normal Order) and one actor which is the customer.

The Special Order and Normal Order use cases are extended from Order use case.
Hence, they have extended relationship. Another important point is to identify the
system boundary, which is shown in the picture. The actor Customer lies outside the
system as it is an external user of the system.

2 0
 Where to Use a Use Case Diagram?

As we have already discussed there are five diagrams in UML to model the
dynamic view of a system. Now each and every model has some specific purpose to use.
Actually these specific purposes are different angles of a running system.

To understand the dynamics of a system, we need to use different types of

diagrams. Use case diagram is one of them and its specific purpose is to gather system
requirements and actors.

Use case diagrams specify the events of a system and their flows. But use case
diagram never describes how they are implemented. Use case diagram can be imagined
as a black box where only the input, output, and the function of the black box are known.

These diagrams are used at a very high level of design. This high level design is
refined again and again to get a complete and practical picture of the system. A well-
structured use case also describes the pre-condition, post condition, and exceptions.
These extra elements are used to make test cases when performing the testing.

Although use case is not a good candidate for forward and reverse engineering,
still they are used in a slightly different way to make forward and reverse engineering.
The same is true for reverse engineering. Use case diagram is used differently to make it
suitable for reverse engineering.
In forward engineering, use case diagrams are used to make test cases and in reverse engineering use cases are
used to prepare the requirement details from the existing application.
Use case diagrams can be used for −

• Requirement analysis and high level design.

• Model the context of a system.

• Reverse engineering.

• Forward engineering.

2 0
5.1.1 Use case

Fig: Use case diagram

2 0
 5.3 Entity Relationship Diagram:

The ER Model is represented by means of an ER diagram. Any object, for example, entities,
attributes of an entity, relationship sets, and attributes of relationship sets, can be represented
with the help of an ER diagram.

Entity

Entities are represented by means of rectangles. Rectangles are named with the
entity set they represent.

Attributes

Attributes are the properties of entities. Attributes are represented by means of

ellipses. Every ellipse represents one attribute and is directly connected to its entity
(rectangle).

If the attributes are composite, they are further divided in a tree like structure.
Every node is then connected to its attribute. That is, composite attributes are
represented by ellipses that are connected with an ellipse.

Multivalued attributes are depicted by double ellipse.

Derived attributes are depicted by dashed ellipse.

2 0
Purpose of Class Diagrams

The purpose of class diagram is to model the static view of an application. Class
diagrams are the only diagrams which can be directly mapped with object-oriented
languages and thus widely used at the time of construction.UML diagrams like activity
diagram; sequence diagram can only give the sequence flow of the application; however
class diagram is a bit different. It is the most popular UML diagram in the coder
community.

The purpose of the class diagram can be summarized as −

• Analysis and design of the static view of an application.

• Describe responsibilities of a system.

• Base for component and deployment diagrams.

How to Draw a Class Diagram?

Class diagrams are the most popular UML diagrams used for construction of
software applications. It is very important to learn the drawing procedure of class
diagram.Class diagrams have a lot of properties to consider while drawing but here the
diagram will be considered from a top level view.

Class diagram is basically a graphical representation of the static view of the

system and represents different aspects of the application. A collection of class diagrams
represent the whole system.
 The following points should be remembered while drawing a class diagram −

• The name of the class diagram should be meaningful to describe the aspect of the
system.

• Each element and their relationships should be identified in advance.

• Responsibility (attributes and methods) of each class should be clearly identified

• For each class, minimum number of properties should be specified, as

unnecessary properties will make the diagram complicated.

• Use notes whenever required to describe some aspect of the diagram. At the end
of the drawing it should be understandable to the developer/coder.

• Finally, before making the final version, the diagram should be drawn on plain
paper and reworked as many times as possible to make it correct.

The following diagram is an example of an Order System of an application. It describesa

particular aspect of the entire application.

• First of all, Order and Customer are identified as the two elements of the system.
They have a one-to-many relationship because a customer can have multiple
orders.
2 0

• Order class is an abstract class and it has two concrete classes (inheritance

• The two inherited classes have all the properties as the Order class. In addition,
they have additional functions like dispatch () and receive ().

The following class diagram has been drawn considering all the points mentioned above.
Where to Use Class Diagrams?

Class diagram is a static diagram and it is used to model the static view of a
system. The static view describes the vocabulary of the system.

Class diagram is also considered as the foundation for component and

deployment diagrams. Class diagrams are not only used to visualize the static view of
the system but they are also used to construct the executable code for forward and
reverse engineering of any system.
Generally, UML diagrams are not directly mapped with any object-oriented
programming languages but the class diagram is an exception.

Class diagram clearly shows the mapping with object-oriented languages such as
Java, C++, etc. From practical experience, class diagram is generally used for
construction purpose.

In a nutshell it can be said, class diagrams are used for −

• Describing the static view of the system.

• Showing the collaboration among the elements of the static view.

• Describing the functionalities performed by the system.

5.2 Use Case Diagram

To model a system, the most important aspect is to capture the dynamic

behaviour. Dynamic behaviour means the behaviour of the system when it is
running/operating.

Only static behaviour is not sufficient to model a system rather dynamic

behaviour is more important than static behaviour. In UML, there are five diagrams
available to model the dynamic nature and use case diagram is one of them.

Now as we have to discuss that the use case diagram is dynamic in nature, there
should be some internal or external factors for making the interaction.

These internal and external agents are known as actors. Use case diagrams consist
of actors, use cases and their relationships. The diagram is used to model the
system/subsystem of an application. A single use case diagram captures a particular
functionality of a system.

Hence to model the entire system, a number of use case diagrams are used.

In brief, the purposes of use case diagrams can be said to be as follows –

• Used to gather the requirements of a system.

• Used to get an outside view of a system.

• Identify the external and internal factors influencing the system.

• Show the interaction among the requirements is actors.

2 0
How to Draw a Use Case Diagram?

Use case diagrams are considered for high level requirement analysis of a system.
When the requirements of a system are analysed, the functionalities are captured in use
cases.

We can say that use cases are nothing but the system functionalities written in an
organized manner. The second thing which is relevant to use cases is the actors. Actors
can be defined as something that interacts with the system.

• Functionalities to be represented as use case

• Relationships among the use cases and actors.

Use case diagrams are drawn to capture the functional requirements of a system. After
identifying the above items, we have to use the following guidelines to draw an efficient
use case diagram

• The name of a use case is very important. The name should be chosen in such a
way so that it can identify the functionalities performed.

• Give a suitable name for actors.

• Show relationships and dependencies clearly in the diagram.

ONLINE BICYCLE RENTAL SYSTEM

• Do not try to include all types of relationships, as the main purpose of the
diagram is to identify the requirements.

• Use notes whenever required to clarify some important points.

Following is a sample use case diagram representing the order management system.
Hence, if we look into the diagram then we will find three use cases (Order, Special
Order, and Normal Order) and one actor which is the customer.

The Special Order and Normal Order use cases are extended from Order use case.
Hence, they have extended relationship. Another important point is to identify the
system boundary, which is shown in the picture. The actor Customer lies outside the
system as it is an external user of the system.

Where to Use a Use Case Diagram?

dynamic view of a system. Now each and every model has some specific purpose to use.
Actually these specific purposes are different angles of a running system.

To understand the dynamics of a system, we need to use different types of

diagrams. Use case diagram is one of them and its specific purpose is to gather system
requirements and actors.

Use case diagrams specify the events of a system and their flows. But use case
diagram never describes how they are implemented. Use case diagram can be imagined
as a black box where only the input, output, and the function of the black box are known.

These diagrams are used at a very high level of design. This high level design is
refined again and again to get a complete and practical picture of the system. A well-
structured use case also describes the pre-condition, post condition, and exceptions.
These extra elements are used to make test cases when performing the testing.

Although use case is not a good candidate for forward and reverse engineering,
still they are used in a slightly different way to make forward and reverse engineering.
The same is true for reverse engineering. Use case diagram is used differently to make it
suitable for reverse engineering.

2 0
 In forward engineering, use case diagrams are used to make test cases and in
reverse engineering use cases are used to prepare the requirement details from the
existing application.

Use case diagrams can be used for −

• Requirement analysis and high level design.

• Model the context of a system.

• Reverse engineering.

• Forward engineering

.
5.1.1Use Case:

Fig: Use case diagram

 5.3 Entity Relationship Diagram:

The ER Model is represented by means of an ER diagram. Any

object, for
example, entities, attributes of an entity, relationship sets, and attributes of
relationship sets, can be represented with the help of an ER diagram.
Entity
Entities are represented by means of rectangles. Rectangles are
named with theentity set they represent.
An entity is a real-world object or concept that is represented in the database.
It can be a person, place, thing, or event. For example, in a database for a
library, the entities could be books, authors, publishers, and borrowers.

Relationship:
A relationship is a connection or association between two or more entities. It
describes how the entities are related to each other. For example, in a library
database, the relationship between books and authors is that a book is written
by an author.

Attribute:
An attribute is a characteristic or property of an entity. It describes the
specific details or characteristics of an entity. For example, in a library
database, the attributes of a book could be its title, author, ISBN number, and
publication date.
The ER model is used to create a visual representation of the data model,
which helps to identify the relationships between different entities and
attributes. This allows database designers and developers to create a database
structure that is efficient, organized, and easy to use.
Attributes

Attributes are the properties of entities. Attributes are represented by means of

ellipses. Every ellipse represents one attribute and is directly connected to its entity
(rectangle).

If the attributes are composite, they are further divided in a tree like structure.
Every node is then connected to its attribute. That is, composite attributes are
represented by ellipses that are connected with an ellipse.

Multivalued attributes are depicted by double ellipse.

Derived attributes are depicted by dashed ellipse.

 Relationship

Relationships are represented by diamond-shaped box. Name of the

relationship is written inside the diamond-box. All the entities (rectangles)
participating in a relationship, are connected to it by a line.

Binary Relationship and BICYCLEdinality

A relationship where two entities are participating is called a binary

relationship. BICYCLEdinality is the number of instance of an entity from a
relation that can be associated with the relation.
One-to-one − when only one instance of an entity is associated with the relationship, it is
marked a2s '1:10'. The following image reflects that only one instance of each entity
should be associated with the relationship. It depicts oneto-one relationship.
• One-to-many − When more than one instance of an entity is associated with a
relationship, it is marked as '1: N’. The following image reflects that only one
instance of entity on the left and more than one instance of an entity on the right
can be associated with the relationship. It depicts one-to-many relationship.

2 0
 • Many-to-one − when more than one instance of entity is associated with the
relationship, it is marked as 'N:1'. The following image reflects that more than
one instance of an entity on the left and only one instance of an entity on the right
can be associated with the relationship. It depicts many-to-one relationship.

• Many-to-many − The following image reflects that more than one instance of an
entity on the left and more than one instance of an entity on the right can be
associated with the relationship. It depicts many-to-many relationship.

Participation Constraints

• Total Participation − each entity is involved in the relationship. Total

participation is represented by double lines.

• Partial participation − Not all entities are involved in the relationship. Partial
participation is represented by single lines.

2 0
5.3.1 ER-Diagram

Fig:ER-Diagram
5.4 Database Design

ADMIN

CREATE TABLE ADMIN ( EMAIL VARCHAR2(20),

PASSWORD VARCHAR2(15));

USER

CREATE TABLE USER ( FNAME VARCHAR2(15),

LNAME VARCHAR2(15),

EMAIL VARCHAR2(20) PRIMAR2Y KEY

0 , PASSWORD VARCHAR2(15),

PHONE BIGINT(12)
ONLINE BICYCLE RENTAL
SYSTEM
6.2.2 Login

6.2.4 Registration
6.2.6 About

6.2.6 Listing BICYCLE

6.1.8 Footer
7.1 Introduction:

Software testing is a critical element of software quality assurance and represents

the ultimate review of specification, designing and coding.

Testing is the process of executing a program with the intent of finding errors.
During testing, the program to be tested is executed with a set of test cases, and the output
of the program for the test cases is evaluated to determine if the program is performing as
it is expected.

Testing Objectives:

1. Testing is process of executing a program with the intent of finding an error.

2. A good test case design is one that has a probability of finding an as yet
undiscovered error.
3. A successful test is one that uncovers an as yet undiscovered error.
These above objectives imply a dramatic change in view port. Testing cannot
show the absence of defects, it can only show that software errors are present.

Testing methodologies:

Unit Testing:

Unit testing focuses verification effort on the smallest unit of software design that is the
module. This test focuses on each module individually ensuring that it properly as a unit.
Hence the naming is unit testing so that each module is tested individually.

Integration Testing:

It is a systematic technique for constructing different program module into an integrated

software structure. This test uncovers the errors during the entire module and validated.

Output Testing:

Output testing is done to verify whether the given output is right or wrong.

2 0
Validation Testing:

After the integration testing software is ready as per the specification.

But it has to be validated as per the specification and uncover the
unexpected future errors and to improve its reliability.

Software Testing Strategies:

A software testing strategy provides a road map for the software

developer. Testing is a set of activities that can be planned in advance
and conducted systematically. For this reason a template for software
testing a set of steps into which we can place specific test case design
methods should be defined for software engineering process. Any
software testing strategy should have the following characteristics:

1. Testing begins at the module level and works “outward” toward

the integration of the entire computer based system.
2. Different testing techniques are appropriate at different points in time.
3. The developer of the software and an independent test group conducts testing.
4. Testing and Debugging are different activities but debugging
must be accommodated in any testing strategy.

2 0
LITERATURE REVIEW

There are various natural issues that naturalist have been managing in the course of recent decades; one of
which is contamination. For example, in China, the measure of carbon outflows, brought out via vehicles and
manufacturing plants, have been great to the point that the administration is experiencing serious difficulties
controlling air quality. Moreover, reducing oil assets, and rising gas costs are a couple of different components
that may convince the overall population like never before to look for different methods for transportation [4].
Bike sharing can contribute towards improving air quality and lessening clog in urban areas as a piece of a
manageable travel [5]. Evaluating the vitality ramifications of supplanting car trips with bicycle trips. 

Its ubiquity has expanded over the most recent couple of years internationally fundamentally due its
preferences in expense and accommodation over owning a bike and different types of transport. With the
improvement of "Internet of Things", dock less bike sharing plans originally developed around 2015. In [6] the
genuine spatial area information of the open bicycle-sharing frameworks of Hangzhou and Ningbo in Chinas
utilized which proved that BSSs are useful for equalizing traffic flow. 

BICYCLE-sharing frameworks (BSSs) are generally utilized in two unique ways: as a separated administration o
as a multi-purpose administration giving the missing connection between existing purposes of other transport
and wanted goals. Such frameworks are perceived to have natural, traffic, and medical advantages since they
are without emanation, can expand open transport, and give a motivating force to athletic action. 

Moreover, they offer accommodation for individuals who can utilize the administration without the expenses
and duties related with owning a bicycle. DeMaio et al. showed that there were three ages of BSSs, with the
soonest going back to the 1960s in Netherlands [7].

 The “Witte Fietsen” (White Bikes) program was presented on July 28, 1965, in Amsterdam, denoting the
commencement of the original framework. These white bikes were shared casually and not followed,
prompting various bike-robbers. In 1991, a coin-deposit framework was presented in Denmark, denoting the
commencement of the second-age framework.

 The third-age framework, which uses data innovation to track bicycles and clients, first rose in the late 1990s
in Europe and afterward stretched out to numerous urban areas everywhere throughout the world. Before the
finish of 2016, around 1,175 urban communities or areas in 63 nations have executed BSSs, incorporating 430
urban communities in China [8].

2 0
8 .CONCLUSION

BICYCLE Rental System is a web application and it is restricted to

only limited type of users. In this application, Admin have been
given access rights and are restricted up to certain functionalities, so
that the data is maintained securely and redundant data is prevented.
As the Data is stored electronically, it is necessary to have a
Computer and Network connection to access the Application. It is a
software which helps the user to rent BICYCLE base on their need.
This software reduces the amount of manual data entry and gives
greater efficiency. The User Interface of it is very friendly and can
be easily used by anyone. It also decreases the amount of time taken
to write details and other modules. At the end, this software can
perform all the tasks accurately and can do the work for which it is
made.

Any Suggestions are Welcome.

2 0
 8. FUTURE ENHANCEMENT

Once the final Online car rental , is built, users or clients can book the BICYCLE already
exists in the web application. In future, users or clients can add BICYCLEs to the rent
section and also we like to add slide bar of trending BICYCLEs in web Page. Also we like t
add a Chat Bot which helps user or clients to enquire their doubts related to the
application
Further enhancement, the use of search engine can be customisable using the filter option
according to the user or a reader.

Upgraded components: One of the easiest ways to enhance the performance of a bicycle is to upgrade its
components, such as the brakes, shifters, or wheels. This can improve speed, handling, and overall functionality.

Suspension: If you plan to ride off-road or on rough terrain, adding suspension to your bicycle can make a huge
difference in your comfort and control.

Lights: Adding lights to your bicycle can improve your visibility and safety, especially when riding at night.

Fenders: Fenders can keep you and your bicycle clean and dry, especially in wet conditions.

Comfortable saddle: A comfortable saddle can make a big difference in your overall riding experience, especially if
you plan to ride long distances.

Smartphone mount: A smartphone mount can make it easier to navigate or access music or other apps while riding.

Rack and panniers: Adding a rack and panniers to your bicycle can increase its storage capacity, making it easier to
carry items like groceries or camping gear.

Adjustable stem and handlebars: An adjustable stem and handlebars can allow you to customize your riding position,
making your bicycle more comfortable and efficient.

Tubeless tires: Tubeless tires can reduce the risk of punctures and improve traction and speed.

2 0
METHODOLOGY:

Bicycle renting service was introduced in NUST Islamabad by students in 2017, but this service was
deployed inside the university premises and was only accessible by the students and faculty. 

Therefore, we decided to launch a renting service which would not only be used as a mean of transport
but will also be a way to develop cycling culture, as we already know about the environmental
conditions of our country, 70% of our air pollution is due to emissions of transportation. Hence,
RENT-A-CYCLE is a best fit for the solution of environmental problems.

After doing the literature review and survey about the existing bicycle renting services all around the
world, we came across following features of those services. 
• Few services have docking station with payments done through cards with pop-up machines available
at the station. 
• Few are dock less bicycle sharing services, which work through mobile apps having tracking system
and online payment, but there is no automatic locking mechanism in the bicycle. 
• These bicycle services do not have maintenance feedback option
• They have separate lanes for bicycle riders so they do not encounter any accident but there are places
where these services are closed due to security issues in few cities.

Comparison between RENT-A-CYCLE and CYKIQ:

Figure 3 is a Table 1 containing the differences between RENT A CYCLE and the existing bicycle
renting service in Pakistan i.e. CYKIQ.
Working of locking mechanism

• This lock consists of helical worm gear mechanism and a DC motor. The shaft of the worm gear is
attached to the DC motor. When the DC motor is powered worm gear starts to rotate.

• It is mashed with the helical gear. The helical gear was circular in shape, which was later modified in a
way that it surrounds the tyre when it is locked.

• Both the gears move in similar directions, it is locked when the motor moves anticlockwise and unlocks
when it moves clockwise.

• There are two rollers placed with helical gear so the gear can move smoothly. 

• The whole locking mechanism (figure 3) is protected inside a metal case which will be attached on the
cycle above the type. The lock is designed according to the dimensions of the cycle and it fits perfectly.

Working of the Android Application

Figure 5 shows the working of the android application with the data flow between the hardware and the
software.
• QR Scanning.
• Tracking through GPS.
• Server.
• Arduino Wi-Fi module.
• Automatic lock.
• Online payment deduction.
• Security feature.
System Block Diagram
Methodology
SUSTAINABLE DEVELOPMENT GOALS

After the text edit has been completed, the paper is ready for the template. Duplicate the template file by using
the Save As command, and use the naming convention prescribed by your conference for the name of your
paper.

In this newly created file, highlight all of the contents and import your prepared text file. You are now ready to
style your paper; use the scroll down window on the left of the MS Word Formatting toolbar.

There are seventeen United Nations sustainable development goals. All the goals are interrelated with each
other; every goal is basically a solution of a problem.

These goals are very important to follow to reduce the hazards and problems. These goals cover every aspect of
the society like gender equality, sustainable consumption, reduced inequalities, affordable and clean energy and
many others

1. The application will have an option for feedback. The rider can complain if there is any malfunctioning in the
cycle for example if the lock is not working or if the tire is puncture, etc.

2. The service will be provided in gated societies so that no one will be able to take the bicycle out of the area.

3. All the information of user is taken while logging in the application for example user’s NIC and email
id.

4. If the cycle crosses a specified range, a buzzer will be turn on and lock will be automatically closed.

5. This service is an initiative to introduce the cycling culture in Pakistan. Smart Bicycle-renting services are
already deployed all around the world and is the major factor for urbanization and growth of those countries.
Therefore, Pakistan should also this step towards clean and green environment.
CONCLUSION:

The rental bicycle project can be an effective way to promote eco-friendly transportation options and
encourage people to lead more active lifestyles.

The success of the project may depend on factors such as the availability and accessibility of the bicycles,
the quality of the bicycles, the pricing and payment options, and the level of promotion and marketing.

The project can contribute to reducing traffic congestion, improving air quality, and enhancing the overall
livability of the community.

The project may face challenges such as theft, vandalism, and maintenance issues, which need to be
addressed through appropriate security measures and regular upkeep.

The project can benefit from partnerships with local businesses, community organizations, and government
agencies to promote awareness and support for the initiative.

The project can serve as a model for similar programs in other communities and cities, and can inspire
innovative solutions to urban transportation challenges.
REFERENCES:

1. Bike-sharing: History, Impacts, Models of Provision, and Future.

2. Christopher Moon-Miklaucic, Anna Bray-Sharpin, Ivan De La Lanza, et al. The Evolution of Bike
Sharing:
 10 Questions on the Emergence of New Technologies, Opportunities, and Risks. Working Pap.
2019:1-44.

3. Edgard Antunes, Dias Batista. Bicycle Sharing in Developing Countries: A proposal towards
Sustainable Transportation in Brazilian Median Cities. Master of Science Thesis Stockholm.
2010:1-107.

4. Matrovic M, Namazi A, Lin S. et al. The Bike Share Program. 2014.

5. Lovelace R, Beck SBM, Watson M. et al. Assessing the Energy Implications of Replacing Car
Trips with Bicycle Trips in Sheffield, UK. Energy Policy. 2011;39:2075-2087.

6. Yang XH, Cheng Z, Chen G. et al. The impact of a Public Bicycle-Sharing System on Urban
Public Transport Networks. Transp. Res. Part A Policy Pract. 2018;107:246–256.