Mini Project

U Drive Introduction
CHAPTER 1
INTRODUCTION
1.1 Brief Introduction about the Project
“U Drive” is a car rental website that is used to rent a car. Here user has to login to book a car. The
user can search for cars easily and book. For bookings, the user has to provide information such as
booking dates and text message. All car details are provided and it also includes Car’s feature and
Overview. The user can also post their Testimonials and the user can update their Profile as well as
passwords anytime they want from the site. Admin can add/manage car brands, manage vehicles,
bookings, testimonial, pages and many more. It’s easy to operate and understand by users. This site
makes customers easy for car rental. The design is pretty simple and the user won’t find it difficult to
understand, use and navigate.
The system has three types of accessing modes, administrator, user and guest user. U Drive is man-
aged by an administrator.
A registered user can use all the facilities in the system by logging into it. Like every other manage-
ment system, the car rental management system will have admin. The admin will the entity that will
monitor the activity and the records of the whole system. Admin can view other user’s profiles. That
mean will have the power to delete any other uses from the records of update the data of any other
users. Users in the system will have to update their profile records.
A car rental management system is an autonomous system that will preserve the records of all the cars
available, cars rented, etc. The user can rent a car based on its efficiency, performance, effort, or cost.
The dealer can make a lot of use of this system by providing the cars.
A user can observe the list of cars available in the inventory. The budget is an important factor. It will
be easier to choose a car rather than wondering what if I choose this car and price is higher. No ten-
sion at all, you can analyses the call record and choose your best car. After a user have selected their
favourate car, uses can fill the car rental form which is available online. You said just have to fill in
some details like how many days they want to rent the car.
College of Applied Science, Ayroor 1

1.2 Module Descriptions
i. Guest View
Guest users are unregistered users, who can see only the available cars. Here scription about site
and user manual that shows how to use the site is included.
ii. Login
Register users can login to the site using their username and password.
iii. Registration
New user can register to use the facilities of the site on; they will be given a username and
password that can be changed by the user at a later time.
iv. Profile Management
Users can manage their profile. The sub modules are:
• View Profile
User can view their profile.
• Edit Profile
Users can edit their profile information given at the time of registration.
v. Admin
• Add Car
The shopping cart project contains different kind of cars. The cars can be classified into different
categories by name. Admin can add new cars into the existing system with all its details including
an image.
• Delete Car
Administrator can delete the cars based on the stock.
• Search Car
Admin will have a list view of all the existing products. He can also search for a particular product
by name.

• View Users
The admin will have a list view of all the user registered in the system. Admin can view all the
details of each user in the list except password.
• Add Users
Admin has privileges to add a user directly by providing the details.
• Delete Users
Administrator has a right to delete a user.
• View Order
Administrator can view the orders which is generated by the users. He can verify the details of
the purchase.
• Delete Order
Admin can delete order from the orders list when the car is taken for rent.
• Login
A user must login with his user name and password to the system after registration
• View Car
User can view the list of cars based on their name after successful login. A detailed description of
a particular car with car name, details of the cars, images of the cars and price can be viewed by
users.
• Search Car
Users can search for a particular car in the list by name.

1.3 Scope and Objectives of the Project
1.3.1 Objective
The main objective of the U Drive website is to manage the details of car and users. It manages all
information about car and booking. The project is totally build at administrator and thus only the
administrator is guaranteed the access. The purpose of the project is to build an application program
to reduce the manual work for managing the car, booking and users. It tracks all the details about the
users.
To make sure a user gets his desire car as early as possible; the car rental management system will
provide a faster response to complete the process.
It is a web based the system that allow users to register and reserve car online and for the company to
effectively manage their car rental business.
1.3.2 Scope
Car rental system (U Drive) is a web based system for a company that rents out cars. This system
enables the company to make their services available to the public through the internet and also keep
records about their services. This is a company that rents automobiles for a short period of time for a
few days or week.
The car rental system project has the scope of online application, by searching cars online and cus-
tomer can book the car. We will be a growth-oriented car rental organization by efficiently serving
value-conscious customers for all of their car rental occasions. The functions which cover in this
project are we are focusing on making rent car and online reserve.
The car rental system to keep details records of both the cars and the customers, the cars and the cus-
tomers, the duration they rent car as well as the type of car they rent.
It may help collection perfect management in details. In a very short time, the Collection will be
obvious, simple and sensible. It will help a person to know the Management of passed year perfectly
and vividly. It also helps in current all works relative to car rental system. It will be also reduced the
cost of collecting the management & collection procedure will go on smoothly.

U Drive System Analysis
CHAPTER 2
SYSTEM ANALYSIS
2.1 Feasibility Study
System study aims at establishing requests for the system to be acquired, developedand installed. It
involves studying and analyzing the ways of a user currently processes the data to produce informa-
tion. Analyzing the problem thoroughly forms the vital part of the system study. In system analysis,
prevailing situation of problem carefully examined by breaking them into sub problems. Problem-
atic areas are identified and information is collected. Data gathering is essential to any analysis of
requests. It is necessary that this analysis familiarizes the designer with objectives, activities and the
function of thesystem is to be implemented.
During system analysis, a feasibility study of the proposed system was carried out to see whether it
was beneficial to the user. Three key considerations that are involved in the feasibility study and the
result of the feasibility study are given below.
2.1.1 Technical Feasibility
According to the feasibility analysis procedure the technical feasibility of the system is analyzed
and the technical requirements such as software facilities, procedure, inputs are identified. While
considering the technical factors that are currently available with most of the users, it is feasible to
implement the new system. The new system can use the existing internet access mechanism with the
user and no other communication channel is required.
2.1.2 Economical Feasibility
A car Rental System is being developed for customers so that they can book there vehicles from any
part of the world. This application takes information from the customers through filling their details.
A customer being registered in the website has the facility to book a vehicle which he/she requires
2.1.3 Operational Feasibility
People are inherently resistant to change and computer has been known to facilitate changes. An
estimate should be made about the reaction of the user towards the development of a computerized
system. Computer installations have something to do with turnover, transfers and changes in job
status. These are various levels of users in order to ensure proper authentication and authorization
and security of sensitive data of each user.

2.2 Requirement Analysis
Requirements analysis in systems engineering and software engineering, encompasses those tasks
that go into determining then needs or conditions to meet for a new or altered product, taking account
of the possibly conflicting requirements of the various stakeholders, such as beneficiaries or users.
Requirements analysis is critical to the success of a development project. Requirements must be ac-
tionable, measurable, testable, related to identified business needs or opportunities, and defined to a
level of detail sufficient for system design. Conceptually, requirements analysis includes three types
of activity:
● Eliciting requirements: the task of communicating with customers and users to determine what their
requirements are. This is sometimes also called requirements gathering.
● Analyzing requirements: determining whether the stated requirements are unclear, incomplete,
ambiguous, or contradictory, and then resolving these issues.
● Recording equirements: requirements may be documented in various forms, such as natural
language documents, use cases, user stories, or process specifications.
Requirements analysis can be a long and arduous process during which many delicate psychological
skills are involved. New systems change the environment and relationships between people, so it is
important to identify all the stakeholders, take into account all their needs and ensure they understand
the implications of the new systems.
“U Drive” is a car rental website that is used to rent a car. A car rental management system is an au-
tonomous system that will preserve the records of all the cars available, cars rented, etc. The user can
rent a car based on its efficiency, performance, effort, or cost. The dealer can make a lot of use of this
system by providing the cars. The user has login into their account using username and a password
through a quality login window. Administrator has provision for manage users , manage products and
manage orders.
The system consist of three modules. Admin module, user module and guest user module. Admin
module consists of the functionalities such as add new cars, delete cars, view user details, delete
users, view orders and delete orders. User module consists of the functionalities such as view and
search cars, book cars and manage their profiles. Guest user module consist of the functionalities such
as view cars , search cars and login.

2.3 Existing System
The study of the existing system is a pre-requisite for developing any software system.The study of
the system reveals many features of the existing system. This gives analyst an insight into the work-
ing of the system and helps the developer to design an appropriate system, which eliminate the many
limitations present in the existing system. Limitations of the Existing System:
● Error prone.
● Results are not precise.
● Result processing takes more time.
● More human efforts.
● Less efficient.
● Not reliable.
2.4 Proposed System
The proposed computerization is developed using MySQL server as backend and the most powerful
PHP as front end. PHP language is a managed and type safe environment for dynamic web applica-
tion development and execution. This software is developed as a simulated system and the complex
procedures are avoided to make the system easy to use. The proposed system is user friendly and has
simplicity and security.
(a) Advantages of the Proposed System
● Give solutions to the current system problems.

● Less time consuming and more efficient.
● Easy to use and fast.
● Simple user interface.
● Customizable features and reports.
● More manpower
● Time consuming
(b) Features of the Proposed System
The various features of proposed system are as follows:
● The maximum security ensured.

● User- friendly
● Better services
● Minimum time required
● Greater efficiency

2.4.1 Requirement Specification
The primary goal of the system analyst is to improve the efficiency of the existing system. For that the
study of specification of the requirements is very essential. For the development of the new system,
a preliminary survey of the existing system will be conducted. An investigation is done whether the
upgradation of the system into an application program could solve the problems and eradicate the
inefficiency of the existing system.
Thus, Software/System Requirement Specification (SRS) is the medium through which the client’s
needs are accurately specified; indeed, SRS forms the basis of software development. A good SRS
should satisfy all the parties- something very hard to achieve and involving tradeoffs and persuasion.
A software requirement describes how a product will work entirely from the user’s perspective. It
doesn’t care how the thing is implemented. A SRS is a complete description of the behavior of a sys-
tem to be developed
The Requirement Specification for the system can be as:
Sl No Requirment Essential or De- Description of the Remark

sirable Requirement
RS1 The system The best view should The gust view
should have a Essential appear when any type contains basic in-
gust view. of user visit the site for formation about
first time. the site.
RS2 There should be This page allows user Registered users
an option for user Essential to register for the can utilise the
registration. online examination system.
system.
RS3 The system A login page should User should log-
should have a Essential appear when user select in to the system
login. it. with their user-
name and pass-
word.
RS4 The system A home page should This page shows
should have a Essential appear when user login. the paging each
user home page. user can access.

2.4.2 Hardware Specification
Processor : Intel core i5 10th generation

Memory : 8gb
SSD : 512gb
Display : 15.6 inch, FHD
Ethernet : wifi
Keyboard : Natural keyboard
Mouse : Compatible / Wired mouse
2.4.3 Software Specification
Operating System : Windows

Front End : PHP
Back End : MySQL
Tools used : HTML , CSS
Web Server : XAMPP
Browser : Google Chrome
2.4.4 Software Description
PHP
PHP is a server-side scripting language designed for web development but also used as a general
purpose programming language. Originally created by Rasmus Lerdorf in 1994, the PHP reference
implementation is now produced by The PHP Group. PHP originally stood for Personal Home Page,
but it now stands for the recursive backronym PHP: Hypertext Preprocessor.
PHP code may be embedded into HTML code, or it can be used in combination with various web tem-
plate systems, web content management system 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 standard PHP interpreter, powered by the Zend Engine, is free software released
under the PHP License. PHP has been widely ported and can be deployed on most web servers on
almost every operating system and platform, free of charge.

The PHP language evolved without a written formal specification or standard until 2014, leaving the
canonical PHP interpreter as a de facto standard. Since 2014 work has gone on to create a formal PHP
specification.
PHP 6 and Unicode
PHP received mixed reviews due to lacking native Unicode support at the core language level. In
2005, a project headed by Andrei Zmievski was initiated to bring native Unicode support throughout
PHP, by embedding the International Components for Unicode (ICU) library, and representing text
strings as UTF-16 internally. Since this would cause major changes both to the internals of the lan-
guage and to user code, it was planned to release this as version 6.0 of the language, along with other
major features then in development.
However, a shortage of developers who understood the necessary changes, an performance problems
arising from conversion to and from UTF-16, which is rarely used in a web context, led to delays in
the project. As a result, a PHP 5.3 release was created in 2009, with many non-Unicode features
back-ported from PHP 6, notably namespaces. In March 2010, the project in its current form was
officially abandoned, and a PHP 5.4 release was prepared containing most remaining non-Unicode
features from PHP 6, such as traits and closure re-binding. Initial hopes were that a new plan would
be formed for Unicode integration, but as of 2014 none has been adopted.
PHP is a general-purpose scripting language that is especially suited to serverside web development,
in which case PHP generally runs on a web server. Any PHP code in a requested file is executed by
the PHP runtime, usually to create dynamic web page content or dynamic images used on websites
or elsewhere. It can also be used for command-line scripting and client-side graphical user inter-
face (GUI) applications. PHP can be deployed on most web servers, many operating systems and
platforms, and can be used with many relational database management systems (RDBMS). Most web
hosting providers support PHP for use by their clients. It is available free of charge, and the PHP
Group provides the complete source code for users to build, customize and extend for their own use
Fig: Dynamic web page: example of server-side scripting (PHP and MySQL).

PHP acts primarily as a filter, taking input from a file or stream containing text and/or PHP instructions
and outputting another stream of data. Most commonly the output will be HTML, although it could
be JSON, XML or binary data such as image or audio formats. Since PHP 4, the PHP parser compiles
input to produce byte code for processing by the Zend Engine, giving improved performance over its
interpreter predecessor. Originally designed to create dynamic web pages, PHP now focuses mainly
on server-side scripting, and it is similar to other server-side scripting languages that provide dynamic
content from a web server to a client, such as Microsoft’s ASP.NET, Sun Microsystem’s Java Server
Pages, and mod_perl. PHP has also attracted the development of many software frameworks that pro-
vide building blocks and a design structure to promote rapid application development (RAD). Some
of these include PRADO, CakePHP and Symfony, CodeIgniter, Laravel, Yii Framework, Phalcon and
Zend Framework, offering features similar to other web frameworks.
The LAMP architecture has become popular in the web industry as a way of deploying web applica-
tions. PHP is commonly used as the P in this bundle alongside Linux, Apache and MySQL, although
the P may also refer to Python, Perl, or some mix of the three. Similar packages, WAMP and MAMP,
are also available for Windows and OS X, with the first letter standing for the respective operating
system. Although both PHP and Apache are provided as part of the Mac OS X base install, users of
these packages seek a simpler installation mechanism that can be more easily kept up to date.
For specific and more advanced usage scenarios, PHP offers a well-defined and documented way for
writing custom extensions in C or C++. Besides extending the language itself in form of additional
libraries, extensions are providing a way for improving execution speed where it is critical and there
is room for improvements by using a true compiled language. PHP also offers well defined ways for
embedding itself into other software projects. That way PHP can be easily used as an internal scripting
language for another project, also providing tight interfacing with the project’s specific
internal data structures.
PHP received mixed reviews due to lacking support for multithreading at the core language level,
though using threads is made possible by the “pthreads” PECL extension.

Introduction to the MySQL PHP API
PHP is a server-side, HTML-embedded scripting language that may be used tocreate dynamic Web
pages. It is available for most operating systems and Web servers, and can access most common da-
tabases, including MySQL. PHP may be run as a separate program or compiled as a module for use
with a Web server.Depending on the version of PHP, there are either two or three PHP APIs for acces-
sing the MySQL database. PHP 5 users can choose between the deprecated mysql extension, mysqli,
or PDO_MySQL. PHP 7 removes the mysql extension, leaving only the latter two options
API
An Application Programming Interface, or API, defines the classes, methods, functions and variables
that your application will need to call in order to carry out its desired task. In the case of PHP app-
lications that need to communicate with databases the necessary APIs are usually exposed via PHP
extensions. APIs can be procedural or object-oriented. With a procedural API you call functions to
carry out tasks, with the object-oriented API you instantiate classes and then call methods on the re-
sulting objects. Of the two the latter is usually the preferred interface, as it is more modern and leads
to better organized code. When writing PHP applications that need to connect to the MySQL server
there are several API options available. This document discusses what is available and how to select
the best solution for your application.
PHP’s mysqli Extension
The mysqli extension, or as it is sometimes known, the MySQL improved extension,was developed
to take advantage of new features found in MySQL systems versions 4.1.3 and newer. The mysqli
extension is included with PHP versions 5 and later. The mysqli extension has a number of benefits,
the key enhancements over the mysql extension being:
• Object-oriented interface
• Support for Prepared Statements
• Support for Multiple Statements
• Support for Transactions
• Enhanced debugging capabilities
• Embedded server support

U Drive System Design
CHAPTER 3
SYSTEM DESIGN
The purpose of System Design is to create a technical solution that satisfies the functional require-
ments for the system. At this point in the project lifecycle there should be a functional specification,
containing a complete description of the operational needs of the various organizational entities that
will use the new system. The challenge is to translate all of this functional information in SRS into
technical specifications that accurately describe the design of the system, and that can be used as input
to system construction.
This phase consists of the following processes:
● Prepare for System Design, where the existing project repositories areexpanded to accommodate
the design work products, the technical environmentand tools needed to support system design are
established, and training needsof the team members involved in system design are addressed.
● Define Technical Architecture, where the foundation and structure of thesystem are identified in
terms of system hardware, system software, and supporting tools.
● Define System Standards, where common processes, techniques, tools, and conventions that will
be used throughout the project are identified in an attempt to maximize efficiencies and introduce
uniformity throughout the system.
● Create Physical Database,where the actual database to be used by the system is defined, validated,
and optimized to ensure the completeness, accuracy, and reliability of the data.
● Prototype System Components, where various components of the solutionmay be developed or
demonstrated in an attempt to validate preliminaryfunctionality, to better illustrate and confirm the
proposed solution, or todemonstrate “proof-of-concept.”
● Produce Technical Specifications, where the operational requirements of the system are translated
into a series of technical design specifications for all components of the system, setting the stage
for System Construction.
3.1 Data Flow Diagram
A data flow diagram (DFD) or a bubble chart is a graphical tool for structured analysis. DFD mod-
els a system by using external entities from which data flows to a process, which transforms the
data and creates output-data-flows which go to other processes or external entities or files. Data in
files may also flow to processes as inputs.Data flow diagram (DFD) is used to show how data flows
through the system and the processes that transform the input data into output. Data flow diagrams
are a way of expressing system requirements in a graphical manner. DFD represents one of the
most ingenious tools used for structured analysis.

DFDs can be hierarchically organized, which help in partitioning and analyzing large systems. As a
first step, one dataflow diagram can depict an entire system which gives the system overview. It is
called context diagram of level 0 DFD. The context diagram can be further expanded.
The successive expansion of a DFD from the context diagram to those giving more details is known
as leveling of DFD .Thus a top down approach is used, starting with an overview and then working
out the details. The main merit of DFD is that it can provide an overview of what data a system would
process, what transformation of data are done, what files are used, and where the results flow. The
data flow has been represented as a hierarchical DFD. Context Level DFD was drawn first. Then the
processes were decomposed into several elementary levels and were represented in the order of
importance.
3.1.1 Basic DFD Symbols

A data flow is a route, which enables packets of data travel from one
.
point to another. Data may flow from a so source to a processor and
from data store or process. An arrow line depicts the flow, with arrow
head pointing in he direction of flow
A process represents transformation where incoming data Flows are

changed into out going data flows.
A data store is a repository of data that is to be stored for Use by a one

or more process may be simple as buffer or queue or sophisticated as
.
relational database. The shoul have clear names. If a process merely
uses the content of store and does not alter it, the arrow head goes only
from the store the process. If a process alter the details in the store then
a double headed arrow is used.
A source or sink is person or part of an organization that enters or re-

ceives information from the system, but is considered to be outside the
context of data flow model

User User
Administrator U Drive Administrator
Guest Guest
Fig 1 : Level 0 DFD
Vehicles
Authentication
Manage
Booking
Admin
Admin Reg Users
Dashboard Dashboard
Home
Logout
Manage
Page
Change
password Update
contact
info
Fig 2: Admin Level

View
Contact us
Guest User Home Page User home
About us
Login
Fig 3 : Guest User Level
Authentication
About us
User User home Contact us User home
Change
Logout password
Fig 4 : User Level

User Book a Car Book Now Book a Car
Fig 5: booking level
3.2 Database Structure
The purpose of physical database process is to accommodate all of the data that needs to be
managed by the system within the system database tables and files. This information must be stored
in a manner that ensures its reliability, accuracy, and completeness, while minimizing redundancy
and meeting system performance expectations. This section reveals the final design of the DBMS
files and includes the following information, as appropriate to data dictionary:
• Refined logical model; provide normalized table layouts, entity relationship diagrams, and other
logical design information
• A physical description of the DBMS schemas, sub-schemas, records, sets, tables, storage page
sizes, etc.
• Access methods (such as indexed, via set, sequential, random access etc.)
• Estimate of the DBMS file size or volume of data within the file, and data pages, including over-
head resulting from access methods and free space.
• Definition of the update frequency of the database tables, views, files, areas, records, sets, and
data pages; estimate the number of transactions if the database is an online transaction-based
system.
To group the given data and to give them a logical structure, a database design is necessary. The
overall objective in the development of a database is to treat data as an organized resource and is
an integrated whole. A database is an integrated collection of data and provides centralized access
to the data. Usually the centralized data managing software is called RDMS. The main significant
difference between RDMS and other DBMS is the separation of data as seen by the program and data
as stored in direct access to storage device. This is the difference between logical and physical data.

A database is a collection of interrelated data stored with minimum redundancy to serve many users
quick and efficiently. In this project, we are mainly concentrated into relational databases. Relational
databases stores data in tables, which in turn, are composed of rows also known as records, columns
also known as fields.
3.2.1 Tables
Table No :1
Table Name : Admin Table
Primary Key : id
Foreign Key : uname
Name Type Size Constraints
Id int 11 AUTO-INCREMENT
UserName varchar 100
Password varchar 100
UpdationDate timestamp ON UPDATE CURRENT-TIMESTAMP
Table No :2
Table Name : tblbooking
Primary Key : id
Foreign Key : uname
UserEmail varchar 100
Vechicle ID int 11
FromDate varchar 20
ToDate varchar 20
Message varchar 225
Status int 11
PostingDate timestamp

Table No :3
Table Name : tblbrands
Primary Key : id
Foreign Key : uname
BrandName varchar 120
CreationDate timestamp
UpdationDate timestamp ON UPDATE CURRENT-TIMESTAMP
Table No :4
Table Name : contactusinfo
Primary Key : id
Foreign Key : uname
Address tinytext
EmailID varchar 255
ContactNo char 11
Table No :5
Table Name : contactusquery
Primary Key : id
Foreign Key : uname
Name varchar 100
EmailID varchar 120
ContactNumber char 11
Message longtext
Status int 11

Table No :6
Table Name : tblpages
Primary Key : id
Foreign Key : uname
PageNumber varchar 255
Type varchar 255
Details longtext
Table No :7
Table Name : tblsubscribers
Primary Key : id
Foreign Key : uname
PageNumber varchar 255
Type varchar 255
Details longtext
Table No :8
Table Name : tbltestimonial
Primary Key : id
Foreign Key : uname
UserEmail varchar 100
Testimonial mediumtext
Status int 11

Table No :9
Table Name : tblusers
Primary Key : id
Foreign Key : uname
Id ini 11 AUTO-INCREMENT
FullName varchar 120
EmailID varchar 100
Password varchar 100
ContactNo char 11
dob varchar 100
Address varchar 255
City varchar 100
Country varchar 100
RegDate timestamp
UpdationDate timestamp ON UPDATE CURRENT-TIME-

STAMP()
Table No : 10
Table Name : tblvechicles
Primary Key : id
Foreign Key : uname
Vechicles Tittle varchar 150
Vechicles Brand int 11
FuelType varchar 100
ModelYear int 6
SeatingCapacity int 11

U Drive System Testing
CHAPTER 4
SYSTEM TESTING
Software testing is the process of executing a program with intension of finding errors in the code.
Testing is the fundamental process of software success. Testing is not a distinct phase in system de-
velopment life cycle but should be applicable throughout all phases.
System testing is the stage of implementation highly aimed at ensuring that the system works ac-
curately and efficiently before the live operation commences. Testing is vital to the success of the
system. The primary objective of testing is to derive a set of tests that has the highest likelihood for
uncovering defects in the software. The system test in implementation should conform that all is
correct and an opportunity to show the users that the system work as expected. It accounts the largest
percentage of technical effort in the software development process. Testing phase in the development
cycle validates the code against the functional specification.
The different software testing strategies used in the project are:

1) Unit testing. In this testing, individual components are tested to ensure that they operate correctly.
It focuses on verification efforts.
2) Integration testing. It is a systematic technique for constructing the program structure. In this
testing, many tested modules are combined into the subsystem which is then tested.
3) System testing is actually a series of different tests whose primary purpose is to fully exercise
computer based system.
4) Black-box testing looks at the available inputs for an application and the expected outputs that
should result from each input.
5) White-box testing looks into the complex inner working of the application; it tests the processes
undertaken and other internal aspects of the application.
Here white box is a test case design method that uses the control structure of the procedural design
to derive test cases. Using the white box testing methods, we derived test cases that guarantee that all
independent paths within a module have been exercised at least once. This testing should:
• Exercise all logical decisions on their true and false sides.

• Execute all loops at their boundaries and within their operational bounds.
• Exercise internal data structures to ensure their validity.

Black box tests the external behavior of the system. Black box testing is done to find incorrect or
missing function, interface errors, errors in external database access, performance errors and initial-
ization and termination error
4.1 Unit Testing
In unit testing each module of the project is individually tested. Unit testing focuses verification
efforts and small unit of software design in the module. This is the first level oftesting. In this testing
of each module and the integration of the overall system is done. This testing is carried out during the
programming stage itself. In this testing step, each module is found to be working satisfactorily as
regard to the expected output from the module. There are some validation checks for the fields. It is
very easy to find error and debug the system.
After coding, each dialog was tested and run individually. All the unnecessarily coded statements
were removed and it was endured that all the functionalities worked as expected. Any logical errors
found were corrected. In this project all the modules are tested. In this the validation process is done.
If the username or password in the login is not correct, the validations such as password is not valid
or username is not valid etc. are occurred. Also in the registration process the validations can occur.
If the e-mail id is not in the correct format, it will display an error in that page. So the unit testing is
an important testing method.
The specification states what the program should do and how it should perform under various condi-
tions used. The test cases are developed for processing. By examining the result, the performance of
the program according to the specified requirements can be determined. Test cases are developed, that
will result in the execution of every instruction on the program or module.
4.2 Integration Testing
Integration testing is the phase in software testing in which individual software modules are combined
and tested as a group. It occurs after unit testing and before system testing. Integration testing takes as
its input modules that have been unit tested, groups them in larger aggregates, applies tests defined in
an integration test plan to those aggregates, and delivers as its output the integrated system ready for
system testing.Integration testing is a systematic testing for constructing the program structure, while
at the same time conducting tests to uncover errors associated within the interface. The objective is
to do unit test as a whole. Here correction is difficult because the vast expenses of the entire program
complicate the isolation of causes. Thus in the integration testing step, all the errors uncovered are
corrected for the next testing steps. In this project the three applications are tested for proper

communication between them. Logging client and Log monitor has to exchange the half upload tags
to generate the upload tag. Log monitor should also store the keys received from the logging client.
Logging client and Logging cloud has to communicate for the storage of the upload tag, delete tag
and batches.
4.3 System Testing
It is the final testing method, where all the modules are run as a whole. Here testing is done whether
the different user criteria are met or not. And whether all the functionalities as proposed earlier are
provided or not. By using the test plans all inputs and outputs are tested. After that I ensured that the
system is satisfying all the requirements. The whole system is tested to ensure that the three applica-
tions work properly. The three applications have to work together as a single unit.
On clicking the start logging button of Logging client the log files have to be retrieved from the system
and this application have to communicate with the Log Monitor for the exchange of half upload tags.
The records have to be encrypted and they are to be uploaded to the Logging cloud. The process has to
repeat after the specified time interval for the new updates of log records.
During the monitoring process the Log monitor have to request for the log records from the Logging
cloud and each record is verified to find that the data is secure. On batch deletion the Log monitor
request for delete tag from the Logging client and sends the delete tag to the Logging cloud for the
deletion of a particular batch.
4.4 Test Reports
The functionalities of each module of the system are tested.
4.4.1. Unit Testing for User Login
Unit: Admin & User Login
Sl Input/Procedure Expected Result Actual Result Pass/Fail

No:
1 Correct value for user- Login is successful & Same as excepted Pass
name & password for user home page is dis-
user play
2 Correct value for user- Login is successful & Same as excepted Pass
name & password for admin home page is
admin display
3 Incorrect value for user- Login failure is reported Same as excepted Pass
name & password
4 When password entry is It should encrypt and Same as excepted Pass
made display as “*”

U Drive System Implementation
CHAPTER 5
SYSTEM IMPLEMENTATION
5.1 Introduction
Implementation is the stage of the project where the theoretical design is turned into a working sys-
tem. At this stage the main work load, the greatest upheaval and the major impact on the existing
system shifts to the user department. If the implementation is not carefully planned and controlled, it
can cause chaos and confusion.
Implementation includes all those activities that take place to convert from the old system to new
system. The new system may be totally new, replacing an existing manual or automated system or it
may be a major modification to an existing system. Proper implementation is essential to provide a
reliable system to meet the organization requirements. Successful implementation may not guarantee
improvement in the organization using the new system, but improper installation will prevent it.
The implementation stage involves the following tasks:
● Careful planning.
● Investigation of system and constrains.
● Design of methods to achieve the changeover.
● Training of staff in the changeover phase.
● Evaluation of the changeover method.
The method of implementation and the time scale to be adopted are found out initially. Next the sys-
tem is tested properly and the same time users are trained in the new procedures.
5.2 Implementation Procedures
Implementation of software refers to the final installation of the package in its real environment, to
the satisfaction of the intended users and the operation of the system. In many organizations someone
who will not be operating it, will commission the software development project. In the initial stage,
they doubt about the software but we have to ensure that the resistance does not built up as one has
to make sure that.

U Drive System Implementation
● The active user must be aware of using the system

● Their confidence in the software is built up.
● Proper guidance is imparted to the user so that he is comfortable in using the application.
Before going ahead and viewing the system, the user must know that for viewing the result, the server
program should be running in the server. If the server object is not up running on the server, the actual
processes won’t take place.
5.3 Implementation Plan
Implementation includes all those activities that take place to convert from the old systemto the new
one. The new system may be totally new, replacing an existing manual or automated system. Proper
implementation is essential to provide a reliable system to meet organization requirements Success-
ful implementation may not guarantee improvement in the organization using the new system, but
improper installation will prevent it.
The process of putting the developed system in actual use in called system implementation. This
includes all those activities that take place to convert from old system to the new system. The system
can be implemented only after through testing is done and if it is found to be working according to the
specifications. The system personal checks the feasibility of the system. The implementation stages
involve the following tasks.
● Investigation of system and constraints.

● Design of method to achieve the changeover.
● Training of the staff in the changeover phase.
● Evaluation of the changeover method.
The newly proposed system is implemented after the successful testing of the system.
5.4 Post Implementation
The final step of the systems approach recognizes that implemented solution can fail to solve the
problem for which it was developed. The results of implementing a solution should be monitored
and evaluated .This is called post implementation review process, since the success of a solution is
reviewed after it is implemented

U Drive System Maintenance and Enhancement
CHAPTER 6
SYSTEM MAINTENANCE AND ENHANCEMENT
6.1 Introduction
System maintenance is the modification of the system after delivery to correct faults, to improve
performance or other attributes. A system should be created whose design is comprehensive and
farsighted enough to serve current and projected user for several years to come. Part of the analyst’s
expertise should be in projecting what those needs might be in building flexibility and adaptability
into the system.
The better the system design, the easier it will be to maintain and the maintenance costs is a major
concern, since software maintenance can prove to be very expensive. It is important to detect software
design errors early on; as it is less costly than errors remain unnoticed until maintenance is necessary.
Maintenance is performed most often to improve the existing software rather than to respond to a
crisis or system failure. As user requirements change, software and documentation should be changed
as part of the maintenance work.
Mainatenance accounts for 50-80 percent of the total system development .To put maintenance in
its proper percepcitve requires considerable skill and experience and is an important and ongoing
aspect of system development.Maintenance demands more orientation and training than any other
programming activities.The environment must recognize the names of the maintenance programmer
for tools,methods and training,Maintenance involves the software industry captive ,typing up the
system resources.It means restoring something to its original condition.Maintenance involves a wide
range of activities including correcting,coding and design errors,updating documentation and test
data and upgrading user support.
Maintenance is done after the successful implementation.Maintenance is continued till the product is
reenginered or deployed to another platform.Maintenance is also doen based on fixing the problems
reported,changing the interface with other software or hardware enhancing the software.The results
obtained from the evaluation process help the organization to determine whether its information sys-
tems are effective and efficient or otherwise. The process of monitoring, evaluating, and modifying of
existing information systems to make required or desirable improvements may be termed as System
Maintenance

For the purpose of convenience, maintenance may be categorized into three classes,
namely:
i. Corrective
ii. Adaptive
iii. Perfective
iv. Predictive
6.1.1. Corrective Maintenance
This type of maintenance implies removing errors in a program, which might have crept in the system
due to faulty design or wrong assumptions. Thus, in corrective maintenance, processing or perfor-
mance failures are repaired.
6.1.2. Adaptive Maintenance
In adaptive maintenance, program functions are changed to enable the information system to satisfy
the information needs of the user. This type of maintenance may become necessary because of orga-
nizational changes which may include:
a) Change in the user‘s procedures,

b) Change in user objectives, goals, policies, etc.
c) Change in forms,
d) Change in information needs of different users.
e) Change in system controls and security needs, etc.
6.1.3Perfective Maintenance
Perfective maintenance means adding new programs or modifying the existing programs to enhance
the performance of the information system. This type of maintenance undertaken to respond to
user’s additional needs which may be due to the changes within or outside of the organization. Out-
side changes are primarily environmental changes, which may in the absence of system maintenance,
render the information system ineffective and inefficient.
These environmental changes include:

a) Changes in governmental policies, laws, etc.,

b) Economic and competitive conditions, and
c) New technology.
6.1.4. Predictive maintenance (PdM)
Techniques help determine the condition of in-service equipment in order to predict when main-
tenance should be performed. This approach offers cost savings over routine or time-based pre
ventive maintenance, because tasks are performed only when warranted.The main value of Predicted
Maintenance is to allow convenient scheduling of corrective maintenance, and to prevent unexpected
equipment failures. The key is “the right information in the right time”. By knowing which equip-
ment needs maintenance, maintenance work can be better planned (spare parts, people etc.) and what
would have been “ unplanned stops ” are transformed to shorter and fewer “ planned stops ”, thus
increasing plant availability. Other advantages include
• Increased equipment lifetime

• Increased plant safety
• Fewer accidents with negative impact on environment
• Optimised spare parts handling.

U Drive Conclusion
CHAPTER 7
CONCLUSION
“U Drive” is a car rental website that is used to rent a car. Here user has to login to book a car. The
user can search for cars easily and book. For bookings, the user hasto provide information such as
booking dates and text message. All car details are provided and it also includes Car’s feature and
Overview.This site makes customers easy for car rental.
7.1 Future Enhancements
Enhancements are the perquisite for development of a system. Every existing system has proposed
enhancements which make it better and easier to use and more secure.The enhancements that have
been proposed for this system are listed here:
● This website can provide second hand vehicles for sale.
Currently the system allows the users to rent a car . The user can rent a car based on its efficiency,
performance, effort, or cost. This new feature will allow the users to buy a second hand car based
on its efficiency, performance and cost.
● This website can provide services for the cars
Car services are a fundamental part of looking after your vehicle. This service is not only help your
car run at its optimum, It makes your vehicle more efficient which could save you money and be
safer to drive

U Drive Bibliography
CHAPTER 8
BIBLIOGRAPHY
Books:
1. Web Programming Using PHP

Binu M.B
Amala Devi V.C
2. Web Programming with HTML5, CSS,Ad JavaScript
John Dean
3. PHP The Complete Reference
Steven Holzner
4. PHP Reference: Beginner to Intermediate PHP5
Mario Lurig
Websites:
1. www.homeandlearn.co.uk/php/php.html
2. html.net/tutorials/php/
3. php.net/manual/en/tutorial.php
4. www.tutorialspoint.com/php/
5. www.w3schools.com/php

U Drive Appendix
CHAPTER 9
APPENDIX
9.1 Appendix A: Screenshots
9.1.1 System Home Page

U Drive Appendix

U Drive Appendix
9.1.2 Login Page
9.1.3 Sign up Page

U Drive Appendix
9.1.4 User Page
9.1.5 User Profile Page

U Drive Appendix

U Drive Appendix
9.1.6 User Password Change Page

U Drive Appendix
9.1.7 User Booking Page

U Drive Appendix
9.1.8 User Testimonial Pages

U Drive Appendix

U Drive Appendix
9.1.9 Car Details Page

U Drive Appendix

U Drive Appendix
9.1.10 Admin Login Page
9.1.11 Admin Dashboard Page

U Drive Appendix
9.1.12 Admin Brand

U Drive Appendix
9.1.13 Admin Vechicles Page

U Drive Appendix
9.1.14 Admin Manage Booking Pages

U Drive Appendix
9.1.15 Admin Manage Testimonials Page
9.1.16 Admin Manage Contact Us Page

U Drive Appendix
9.1.17 Reg User Page
9.1.18 Admin Manage

U Drive Appendix
9.1.19 Admin Contact Page
9.1.20 Admin Change Passord and Logout Page

U Drive Appendix

Mini Project

Uploaded by

Copyright:

Available Formats

Mini Project

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mini Project

Uploaded by

Copyright:

Available Formats

U Drive Introduction

1.1 Brief Introduction about the Project

College of Applied Science, Ayroor 1

1.2 Module Descriptions

iv. Profile Management

Users can manage their profile. The sub modules are:

User can view their profile.

Administrator can delete the cars based on the stock.

College of Applied Science, Ayroor 2

Admin has privileges to add a user directly by providing the details.

Administrator has a right to delete a user.

Users can search for a particular car in the list by name.

College of Applied Science, Ayroor 3

1.3 Scope and Objectives of the Project

College of Applied Science, Ayroor 4

2.1 Feasibility Study

2.1.1 Technical Feasibility

2.1.2 Economical Feasibility

2.1.3 Operational Feasibility

College of Applied Science, Ayroor 5

2.2 Requirement Analysis

College of Applied Science, Ayroor 6

2.3 Existing System

2.4 Proposed System

(a) Advantages of the Proposed System

● Give solutions to the current system problems.

(b) Features of the Proposed System

The various features of proposed system are as follows:

● The maximum security ensured.

College of Applied Science, Ayroor 7

2.4.1 Requirement Specification

The Requirement Specification for the system can be as:

Sl No Requirment Essential or De- Description of the Remark

College of Applied Science, Ayroor 8

2.4.2 Hardware Specification

Processor : Intel core i5 10th generation

2.4.3 Software Specification

Operating System : Windows

2.4.4 Software Description

College of Applied Science, Ayroor 9

PHP 6 and Unicode

College of Applied Science, Ayroor 10

College of Applied Science, Ayroor 11

Introduction to the MySQL PHP API

PHP’s mysqli Extension

College of Applied Science, Ayroor 12

3.1 Data Flow Diagram

College of Applied Science, Ayroor 13

3.1.1 Basic DFD Symbols

A process represents transformation where incoming data Flows are

A data store is a repository of data that is to be stored for Use by a one

A source or sink is person or part of an organization that enters or re-

College of Applied Science, Ayroor 14

Administrator U Drive Administrator

Fig 1 : Level 0 DFD

College of Applied Science, Ayroor 15

Fig 3 : Guest User Level

User User home Contact us User home

Fig 4 : User Level