VIVEKANAND COLLEGE

FOR ADVANCED COMPUTER & INFORMATION SCIENCE,

SURAT .

VEER NARMAND SOUTH GUJARAT UNIVERSITY

SURAT.

PROJECT TITLEHI-TECH MOTOR WORKS

HI-TECH MOTOR WORKS
AS PARTIAL REQUIREMENT FOR
THE BECHELOR OF COMPUTER APPLICATION
(B.C.A)
2022-23

GUIDED BY: SUBMITTED BY:

Dr. Asma Patel Kanani Vatsal K. (1188)

Mangukiya Dharmik R. (1208)

Mangukiya Ronak K. (1211)

Miyani Parthiv R. (1218)
 ACKNOWLEDGEMENT

When we reach the completion of the project, giving credit becomes a

must, as without the support of other so many people’s help and
guidance, this project couldn’t be completed successfully.

First, we would like to thank our parents with their great support we can
reach at the stage. Then our humble thanks to all professors and all
staff members of our college “Vivekanand College for Advanced
Computer & Information Science.” For the Cooperation & keep
interest extended by them, throughout our degree course. It is the base
that they have built, which sustains such good jobs.

We would like to thank Ms. Sumathi Shenoy the campus director of

the Vivekanand College for B.C.A. and Dr. Sandip Surati I/C principal
of Vivekanand College for BCA, for granting us an opportunity to work
on this project. We would also like to thank to our guide Dr. Asma
Patel for her valued guidance and encouragement towards the
completion of our project.

Last but not the least, our heartfelt appreciation goes to all those not
named here, but who have rendered their co-operation, little or more,
directly or indirectly involved in the development of this system.

Thanking All.

Kanani Vatsal K.

Mangukiya Dharmik R.

Mangukiya Ronak K.

Miyani Parthiv R.
 ABSTRACT

This document is meant for describing all the features and

procedures that were followed while developing the system.
This document specially mentions the details of the project how
it was developed, the primary requirement, as well as various features
and functionalities of the project and procedures followed in achieving
these objectives.
The aim of this project was to design and create a web
application that gives easy interaction to the online services. This
application allows the user to view different services.
The garage management system is simple, user friendly and
secured. The solution is design to implement several database
management techniques and was primarily evaluated by its ability to
transfer data speedily, maintaining secure transaction and easy
interaction. The final result is on web, which provides facilities at an
instance.
It has many technical elements and the rules are fairly simple.
This simplicity makes it a good choice for learning a new program
environment. It covers a range of areas (data modeling, some coding
challenges, user interface, etc.) but none too difficult.
 INDEX
SR NO. CONTENTS PAGE NO.
1 Introduction 1-5
1.1 Project Profile
1.2 Project Introduction
2 Environment Description 6 - 17
2.1 Hardware / Software Requirement
2.2 Tools & Technology
3 Proposed System 18 - 23
3.1 Scope
3.2 Aim & Objectives
3.3 Expected Advantages
4 System planning 24 - 31
4.1 Requirement Specification
4.2 Feasibility Study
4.3 Life Cycle Model
4.4 Effort Distribution Diagram
4.5 Task Dependency Diagram
4.6 Project Schedule Chart (Time Line Chart)
5 System Model Architecture 32 - 70
5.1 Use Case Diagram
5.2 Activity Diagram
5.3 Sequence Diagram
6 System Design 71 - 128
6.1 Class Diagram
6.2 Table Structure
6.3 Navigation Map
6.4 System Layout
7 System Testing 129 - 137
7.1 Testing Introduction
7.2 Test Case
8 System Limitation & Future 138 – 140
Enhancement
9 References 141 - 143
9.1 Bibliography
9.2 Webography
 CHAPTER: 1

Introduction
1.1 Project Profile
1.2 Project Introduction

P a g e 1 | 149
 1.1 Project Profile

Title : HI-TECH MOTOR WORKS

Project Type : Web Application

Duration : 3 Month

Team Members : 4

Front End Tools : Php

Back End Tools : MySQLi

Other Tools : HTML, CSS, Bootstrap, jQuery, JavaScript,

Xampp Server

Guided By : Dr. Asma Patel

Submitted To : Vivekanand College for BCA

Submitted By : Kanani Vatsal K.

Mangukiya Dharmik R.

Mangukiya Ronak K.

Miyani Parthiv R.

P a g e 2 | 149
 1.2 Project Introduction

 This project is designed so as to be used by HI-TECH MOTOR WORKS

specializing in car servicing, old car sells and car parts selling. It is an online
system through which customer can view available services, registration and
book service, buy parts and also purchase old car.

 Every organization, whether big or small, has challenges to overcome and

managing the information of car, service center, parts of car, registration.
Every car service center management system has different service center
needs therefore we design exclusive car care system that are adapted to you.

 There are 5 panels in our website:

1. Admin
2. Customer
3. Employee
4. Vendor
5. Visitor

P a g e 3 | 149
1. Admin

 Admin can manage all services.

 Admin can manage car modification details.
 Admin can manage car parts.
 Admin can approve seller.
 Admin can approve old car.
 Admin can view order details.
 Admin can view invoice.
 Admin can view and manage inquiry.
 Admin can view and manage FAQ.
 Admin can manage payment information.
 Admin can manage about us information.

2. Customer

 Customer can view all services and book appointment for car service.
 Customer can view modified cars and book appointment for modify
their car.
 Customer can view all parts and purchase car parts.
 Customer can view old cars and also buy old cars.
 Customer can make payment.
 Customer can make inquiry.
 Customer can give the review & rating.

P a g e 4 | 149
3. Employee

 Employee can view works.

 Employee can view profile.
 Employee can update profile.
 Employee can update status.
 Employee can view review & rating.

4. Vendor

 Vendor can add old car for sell.

 Vendor can add old car details.
 Vendor can contact(email) with customers.
 Vendor can manage inquiry.

5. Visitor

 Visitor can visit the website.

 Visitor can view the service, car parts and old cars.
 Visitor can register in the website as a customer.
 Visitor can make inquiry.
 Visitor can contact by email.

P a g e 5 | 149
 CHAPTER: 2

Environment Description
2.1 Hardware / Software Requirement
2.2 Tools & Technology

P a g e 6 | 149
 2.1 Hardware / Software Requirement

Hardware Requirements
 Development side:

 Processor : RYZEN 5
 Ram : Minimum 8 GB or Above
 Disk Space : Minimum 256 GB or Above

 Client side:

 Ram : Minimum 2 GB or Above

 Internet enabled device

 Server side:

 Disk space: Minimum 256 GB or Above

Software Requirements
 Development side:

 Figma (Design)
 Xampp
 Visual Studio Code
 PhpMySQLi

 Client side:

 Browsers (Any)

 Server side:

 Xampp

P a g e 7 | 149
 2.2 Tools & Technology

2.2.1) Core Technology:

 PHP:

 PHP is a server – side cross- platform, HTML embedded scripting language.

 PHP is also the oldest HTML – embedded scripting language, giving it a
head start on all the others.
 PHP stands for PHP: “Hypertext Preprocessor”
 PHP is a server-side scripting language.
 PHP script executed on the server.
 PHP supports many databases (MySQL, Oracle, Sybase etc.)
 PHP is open-source software.
 PHP is free to download and use.
 PHP runs on different platforms (Windows, Linux etc.)
 PHP is compatible with almost all servers used today (Apache, IIS)
 PHP is easy to learn and runs efficiently on the server side.

 Advantages of PHP:
 PHP applications are very stable and do not depend on the browser
technologies unlike JavaScript applications which depend on browsers.
 PHP provides the freedom to select any server platform.
 The browser does not know that the HTML page is generated by PHP.
 PHP excellent database connectivity to all SQL database servers.
 PHP has partial support for Object Oriented features.
 PHP has very large user base and developer base.

P a g e 8 | 149
 MYSQL:

 MYSQL is a relational database system that is used to store information.

 MYSQL can store many types of data from something as tiny as a single
character to as large as complete files or graphics.
 MYSQL is ideal for both small and large applications.
 Information stored in a MYSQL database hosted on a web server can be
accessed from anywhere in the world with a computer.
 MYSQL databases are typically used for web application development
(Often accessed using PHP).
 MYSQL is currently available under two different licensing agreements: Free
of charge, under the GNU General Public License (GPL) open-source
system
 MYSQL is used in a wide range of applications, including data warehousing,
e- commerce, Web databases, logging applications and distributed
applications.
 MYSQL complies on a number of platforms.

 Reasons of using MYSQL:

 MYSQL is an extensible, open storage database engine, offering multiple

variations such as Berkeley DB, InnoDB, Heap and MyISAM.
 MYSQL integrates seamlessly with a number of programming languages
and other web – based technologies.
 MYSQL is an open-source system under the GNU General Public License;
Developers can use it at no cost as long as the associated projects are also
open – source.
P a g e 9 | 149
  In the way of performance, MYSQL is the clear leader, mainly due to the
format of its default table, MyISAM.
 MySQL is characterized as a free, fast, reliable open-source relational
database.
 MySQL executes most queries much faster than most other database
systems.
 Because of its modularity and its flexibility in configuration, MySQL can run
in systems varying in size from embedded systems to large multiprocessor.
 MySQL is easy to install and administer. While other database system
requires special knowledge.

 XAMPP Server:

 XAMPP is a free, open-source software package that includes a collection of

tools and software used for web development.
 The name XAMPP is an acronym for the key components that are included
in the package:

X: Cross-platform

A: Apache HTTP Server

M: MariaDB or MySQL database

P: PHP programming language

P: Perl programming language

 XAMPP allows developers to easily set up and run a local web server
environment on their own computer, without having to install and configure
each of the necessary components separately.

P a g e 10 | 149
 This is especially useful for web developers who need to test their websites or
web applications before publishing them to a live web server.
 XAMPP is a convenient and powerful tool for web development and testing,
and it has become a popular choice among developers worldwide.

 Advantages of XAMPP Server:

 XAMPP is easy to install and setup, as it comes with an installer that guides
you through the process.
 XAMPP includes all the necessary components for web development,
including Apache, MySQL or MariaDB, PHP, Perl, and other essential tools.
 This means that you don't need to install and configure each component
separately.
 XAMPP comes with a user-friendly interface that allows you to manage your
web server settings, install add-ons and extensions, and start and stop the
Apache and MySQL servers with ease.
 XAMPP is a free and open-source software package, which means that you
can use it for commercial and non-commercial purposes without any
restrictions.

P a g e 11 | 149
  PHPMYADMIN:

 PhpMyAdmin can manages a whole MYSQL server (needs a super-user)

 as well as a single database.

Supported features currently PhpMyAdmin can:

 Browse and drop databases, tables, views, columns and indexes.

 Display multiple result sets through stored procedures or queries.
 Create copy, drop, rename and alter databases, tables, columns and
 indexes.
 Maintenance server, databases and tables with proposals on server
 configuration.
 Execute, edit and bookmark any SQL-statement, even batch-queries.
 Load text files into tables

P a g e 12 | 149
 CSS:

 CSS stands for Cascading Style Sheets

 CSS describes how HTML elements are to be displayed on screen, paper, or
in other media.
 CSS saves a lot of work. It can control the layout of multiple web pages all at
once.
 External stylesheets are stored in CSS files.
 CSS is designed to enable the separation of presentation and content,
including layout, colors and fonts.
 This separation can improve content accessibility, provide more flexibility
and control in the specification of presentation characteristics,
enablemultiple web pages to share formatting by specifying the relevant
CSS in a separate.
 CSS file, and reduce complexity and repetition in the structural content.

 Advantages of CSS:

 Allows separating content of an HTML document from style and layout of

that document.
 Make documents much easier to maintain and give much better control over
the layout of your web pages.
 CSS saves lots of time.
 Easy maintenance.
 Pages load faster.
 Multiple device compatibility.

P a g e 13 | 149
2.2.2) Extra Technology:
 JavaScript:
 JavaScript is a high-level, interpreted programming language that conforms
to the ECMAScript specification. It is a programming language that is
characterized as dynamic, weakly typed, prototype-based and multi-
paradigm.
 JavaScript is one of the core technologies of the World Wide Web.
 JavaScript enables interactive web pages and is an essential part of web
applications.
 The vast majority of website use it, and major web browser have a
dedicated JavaScript engine to execute it.
 JavaScript is use for validation.

 Advantages of JavaScript:

 The biggest advantages to a JavaScript having a ability to produce the same

result on all modern browsers.

 Client-Side execution:
No matter where you host JavaScript, execute always on client environment to save
a bandwidth and make execution process fast.

 Browser Compatible:
The biggest advantages to a JavaScript having a ability to support all modern
browser and produce the same result.

 User Interface Interactivity:

JavaScript used to fill web page data dynamically such as drop-down list for
a Country and State. Base on selected Country, State drops down list
dynamically filled. Another one is Form validation, missing/incorrect fields
you can alert to a user’s using alert box.

P a g e 14 | 149
 jQuery:
 jQuery is a cross-platform JavaScript library designed to simplify the client-
side scripting of HTML.
 jQuery is a fast, small, and feature-rich JavaScript library.
 It makes things like HTML document traversal and manipulation, event
handling, animation, and Ajax much simpler with an easy-to-use API that
works across a multitude of browsers.
 With a combination of versatility and extensibility, jQuery has changed the
way that millions of people write JavaScript.

 Advantages of jQuery:
 Its light weight when compared to other JavaScript frameworks.
 It has a wide range of plugins available for various specific needs.
 It is easier for a designer to learn jQuery as it uses familiar CSS syntax.
 jQuery is open-source software.

P a g e 15 | 149
 Bootstrap:

 Bootstrap is a front-end framework that is developed to support creating

dynamic websites and web applications.
 It is one of the most preferred front-end frameworks as it aids an easy and
fast processing to develop a website.
 It supports all major browsers and fast loading responsive web pages.
 Bootstrap consists of HTML and CSS-based design templates for various
interface components and is aimed to ease web development.
 Bootstrap is compatible with almost all the latest version browsers such as
Internet Explorer, Google Chrome, Opera, Firefox, and Safari. It supports the
responsive web design and dynamically adjusts the layout of web pages by
considering the characteristics of the device used.

 Advantages of Bootstrap:

 Easy to use.
 Responsive features
 Consistent Design
 Save time
 Open Source

P a g e 16 | 149
 Miro:

 Miro is an online collaborative whiteboarding platform that enables

teams to work together and share ideas visually in real-time. It allows
teams to create and collaborate on various types of digital boards such
as mind maps, diagrams, flowcharts, wireframes, and more.
 Miro is popular among teams in various industries such as design,
marketing, product management, and education. It allows teams to
collaborate remotely, making it easier to work with team members who
are located in different regions or time zones.

 Advantages of Miro:

 Miro enables teams to work together on digital whiteboards in real-time,

allowing for seamless collaboration regardless of team members'
location.
 Miro integrates with popular collaboration tools such as Trello, Slack,
and Google Drive, making it easier to manage projects and
communicate with team members.
 Miro is available on various devices such as desktops, laptops, tablets,
and smartphones, enabling team members to access their digital
boards from anywhere at any time.
 Miro has a user-friendly interface.
 Miro provides enterprise-grade security features, including two-factor
authentication and data encryption, to ensure that team data remains
secure.

P a g e 17 | 149
 CHAPTER: 3

Proposed System
3.1 Scope
3.2 Aim & Objectives
3.3 Expected Advantages

P a g e 18 | 149
 3.1 Scope

This project is designed so as to be used by HI-TECH MOTOR WORKS

specializing in car servicing, old car sells and car parts selling. It is an online system
through which customer can view available services, registration and book service,
buy parts and also purchase old car.

Every organization, whether big or small, has challenges to overcome and

managing the information of car, service center, parts of car, registration. Every car
service center management system has different service center needs therefore we
design exclusive car care system that are adapted to you.

There are five types of users in our application:

 Admin
 Customer
 Employee
 Vendor
 Visitor

P a g e 19 | 149
1. Admin

 Admin can manage all services.

 Admin can manage car modification details.
 Admin can manage car parts.
 Admin can approve seller.
 Admin can approve old car.
 Admin can view order details.
 Admin can view invoice.
 Admin can view and manage inquiry.
 Admin can view and manage FAQ.
 Admin can manage payment information.
 Admin can manage about us information.

2. Customer

 Customer can view all services and book appointment for car service.
 Customer can view modified cars and book appointment for modify
their car.
 Customer can view all parts and purchase car parts.
 Customer can view old cars and also buy old cars.
 Customer can make payment.
 Customer can make inquiry.
 Customer can give the review & rating.

3. Employee

 Employee can view works.

 Employee can view profile.
 Employee can update profile.
 Employee can update status.
 Employee can view review & rating.

P a g e 20 | 149
4. Vendor

 Vendor can add old car for sell.

 Vendor can add old car details.
 Vendor can contact(email) with customers.
 Vendor can manage inquiry.

5. Visitor

 Visitor can visit the website.

 Visitor can view the service, car parts and old cars.
 Visitor can register in the website as a customer.
 Visitor can make inquiry.
 Visitor can contact by email.

P a g e 21 | 149
 3.2 Aim & Objectives

1) Increasing accuracy and work speed:

 By maintaining all the work on computer will increase accuracy as well as

speed of work.
 The report can be generated at any time by Admin.
 It can be easily used and the time is decreased.

2) To Store information safely:

 To store the information of all the registered Users.

 To keep track of information of every visitor.
 To keep information about active users.
 To keep details of all uploads.
 To store information of Admin.

3) To evolve information the latest technology:

 To evolve the latest technology using internet of traditional style.

 To minimize the human effort made by the admin evolved in the manual Rent-
N-Go.

4) Generate Reports in time:

 To provide timely reports to the admin as and when required.

 To produce summarized and accurate reports required for the decision
making.
 To get the result quicker than the manual process.

P a g e 22 | 149
 3.3 Expected Advantages

 This garage management system is fully functional and flexible.

 It is very easy to use.
 This garage management system helps in back-office administration by
streamlining and standardizing the procedures.
 It saves a lot of time, money and labour.
 Eco-friendly: The monitoring of the vehicle activity and the overall
business becomes easy and includes the least of paper work.
 The website acts as an office that is open 24/7.
 It increases the efficiency of the management at offering quality services
to the customers.
 It provides custom features development and support with the software.

P a g e 23 | 149
 CHAPTER: 4

System Planning
4.1 Requirement Specification
4.2 Feasibility Study
4.3 Life Cycle Models
4.4 Effort Distribution Diagram
4.5 Task Dependency Diagram
4.6 Project Schedule Chart

P a g e 24 | 149
 4.1 Requirement Specification

❖ Admin Side:

 Maintain car details

 Maintain driver details
 Maintain customer details
 Maintain company details
 Maintain uploaded cars details
 Maintain gallery

❖ Client Side:

 User can book car

 User can register
 User can login
 User can check about us page
 User can check contact us page

P a g e 25 | 149
 4.2 Feasibility Study

Feasibility study plays very important role in the development of any

system, but when it is the case of development of any software then its
importance increases much more because in the case one should be
very clear about availability of the time and resources. Before starting
the development of the software, one should give considerable amount
of time for feasibility study because the successful completion of project
depends upon feasibility. The feasibility of our project has been judged
on the basis of time, technology, resources available and project
length.

 Time:

This project takes at least 3 months to be completed if we take help of

reused components otherwise it will take 6 months to be complete. We
will not make use of components and therefor will be complete the
project in 6 months. Thus according to time the feasibility is not that
right.

 Technology:

The necessary technology, front-end development tool, back-end

database technology and various other tools namely installation tools,
etc. for developing the system, are already available within the
organization. So this problem is feasible.

 Resources:

We need good knowledge software engineers and practitioners. We

need net connection. We have all the resources in the desired amount.

 Project Size:

The Project size might be above 1500 LOC. This is just the rough
assumption because we don’t have any basis of the past projects. Thus
the project overall feasibility is normal and therefore we have
undertaken this project.

P a g e 26 | 149
 4.3 Life Cycle Model

Requests Proposal

Requirement 90% of requirements understood

Definition

Prototype 1

High Level
Requirements met
Design

Detail Design 90% of design done

Prototype 2
System
Construction Design Approved

Coding Complete

System
Construction

Product Delivery

P a g e 27 | 149
 4.4 Effort Distribution Diagram

Testing
Debugging
(40 %)
Analysis and

Design

(40 – 50 %)

Coding

(10 %)

Project Planning : 2 To 3%

Requirement Analysis : 10 To 25%

Design : 20 To 25%

Coding : 10 %

Testing/Debugging : 40 %

P a g e 28 | 149
 4.5 Task Dependency Diagram

Requirment Cathering

Requirment Analysis

Estimation Scheduling

Testing

Estimation

Coding & Integrationing Module

Testing

Delivery Confirmation

P a g e 29 | 149
 Work breakdown Structure:
It is divided into five main parts:

1.Scope& Planning:

In this particular phase of the project, we have explained the program

definition along with its requirements in detail. All the research work
and background study prior the project initialization has been
conducted in this phase. The work breakdown structure and scheduling
chart is prepared after conducting the feasibility study and risk analysis.

2.Requirement Analysis:

Here we have tired to gather all the requirements pertaining program

code, user interface and database design. The detailed flow of data in
the system is depicted. We have shown relationship between the
entities of data through entities relationship diagrams. This particular
phase leads milestone software requirement specification.

3.User Interface Designing:

Depending on the inputs and outputs of the system i.e., the interaction
between the user and the system we have designed the interface. We
have made it simple and attractive which makes it more users friendly.
4.Implementation and Testing:

Depending upon the requirement specified in scope, we have

implemented the system using latest ASP.Net technology.

5.Other Peripheral Activities for Quality Assurance:

Continuously meeting were held for project tracking and analyzing the
higher risks. Their degree of rigor was always tested and properly
documented. These activities were conducted considering our budget
constraints and required accuracy, it helped us to be focused and built
a quality product.

P a g e 30 | 149
4.6 Project Schedule Chart

P a g e 31 | 149
 CHAPTER: 5

UML Diagram
5.1 Use-Case Diagram
5.2 Activity Diagram
5.3 Sequence Diagram

P a g e 32 | 149
 5.1 Use Case Diagram

Admin Side:

P a g e 33 | 149
 Manage Service:

 Manage Parts:

 Manage Car Brands:

P a g e 34 | 149
 Manage Employee:

 Manage Parts Order:

P a g e 35 | 149
 Manage Service Booking:

 Manage Car Booking:

P a g e 36 | 149
 Manage Vendors:

 Manage Users:

P a g e 37 | 149
 Manage Profile:

 Inquiry:

 Review & Rating:

P a g e 38 | 149
 About Us:

 Contact Us:

 Faq:

P a g e 39 | 149
Customer Side:

P a g e 40 | 149
 View Service:

 Book Service Appointment:

 View & Buy Parts:

P a g e 41 | 149
 View & Buy Old Cars:

 Make Payment:

 Purchase Invoice:

P a g e 42 | 149
 Manage Profile:

 Review & Rating:

 Make Inquiry:

P a g e 43 | 149
Employee Side:

 Manage Work:
P a g e 44 | 149
 Manage Profile:

 Review & Rating:

P a g e 45 | 149
Vendor Side:
P a g e 46 | 149
 Manage Car:

 Manage Booking:

P a g e 47 | 149
Visitor Side:

P a g e 48 | 149
 5.2 Activity Diagram

Admin:

P a g e 49 | 149
Manage service:

P a g e 50 | 149
Manage parts:

P a g e 51 | 149
Manage car brands:

P a g e 52 | 149
Manage Employee:

P a g e 53 | 149
Manage parts order:

P a g e 54 | 149
Manage service booking:

P a g e 55 | 149
Manage car booking:

P a g e 56 | 149
Manage vendors:

P a g e 57 | 149
Manage User:

P a g e 58 | 149
Manage Profile:

P a g e 59 | 149
Inquiry:

P a g e 60 | 149
Review & Rating:

P a g e 61 | 149
FAQ:

P a g e 62 | 149
Customer:

P a g e 63 | 149
Employee:

P a g e 64 | 149
Vendor:

P a g e 65 | 149
 5.3 Sequence Diagram

Admin:

P a g e 66 | 149
User:

P a g e 67 | 149
Employee:

P a g e 68 | 149
Vendor:

P a g e 69 | 149
 CHAPTER: 6

System Design
6.1 Class Diagram
6.2 Table Structure
6.3 Navigation Map
6.4 Screen Layout

P a g e 70 | 149
6.1 Class Diagram

P a g e 71 | 149
 6.2 Table Structure

1. Table Name: admin_master

Use: This table contains details of the admin.

Field Data
Size Constraints Description
Name Type

auto increment id the

aid integer 03 primary
admin_master

username varchar 15 not null it is use to store name

it is use to store
password varchar 15 Not null
password

2. Table Name: aboutus

Use: This table contains details of the aboutus.

Field Data
Size Constraints Description
Name Type

auto increment id the

id integer 03 primary
aboutus

title varchar 100 not null it is use to store title

it is use to store
description varchar 100 not null
description

3. Table Name: addtocart

P a g e 72 | 149
Use: This table contains details of the add to cart.

Field Data
Size Constraints Description
Name Type
auto increment id the
cartid integer 03 primary
addtocart

uid integer 03 not null it is use to store user id

pdid integer 03 not null it is use to store product id

qty integer 11 not null it is use to store quantity

it is use to store product add

adddate date - not null
date

4. Table Name: brand_master

Use: This table contains details of the car brand

Field Data
Size Constraints Description
Name Type

auto increment id the

bid integer 03 primary
brand_master

it is use to store brand

bname varchar 15 not null
name

logo varchar 01 not null it is use to store logo

5. Table Name: car_one

P a g e 73 | 149
 Use: This table contains details of the car detail.

Field Data
Size Constraints Description
Name Type

auto increment id the

cdid integer 03 primary
car_detail

bid integer 03 not null it is use to store car brand id

vid integer 03 not null it is use to store vender id

it is use to store car model

cmyear year 04 not null
year

it is use to store car model

cmname varchar 20 not null
name

it is use to store car front

cfphoto varchar 20 not null
photo

it is use to store car back

cbphoto varchar 20 not null
photo

it is use to store car interial

ciphoto varchar 20 not null
photo

fueltype varchar 20 not null it is use to store fuel type

it is use to store car engine

engcc integer 20 not null
cc

colour varchar 10 not null it is use to store car colour

km integer 10 not null it is use to store kilometer

type varchar 20 not null it is use to store car type

feature integer 100 not null it is use to store car feature

price integer 10 not null it is use to store car price

6. Table Name: car_booking

Use: This table contains details of the car booking.

P a g e 74 | 149
 Field Data
Size Constraints Description
Name Type

auto increment id the

bid integer 03 primary
car_booking

uid integer 03 not null it is use to store user id

it is use to store car

cdid integer 03 not null
details id

it is use to store vender

vid integer 30 not null
id

it is use to store booking

bdate date - not null
date

it is use to store delivery

ddate date - not null
date

it is use to store car

price integer 15 not null
price

it is use to store
is_pay integer 02 not null
payment status

it is use to store booking

status integer 02 not null
status

7. Table Name: contactus

Use: This table contains details of the contact us.

P a g e 75 | 149
 Field Data
Size Constraints Description
Name Type

auto increment id the

cid integer 03 primary
contactus

name varchar 50 not null it is use to store name

it is use to store email

email varchar 50 not null
address

it is use to store phone

phone integer 12 not null
number

sub varchar 25 not null it is use to store subject

it is use to store
mess varchar 200 not null
message

8. Table Name: emp

Use: This table contains details of the employee.

Field Name Data Type Size Constraints Description

eid integer 03 primary auto increment id the emp

it is use to store employee

ename varchar 20 not null
name

it is use to store image of

ephoto varchar 10 not null
employee

password varchar 10 not null it is use to store password

it is use to store mobile

mobile integer 12 not null
number

sid integer 10 not null it is use to store service id

9. Table Name: faq

Use: This table contains details of the frequently asked questions.

P a g e 76 | 149
 Field Data
Size Constraints Description
Name Type

auto increment id the

id integer 03 primary
faq

it is use to store
question varchar 100 not null
question

answer varchar 100 not null it is use to store answer

10. Table Name: order_history

Use: This table contains details of the order history.

Field Name Data Type Size Constraints Description

auto increment id the

oid integer 03 primary
order history

uid integer 03 not null it is use to store user id

ofname varchar 25 not null it is use to store name

ophone integer 12 not null it is use to store phone

oemail varchar 30 not null it is use to store e-mail

oaddress varchar 100 not null it is use to store address

ocity varchar 20 not null it is use to store city

ostate varchar 20 not null it is use to store state

opincode integer 11 not null it is use to store pincode

it is use to store order

odate date - not null
date

ototal integer 10 not null it is use to store total

ostatus integer 02 not null it is use to store status

P a g e 77 | 149
 11. Table Name: order_master

Use: This table contains details of the order master.

Field Name Data Type Size Constraints Description

auto increment id the

oid integer 03 primary
order history

it is use to store user

uid integer 03 not null
id

ofname varchar 25 not null it is use to store name

ophone integer 12 not null it is use to store phone

oemail varchar 30 not null it is use to store e-mail

it is use to store
oaddress varchar 100 not null
address

ocity varchar 20 not null it is use to store city

ostate varchar 20 not null it is use to store state

it is use to store
opincode integer 11 not null
pincode

it is use to store order

odate date - not null
date

ototal integer 10 not null it is use to store total

ostatus integer 02 not null it is use to store status

12. Table Name: parts_detail

Use: This table contains details of the parts details.

Field Data Size Constraints Description

P a g e 78 | 149
 Name Type

auto increment id the

pdid integer 10 primary
parts detail

it is use to store parts

pid integer 10 not null
id

it is use to store parts

pdname varchar 20 not null
name

it is use to store part

photo varchar 10 not null
photo

it is use to store part

brand varchar 20 not null
brand

it is use to store part

description varchar 100 not null
description

it is use to store
qty integer 10 not null
quantity

it is use to store part

price integer 10 not null
price

13. Table Name: parts_master

Use: This table contains details of the parts master.

Field Data Size Constraints Description

P a g e 79 | 149
 Name Type

auto increment id the

pid integer 10 primary
parts_master

it is use to store parts

pname varchar 20 not null
name

photo varchar 01 not null it is use to store image

14. Table Name: parts_order

Use: This table contains details of the parts order.

Field Data
Size Constraints Description
Name Type

auto increment id the

poid Integer 10 primary
parts order

Uid Integer 10 not null it is use to store user id

Pdid Integer 10 not null it is use to store parts id

Pdname Varchar 20 Not null it is use to store name

it is use to store
Qty Integer 10 Not null
quantity

Pphoto Varchar 50 Not null it is use to store photo

Price Integer 10 Not null it is use to store price

Status Integer 02 Not null it is use to store status

15. Table Name: register_user

Use: This table contains details of the register user

Field Data Size Constraints Description

P a g e 80 | 149
 Name Type

auto increment id the

uid integer 10 primary
register_user

uname varchar 50 not null it is use to store name

mobile integer 12 not null it is use to store mobile

email varchar 50 not null it is use to store email

it is use to store
password varchar 10 not null
password

status integer 02 not null it is use to store status

otp integer 04 not null it is use to store otp

P a g e 81 | 149
 16. Table Name: service_booking

Use: This table contains details of the car brand

Field Data
Size Constraints Description
Name Type

auto increment id the

sbid integer 03 primary
service booking

Uid Integer 03 not null it is use to store user id

Eid Integer 03 not null it is use to store emp id

Sdid Integer 03 not null it is use to store id

Name Varchar 50 not null it is use to store name

Email Varchar 50 not null it is use to store email

it is use to store
Phone Integer 12 not null
number

it is use to store
Compname Varchar 20 not null
company name

Model Varchar 20 not null it is use to store model

Year Integer 04 not null it is use to store year

it is use to store
Bdate Date - not null
booking date

it is use to store
Ddate Date - Not null
delivary

Total Integer 10 Not null it is use to store total

it is use to store
Is_pay Integer 10 Not null
method

Status Integer 02 Not null it is use to store status

P a g e 82 | 149
 17. Table Name: service_detail

Use: This table contains details of the service detail.

Field Data
Size Constraints Description
Name Type

auto increment id the

sdid integer 10 primary
service detail

sid integer 15 not null it is use to store id

it is use to store service

sdname varchar 20 not null
name

photo varchar 10 not null it is use to store photo

it is use to store
description varchar 100 not null
description

it is use to store
duration varchar 20 not null
duration

status Integer 02 not null it is use to store status

price integer 10 not null it is use to store price

18. Table Name: service_master

Use: This table contains details of the service master.

Field Data
Size Constraints Description
Name Type

auto increment id the

sid integer 10 primary
service_master

it is use to store service

sname varchar 20 not null
name

photo varchar 10 not null it is use to store photo

19. Table Name: vender_registration

P a g e 83 | 149
Use: This table contains details of the car brand

Field Data
Size Constraints Description
Name Type

auto increment id the

vid integer 10 primary
vender registration

it is use to store vender

vname varchar 20 not null
name

it is use to store phone

phone integer 12 not null
number

it is use to store email

email varchar 20 not null
id

it is use to store
password varchar 15 not null
password

it is use to store vender

address varchar 50 not null
address

it is use to store vender

city varchar 20 not null
city

it is use to store vender

status integer 02 not null
status

P a g e 84 | 149
 6.3 Navigation Map

Admin Side:

To be Continued…

P a g e 85 | 149
To be Continued…
P a g e 86 | 149
P a g e 87 | 149
Customer Side:

P a g e 88 | 149
Employee Side:

P a g e 89 | 149
Vendor Side:

P a g e 90 | 149
Visitor Side:

P a g e 91 | 149
 6.4 Screen Layout

 Admin Side:

Login:

P a g e 92 | 149
Dashboard:

P a g e 93 | 149
Service Master:

Service details:

P a g e 94 | 149
Parts Master:

Parts Details:

P a g e 95 | 149
Car brand master:

Employee:

P a g e 96 | 149
Parts order:

Service booking detail:

P a g e 97 | 149
Complete service detail:

Car booking:

P a g e 98 | 149
Vendor detail:

User detail:

P a g e 99 | 149
About us:

Contact us:

P a g e 100 | 149
Faqs:

Edit profile:

P a g e 101 | 149
  Employee Side:

Login:

Dashboard:

P a g e 102 | 149
Service detail:

Completed service:

P a g e 103 | 149
Employee profile:

P a g e 104 | 149
  Vendor Side:

Login:

Dashboard:

P a g e 105 | 149
Car detail:

Car booking:

P a g e 106 | 149
Edit profile:

P a g e 107 | 149
  User Side:

Registration:

Login:

P a g e 108 | 149
P a g e 109 | 149
Parts:

P a g e 110 | 149
Parts detail:

View Cart:

P a g e 111 | 149
Cart:

P a g e 112 | 149
Check out:

P a g e 113 | 149
Payment:

P a g e 114 | 149
Payment method:

P a g e 115 | 149
Payment success:

P a g e 116 | 149
Payment message:

P a g e 117 | 149
Services:

P a g e 118 | 149
Services:

P a g e 119 | 149
Schedule service:

P a g e 120 | 149
Car:

P a g e 121 | 149
shop:

P a g e 122 | 149
Car detail:

P a g e 123 | 149
Car booking:

P a g e 124 | 149
Contact us:

P a g e 125 | 149
Faqs:

P a g e 126 | 149
User profile:

P a g e 127 | 149
 CHAPTER: 7

System Testing
7.1 Testing Introdcution
7.2 Test Case

P a g e 128 | 149
 7.1 Testing Introduction

 What is Testing?

 Testing is the process of examining an application to ensure it fulfills

the requirements for which it was designed and meets quality
expectations.
 More importantly, testing ensure the application meet customer
expectations.
 Testing accomplished a verity of things but most importantly it
measures the quality of websites you are developing.
 This view presupposes there are defect in your website waiting to be
discovered and this view is rarely disproved or even disputed.

 Types Of Testing:

 Integration Testing:
We have used top-down testing strategy for integrating web pages. The
separately generated web pages will be integrated and for checking
that they work properly after their integration, tests will be conducted to
ensure their proper functionality.

Using dummy web pages, it is checked that weather output of page

will redirect to specific webpage After that regression testing strategy
help us to ensure that changes do not introduce unintended behavior or
additional.

P a g e 129 | 149
 Validation Testing:

After integration testing, Web site is completely assembled as a

package interfacing error has been uncovered and correct and the final
series of the web site test. The validation succeeds when the web site
function in a manner that can be reasonably accepted by the client.
Validation tests provide assurance that the website as written meets
requirement.

 White Box Testing:

While box testing is testing case design method that uses the control
structure of the procedural design testcases. Using white box testing
methods, one can devices that cases that –
 Grantees that all independent paths within a module have been
exercised at least once.
 Exercise all logical decision on their true and false sides.
 Exercise all loops at their boundaries and within their operational
bounds.
 Exercises internal data structure to ensure their validity

 Black Box Testing:

Black box s the method of software testing that tests the factuality of
applications appeased to it internal structure or workings. Specific
knowledge of application’s code /internal structure & programming
knowledge in general is not require Test cases are built around
specification & requirement, i.e., what application supposed to do.it
uses external description of the software, including specification,
requirements and design to derive test cases. These cases can be
functional or non-functional through usually function. The test designers
select valid and invalid inputs and determine the correct output. There
is no knowledge of the test object’s internal structure testing.

P a g e 130 | 149
 Unit Testing:

In the web-based application smallest testable unit is web page itself.

So, the web pages of the site are to be unit tested. Each web page
contains content, navigational links and processing elements (Scripts,
event handlers etc.). The testing will be driven by the content
processing and links contained in the site.

Using black box testing technique web pages are tested unit by unit for
whether they receive input properly and give output in proper format or
redirect to specific web page. It is also tested that the error message
are properly displayed and give user-friendly information.

 Alpha Testing:

Alpha testing makes use of prototypes to test the software in its beta
stage. However, you cannot expect the software to possess complete
functionality for which it is designed especially at this stage. This is
because alpha testing is usually conducted to ensure that the software
that is being developed provides all necessary core function and that
accepts all inputs and gives expected output.

Alpha test are conducted in the software developers’ offices or on any

designated systems so that they can monitor the test and list out any
errors or bugs that may be present. Thus, some of the most complex
codes are developed during alpha testing stage. Furthermore, the
project manager who is handling the testing process will need to talk to
the software developer on the possibilities of integrating the results
procured from alpha testing process with the future software design
plans so that all potential future problem can be avoided.

 Beta Testing:

In software development, beta test is the second phase of software

testing in which a sampling of intended audience tries the product out.
Originally, the term alpha test meant the first phase of testing in a
software development process. The first phase includes unit testing,
component testing and system testing. Beta testing can be considered
“pre-release testing “. Beta test versions of software are now distributed
P a g e 131 | 149
 to a wide audience on the web partly to give the program a “Real World
“test and partly to provide a preview of the next release.

Beta testing comes after alpha testing and can be

consider as a form of extremer user acceptance testing. Version of the
software, known as beta versions, is released to a limited audience
outside of the programming team. The software is released to group of
people so that further testing can ensure the products have few faults
or bugs. Sometimes, Beta version are made available to the open
public to increase the feedback field to a maximal number of the future
users.

 System Testing:

The uncovered weakness that was not found in earlier tests are
removed In System testing. The system is corrected such a way that it
does not affect the forced system failure. The testing is done with the
low volume of transaction based on live data. Finally, the total system is
also tested to ensure that no data are lost.

Following testing on the completed system will be performed in order to

find the errors before they become defects and correct them.

 In order to eliminate navigational errors, the site will be reviewed and

tested. The use cases scenarios that we have developed in the same
document while requirement analysis activity will be considered to
uncover errors in the navigational links.
 Web pages of the site will be unit tested. For the web pages
sometimes, the smallest testable unit is the single web page itself.
Each web page contains content, Navigational links, and processing
elements (Scripts, event handlers etc.). The testing will be driven by the
content processing and links contained in the site.
 The separately generated web pages will be integrated and for
checking that they work properly after their integration, tests will be
conducted to ensure their proper functionality.
 The functionality of the site will be checked with the different versions of
the Internet Explorer, Netscape Navigator etc. and wherever necessary
it will be attempted to change the implementation of the not working for
some browsers fir some case and of course without losing the purpose
of the functionality if possible.

P a g e 132 | 149
P a g e 133 | 149
 7.2 Test Case

Admin:

No. Field Input Valid / Validation

data Invalid
1 Username Black Invalid Username can’t be blank
Admin Valid Redirect towards the
page
2 Password Black Invalid Password can’t be
blank
Admin28 Valid Redirect towards the
page

P a g e 134 | 149
Customer:

No. Field Input data Valid / Validation

Invalid

1 Customer Black Invalid Customer name can’t be blank

name

xyz Valid Redirect towards the page

2 Phone Black Invalid Contact number can ‘t be blank

Character Invalid Contact number can’t contain

character

$$$ Invalid Contact number can’t contain

special character

123 Valid Redirect towards the page

3 Password Black Invalid Password can’t be blank

Character Valid Enter greater than eight

characters

123 Valid Enter greater than eight digits

4 Email abc@ Invalid Email incorrect

abc@gmail Invalid Email incorrect

[email protected] Valid Redirect towards the page

5 Status Black Invalid Status can’t black

Number Valid Redirect towards the page

P a g e 135 | 149
Vendor:

No. Field Input data Valid / Validation

Invalid

1 Vendor Black Invalid Vendor name can’t be blank

name

xyz Valid Redirect towards the page

2 Phone Black Invalid Contact number can ‘t be blank

Character Invalid Contact number can’t contain

character

$$$ Invalid Contact number can’t contain

special character

123 Valid Redirect towards the page

3 Password Black Invalid Password can’t be blank

Character Valid Enter greater than eight

characters

123 Valid Enter greater than eight digits

4 Email abc@ Invalid Email incorrect

abc@gmail Invalid Email incorrect

[email protected] Valid Redirect towards the page

5 Address Black Invalid Address can’t be black

$$$ Invalid Special character is not valid

19abc Valid Redirect towards the page

6 City Black Invalid City can’t be black

123 Invalid Number is not valid

Character Valid Redirect towards the page

7 Status Black Invalid Status can’t black

Number Valid Redirect towards the page

P a g e 136 | 149
Employee:

No. Field Input data Valid / Validation

Invalid

1 Employee Black Invalid Vender name can’t be blank

name

123 Invalid Number is not valid

xyz Valid Redirect towards the page

2 Phone Black Invalid Contact number can ‘t be blank

Character Invalid Contact number can’t contain

character

$$$ Invalid Contact number can’t contain

special character

123 Valid Redirect towards the page

3 Password Black Invalid Password can’t be blank

Character Valid Enter greater than eight

characters

123 Valid Enter greater than eight digits

4 Employee Black Invalid Photo can’t be black

photo

123.jpg Valid Redirect towards the page

P a g e 137 | 149
 CHAPTER: 8

System Limitation &

Future Enhancement
8.1 System Limitation
8.2 Future Enhancement

P a g e 138 | 149
 8.1 System Limitation

The project report entitled "Garage Management System" has finally ended up in its
last stage thus achieving almost all its expectations. Based on a truly innovative “HI-
TECH MOTOR WORKS” concept, the system website has been developed with
much care that it is free of errors and at the same time it is efficient.

I have tried my level best to make the site as dynamic as possible for updating the
website information regularly as and when needed. Also, provision is provided for
future developments in the system website as per the requirements. Moreover, the
entire system website is made secured up to a certain level.

Limitations:

 Though it is web application but HI-TECH MOTOR WORKS is not in all cities,
so limited user will have advantage of site.
 We assign categorizing the customers two type user and vendor.

P a g e 139 | 149
 8.2 Future Enhancement

Once the s/w is developed tested and independent the focus is laid on
the support those focuses on change associated with error correction,
adaption required as the software environment evolves and changes
due to enhancement brought about by changing requirement.

 As software is used, the user will recognize additional functions that will
provide benefits, perfective maintenance extends the software beyond
is original functional requirements.
 At same time, the requirements as shown in this project report may
also change to provide user’s need or per software enhancement
requirements.
 The duration of three months was insufficient for the solution to be
developed. hence, in the future enhancement, the project can be
extended to have facility for users to upload their images, to give facility
to user to view update news and book helper to take services. The
project can be enhanced in many facilities in future.
 Adds up more searching features.
 Another addon futures supports that is useful in making application
better.

P a g e 140 | 149
 CHAPTER: 9

References
9.1 Bibliography
9.2 Webography

P a g e 141 | 149
 9.1 Bibliography

 All the needed information related to my project “HI-TECH MOTORS

WORKS” was being clumped from the following sources:

Books:

 For PHP: -
 PHP Manual

 PHP 5 Fast & Easy Web Development, Julie C. Meloni, 2nd Ed,
2002.

P a g e 142 | 149
 9.2 Webography

Sites URL:

 For PHP

 www.php.net
 http://www.w3schools.com/php/

 For MySQL

 http://dev.mysql.com/doc

 For JQuery and CSS

 http://jquery.com/
 http://css-tricks.com/
 http://cssglobe.com/

P a g e 143 | 149