Vechicle Record System Final Report
Vechicle Record System Final Report
COMPUTER APPLICATIONS
BHATKAL-581320
DEPARTMENT OF COMPUTER APPLICATION
CERTIFICATE
This is to certify that the project entitled “VEHICLE RECORD
SYSTEM” is Bonafide work carried out by
Examiners: 1.
2.
SHREE GURU SUDHINDRA COLLEGE OF
COMPUTER APPLICATIONS
BHATKAL - 581320
DEPARTMENT OF COMPUTER APPLICATION
VEHICLE RECORD SYSTEM
Submitted to
Karnataka University during the year 2024-25 in fulfillment of the
requirement for the Degree certificate of
Bachelor of Computer Application
Date:
Place: Signature
SHREE GURU SUDHINDRA COLLEGE OF
COMPUTER APPLICATIONS
BHATKAL – 581320
DEPARTMENT OF COMPUTER APPLICATION
ATTENDANCE CERTIFICATE
Date:
Place:
We also convey our heartily thanks to our parents and all the
individuals who have helped us directly and indirectly to carry out this
project successfully.
Thank You…
DATE:
Signature of Student
Abstract
In the age of digital transformation, efficient and secure data management systems have become
essential for organizations. The Vehicle Record System is a comprehensive, web-based application designed to
manage vehicle-related information with enhanced efficiency, accessibility, and data integrity. It replaces
conventional paper-based logbooks and spreadsheets with a centralized, automated platform tailored for use by
administrative personnel in various sectors such as transportation departments, vehicle dealerships, and corporate
entities.
This system is developed using HTML, CSS, and JavaScript on the frontend to deliver a user-
friendly interface, while PHP and MySQL power the backend, ensuring robust data handling and secure storage.
The system provides key functionalities including vehicle and brand management, secure admin login, report
generation based on brand or date range, profile management, and feedback submission. Role-based access
control ensures that sensitive data is protected and only accessible to authorized users.
Beyond its core features, the system is designed for scalability and future enhancements. Potential
upgrades include support for multiple user roles, integration with SMS/email notifications, graphical analytics,
mobile app compatibility, and cloud deployment.
With its modular architecture and real-time data processing, the Vehicle Record System not only
enhances operational productivity but also supports transparency and accountability in record-keeping. Its
adaptable structure makes it a valuable asset for growing organizations, enabling smooth upgrades and
integration with future technologies. This project exemplifies how traditional administrative processes can be
effectively transformed into modern, efficient systems using web technologies.
3.2 Purpose
3.3 Scope
3.4 Software Requirements
3. System Requirement 3.5 Hardware Requirements
Specification
3.6 Module Specification
3.6.1 User Side 13-21
3.6.2 Admin Side
3.7 Languages Used
3.8 Functional Requirements
3.9 Non-functional Requirements
4.1 Introduction
4.2 Use Case Diagram
4.3 Use Case Components
4.4 Use Case Identification
4. System Design 4.5 Use Case Diagram for User Side 22-32
4.6 Use Case Diagram for Admin Side
4.7 Data Flow Diagram (DFD)
4.8 Entity-Relationship (ER) Diagram
4.9 Class Diagram
5.1 Introduction
5. MySQL Data Tables 5.2 Coding 33-45
5.3 System Implementation
6.1 Unit Testing
6.2 Integration Testing
6. Testing 6.3 Performance Testing
6.4 Security Testing 45-47
6.5 Test Cases
6.6 Sample Test Case – Login
7. Future Scope
8. Conclusion 48-50
9. Bibliography
7
Vehicle Record System
1. Introduction
1.2 Overview:
In the modern era of digital record-keeping, the Vehicle Record System is a streamlined and
efficient way to manage vehicle-related information for administrative and organizational purposes. This
system transforms traditional, manual record management into a secure, dynamic, and interactive web-based
platform. The Vehicle Record System is developed using HTML, CSS, JavaScript for the frontend, and PHP
with MySQL on the backend. The platform provides functionalities such as adding vehicle information,
managing vehicle brands, generating reports, and user authentication. Whether it's for an organization,
dealership, or government agency, the Vehicle Record System provides an effective solution for maintaining
up-to-date vehicle records in a centralized manner.
1.3 Objectives:
The main objectives of the Vehicle Record System are:
1. To digitalize and streamline the process of managing vehicle-related records for administrative
use.
2. To provide an efficient and secure platform for adding, updating, deleting, and retrieving
vehicle data.
3. To offer a centralized dashboard for managing vehicle brands, registration details and owner
information.
4. To provide administrators with various reporting tools to generate vehicle reports based on date
range or brand.
5. To implement user authentication and data access control for enhanced system security.
1.4 Scope:
The scope of the Vehicle Record System includes the design and implementation of a
complete web-based application for managing vehicle information. The system is intended for use by
administrative staff to efficiently handle and track vehicles in a structured manner. The features included are:
• Admin Dashboard:
A control panel for navigating key features like adding brands, vehicle, and generating reports.
• Brand Management:
Functionality for adding, editing, and deleting vehicle brand information.
• Vehicle Management:
Interfaces for inputting and maintaining vehicle - specific data including registration number,
type, model, and brand.
• User Authentication:
Secure login for administrators to prevent unauthorized access.
1.5 Purpose:
The Vehicle Record System is designed to simplify and secure the management of vehicle-
related information within an organization. It replaces paper-based and spreadsheet methods with a
centralized web application that provides real time access to vehicle data like brand details and registration
records. The system includes authentication and role-based access to ensure security and proper data
handling. By reducing manual work and eliminating the need for physical storage, it improves efficiency
and accuracy. It also promotes accountability and transparency, while supporting better decision-making
and future upgrades based on organizational needs.
2. System Analysis
The existing system for managing vehicle records typically relies on traditional paper-based
logbooks or basic digital spread sheets. These outdated approaches present several challenges in
maintaining accurate, accessible, and secure records. Here are some details about the shortcomings of the
existing system:
• Lack of Centralization:
Information is often scattered across multiple documents or locations, making it difficult to
retrieve complete vehicle histories or generate comprehensive reports.
• Limited Security:
Physical records are prone to loss, damage, or unauthorized access, and spread sheets often lack
proper user authentication and data protection.
• Time-Consuming Processes :
Tasks like searching for a specific vehicle record, updating information, or generating reports are
inefficient and slow with manual systems.
• No Real-Time Access:
Users cannot access or update records remotely or in real-time, leading to delays and outdated
information.
1
The proposed system for the Vehicle Record System envisions a dynamic, secure,
and centralized platform that overcomes the limitations of traditional record-keeping methods. This modern
solution uses web technologies and an intuitive interface to provide administrators with a streamlined and
efficient vehicle management experience. Here are some key aspects of the proposed system:
• User-Friendly Interface:
The platform will provide an intuitive and accessible web interface, allowing users to navigate
through various modules such as brand management, vehicle registration, and report generation with
minimal effort.
• Responsive Design:
The web interface will be responsive, making it accessible across different devices, including
desktops, laptops, tablets, and smartphones, ensuring convenience for administrators on the go.
Hardware Configuration:
Client Side:
RAM 512 MB
Hard disk 10 GB
Server Side:
RAM 1GB
Hard disk 20 GB
Software Requirement:
Client Side:
Server Side:
3.1 Introduction
The Software Requirement Specification (SRS) describes the intended functionality, behavior,
and constraints of the Vehicle Record System. It defines both functional and non- functional
requirements and serves as a foundation for development and testing..
3.2 Purpose
The purpose of this SRS is to detail all the software requirements necessary for building and
maintaining the Vehicle Record System. It ensures that the development process is guided by clear
and structured specifications.
3.3 Scope
This system allows the admin to perform vehicle data management efficiently. The software
will support record creation, brand management, report generation, and secure access. It will be used
by organizations or individuals needing centralized vehicle information handling.
1. Login Module:
• This module ensures only registered users can access the system by requiring a valid
username and password.
• It uses session management to maintain the user's login state across different pages and
includes validation to protect against invalid or malicious login attempts.
• This module allows users to browse a list of vehicles with basic public details such as model,
brand, registration number, and purchase date.
• Users can apply search filters or sort records based on various parameters to quickly find
relevant information.
• Users can view their saved profile information and make updates to keep their contact
details current.
• This helps improve personalized interaction and ensures users remain reachable for
communication or notifications.
4. Feedback Module:
• Through this module, users can submit feedback, suggestions, or bug reports directly to the
administrator.
• The system captures each message along with the user ID and timestamp, helping the admin
analyze common issues and improve the system.
• This module enhances user security by allowing them to change their password from their
account settings.
• It typically requires the current password for verification, and uses encryption to securely
store the new password in the database.
6. Logout Module:
• Provides a secure way for users to end their session and prevent unauthorized access to their
account.
• It clears all session variables and redirects users to the login page, ensuring data privacy
when users log out from shared or public devices.
1. Dashboard Module:
• Provides a centralized view of system statistics, such as the total number of vehicles,
brands, and recent activities.
• Offers quick access links to various sections like add vehicle, reports, and settings.
• Enables the admin to add detailed vehicle records including model name, registration
number, brand, and purchase date.
• Includes features like filtering by brand or date, sorting, and search for better record
management.
• Admin can generate custom reports based on brand, registration date, or other filters.
• Provides the admin with the ability to securely change their system
login password.
7. Logout Module:
• Clears session data and redirects to the login page to prevent unauthorized access.
• Provides the admin with the ability to securely change their system
login password.
9. Logout Module:
• Clears session data and redirects to the login page to prevent unauthorized access.
3.7 Languages:
HTML:
The Hypertext Markup Language, or HTML is the standard markup language
for documents designed to be displayed in a web browser. It can be assisted by
technologies such as Cascading Style Sheets (CSS) and scripting languages such as
JavaScript. Web browsers receive HTML documents from a web server or from local
storage and render the documents into multimedia web pages. HTML describes the
structure of a web page originally included for the appearance of the document. HTML
elements are the building blocks of HTML pages. With HTML constructs, images and
other objects such as interactive forms may be embedded into the rendered page. HTML
provides a means to create structured documents by denoting structural semantics for
text such as headings, paragraphs, lists, links, quotes and other items.
CSS:
CSS stands for Cascading Style Sheets. It is a style sheet language which is used
to describe the look and formatting of a document written in markup language. It provides
an additional feature to HTML. It is generally used with HTML to change the style of
web pages and user interfaces. It can also be used with any kind of XML documents.
JAVASCRIPT:
JavaScript is a light-weight object-oriented programming language which is used by
several websites for scripting. It is an interpreted, full-fledged programming language that
enables dynamic interactivity on websites when applied to an HTML document. It was
introduced in the year 1995 for adding programs to the webpages in the Netscape
Navigator browser. Since then, it has been adopted by all other graphical web browsers.
With JavaScript, users can build modern web applications to interact directly without
reloading the page every time.
PHP:
PHP (Hypertext Preprocessor) is a popular server-side scripting language for web
development. It is embedded within HTML and handles server-side logic, including
database interactions, user authentication, and form processing. PHP supports various
databases and is widely used to create dynamic web applications. It is known for its ease
of use, flexibility, and extensive community support.
MySQL:
MySQL is a widely-used open-source relational database management system
(RDBMS). It uses structured query language (SQL) for accessing and managing data.
MySQL is known for its speed, reliability, and flexibility, making it ideal for handling
large databases in web applications. It integrates seamlessly with PHP and provides robust
security features, ensuring data protection.
• Response Time: The system should respond to user actions (e.g. form submissions,
page loads) within 2 seconds under normal load.
• Scalability: The system should be designed to handle increased data and user volume
without degradation in performance.
2. Reliability and Availability
• System Uptime: The system should be available 99% of the time to ensure
continuous access.
• Error Handling: The system must provide clear error messages and handle
unexpected failures gracefully.
• Backup and Recovery: Daily database backups should be performed to prevent data
loss. The system must support recovery within 1 hour after a failure.
3. Security
• Authentication: Only authorized users should be able to log in and access sensitive
modules.
• Data Protection: User data should be stored securely and protected from
unauthorized access.
• Session Management: The system must manage user sessions securely and include
auto-logout after periods of inactivity.
4. Usability
• The user interface must be intuitive and easy to navigate for users with minimal
technical knowledge.
• Forms, buttons, and messages must be clearly labelled and styled for clarity.
5. Maintainability
• The system should be deployable across multiple platforms (Windows, Linux) with
minimal configuration changes.
• The system should work seamlessly on major modern browsers (e.g., Chrome,
Firefox, Edge).
7. Flexibility
• The system should be easy to configure for different organizational needs (e.g.,
branding, data fields).
• It should support the addition of new modules or features without major redesign.
4. SYSTEM DESIGN
4.1 Introduction
System design is the process of defining the architecture, components, modules,
interfaces, and data for a system to satisfy specified requirements. For the Vehicle
Record System, the design phase translates the gathered requirements into a structured
blueprint for development.
The goal of system design is to identify and create a robust, scalable structure
that effectively supports all intended functionalities. This includes identifying system
modules, their interactions, user roles, data flows, and system boundaries. The design
is critical to ensuring that the final system is efficient, secure, and user-friendly.
In a use case diagram, the actors are represented as stick figures and the system
is represented as a rectangle. The interactions between the actors and the system are
shown as arrows connecting the actors and the system. Each use case in the diagram
represents a specific function or capability of the system.
• Use case:
A description of sequence of actions, including variants, that a system
performs that yields an observable result of value of an actor..
Visit Website
View About us
View Contact us
Search Vehicle
User System
Login
Dashboard
Manage Brand
(Add/Update/Del)
Manage Vehicle
(Add/Update/Del)
Search Vehicle
Manage Website
Update Profile
Change Profile
Admin System
4.8 ER DIAGRAM:
5. Implementations
5.1 Introduction
The implementation phase is where the theoretical design and planned
functionalities of the Vehicle Record System are translated into actual working software. It
involves the development and integration of front-end and back-end components using the
chosen technologies such as HTML, CSS, PHP, and MySQL.
5.2 Coding
Index.php
<?php
session_start();
error_reporting(0);
require_once('admin/include/config.php');
?>
<!DOCTYPE html>
<html>
<head>
<!-- basic -->
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- mobile metas -->
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="viewport" content="initial-scale=1, maximum-scale=1">
<!-- site metas -->
<title>Vehicle Record System|| Home Page</title>
<meta name="keywords" content="">
<meta name="description" content="">
<meta name="author" content="">
<!-- bootstrap css -->
<link rel="stylesheet" type="text/css" href="css1/bootstrap.min.css">
<!-- style css -->
<link rel="stylesheet" type="text/css" href="css1/style.css">
<!-- Responsive-->
<link rel="stylesheet" href="css1/responsive.css">
<!-- fevicon -->
<link rel="icon" href="images/fevicon.png" type="image/gif" />
<!-- font css -->
<link
href="https://fonts.googleapis.com/css2?family=Poppins:wght@400;700&family=Raleway:wght@400;50
0;600;700;800&display=swap" rel="stylesheet">
<!-- Scrollbar Custom CSS -->
<link rel="stylesheet" href="css1/jquery.mCustomScrollbar.min.css">
<!-- Tweaks for older IEs-->
<link rel="stylesheet" href="https://netdna.bootstrapcdn.com/font-awesome/4.0.3/css/font-awesome.css">
</head>
SHREE GURU SUDHINDRA COLLEGE, BHATKAL 33
Vehicle Record System
<body>
<!-- header section start -->
<div class="header_section">
<div class="container">
<nav class="navbar navbar-expand-lg navbar-light bg-light">
<strong style="color: white;font-size: 20px;">Vehicle Record System</strong>
<button class="navbar-toggler" type="button" data-toggle="collapse" data-
target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false" aria-
label="Toggle navigation">
<span class="navbar-toggler-icon"></span>
</button>
<div class="collapse navbar-collapse" id="navbarSupportedContent">
<ul class="navbar-nav ml-auto">
<li class="nav-item">
<a class="nav-link" href="index.php">Home</a>
</li>
<li class="nav-item">
<a class="nav-link" href="admin/index.php">Admin</a>
</li>
</ul>
</div>
</nav>
</div>
</div>
<!-- header section end -->
<div class="call_text_main">
<div class="container">
<div class="call_taital">
<div class="call_text"><a href="#"><i class="fa fa-map-marker" aria-hidden="true"></i><span
class="padding_left_15">Bhatkal</span></a></div>
<div class="call_text"><a href="#"><i class="fa fa-phone" aria-hidden="true"></i><span
class="padding_left_15">(+91) 9591628058 </span></a></div>
<div class="call_text"><a href="#"><i class="fa fa-envelope" aria-hidden="true"></i><span
class="padding_left_15">[email protected]</span></a></div>
</div>
</div>
</div>
<!-- banner section start -->
<div class="banner_section layout_padding">
<div class="container">
<div class="col-md-6">
<div class="carousel-item active">
<div class="banner_taital_main">
<h1 class="banner_taital">Vehicle Record <br><span style="color: #fe5b29;">For You</span></h1>
<p class="banner_text">There are many variations of passages of Lorem Ipsum available, but the
majority</p>
<div class="btn_main">
</div>
</div>
</div>
</div>
<div class="col-md-6">
SHREE GURU SUDHINDRA COLLEGE, BHATKAL 34
Vehicle Record System
<div class="search_section">
<div class="container">
<div class="row">
<div class="col-md-12">
<h1 class="search_taital">Search By VehicleName, RegNum, Model Number</h1>
<div class="col-md-4">
<input type="Submit" name="Submit" id="Submit" class="btn btn-primary" value="Submit">
</div>
</div></form>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<!-- select box section end -->
<!-- gallery section start -->
<div class="gallery_section layout_padding">
<div class="container">
<?php
if(Isset($_POST['Submit'])){?>
<?php
$searchinput=$_POST['searchinputdata'];
?>
<div class="row">
<div class="col-md-12">
<h1 class="gallery_taital">Search Result against <?php echo $searchinput;?></h1>
</div>
</div>
<div class="gallery_section_2">
<?php
$sql="SELECT tblvehicle.*, tblbrand.id,tblbrand.BrandName FROM tblvehicle join tblbrand on
tblbrand.id=tblvehicle.BrandID
SHREE GURU SUDHINDRA COLLEGE, BHATKAL 35
Vehicle Record System
$query-> execute();
$results = $query -> fetchAll(PDO::FETCH_OBJ);
$cnt=1;
if($query -> rowCount() > 0)
{
foreach($results as $result)
{
?>
<div class="row">
<div class="col-md-120">
<div class="gallery_box">
<?php }?></div>
</div>
<!-- gallery section end -->
<div class="col-sm-12">
<p class="copyright_text">Vehicle Records System</p>
</div>
</div>
</div>
</div>
<!-- copyright section end -->
<!-- Javascript files-->
<script src="js1/jquery.min.js"></script>
<script src="js1/popper.min.js"></script>
SHREE GURU SUDHINDRA COLLEGE, BHATKAL 36
Vehicle Record System
<script src="js1/bootstrap.bundle.min.js"></script>
<script src="js1/jquery-3.0.0.min.js"></script>
<script src="js1/plugin.js"></script>
<!-- sidebar -->
<script src="js1/jquery.mCustomScrollbar.concat.min.js"></script>
<script src="js1/custom.js"></script>
</body>
</html>
System Implementation
Home Page
Admin Panel
Login Page
Forgot Password
Dashboard
Change Password
Admin Profile
Add Brand
Manage Brand
Update Brand
Update Vehicle
Search Vehicle
About Us Page
Contact Us Page
6. TESTING
Testing is a crucial phase in software development that ensures the application
meets its requirements, performs reliably under various conditions, and maintains data
integrity. The Vehicle Record System was thoroughly tested using different strategies to
verify its functionality, usability, performance, and security.
• Each module (e.g., Add Vehicle, Login, Report Generation) was tested individually to
ensure it functions as expected in isolation.
• Sample tests included checking input validations, correct data storage in the database,
and proper error handling for missing or incorrect input
Expected
ID Test Case Pre - Test Steps Test Data
Output
condition
Username: Error
Login with invalid Admin Enter correct admin message:
Login_02 username and wrong
password account exists Password: "Invalid
password
wrong pass credentials"
Model: Swift
Success alert:
Add vehicle with Admin is Fill all required Brand: Maruti
Add_01 "Vehicle
valid data logged in fields and submit Reg No:
added"
KA19AB1234
Validation
Add vehicle with At least one Leave one field Model: (empty) error: "All
Add_02
missing fields record exists blank and submit Brand: Maruti fields
required"
Choose Report
Choose brand/date From: 2024-01-
Generate report for brand/date displays
Report_01 range and click 01
valid filters range and matching
generate To: 2024-12-31
click generate records
7. Future Scope
The Vehicle Record System has been designed with scalability and flexibility in
mind, making it suitable for future enhancements and expansions. As the needs of users and
administrators evolve, several features and improvements can be implemented to increase the
system’s value and impact.
• Multi-role Access
Extend the system to support multiple user roles (e.g., super admin, clerk, auditor)
with different permission levels.
• Cloud Deployment
Move the system to a cloud-based infrastructure to support remote access, scalability,
and data redundancy.
8. Conclusion
9. BIBLIOGRAPHY
• www.google.com
• www.w3schools.com
• www.tutorialspoint.php