Main
Main
1. INTRODUCTION
This vehicle management system is fully customized web application where company staff
can view each customer order and give a solution to those vehicle problems. The locating
system allows you to search Mechanics from different locations. Admin handles and can
access the user details as well as the Mechanic details. Admin has the access to allow/block
and view the mechanics. This online mechanic locator reduces your work and can easily
find the mechanics from various areas. Reduces your time and cost.
Admin
Mechanic:
e. Register: Mechanics can register with all their information.
f. Login: Registered mechanics will be provided access to Login only if the Admin
will allow or block.
g. View Request: Mechanics can view the request which is sent by the user.
h. Feedback: Mechanics can provide their own feedback.
2. User:
a. Register: User can register with all their details.
b. Login: Registered user can Login with their credentials.
c. Search Mechanics: User can search for local mechanics on the basis of their
locations.
d. Send Request: On selection of the mechanics, the user can send the request to the
respective mechanic.
e. Feedback: User can give their feedback accordingly.
PHP is a server side scripting language that is embedded in HTML. It is used to manage
dynamic content, databases, session tracking, even build entire e-commerce sites.
PHP is pleasingly zippy in its execution, especially when compiled as an Apache module
on the Unix side. The MySQL server, once started, executes even very complex queries
with huge result sets in record-setting time.
PHP supports a large number of major protocols such as POP3, IMAP, and LDAP. PHP4
added support for Java and distributed object architectures (COM and CORBA), making
n-tier development a possibility for the first time.
PHP can handle forms, i.e. gather data from files, save data to a file, through email you
can send data, return data to the user.
You add, delete, and modify elements within your database through PHP.
Using PHP, you can restrict users to access some pages of your website.
Characteristics of PHP
Five important characteristics make PHP's practical nature possible −
Simplicity
Efficiency
Security
Flexibility
Familiarity
All of the PHP present in the Web page is processed and stripped from the page; the only
thing returned to the client from the Web server is pure HTML output.
All PHP code must be included inside one of the three special markup tags ATE are
recognized by the PHP Parser.
In order to develop and run PHP Web pages three vital components need to be installed on your
computer system.
Web Server − PHP will work with virtually all Web Server software, including
Microsoft's Internet Information Server (IIS) but then most often used is freely available
Apache Server. Download Apache for free here − https://httpd.apache.org/download.cgi
Database − PHP will work with virtually all database software, including Oracle and
Sybase but most commonly used is freely available MySQL database. Download
MySQL for free here − https://www.mysql.com/downloads/
PHP Parser − In order to process PHP script instructions a parser must be installed to
generate HTML output that can be sent to the Web Browser. This tutorial will guide you
how to install PHP parser on your computer.
2.2 DATABASE
MY SQL
MySQL exceeds dependability requirements and provides innovative capabilities that increase
employee effectiveness, integrate heterogeneous IT ecosystems, and maximize capital and
operating budgets. MySQL provides the enterprise data management platform the organization
needs to adapt quickly in a fast-changing environment. With the lowest implementation and
maintenance costs in the industry, MySQL delivers rapid return on data management investment.
It supports the rapid development of enterprise-class business applications that can give an
insurance company a critical competitive advantage. Benchmarked for scalability, speed, and
performance, it is a fully enterprise-class database product, providing core support for Extensible
Mark-up Language (XML) and Internet queries.
WINDOWS XP
Windows XP, the successor to Windows Me, was the first consumer-oriented operating system
produced by Microsoft to be built on the Windows NT kernel. Windows XP was released
worldwide for retail sale on October 25, 2001, and over 400 million copies were in use in
January 2006. It was succeeded by Windows Vista in January 2007. Direct OEM and retail test
of windows XP ceased on June 30, 2008. Microsoft continued to sell Windows XP through their
System Builders (smaller OEMs who sell assembled computers) program until January 31, 2009.
On April 10, 2012, Microsoft reaffirmed that extended support for Windows XP office 2003
would end on April 8, 2014 and suggested that administrators begin preparing to migrate to a
newer OS.
We make use of the latest OS because, now a days, all the users are friendly with the latest
technologies , so as the latest the OS, that well the user will be able to handle the new software.
3. SYSTEM ANALYSIS
3.1 INTRODUCTION
System Analysis refers to the process of examining a situation with the intention of improving it
through better process and methods. System analysis is therefore, the process of gathering and
interpreting facts, diagnosing problem and using the information to recommend information in
system or in other words, it means a detailed explanation or description. Before computerizing a
system under consideration, it has to be analyzed. We need to study how it functions currently,
what are problems and what are requirements that proposed software should meet.
The software provides a user friendly interface which can be operated by anyone with a
minimum knowledge of the computer system. It should maintain a well-organized database for
storing the resources .This helps us to eliminate the entering of invalid data. Most problems of
manual system can be solved by this required system.
The main components of making software are:
• System and software requirements analysis.
In the present system a customer has to approach various services to get proper and well
maintained result. This often requires a lot of time and effort. A customer may not get the
desired services from the centers and often the customer may be misguided.
Validating problems.
Time consumption.
More formalities needed.
Need of more administrator assistants.
The computerization of the system allows the easy maintenance of the details. Large amount of
data can be stored easily. Addition and updating other changes can be done easily. The
information can be retrieved with high speed and accuracy. The use of GUI oriented software
makes the system user friendly. Since all work is computerized, the calculations are effortless
and less time consuming. Speed, accuracy, storage capacity, versatility, automation etc are the
advantages of using a computerized system.
The main purpose behind the proposed system is to provide a comprehensive computerized
system, which can capture, collate and analyze the data from these wards and evaluate the impact
of the program.
User Friendly:
This package is very user friendly because it is easy to maintain and operate. All data
entry operations are simple, administrator needs only to enter data and all other
operations are performed by the computer.
Automation: The proposed system automates each and every activity of the manual
system and increases its throughput. Thus the response time of the system is very less and
it works very fast.
The propose system is interactive, highly user friendly and designed exclusively for “On Road
Vehicle Breakdown Assistance”. The system covers almost all the functional areas of the
training and placement cell management.
The “On Road Vehicle Breakdown Assistance” is a database system used to store the
information regarding details of users, mechanics, feedback etc...
All the operations and activities related to “On Road Vehicle Breakdown Assistance “can be
carried out efficiently. The project maintains well organized database for storing the resources
that they are provided by the members. This helps us to eliminate the entering of invalid data.
Most problems of manual system can be solved by this system.
The new system works on a windows based platform, PHP as front end. The computerization of
the system allows the easy maintenance of the details. Large amount of data can be stored easily.
Addition and updating other changes can be done easily. The information can be retrieved with
high speed and accuracy. The use of GUI oriented software makes the system user friendly.
Since all work is computerized, the calculations are effortless and less time consuming. Speed,
accuracy, storage capacity, versatility, automation etc. are the advantages of using a
computerized system.
Security:
The software used for this project includes the password, so the security is provided.
When anyone opens the software it has the provision for entering password. We have to
enter the correct password; otherwise we cannot enter into the system. Password is saved
in system registry for more security.
User Friendly:
This package is very user friendly because it is easy to maintain and operate. All data
entry operations are simple, administrator needs only to enter data and all other
operations are performed by the computer.
Automation: The proposed system automates each and every activity of the manual
system and increases its throughput. Thus the response time of the system is very less and
it works very fast.
4. SYSTEM SPECIFICATION
We require much different software to make the application which is in making to work
efficiently. It is very important to select the appropriate software so that the software works
properly.
2. PHP
3. MySQL
The selection of hardware is very important in the existence and proper working of any
software. When selecting hardware, the size and capacity requirements are also important. Below
is some of the hardware that is required by the system
5. SYSTEM DESIGN
The most creative and challenging phase of the system life cycle in the system design. The term
design describes a final system and the processed by which it is developed, it refers to the
technical specifications that be applied in implementing a candidate system. It also includes the
construction of program testing.
The goal of design process is to produce a model as representation of the system; which can be
used later to build the system. The design process for software for the system, the specification
of those modules, and how the modules should be interconnected. This is called top level design.
In the second level, the internal design of the module can be satisfied, is decided. This design is
called logical design.
System designing is the process of defining the architecture, components, modules, interfaces
and data for the “On Road Vehicle Breakdown Assistance” to satisfy specified requirements of
the customer. It says “how to” approach compared to system analysis which is a “what is”
orientation. It translates the system requirements into ways of making them operational. The
design phase focuses on the detailed implementation of the training and placement cell
management recommended in the feasibility study.
Input design is the process of converting user originated inputs to a computer based format. Input
data are collected and organized into groups of similar data. Data are entered through keyboard
and also the user can use the mouse for selecting options. Errors entered by data entry operation
can be controlled by input design. The goal of designing input data is to make data entry an easy.
Logical and free from errors are possible.
All input data are validated in the order and if any data violates any condition the user is warned
by a message and asks to re-enter data. If the data satisfies all the condition then it is transferred
to the appropriate tables in the database.
Output design is used to provide outputs to the users of the system. Computer output is the most
important direct source of information to the user. Efficient intelligible output design improves
the system relationships with the user and help in decision making major form of the output is
the hardcopy from the printer and the screen reports. The output devices to consider depend on
factors such as compatibility of the devices with the system, expected print quality and number
of copies needed.
A database is a collection of interrelated data stored within minimum redundancy to serve many
users quickly and efficiently. It is a process of designing the database file, which is the key
source of the information in the system. The objective of database is to design is to provide
storage and it contributes to the overall efficiency of the system. The file should properly design
and planned for collection, accumulation, editing and retrieving the required information. The
primary objective of a database design are fast response time to inquiries ,more information at
low cost, control of redundancy, clarity and ease of use, accuracy and integrity of the system, fast
recovery and availability of powerful end-user languages. The theme behind a database is to
handle information as an integrated whole thus the main objective is to make information as
access easy, quick, inexpensive and flexible for the users. In this project, we mainly concentrated
into relational databases. Relational database stores data in tables, which is turn, are composed of
rows also known as records, columns also known as fields. The fields in the relational model
are:-
Primary Key
The key which is uniquely identify records. They also notify the not null constraints.
Foreign Key
The key which reference the primary key, is the data inserted in the primary key column of the
table.
Normalization
After the conceptual level, the next level of process of database design to organize the database
structure into a good shape called Normalization. The normalization simplifies the entries,
removing redundancies from the system data and finally builds a data structure, which is both
flexible and adaptable to the system. The different normal forms obtained during the database
design are given below:
In the database design, we create a database with different tables that is used to store the data.
We normalize the data in the table. Database normalization is the process of organizing the
fields and tables in a relational database to minimize redundancy and dependency. Normalization
usually involves dividing large tables into smaller (and less redundant) tables and defining
relationships between them. The objective is to isolate data so that additions, deletions, and
modifications of a field can be made in just one table and then propagated through the rest of the
database via the defined relationships.
In the project I have made used of the 3rd normal form, Third Normal Form (3NF) is a property
of database tables. A relation is in third normal form if it is in Second Normal Form and there are
no functional (transitive) dependencies between two (or more) non-primary key attributes. The
overall objective in the development of database technology has been to treat data as an
organizational resource and as an integrated whole. Database Management System allows data to
be protected and organized separately from other resources. Database is an integrated collection
of data. This is the difference between logical and physical data.
The tables are used to store the values that are generated by the application. The main field
names and the key constraints of all the tables are shown below in detailed
provision must be taken in design for the future enhancement of the program. Here we
have designed a database with some tables as shown.
For the database normalization different tables used for storing data is
broken to simplified tables in a relational database to minimize redundancy and
dependency. Normalization usually involves dividing large tables into smaller tables and
defining relationships between them. Database Management System allows data to be
protected and organized separately from other resources. Database is an integrated
collection of data. This is the difference between logical and physical data. Are used to
store the values that are generated by the application.
A DFD also known as ‘bubble chart’ has the purpose of clarifying system requirements and
identifying major transformations. It shows the flow of data through a system. It is a graphical
tool because it presents a picture. The DFD may be partitioned into levels that represent
increasing information flow and functional detail. Four simple notations are used to complete a
DFD. These notations are given below:-
The data flow is used to describe the movement of information from one part of the system to
another part. Flows represent data in motion. It is a pipe line through which information flows.
Data flow is represented by an arrow.
PROCESS
A circle or bubble represents a process that transforms incoming data to outgoing data. Process
shows a part of the system that transforms inputs to outputs.
EXTERNAL ENTITY
A square defines a source or destination of system data. External entities represent any entity
that supplies or receive information from the system but is not a part of the system.
DATA STORE
The data store represents a logical file. A logical file can represent either a data store symbol
which can represent either a data structure or a physical file on disk. The data store is used to
collect data at rest or a temporary repository of data. It is represented by open rectangle.
This depicts relationship between data objects. The attribute of the each data objects noted in the
entity relationship diagram can be described using a data object description.
Data objects: a data is a representation of almost any composite information that must
understood by the software.
Attribute: it defines the properties of a data object and takes on one of three different
characteristics.
Entity –
Relationship –
Attribute –
Line-
.
Level 0
Table 5.7.1
Table 5.7.2
Table Name:book
Table 5.7.3
bid Int(11)
bdte varchar(20)
smid int(20)
uid Int(11)
Table 5.7.4
Table 5.7.5
Table 5.7.6
Table 5.7.7
6. SYSTEM TESTING
System testing is actually a series if different tests whose primary process is to fully exercise the
computer based system. Each test has different purpose, but all work that system elements have
been properly integrated and perform allocated functions.
System testing is the stage of implementation, which is aimed at ensuring that the system works
accurately and efficiently before live operation commences. Testing is vital to the success of the
system. Testing is the process of executing programs with the explicit intention of finding errors
that is making the program fail.
System testing is a critical aspect of software quality assurance and represents the ultimate
review of specification, design and ending. Testing is a process of executing a program with the
intent finding an error. No system design is ever perfect. The basic types of testing procedure
are:
Unit testing
Integration testing
Validation testing
Output testing
User acceptance
Unit testing focuses verification efforts on the smallest unit of software design, the Module. This
is also known as module. This is also known as module testing. The module testing is tested
separately. The important control paths are tested to uncover errors within the boundary of the
module. These testing are carried out during the programming itself.
This testing is carried out during the programming stage itself. In this testing step each module is
found to be working satisfactorily as regards to the expected output from the module. Using a
method called white box testing in which the software tester has knowledge of the inner
workings, structure and language of the software, or at least its purpose and where each module
or component of the software is tested individually.
After splitting the program into units were tested together to see the defects between each
module which are connected to each and function. It is testing 2 or more modules or functions
together with the intent of finding interface defects between the modules or functions. Testing
completed as part of unit or functional testing, and sometimes, becomes its own standalone test
phase. On a larger level, integration testing can involve putting together of groups of modules
and functions with the goal of completing and verifying that the system meets the system
requirements.
Validation testing is the process of evaluating software at the end of the software development
process to ensure the compliance with software requirements. Validation testing is where
requirements established as a part of software requirement analysis is validated against the
software that has been constructed. This test provides the final assurance that the software meets
all the functional, behavioral and performance requirements. The errors which are uncovered
during integration testing are corrected during this place. Errors discovered where corrected prior
to completion of this project with the help of user by negotiating to establish the method of
resolving deficiencies. Thus the proposed system under consideration has been tested by using
validation testing and found to be working satisfactory.
During this phase the user check whether the system works in a proper manner or not. The
developer will correct all the errors that are remained unchanged. After integration testing, may
be some bugs will remain in the system. It will affect the proper functionality of the system. In
order to avoid, this validation testing is necessary. Validation testing is defined with a single
definition that validation succeeds when the software functions in a manner that can be
reasonably accepted by the user. By using the helpful information’s from the organization we
can remove the defects of the system. The various modules that require validation are:
Test plan
A test plan is a general document for the entire project that defines the scope, approach to be
taken and the schedule of testing as well as identifies the test item for the entire testing process
and personal responsibility for the different activities of testing. The test pan can do as well
before actual testing and can be done parallel with the coding and design phases. A test plan
should contain the following:
1. Test unit specification
2. Features to be tested
4. Test deliverables
5. Schedule
6. Personal allocation
Testing strategy
Software is viewed as white-box, in white-box testing, as the structure and flow of software
under test are visible to the tester. Testing plan is made according to the details of the software
implementation, such as programming language, logic and styles. Test cases are derived from the
program structure. While white-box testing is applicable at the unit, integration, and system
levels of the software testing progress, it is typically applied to the unit.
So while I normally test paths within a unit, it can also test paths between units during
integration, and between sub systems during level test.
System testing
In principle, system testing is an ongoing activity throughout the project. The logical design and
physical design should be thoroughly and continually examined on paper to ensure that they will
work when implemented. Thus the system test in implication should be a confirmation that all is
correct and an opportunity to show the user that the system works. This checks all the elements
of the system. The most important elements are the hardware, software, people and information.
The 4 types of system test are:
Recovery testing the software is allowed to fail in a number of ways and then recovery of
software is tested. In recovery testing, data recovery or operating system/hardware
recovery are tested.
Security testing in this safety of the system is tested. The test engineer himself attacks
System and checks whether a system is safe or not.
Stress testing in this testing we check the various resources of a system. The resources
that checked include memory limit, OS capacity
Performance testing in this testing we check the runtime performance of the system.
This testing is conducted at the unit level, integration level, and implementation level.
This testing uses both black white box testing methods.
Output testing
It includes producing the output that is generated by the system in the required format, the format
can be both in the screen and printed format. Producing the output in the correct format is very
necessary in the useful implementation of the system.
System testing
When a system is developed it is hoped that it perform properly. In practice, however some
errors will occur. The main purpose of testing and information system is to find the errors and
correct them. A successful test is one which finds an error.
The test plan represents the overall approach to the test. In many ways, the test plan serves as the
summary of the activities that will be performed. It shows how the test will be organized and
outlines all the testers’ need that must be met in orders to properly carryout the test. The test plan
is especially valuable because it is not a difficult document to review, so the members of
engineering team and senior managers can inspect it. The bulk of test planning effort is focused
on creating the rest cases. A test case is a descriptive of a specific interaction that a tester will
have, in order to test the single behavior of the software. Test cases are very similar to use cases,
in that way they are step by step narratives that define a specific interaction between the user and
software. However, unlike use cases, they contain references to specific features of the user
interface. The test case contains actual data that must be entered into software and the expected
result that the software must generate. A test case, in software engineering is a set of conditions
or variables under which a tester will determine whether an application, software system or one
of its feature is working as it was originally established for it to do. The mechanism for
determining whether a software program or a system has passed or failed such a test is known as
test oracle. In some settings, an oracle could be a requirement or a use case, while in other case it
could be a heuristic.
It may take many test cases to determine that software or a system is considered sufficiently
scrutinized to be released. Test cases are often referred to as test scripts; particularly when
written-when they are usually collected into test suites.
7. SYSTEM IMPLEMENTATION
Maintenance covers a wide range of activities including correcting coding and design
errors, updating documentation and test data and upgrading user support.
Any system developed should be secured and protected against possible hazards. Security
measures are provided to prevent unauthorized access of the database at various levels. An
uninterrupted power supply should be that the power failures or voltage fluctuation will not
erase the data in files.
Password protection and simple procedures to prevent the unauthorized access are provided
to the user. The system allows entering the system only through proper username and
password.
8. SYSTEM EVALUATION
The project entitled “On Road Vehicle Breakdown Assistance” has been developed to
meet the requirements of the existing system. it has made operational after going
through a series of phases: study phase, analysis , design, and followed by testing
evaluation.
After considering various feasible solutions the most feasible one was selected and
designed along considering the time and efficiency constraints and named the most
feasible one as “On Road Vehicle Breakdown Assistance”. Software maintenance and
evaluation of the system was first developed by Meir M Lehman in 1969. Over a period
of 20 years researched has led to the formation of Lehman’s law (Lehman 1970). Key
findings of his research include that the maintenance is really solutionary development
and that maintenance decisions are aided by understanding what happens to the
systems overtime. Lehman demonstrated that system control to solve overtime. As they
involve they grow more complex unless some actions such as code, refactoring is taken
to reduce the complexity.
8. CONCLUSION
10.1 APPENDIX A
<!doctype html>
<html>
<head>
<!--bootstrap-->
<!--coustom css-->
<!--default-js-->
<script src="js/jquery-2.1.4.min.js"></script>
<!--bootstrap-js-->
<script src="js/bootstrap.min.js"></script>
</head>
<body>
<!-- Brand and toggle get grouped for better mobile display -->
<div class="navbar-header">
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
</div>
<!-- Collect the nav links, forms, and other content for toggling -->
<li class="col-md-2">
Home
</a>
</li>
<!---->
<li class="col-md-2">
</a>
</li>
<!---->
<li class="col-md-2">
</a>
</li>
<!---->
<li class="col-md-2">
</a>
</li>
<!---->
<li class="col-md-2">
User Register
</a>
</li>
<li class="col-md-2">
Mechanics
</a>
</li>
<div class="clearfix">
<!--script-->
<script type="text/javascript">
jQuery(document).ready(function($) {
$(".scroll").click(function(event){
event.preventDefault();
$('html,body').animate({scrollTop:$(this.hash).offset().top},900);
});
});
</script>
<!--script-->
</ul>
<div class="clearfix"></div>
</nav>
</div>
<div class="container">
<div class="logo">
</div>
<div class="ad-ph">
<form action="loginaction.php">
<table>
<tr>
</tr>
</table>
</form>
</div>
<div class="clearfix"></div>
</div>
<div class="banner">
<div class="container">
<div class="banner-info">
</div>
</div>
</div>
<div class="our">
<div class="container">
<div class="our-top">
<div class="clearfix"></div>
</div>
</div>
</div>
<div class="footer">
<div class="container">
<div class="foot-bottom">
</div>
</div>
</div>
</body>
</html>
10.2 APPENDIX B
10.1.2.4
10.3 APPENDIX C
10.3.1 Acronym
10.3.2 Bibliography
Henry Korth,” Data Base Design Concept”, Mc grew hill – Fifth Edition 2001.