This system is named as Bike on Rent Management System.

This
system is designed to help the customers to take bikes or two-wheelers
on rent. When we go on any trip outside the town or country we want
to be free of time so instead of going through metros and taxis we
prefer to have our own vehicle for rent.

Using this system vehicle owner can register as sellers and customers
who want to take bikes on rent can register themselves as renters and
can take any bike on rent.

Address of the both are required as the customer can only take bike by
going to the address provided and the vehicle owners can know the
address that a customer is verified or not. The customer also has to
upload some proofs to take the bike on rent.

Proofs like license, pan card and identity card are compulsory so that
no one could run taking the bike. Any customer whose proofs are not
uploaded and are not valid will not be allowed to take any bike on rent.

This has one admin account who verifies the registering user and two
types of the user account. One for bike sellers and one for customers
who take the bike on rent. This system has only one admin account
and cannot have more than one admin account.

Admin can verify and register the user who is registering. If the admin
does not verify, the user cannot register. All other features are
explained further with details.

MODULES OF BIKE Rental SYSTEM

Our system has two main modules. One is the admin and the other is
the user. User module is again divided into two parts, either the user
can be event or function arranger or customer. Along with these, we
have other interfaces which can be discussed as below:

Bikes:
This is one of the most important modules. This module helps the
customers to take any bike on rent from any bike seller. Status of bikes
can be updated as soon as it gets free or it gets booked so that no other
customer tries to book the same bike.

The information that is added to a bike is its model no, vehicle no and
owner name.

Login:
After registration, one can login into 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 any one for this event.

Admin:
This module is present only for one account. That is, no one can
register as admin after the one account is created. Admin account has
all the privileges, to check about any particular bike 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, making 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 bikes that
are free card can be given on rent. If the user is a customer then he can
see all the available bikes that he can take on rent.
Payment:
This module is present so that customer can easily pay the amount as
the amount paid through this system goes to admin and then admin
can make the payments to all the event managers according to their
work.

It reduces the customer’s headache. The customer can pay the amount
through net banking, debit card or credit card.

Adding and Deleting Other Staff Members:

The other module that is provided in this system is that the data of all
the staff members working in any workshop can be saved on it. The
benefit of storing their information is that when any person is on leave
and when the salary is calculated then this system can automatically
calculate the salary by deducting the amount according to the leaves
taken.

The information that is added to the staff is a name, address, phone

number, employee id, the job of the employee and the salary of the
employee.

Other Features:
There are other various features that are provided in this Invitation
management system inviting guests to the event, doing the
preparation of the event, selecting staff members etc. Paying amount
either by online mode or by the offline mode.

check Bus Management System Project

SYSTEM DESIGN OF BIKE Rental SYSTEM:
Now this prison management system is designed in such a way that it
takes fewer resources to work properly. It has its own sort of minimum
requirements that we need to take care of :

The system needs a minimum of 2 GB of ram to run all the features

smooth and sudden.
It needs a minimum 1.3 GHz processor to run smooth as less than that
may create problems.

The system needs to be operated by some authorized person as wrong

hands can make it irresponsible.

Rest is all up to the user’s usage will care for hardware

For security Antivirus is recommended.

The system is made properly and all the testing is done as per the
requirements. So, the rest of the things depend on the user and no one
can harm the data or the software if the proper care is done.

All the attributes are working perfectly and if any error is found then it
can be removed easily.

Entity Employee:
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. Other attributes of entity employee are as follows:

Name:
The user must know the name through which he or she has chosen to
register itself on the system.

Number:
The phone number is taken here to keep the member updated and for
the confirmation of the event is also managed through this method.

Email:
Email is taken to make member aware of new offers a new event and
for future reference, it is also relevant.
Address:
Address of the user is required at the time the customer is registering
itself on the system.

Employee id:
Employee id is generated when the user registers itself and it is always
unique so that every employee can be found easily.

Entity User:
Every User’s details need to be stored in a proper manner with very
needed attributes. As all the other tasks can be performed only if the
user is authenticated.

After the admin has registered and is verified by the admin then the
user can perform all the tasks on it. Some of the features of the user
are as follows:

Primary key User id:

The user id is system generated and unique, which can be referenced
in any other entity.This mostly for recognizing it in the unique way
anywhere in the program.

Username:
Username is taken from the user and fed into this it is properly
validated so that no mistake happens.

Number:
The phone number is taken here to keep the member updated and for
the confirmation of the event is also managed through this method.

Email:
Email is taken to make member aware of new offers for new events
and for future references it is also relevant.
Address:
Address of the user is required at the time the customer is registering
itself on the system

Password:
The password is required to login into the system and the password
must contain a special character, a numeric character and an upper-
case letter. Password must contain at least six characters.

One must keep the password difficult so that no one can get into your
account and make any changes.

Entity payment:
This module is present in both the interfaces but the options that are
provided are different. In the customer’s interface, there is an option
to make the payment using their debit card or by net banking.

The customer can also pay the bill by cash by going to the particular
branch. Customers can also see their payment status after paying their
bill. In the employee’s module, there is no option to pay the bill, they
can only see the monthly salary status after deducting their leaves.

Admin cannot see any details they can only help the user in
registration by verifying the user. Some features of payment entity are
explained further :

Name:
The user must know the name through which he or she has chosen to
register on the system.

Number:
The phone number is taken here to keep the member updated and for
the confirmation of the event is also managed through this method.
Address:
Address of the user is required at the time the customer is registering
itself on the system.

Entity Admin:
This module is present only for one account. That is, no one can
register as admin after the one account is created. Admin account has
all the privileges, to check about any particular courier,

to block any account, to calculate the salary of the employees after

deducting their leaves, to update the status about any courier, to track
any courier, to calculate the payment, checking the courier payment
type etc.

Admin Name:
Username is taken from the user and fed into this it is properly
validated so that no mistake happens.

In this use case as you can see we have our system as box and the users
who use our system are of the kind of outside the box but related to
the system. There are two kinds of user one is admin and the other is
user type.

Users:
There are two users that are present here in this system. One is admin
but the other is a user. This user has all the privileges but it cannot
register itself on this system as the admin needs to verify the
registering user. After the admin verifies the user only when he is
eligible to use the system.Attributes given to the user are:

Admin panel:
There can be only one account of admin. Admin can add the users.
When a user tries to register on this system then the request goes to
admin and if the admin verifies only the user can register itself on it.
Other privileges that admin has been explained below:
He can, Login through his id and password. The password is made
very secure so that no person can guess and make it difficult for
hackers to crack.

He has access to the profile of his own and he can search detail of
other Users and can see the detail of him.

This admin is responsible for creating and uploading the Menu card to
every User in the Interface.

He can add a user to that account and give access to for handling the
courier management system on their own.He can manipulate the data
of any user.In this, we are showing here the interaction of the users
with our system through our use case diagram.

FUNCTIONAL AND NON-FUNCTIONAL

REQUIREMENTS OF BIKE Rental SYSTEM
The functional requirement of bike system this is that it does what it is
meant for. A functional requirement describes what a software system
should do, while non-functional requirements place constraints on
how the system will do so.

Functional requirements specify a function that a system or system

component must be able to perform. It can be documented in various
ways. The most common ones are written descriptions in documents
and use cases.

Few of its functional requirements are as given below:-

User data should be fed into the system: this system is doing that
properly in user entity.

Admin can add the users: Admin can verify and add the user, which is
they are doing with this system.