Professional Documents
Culture Documents
CRS Docsx
CRS Docsx
INTRODUCTION
CHAPTER: 1
INTRODUCTION
The project entitled with “Rent a Car” is done to make the manual process easier by making it a
computerized system for booking and maintaining the process. Providing the facility to the users that
can make bookings for car on rent from the showroom. The rent a car showroom manager can issue
desired vehicles on rent to the customer when a customer approaches the showroom manager for
vehicles. This process is computerized and the details of the customer who hire the vehicle are stored in
the system. The customer can view the details about the available vehicles in the showroom and can
choose any vehicle from them based on is requirements.
The transactions related to the customers are maintained manually. Updating, changes in details is a
tedious task. All these are to be automated and an application is required to relate all of them relatively
and logically. So that the current system can be replaced and accepted without major changes and
problems.
This is an automated application software for car booking. This application is used in the car rental
company for managing the car booking efficiently. The primary project goal consist of providing a user
friendly and time efficient application for both the customers and the company employees .The
employees of the company are able to keep the track of the renting process easily .To keep the whole
data into a database system . It not only provides a quick access to the desired data but also it helps to
organize and store the data easily.
1.4 Objective:
Administrator is power user. He has the power to verify the data entered by the user, processing of data
and provide appropriate solutions. Any person who have been authorized by the administrator. An
authorized user should have a user name and password to access detailed information from the site
excluding for accessing general information in shared, public pages. User is the person who gets the full
benefits of this application. By introducing the new system we have been organized some striking
felicities.
SYSTEM ANALYSIS
CHAPTER: 2
SYSTEM ANALYSIS
2.1 INTRODUCTION
System analysis is the process of gathering and interpreting facts and diagnosing problems and
using the information improvement on the system. The system analysis is the problem solving
activity that requires intensive communication between the user and the system development
process. The system is studied to the minute, detailed and analyzed. System is viewed as a whole
and inputs to the system are identified. The outputs from the organization are traced to the various
processing that the input phased.
A detailed study of the process must be made by various techniques like interviews, questioners
etc. The data collected by these resources must scrutinize to arrive at a conclusion. The conclusion
is an understanding of how the system functions. This system is called existing system. Now the
existing system is subjected to close study and the problem areas are identified. The designer
functions as a problem solver and tries to sort out difficulties that enterprise fact. The solutions
are given as proposal.
Preliminary study is the process of gathering and interpreting facts using the information for
further studies of the system Preliminary study is a problem solving activity that requires intensive
communication between system users and system developers. It does the valuable feasibility
studies. In these studies, a rough of the system activities can be obtained from which the decision
about the strategies tube followed for effective system study and analysis can be taken.
Information about the customer and others records are stored in files are entered manually which includes
bulk of paper works where retrieving a single entity becomes a difficult task. Data entry, reports, receipts
etc. are all manually done. It is very difficult to keep all data in records and it is a time consuming
process. Manipulation or updating retrieval of existing information is tough and it requires more
manpower and time.
The existing system needs a number of registers for handling the records .This leads to
tedious manual labor highly time consuming.
Cost consumption.
Low accuracy.
Maintenance is a huge problem.
Document preparation and accounting are time consuming and difficult.
Redundancy of records may occur.
Updating, changes in details is a tedious task.
Performance is not achieved up to the requirements.
Details are stored in papers
Taking into account the various drawbacks that inherit in the existing system, a new system is proposed
which eliminated them. A computerized system is adopted to resolve these problems.
In the previous system, Details are stored manually in papers, to share the details between
employees was a financial drawback. Updating in the details is a tedious task. In the proposed system
the record keeping is easier and enormous space is available to store data.
The data can be retrieved more quickly. Modifications can be done more accurately
and correctly.
In any project, feasibility analysis is very important stage: here the project is checked for its
feasibility. Any project may face scarcity in resources, time or work force. Hence all these are to
be studied in detail and a conclusion should be drawn whether the project under consideration is
feasible or not. This analysis is a test of the proposed system, regarding the working, impact on
user and client and resource management. Feasibility and risk involved are inversely related to
each other. The main aim of the feasibility is to test the technical, social and economic feasibility
of the project.
Technical feasibility is the most important of all types of feasibility analysis. An idea from the outline
design to system requirements in terms of inputs, outputs, files and procedures is drawn and the type of
hardware, software and the methods required for running the system are analyzed. Keeping in mind the
above considerations, the resource availability at this company was observed. It was found that the
company has the sufficient resources to develop the current project; hence the system is technically
feasible. The assessments of technical feasibility centers on the existing system and to what extend it
can support the proposed addition. This was based on an outline design of system requirements in turns
of inputs, files, programs, procedures.
It is considered with specifying the equipment and software that will successfully support the
task required. It is the configuration of the system that is more important than the actual make of
hardware. The configuration should show the system requirements, how many workstations are
provided, how these units should be able to operate and communicate, what input and output speeds
should be able to operate and communicate, what input and output speeds should be achieved and at
what print or screen quality.
Operational feasibility is concerned with the working of the system after its installation. The
company has a good record of development, installation and maintenance of system for its clients. So
this system can be installed in the client environment and the company will help in the maintenance of
the system in future. People are inherently resistant to change, and computer have been known to
facilitate change. The system is designed in a user friendly manner. Any layman with basic computer
knowledge can use the system, with a little bit of training. Thus the system can manage by the existing
staff itself after a short period of training. The system was developed user friendly, needless training and
improves the working environment. The system RENT A CAR A MANAGEMENT SYSTEM is very
much user friendly, so that even user with minimum computer knowledge can operate the system easily.
Only very little effort is required to educate and train the user.
Economic feasibility is the most frequently used method for evaluating the effectiveness of a
candidate system. More commonly known as cost or benefit analysis, the procedure is to determine the
benefit and saving that are expected from a candidate system and compare them with the term of time
by automating the process o report generation This is an ongoing process for improving the accuracy at
each phases of SDLC. A system that can be developed technically and that will be used if installed must
be a good investment for the organization. Hence this package is economically feasible. This is judged
by comparing the development cost against the income or benefit analysis, which is the basis for
economic justification of a system. In terms of benefits, we have to consider both tangible and intangible
benefits. Here it is seen that no new software and hardware is needed for the development of the system.
Thus, this project is economically feasible for development in this company.
This establishment and use of sound engineering principles in order to obtain economically
developed software that is reliable and works efficiently on real machines is called software
engineering.
Software process is the way in which we produce the software. Apart from hiring smart,
knowledgeable engineers and buying the latest development tools, effective software
development process is also needed, so that engineers can systematically use the best technical
and managerial practices to successfully complete their projects.
A software life cycle is the series of identifiable stages that a software product undergoes during
its lifetime. A software lifecycle model is a descriptive and diagrammatic representation of the
software life cycle. A life cycle model represents all the activities required to make a software
product transit to life cycle phases. It also captures the order in which these activities are to be
taken.
There are various Life Cycle Models to improve the software processes
1. Waterfall Model
2. Prototype Model
4. Evolutionary Model
5. Spiral Model
Waterfall approach was first SDLC Model to be used widely in software engineering to ensure
success of the project. In “The Waterfall” approach, the whole process of software development
is divided into separate phrases. In this Waterfall model, typically, the outcome of one phrase acts
as the input for the next phase sequentially.
The following illustration is a representation of the different phrases of the Waterfall Model
• System Design – The requirement specification from first phase are studied in this phase
and the system design is prepared. This system design helps in specifying hardware and
system requirements and helps in defining the overall system architecture
• Implementation – With inputs from the system design, the system is first developed in
small programs called units, which are integrated in the next phase. Each unit is developed
and tested for its functionality, which is referred to as Unit Testing.
• Deployment of system – Once the functional and non-functional testing is done; the
product is deployed in the customer environment or released into the market.
• Maintenance – There are some issues which comes up in the client environment. To fix
those issues, patches are released. Also to enhance the product some better versions are
released. Maintenance is done to deliver these changes in the customer environment.
All these phases are cascaded to each other in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases. The next phase is started only after the defined
set of goals are achieved for previous phase and it is signed off, so the name “Waterfall Model”.
In this model, phases do not overlap.
SYSTEM DESIGN
CHAPTER 3
SYSTEM DESIGN
3.1 INTRODUCTION
System design is the solution to the creation of a new system. This is the important aspect made
up of several steps. System design is the process of developing specifications for a candidate
system that meet the criteria established in the system analysis. Major step in system design is the
preparation of the input forms and the output reports in a form applicable to the user.
The main objective of the system design is to use the package easily by a computer operator.
System design is the creative act of invention, developing new inputs, a database, off-line files,
method, procedure and output for processing business to meet an organization objective. System
design built information gathered during the system analysis.
The complete, efficient and successful system should provide the following in succession:
• Where we have to go
If the project is to be successful, we will need answer these questions. The answer of these
questions is schema manner and is known as system design. A systematic manner will be followed
so as to achieve beneficial result at the end. It involves starting with a vague idea and ultimately
developing it up into a useful system. The design phase is transition from a user oriented to a
document oriented to the programmers. Software report can be broken into a series of steps
starting with the basic ideas and ending with the finished projects.
Database design is the process of producing a detailed data model of a database. This logical data
model contains all the needed logical and physical design choices and physical storage parameters
needed to generate a design in a Data Definition Language, which can then be used to create a
database. A fully attributes for each entity.
The term database design can be used to describe many different parts of the design of an overall
database system. Principally, and most correctly, it can be thought of as the logical design of the
base data structures used to store the data. In the relational model these are the tables and views.
In an object database the entities and relationships map directly to object classes and named
relationships. However, the term database design could also be used to apply to the overall process
of designing, not just the base data structures, but also the forms and queries used as part of the
overall database application within the database management system.
NORMALIZATION
The process of normalization is concerned with the transformation of the conceptual schema to a
computer represent able form. Normalization reduces the redundancies and anomalies.
First normal form does not allow multi valued and composite valued attributes. It states that the
domain of an attribute must include only atomic values and that value of any attribute in a table
must be single value from the domain of that attribute.
In second normal form, for relation where primary key contains multiple attributes, on key attribute
should not be functionally dependent on a part of the primary key.
Database designs also include ER (Entity relationship model) diagrams .An ER diagram is a
diagram that helps to design database in an efficient way .Attributes in ER diagram are usually
modeled as an oval with the name of the attribute , linked to the entity or relationship that contains
the attribute. Within the relational model the final step can generally be broken down into 2 further
steps that of determining the grouping oif information within the system , generally determining
what are the basis objects about which information, is being stored , and then determining the
relationships , or objects .This step nis not necessary with an object database .
• Entities, which are represented by rectangles. An entity is an object or concept about which
you want to store information. A weak entity is an entity that must defined by a foreign
key relationship with another entity as it cannot be uniquely identified by its own attributes
alone.
Entity
• Relationships, which are represented by a diamond shapes, show how to entities share
information in the database. In some cases entities can be self-linked .For example,
employees can supervise other employees.
Relationship
• Attributes, which are re[presented by ovals .A key attribute is the unique , distinguishing
characteristic of the entity .For example , employee’s social security number might be the
employee’s key attribute .
Attribute
• Connecting lines, solid lines that connect attributes to show the relationships of entities in
the diagram.
TABLE DESIGN
TABLE 1: cart
TABLE 2: customers
TABLE 3: items
TABLE 4: orders
A data flow diagram (DFD) is a graphical representation of the “flow” of data through an
information system, modeling its process aspects. Often they are a preliminary step used to create
an overview of the system which can later be elaborated. DFDs can also be used for the
visualization of data processing. A DFD shows what kinds of information will be input to and
output from the system, where the data will come from and go to, and where the data will be
stored. It does not show information about the timing of processes, or information about whether
processes will operate in sequence or in parallel.
Data Flows
Data flows show the passage of data in the system are represented by the lines joining system
components .An arrow indicate the direction of flow and the line is labeled by name of the data
flow.
• An arrow identifies data flow, data in motion .It is a pipeline through which information flows.
• A circle or bubble represents a process at transforms incoming data flows into outgoing data
flows
Note that a DFD describe what data flow (logical) rather than they are processed, so it does not depend
on hardware, software and data structure or file organization.
2. The direction of flow is from top to bottom and from left to right
3. When a [process is explored into lower level details they are numbered
4. The name of data stores sources and destinations are written in capital letters.
UML stands for Unified Modelling Language which is used in object oriented software
engineering. Although typically used in software engineering it is a rich language that can be used
to model an application structures, behavior and even business processes. There are 14 UML
diagram types to help you model this behavior.
Activity diagrams represent workflows in a graphical way. They can be used to describe business
workflow or the operational workflow of any component in a system. Sometimes activity
diagrams are used as an alternative to State Machine Diagrams.
Sequence diagrams in UML show how objects interact with each other and the order those interactions
occur. It’s important to note that they show the interactions for a particular scenario.
The processes are represented vertically and interactions are show as arrows.
A Use Case is a description of a system’s behavior from user’s standpoint. For system developers,
that is a valuable tool. A Use Case diagram is a graph of actors, a set of Use Case enclosed by a
system boundary, communications and associations between the actors. Use case model
represents the functionality of a system or a class manifested to external interaction with the
system.
Use cases: A use case describes a sequence of actions that provide something of measurable value to
an actor and is drawn as a horizontal ellipse.
Actors: An actor is a person, organization, or external system that plays a role in one or more interactions
with yours system.
Associations: Associations between actors and use cases are indicated in use case diagrams by
solid lines. An association exists whenever an actor is involved with an interaction described by
a use case. Associations are modeled as lines connecting use cases and actors to one another, with
an optional arrow head on one end of the line. The arrow head is often used for indicating the
direction of the initial invocation of the relationship or to indicate the primary actor within the use
case.
In the input design, user-oriented inputs are converted into a computer based system format. It
also includes determining the record media, method of input, speed of capture and entry on to the
screen. Online data entry accepts commands and data through a keyboard. The major approach to
input design is the menu and the prompt design. In each alternative, the user’s options are
predefined. The data flow diagram indicates logical data flow, data stores, source and destination.
Input data are collected and organized into a group of similar data. Once identified input media
are selected for processing. Once required data are identified appropriated input are identified.
The input medias used in this project are keyboard and mouse.
It is the part of overall system design. The goal of the output design is to capture the output and
get the data into format suitable for the computer. Data flow diagram identifies the data tone
captured and the output to the system. One of the important features of an information system for
users is the output it produces. Output is the information delivers to the users delivered to the
users through the information system. Without quality output the entire system appears to be
unnecessary that users will avoid using it. Users generally merit the system solely by its output in
order to create the most useful output possible. One works closely with the user through an
interactive process, until the result is considered to be satisfactory.
SYSTEM ENVIRONMENT
CHAPTER-4
SYSTEM ENVIRONMENT
An important matter in building an application is selecting hardware and software. The hardware
drives the software to facilitate solutions. Factors like cost performance and reliability etc are
taken into consideration during the purchase of the hardware component for any computerized
system.
4.1 INTRODUCTION
An operating environment is usually not a full operating system but is a form of middleware that
rests between the OS and the application. For example, the first version of Microsoft Windows,
Windows 1.0, was not a full operating system, but a GUI laid over DOS albeit with an API of its
own. Similarly, the IBM U2 system operates on both Unix/Linux and Windows NT. Usually the
user interface is text-based or graphical, rather than a command-line interface (e.g., DOS or the
Unix shell), which is often the interface of the underlying operating system.
The system requirement specification is a technical specification of requirement for the product.
The goal of the system requirement definition is to completely specify the technical requirements
for the software product in a concise and unambiguous manner. A software requirements
specification (SRS) is a description of a software system to be developed. It lays out functional
and non-functional requirements, and may include a set of use cases that describe user interactions
that the software must provide. Software requirements:
Platform : WAMP
The application must inform the user with proper message when there is an error in data entry or when
an activity is successfully completed.
This describes the logical and physical characteristics of each interface between the software product
and hardware components of the system.
In software engineering, the terms front end and back refers to the separation of concerns between
the presentation layer (front end), and the data access layer (back end) of a piece of software, or
the physical infrastructure or hardware. In the client-server model, the client is usually considered
the back end, even when some presentation work is actually done on the server.
PHP is a dynamically typed general purpose scripting language which can be embedded in HTML
pages. It was designed in 1995 for implementing dynamic web pages, its name initially standing
for Personal Home Pages. PHP now stands for the recursive acronym PHP: Hypertext
Preprocessor. While predominantly used for server-side scripting PHP can be used for writing
command line scripts and client-side GUI applications. It may also be embedded into host
applications to provide them with scripting functionality. The main implementation of PHP is free
open source software. This provides the de facto definition of the syntax and semantics for the
language since there is no formal specification. While the end user interface and extensions API
for the PHP interpreter are well documented [2, 10], scant documentation exists for the internals
of the parser and the Zend engine (which interprets scripts). The lexical analyzer is defined using
a Flex description of 2000 lines, and the parser a Bison specification of 900 lines. It is difficult to
extract any formal specification from either source file because of: unnecessary redundancy and
poor structuring of the grammars; convoluted rules which attempt to enforce static checks;
embedded semantic actions trying to ensure associativity is appropriately maintained at certain
points during parsing; and the requirement for tight coupling between the lexical analyzer and
parser due to in-string syntax which is not amenable to processing using the traditional lexical
analysis and parser interface.
MY-SQL SERVER
• MySQL is free and open-source software under the terms of the GNU General Public
License, and is also available under a variety of proprietary licenses. MySQL was owned
and sponsored by the Swedish company MySQL AB, which was bought by Sun
Microsystems (now Oracle Corporation). In 2010, when Oracle acquired Sun, Widenius
forked the open-source MySQL project to create MariaDB.
• MySQL is a component of the LAMP web application software stack (and others),
which is an acronym for Linux, Apache, MySQL, Perl/PHP/Python. MySQL is used by
many database-driven web applications, including Drupal, Joomla, phpBB, and
WordPress. MySQL is also used by many popular websites, including Facebook, Flickr
Deployment
MySQL can be built and installed manually from source code, but it is more commonly installed
from a binary package unless special customizations are required. On most Linux distributions,
the package management system can download and install MySQL with minimal effort, though
further configuration is often required to adjust security and optimization settings.
LAMP software bundle, displayed here together with Squid. Though MySQL began as a low-end
alternative to more powerful proprietary databases, it has gradually evolved to support higherscale
needs as well. It is still most commonly used in small to medium scale single-server deployments,
either as a component in a LAMP-based web application or as a standalone database server. Much
of MySQL's appeal originates in its relative simplicity and ease of use, which is enabled by an
ecosystem of open source tools such as phpMyAdmin. In the medium range, MySQL can be
scaled by deploying it on more powerful hardware, such as a multiprocessor server with gigabytes
of memory.
Backup software
mysqldump is a logical backup tool included with both community and enterprise editions of
MySQL. It supports backing up from all storage engines. MySQL Enterprise Backup is a hot backup
utility included as part of the MySQL Enterprise subscription from Oracle, offering native InnoDB hot
backup, as well as backup for other storage engines.
XtraBackup is an open-source MySQL hot backup software program. Features include hot,
nonlocking backups for InnoDB storage, incremental backups, streaming, parallel-compressed
backups, throttling based on the number of I/O operations per second, etc.
Oracle MySQL offers a high availability solution with a mix of tools including the MySQL router and
the MySQL shell. They are based on Group Replication, open source tools.
The Windows operating system (Windows OS) for desktop PCs are more formally called
Microsoft Windows and is actually a family of operating systems for personal computers.
Windows dominates the personal computer world, running, by some estimates, more than 90
percent of all personal computers – the remainder running Linux and Mac operating systems.
Windows provides a graphical user interface (GUI), virtual memory management, multitasking,
and support for many peripheral devices. In addition to Windows operating systems for personal
computers, Microsoft also offers operating systems for servers and mobile devices.
Windows 10
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
system. At this stage the main workload, 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.
• Careful planning
• Investigation of system and constrains
• Design of methods to achieve the changeover phase
• Training of staffs 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 system is tested properly and the same
time users are trained in the new procedures.
5.2CODING
CODING STANDARDS
Once the system was tested, the implementation phase started. Crucial phase in the system
development life cycle is successful implementation of new system design. Implementation
simply means converting new system design into operation. This is the moment of truth the first
question that strikes in everyone’s mind that whether the system will be able to give all the desired
result as accepted from system. Prior to starting the project implementation process project must
have successfully completed the project evaluation process and the project has been approved for
implementation. The project evaluation process includes performing a needs analysis and
architecture review. The implementation phase of the software design consists of different tasks
to be done sequentially for obtaining the desired result.
IMPLEMENTATION METHODOLOGY
Login Page
<?php
session_start();
?>
<!DOCTYPE html>
<html lang="en">
<head>
<style>
#header {
position: absolute;
height:15%;
width:95%;
margin-left:2%;
text-align:center;
background-color: #0000cc;
font-family:impact;
font-size: 50px;
color:azure;
border-radius:12px;
line-height: 100px;
.topnav {
position: absolute;
top:18%;
overflow: hidden;
background-color: #0000cc;
border-radius: 10px;
width: 95%;
margin-left: 2%;
font-family: verdana;
.topnav a {
float: left;
display: block;
color:azure;
text-align: center;
text-decoration: none;
.topnav a:hover {
background-color: #ddd;
color: black;
#formdiv {
position:absolute;
top:30%;
left:25%;
height:30%;
width:50%;
background-color: #0000ff;
color:white;
padding:40px;
border-radius:5px;
.requiredmsg {
color:red;
.inputs {
margin: 8px 0;
display: inline-block;
border-radius: 4px;
#uname {
position:relative ;
top:30%;
width:89.5%;
left:.5%;
right:10%;
#psw{
position:relative;
top:60%;
width:89.5%;
left:.5%;
right:10%;
#submit {
position:relative;
width:100%;
left:-.5%;
//right:-5%;
padding:8px;
border-radius:5px;
color:white;
font-size:13px;
</style>
</head>
<body>
<?php
//$uname = $_POST["uname"];
//$passw = $_POST["psw"];
$err1=$err2="";
if (isset($_POST["submit"])) {
$k = $_POST["uname"];
$l= $_POST["psw"];
if (empty($_POST["uname"])) {
$err1 = "missing";
//header("location:login.php");
if (empty($_POST["psw"])) {
$err2 ="missing";
cont($k,$l);
function cont($uname,$passw){
// Check connection
if ($conn->connect_error) {
$sql = "select fusername , fpassword , previlege from login where fusername='".$uname."' &&
fpassword='". $passw."';";
$result = $conn->query($sql);
if ($result->num_rows == 1) {
$_SESSION['login']=1;
$_SESSION['uname']=$uname;
header("location:dashboard.php");
} else {
$conn->close();
?>
Rent A Car
</div>
<div class="topnav">
<a href="index.php">Home</a>
<a href="about.php">About</a>
<a href="contact.php">Contact</a>
<a href="login.php">Login</a>
<a href="signup.php">Signup</a>
</div>
<div id="formdiv">
?>" >
<label for="psw" > Password </label><span class="requiredmsg"> <?php echo "*".$err2; ?></span>
</form>
</div>
</body>
</html>
Regisration
<!DOCTYPE
html>
<html
lang="en">
<head>
<meta
name="viewport
"
content="width=
device-width,
initial-scale=1">
<style>
#header {
position:
absolute;
height:15%;
width:95%;
margin-
left:2%;
text-
align:center;
background-
color: #0000cc;
font-
family:impact;
font-size:
50px;
color:azure;
border-
radius:12px;
line-height:
100px;
.topnav {
position:
absolute;
top:18%;
overflow:
hidden;
background-
color: #0000cc;
border-radius:
10px;
width: 95%;
margin-left:
2%;
font-family:
verdana;
.topnav a {
float: left;
display: block;
color:azure;
text-align:
center;
padding: 14px
16px;
text-decoration:
none;
.topnav a:hover {
background-
color: #ddd;
color: black;
#formdiv {
position:absolute
top:30%;
left:5%;
height:135%;
width:75%;
background-
color: #0000ff;
color:white;
box-shadow: 0
4px 8px 0
rgba(0, 0, 0, 0.2),
0 6px 20px 0
rgba(0, 0, 0,
0.19);
padding:40px;
border-
radius:5px;
.requiredmsg {
color:red;
.inputs {
padding: 12px
20px;
margin: 8px 0;
display: inline-
block;
border: 1px
solid #ccc;
border-radius:
4px;
font-size:20px;
font-
weight:20px;
font-
family:monospac
e;
label {
color:white;
form input ,
select {
padding: 12px
20px 20px;
margin: 8px 0;
display: inline-
block;
border: 1px
solid #ccc;
border-radius:
4px;
</style>
</head>
<body>
<?php
$uname=$fname
=$lname=$addre
ss=$email=$mob
no=$passw=$uty
peop1=$utypeop
2=$passw1="";
$fnameErr
=$lnameErr=$ad
dressErr=$email
Err=$mobnoErr=
$passwErr=$pass
w1err="";
if(isset($_POST['
submit'])) {
$uname
=$_POST["email
"];
$fname
=$_POST['fname
'];
$lname=$_POST
['lname'];
$address=$_POS
T['address'];
$email=$_POST[
'email'];
$mobno=$_POS
T['mobno'];
$passw=
$_POST["passw"
];
$passw1=$_POS
T["passw1"];
/*
VALIDATION
START */
$valid = 1;
if
(!preg_match("/^
[a-zA-Z
]*$/",$fname)) {
$fnameErr =
white space
allowed";
$valid=0;
if
(!preg_match("/^
[a-zA-Z
]*$/",$lname)) {
$lnameErr =
white space
allowed";
$valid=0;
if(!preg_match('/
^[0-9]{10}+$/',
$mobno)){
$mobnoErr =
"Enter a valid
mobile number";
$valid = 0;
if
(!filter_var($ema
il,
FILTER_VALID
ATE_EMAIL)) {
$emailErr =
"enter a valid
email id";
$valid= 0;
if($_POST["pass
w1"] !=
$_POST["passw"
]){
$passw1err =
"password
mismatch";
$valid= 0;
/*VALIDATION
END */
if($valid==1){
$conn= new
mysqli("localhos
t","root","","crs")
// Check
connection
if ($conn-
>connect_error)
die("Connection
>connect_error);
$prev=4;
$sql =
"INSERT INTO
login
(fusername,fpass
word,previlege)
VALUES
('".$uname."','".$
_POST['passw'].
"',".$prev.");";
$sql1= "insert
into customers
(fname,lname,ad
dress,email,mobn
o,password,lid)
values
('".$_POST['fna
me']."','".$_POS
T['lname']."','".$_
POST['address'].
"','".$_POST['em
ail']."','".$_POST
['mobno']."','".$_
POST['passw']."',
'".$_POST['lno'].
"');";
if($conn-
>query($sql1)) {
if($conn-
>query($sql)) {
echo "<script>
alert('SIGN UP
COMPLETED
SUCCESSFULL
LY');</script>";
$uname=$fname
=$lname=$addre
ss=$email=$mob
no=$passw="";
echo
'<script>window.
location="login.p
hp" </script>';
else {
echo "<script>
alert('Error
signing up');
</script>";
} else {
echo "<script>
alert('Error
signing up');
</script>";
?>
<div id="header"
>
Rent A Car
</div>
<div
class="topnav">
<a
href="index.php"
>Home</a>
<a
href="about.php"
>About</a>
<a
href="contact.ph
p">Contact</a>
<a
href="login.php"
>Login</a>
<a
href="signup.php
">Signup</a>
</div>
<div
id="formdiv">
<form
method="POST"
action="<?php
$_SERVER['PH
<br><label
for="fname" >
first
name</label><br
>
<input
type="text"
name="fname"
value="<?php
echo $fname;
?>" required>
<?php echo
$fnameErr;
?><br>
<label
for="lname">
last
name</label><br
>
<input
type="text"
name="lname"
value="<?php
required> <?php
echo $lnameErr;
?><br>
<?php
$servername =
"localhost";
$username =
"root";
$password = "";
$dbname = "crs";
$conn = new
mysqli($serverna
me, $username,
$password,
$dbname);
// Check
connection
if ($conn-
>connect_error)
die("Connection
>connect_error);
} ?>
<label
for="address" >
address lane
</label><br><br
>
<textarea
name="address"
rows="10"
cols="30"
required> <?php
echo $address;
?>
</textarea>
<?php echo
$addressErr; ?>
<br>
<br><label
for="email"> e-
mail </label>
<br>
<input
type="text"
name="email"
value="<?php
required> <?php
echo $emailErr;
?> <br>
<br><label
for="lno"
>Licencse
ID</label><br>
<input
type="text"
name="lno"
required> <br>
<label
for="mobno"
>mobile
number</label><
br>
<input
type="text"
name="mobno"
value="<?php
echo $mobno;
?>" required>
<?php echo
$mobnoErr;
?><br>
<label
for="passw"> set
password</label
> <br>
<input
type="password"
name="passw"
id="passw"
value="<?php
required> <br>
<label
for="passw1">
confirm
password</label
> <br>
<input
type="password"
name="passw1"
id="passw1"
value="<?php
echo $passw1;
?>"
required><?php
echo $passw1err;
?> <br><br>
<input
type="submit"
id="submit"
value="submit"
name="submit"
>
<form>
</div>
</body>
</html>
Home Page
<!DOCTYPE html>
<html lang="en">
<head>
<style>
#header {
position: absolute;
height:15%;
width:95%;
margin-left:2%;
text-align:center;
background-color:#0000cc;
font-family:impact;
font-size: 50px;
color:azure;
border-radius:12px;
line-height: 100px;
.topnav {
position: absolute;
top:18%;
overflow: hidden;
background-color: #0000cc;
border-radius: 10px;
width: 95%;
margin-left: 2%;
font-family: verdana;
.topnav a {
float: left;
display: block;
color:azure;
text-align: center;
text-decoration: none;
.topnav a:hover {
background-color: #ffffff ;
color:black;
.content {
position: absolute;
top:25%;
width:95%;
height:40%;
margin-left: 2%;
font-size: 20px;
font-family: monospace;
.flex-container {
display: flex;
flex-direction: row;
width:100%;
height:100%;
width: 100%;
height: 100%;
text-align: center;
//line-height: 75px;
font-size: 30px;
height: 100%;
width:100%;
//border-radius: 160px;
.footer {
position: absolute;
bottom: 2px;
height:20%;
background-color:#0000cc;
width: 95%;
border-radius:12px;
margin-left: 2%;
color:azure;
text-align: center;
font-family: verdana;
</style>
</head>
<body>
Rent A Car
</div>
<div class="topnav">
<a href="index.php">Home</a>
<a href="about.php">About</a>
<a href="login.php">Login</a>
<a href="signup.php">Signup</a>
</div>
<div class="content">
<div class="flex-container">
<div><img src="uploads/AUDIQ7.jpg"/></div>
<div><img src="uploads/FORTUNER.jpg"/></div>
<div><img src="uploads/COROLA.jpg"/></div>
<div><img src="uploads/minif.jpg"/></div>
</div>
</div>
<div class="footer">
</div>
</body>
</html>
Validation is the process of evaluating software at the end of the software development to ensure
compliance with software requirements. Testing is a common method for validation. Validation
succeeds when the software functions in a manner that can be reasonably expected by the
customer.
Form data validation comes in a couple different forms. Data can be validated at the field level
when it is entered by the user, and it can be validated at the form level (i.e. all fields) when the
form is submitted or printed. These different types of validation have different, complimentary
purposes and for a complete form design it’s a good practice to use a combination of the two
methods.
The purpose of Field Level Validation is to verify that the input to a single field is entered
correctly. For example, for an e-mail field, the job of the validation script is to make sure the
entered text matches the standard email format, i.e. , two sets of strings separated by an “@”
symbol. The most common way to implement a text pattern test like this is to use a regular
expression. Most of the time validation scripts are used to match input text against a pattern using
a regular expression.
Form level validation is used to ensure all the required form data is filled in, and or to make sure
that any data dependencies between fields are met before the form is submitted.
It is the simplest type of validation. If the user enters a value in any field, then it is valid.
Compare Validator
Range Validator
Range validator checks that the user entry between specified lower and upper boundaries.
Unit testing is a software development process in which the smallest testable parts of an
application, called units, are individually and independently scrutinized for proper operation. Unit
testing can be done manually but is often automated. In computer programming, unit testing is a
software testing method by which individual units of source code, sets of one or more computer
program modules together with associated control data, usage procedures, and operating
procedures, are tested to determine whether they are fit for use.
The goal of unit testing is to isolate each part of the program and show that the individual parts are
correct. A unit test provides a strict, written contract that the piece of code must satisfy.
SYSTEM TESTING
CHAPTER 6
SYSTEM TESTING
6.1INTRODUCTION
Software testing is a critical element of software quality assurance and represents the ultimate
review of specification, design and coding, testing presence an interesting anomaly for the
software engineer.
• A good test case is one that has a probability of finding an as yet undiscovered error.
Testing Principles:
• Testing should begin on a small scale and progress towards testing in large.
Testing phase of system development life cycle will tests system design. Testing of system decides
whether the newly designed system works properly or not. After the development of
documentation manually about the system this stage is checked. And if the system working
properly then it will be considered for implementation and if isn’t then system analyst is informed
to find out generated errors or problems and to find out its solutions. This process is known as
debugging.
Black Box testing also called functional testing, focuses on the functional requirements of the
software. Knowing the specified function that a product designs to perform the test can be
conducted to ensure that each function is fully operational. Black Box tests are carried out to test
that input to function is properly accepted and output is correctly produced. Black Box Testing
treats the software as a black box without any knowledge of internal implementation.
For the proposed system the black box testing ensures the following requirements.
Menu
testing is used to detect errors of the type incorrect or missing functions, interface errors,
errors in data structures or external data base access, initialization and termination errors.
Black Box testing methods include: equivalence partitioning, Boundary value analysis
and specification testing.
This type of testing is also called structural testing, involves checking the actual code following
the control flow and ensuring the validity of the logic involved in the implementation. White Box
Testing is when the tester has access to the internal data structures and algorithms including the
code that implements these.
• Programming portion: For optimizing the speed of execution ,the unwanted portion of the
code are removed
• The structure of each and every web page of the system Test cases:
• Check the validity of the data structures used Check the validity and the effectiveness of the
table design
Through each program work individually, they should work after linking together. This is referred
to as interfacing. Data may be lost across the interface; one module can have adverse effect on
the other subroutines after linking may not do the desired function expected by the main routine.
Integration testing is the systematic technique for constructing the program structure while at the
same time conducting test to uncover errors associated with the interface. Using integrated test
plan prepared in the design phase of the system development as a guide, the integration test was
carried out. All the errors found in the system were corrected for the next testing step.
System Testing is a level of the software testing where a complete and integrated software is
tested. The purpose of this test is to evaluate the system's compliance with the specified
requirements. System testing of software or hardware is testing conducted on a complete,
integrated system to evaluate the system's compliance with its specified requirements. System
testing falls within the scope of black-box testing, and as such, should require no knowledge of
the inner design of the code or logic.
A test plan is a document detailing the objectives, target market, internal beta team, and processes
for a specific beta test for a software or hardware product. The plan typically contains a detailed
understanding of the eventual workflow.
Test Case 1
LOGIN PAGE
Objective : This page can be used for the login into system.
is valid
SYSTEM MAINTAINENANCE
CHAPTER 7
SYSTEM MAINTAINENANCE
7.1 INTRODUCTION
Software maintenance denotes any changes made to the software product after it has been
delivered to the customer. Maintenance is inevitable for almost any kind of products. However,
most products need maintenance due to the wear and tear caused by use. On the other hand
software products do not need maintenance on this account, but need maintenance to correct
errors, enhance features, port to new platform etc.
2 Adaptive: A software product might need maintenance when the customers need the product
to run on new platforms, new operating systems, or when they need the product to be
interfaced with new hardware or software.
3 Perfective: A software product need maintenance to support the new features that uses want
to support, to change different functionalities of the system according to customer demands ,
or to enhance the performance of the system.
The system developed should be secured and protected against possible hazards. Security
measures are provided to prevent unauthorized access of the database at various levels. Password
protection and simple procedures to prevent the unauthorized access are provided to the users.
The system allows the user to enter the system only through proper username and password.
CHAPTER 8
8.1 INTRODUCTION
Using PHP and SQL Server , the software entitled “Rent A Car” has been designed, developed
and tested for all possible samples of data. As a whole the system was well planned and designed.
Since the system is more flexible than the existing similar systems, further modification can be
easily done if time and cost schedule are suitable for it. The performance of the system is proved
to be efficient. The system provides flexibility for incorporating new features, which may be
necessary in future.
The system can be improved in future by adding the facilities for accessing this network or this
site from anywhere. And the site master can provide more and more locations from where the user
can access them easily. Online bill payments can also be added to the system which will help both
the user and owner to save their time .The rate of cars can be reduced more as there is no third
party involvement.
CONCLUSION
CHAPTER 9
CONCLUSION
After the completion of the project the problems in the existing system would overcome. The “RENT A
CAR” process made computerized to produce human errors and to increase the efficiency. The main
focus of the project is to lessen human efforts. The maintenance of the records is made efficient, as all
the records are stored in the My sql database, through which data can be retrieved easily. The navigation
control is provided in all the forms to navigate through the large amount of records. If the no. of record
is very large then user has to just type the customer Id and user gets the result immediately. The vehicle
and customer are given a particular unique id customer Id so that they can be accessed correctly and
without errors. Our main aim of the project is to get the correct information about a particular member
who s hiring the vehicle.
The problem, which existed in the earlier system, has been removed to a large extend and it is
expected that this project will go a long way in satisfying users requirements. The rent a car management
system will improve not only the efficiency but also reduce human stress their by indirectly improving
car hiring.
BIBLIOGRAPHY
CHAPTER 10
BIBLIOGRAPHY
BOOK REFERENCES
Edition,Pearson education
WEBSITE REFERENCE
1. https://www.w3schools.com/php
2. http://www.W3schools/easyhtml.com
APPENDIX
CHAPTER 11
APPENDIX
SCREENSHOTS
Login page
Signup Page
Home Page
My Bookings
Dept. of Computer Application 100 Kristu Jyoti College of Management and Technology
RENT A CAR
Dept. of Computer Application 101 Kristu Jyoti College of Management and Technology
RENT A CAR
Add Locations
Dept. of Computer Application 102 Kristu Jyoti College of Management and Technology
RENT A CAR
Dept. of Computer Application 103 Kristu Jyoti College of Management and Technology
RENT A CAR
Remove Item
Dept. of Computer Application 104 Kristu Jyoti College of Management and Technology
RENT A CAR
Change Password
Dept. of Computer Application 105 Kristu Jyoti College of Management and Technology
RENT A CAR
GLOSSARY
Dept. of Computer Application 106 Kristu Jyoti College of Management and Technology
RENT A CAR
CHAPTER 12
GLOSSARY
Dept. of Computer Application 107 Kristu Jyoti College of Management and Technology
RENT A CAR
16 Actor An actor represents the roles that the user of the use cases
play.
Dept. of Computer Application 108 Kristu Jyoti College of Management and Technology