A WEB APPLICATION

FOR
MOTOR DRIVING SCHOOL SYSTEM
By

Shaival Mehta (CE-117) (14CEUON103)

Aditya Krishnakumar (CE-02) (14ITUON030)
Shingala Kalpesh (CE-118) (14CEUOG064)

A project submitted
in
partial fulfillment of the requirements
for the degree of
BACHELOR OF TECHNOLOGY
in
COMPUTER ENGINEERING

Prof. Nainesh Patel Dr. C.K. Bhensdadia

Assistant Professor, Head,
Dept. Of Comp. Engg. Dept. Of Comp. Engg.

Faculty of Technology
Department of Computer Engineering
Dharmsinh Desai University
April 2017
 CERTIFICATE

This is to certify that the project work titled

MOTOR DRIVING SCHOOL SYSTEM

is the bonafide work of

Shaival Mehta (CE-117) (14CEUON103)

Aditya Krishnakumar (CE-02) (14ITUON030)
Shingala Kalpesh (CE-118) (14CEUOG064)

carried out in partial fulfillment of the degree of

Bachelor of Technology in Computer Engineering
at Dharmsinh Desai University in the academic session
December 2016 to April 2017.

Prof. Nainesh Patel Dr. C.K. Bhensdadia

Associate Professor, Head,
Dept. Of Comp. Engg. Dept. Of Comp. Engg.

Faculty of Technology
Department of Computer Engineering
Dharmsinh Desai University
April 2017
 CONTENTS

Abstract

1. Introduction

1.1 Project Details: Broad Specifications

1.2 Technology Used

2. Software Requirement Specification

2.1 Purpose

2.2 Scope

2.3 Overall Description

2.3.1 Product Perspective

2.3.2 Product Functions

2.3.3 User Classes and Characteristics

2.3.4 Operating Environment

2.3.5 Design and Implementation Constraints

2.3.6 Assumptions and Dependencies

2.4 External Interface Requirements

2.4.1 User Interfaces

2.4.2 Hardware Interfaces

2.4.3 Software Interfaces

2.4.4 Communication Interfaces

 2.5 Functional Requirements

3. Design

3.1 Use-case Diagram

3.2 Class Diagram

3.3 Sequence Diagram

3.4 Activity Diagram

3.5 State Diagram

3.6 E-R Diagram

4. Implementation

4.1 Implementation Environment

4.2 Modules Description

5. Testing

5.1 Testing Plan

5.2 Testing Strategy

5.3 Testing Methods

5.4 Test Cases

6. Screen-Shots

7. Limitations and Future Enhancements

8. Conclusion

9. Bibliography
 Abstract

Anybody above the age of 18 who wishes to drive a four-

wheeler, needs to have a proper understanding of the ins and
outs of a four-wheeler. For understanding and training purposes,
schooling is required.

A Motor Driving School helps to accomplish this task to make

sure the person learns how to drive a four-wheeler perfectly and
safely. It has a short term, 15 days or 30 days, training session,
where the learners are guided and mentored by a tutor on how to
drive the four-wheeler. In todays pacey world, four-wheeler
vehicles are necessary and hence the training for it is required.
 1. Introduction

1.1 Project Details: Broad Specifications

Motor Driving School System is a Web application.

It basically lets the learners or the ones who wish to get
trained sign up for the motor school, EazyDrive.

The system offers the users different packages where the

user chooses the number of days to get trained for and
according to it, pricing is done. A tutor is also allotted to
the learner for the chosen number of days. A learner can
also attempt practice tests for his license requirements.

1.2 Technology Used

Front End : JSP , CSS

As the system is a web application , the need of JSP

and CSS is understood . JSP is a technology used in Java
EE web applications.

Back End : Java EE

The project is built using the Java Enterprise Edition

(EE) stack.

Database : MySQL

MySQL is a relational database developed by Oracle

Corporation.

Diagram Tool : Umlet

 All the UML diagrams and various other diagrams
corresponding to this project are made in Umlet.
2. Software Requirement Specifications

2.1 Purpose

This is a SRS document refers to Motor Driving School

System Release 2017 version 1. It describes the functionality
and specification of how the Motor Driving School System
will help in serving the customers in an efficient way. It also
specifies how it will interact with the end users.

2.2 Scope

This system is designed to manage a Motor Driving

School in an efficient manner where the learners can register
to get trained.

System provides an interface for conducting tests online

by providing a user-friendly interface. System provides a
mechanism for the tutors to view their schedule allotted.

2.3 Overall Description

2.3.1 Product Perspective

This software is developed as a part of course work

the subject System Design Practice. The software aims
to manage four-wheeler training schedules. The web-app
s main perspective is towards providing a user-flexible
system.

2.3.2 Product Functions

The product offers a light weight User Interface to

work with and provides a secure way to deal with the
management stuff. The product also aims at making the
 motor driving school system online and along with the
admin panel, allocate schedule.

2.3.3 User Classes and Characteristics

Basically there are two types of end users i.e.,

(1) Learners:-
System is developed for people of 18 years of age
and above to get four-wheeler training.

(2) Tutors:-

The ones who view their schedule and are allocated

to a specific learner.

2.3.4 Operating Environment

The system is a web-app and not an Android or iOS

application because development in different operating
environment will take time and cross-platform
development is not the base of the development team and
a web-app can be used by everyone in an efficient way.

2.3.5 Design and Implementation Constraints

The tutors as well as learners cannot request for

leaves. Android and iOS native apps are not available.

2.3.6 Assumptions and Dependencies

System may not work if appropriate network is not

available. Mainline network of system highly needs
electricity to work on. System requires the learners to
make the payment offline to access the system.
2.4 External Interface Requirements

2.4.1 User Interfaces

Application can be accessed through any browser

interface. The software will be fairly compatible with
Microsoft Internet Explorer Version 6 and above or other
modern web browsers.

2.4.2 Hardware Interfaces

Server Side:

Operating System: Linux.

Processor: Pentium 3.0 GHz or higher.
RAM: 2GB or higher.
Hard-Disk: 100GB or more.
Client Side:

Operating System: Windows 7,8, 8.1,10.

Processor: Pentium 3.0 GHz or higher.
RAM: 2GB or higher.

2.4.3 Software Interfaces

Client Side:

HTML supported Web Browsers, Windows 7,8,

8.1, 10 ,MAC OS, Linux (All Flavors).

Server Side:

Linux, MySQL Database.

 2.4.4 Communication Interfaces

The Motor Driving School System shall use the HTTP

protocol for communication over the internet and for the
intranet communication will be through TCP/IP protocol
suite.

2.5 Functional Requirements

R1: System provides a feature for creating an account for

learners and tutors.

Input : Learner/Tutor Details

Output : Account Creation Status

Processing : The details added by the admin are

stored into the database.

R2: System requires the tutors and learners to provide the

details for logging in to the system

Input : Learner/ Tutor Credentials

Output : Home Page.

Processing: System takes the user credentials and

compares them with the database and
provides appropriate output.

R3: System provides an interface for the learners to

attempt practice tests.

R3.1: System displays the list of questions one by

one with their options for the ongoing test.
 R3.2: System requires the learners to select their
answer from the multiple choices.

R4: System allows the learner to change their schedule.

R4.1: System shows the current schedule.

Input : None

Output : Current schedule.

Processing : System fetches the information

from the database accordingly.

R4.2: System requires learner to select new start time

and end time.

Input : Start time and End time

Output : Updation status.

Processing : System updates the schedule.

R5: System provides an admin panel

R5.1: System allows the admin to manage tutors

and learners.

R5.2: System allows the admin to allocate a tutor to

the learner.

R6: System allows the tutor to view the schedule.

R6.1: System provides the tutor to view the allocated

learners.
3. Design

3.1 Use-Case Diagram

3.2 Class Diagram
3.3 Sequence Diagram

3.3.1 Attempt Test

3.3.2 Change Tuition Hours

3.3.3 Fill Up Attendance

3.3.4 Register Learner

 3.3.5 User Login

3.4 Activity Diagram

 3.4.1 Register Learner

3.4.2 Attempt Test

3.4.3 Change Tuition Hours

3.4.4 Fill Up Attendance

3.4.5 User Login
3.5 State Diagram

Attempt Test State Diagram

3.6 E-R Diagram
 4. Implementation

4.1 Implementation Environment

Java EE environment in Windows 10

MySQL Client in Windows 10

4.2 Modules Description

Register / Log - In Module

It is used to store information of learners and tutors

who are new to the system and accessing the system
for the first time and also authenticating the learners
and tutors.

Input : Users information or credentials

 Output:Stored or Verified successfully
Processing: Check users credentials in the
database while logging in or store them in the
database while registering new user.

Attempt Test Module

This module comes into action when a learner

attempts a test. It counts the learners attempts and
outputs the test score.

Input: Learners choice from multiple answer

options.
Output: Answer stored successfully and the test
score once the test gets completed.
Processing: Learners answer is checked and
compared with the correct answer.

Change Learners Schedule Module

This module focuses on letting the learner to

change the schedule upon requirement.

It displays the already set schedule. New timings

are asked to the learner and then updated to the
database.

Admin Control Module

This module is used by the administrator of the

system in order to manage the tutors and learners.
Also, the administrator allocates schedules to the
newly registered learners.
5. Testing

5.1 Testing Plan

The testing is a technique that is going to be used in the

project is black box testing ,the expected inputs to the system
are applied and only the outputs are checked .

5.2 Testing Strategy

The development process repeats this testing sub process

a number of the lines for the following phases.
Unit Testing
Integration Testing

Unit Testing tests a unit of code after coding of that unit is

completed. Integration Testing tests whether the previous
programs that make up a system, interface with each other as
desired. System testing ensures that the system meets its
stated design specifications. Acceptance testing is testing by
users to ascertain whether the system developed is a correct
implementation of the software requirements specification.

Testing is carried out in such a hierarchical manner to that

each component is correct and the assembly/combination of
component is correct. Merely testing a whole system at end
would most likely throw up errors in component that would
be very costly to trace and fix. We have performed both Unit
Testing and System Testing to detect and fix errors.

5.3 Testing Methods

We have performed Black-box testing for the testing

purpose. A brief description is given below:
Black-box testing is a method of software testing that
examines the functionality of an application without peering
 into its internal structures or workings. This method of test
can be applied to virtually every level of software testing:
unit, integration, system and acceptance. It typically
comprises most if not all higher level testing, but can also
dominate unit testing as well.

5.4 Test Cases

Test Test Test Test Expected Actual

Case Scenario Steps Data Results Results
ID
T01 Sign Up 1. Go to User Stored Success
Home Information Successfully
page
2. Provid
e
Information
T02 Log In 1. Go to User Display Welcome
Home Credentials Welcome Page
page Page displayed
2.Enter
Crede
ntials
T03 Attempt 1. Login Test Store and Success
Test to Answers compare the
Learn answers and
er calculate the
Page test score
2. Go to
Atte
mpt
Test
3. Click
Start
Test
T04 Change 1.Enter Schedule New Success
Learners timing Details Schedule
Schedule details Updated
T05 New Bid 1.Go to Bid Value If less than Success
Aucti current Bid
on then no
Main action else
Page save Bid.
2.Provid
e
New
Bid
T06 Product 1. Go to Product If timer gets Successfu
Timeout Aucti Timer expired lly stored
on ,show new bid and
Main product and sent new
Page save the Product
2.Wait final bid
for
the
produ
ct to
get
expir
ed
T07 Start 1. Go to Auction Id Auction Auction
/Stop Admi Started Started
Auction n
Panel
2.Start
Aucti
on
T08 Create 1. Go to Auction id Table Created
Tables for Admi and Created Successfu
Auction n respective lly
Panel products
2.Click
Creat
e
Table
s
Butto
n
T09 Register 1. Go to Tutor Save the Saved
New Tutor Admi Details details in the Successfu
n database lly
Panel
2. Click
Add
New
Tutor

T10 Register 1. Go to Learner Save the Saved
New Admi Details details in the successful
Learner n database ly
Panel
2. Click
Add
New
Learn
er
T11 Display 1. Go to Attendance Display Success
Tutor Tutor Panel Details attendance
Attendanc 2. Click according to
e Check the month
Attendance
6. Screen-shots

6.1 Home Page

6.2 Login
6.3 Admin Panel
6.4 Register New Tutor
6.5 Register New Learner

6.6 Set Schedule

6.7 Manage Attendance
6.8 Learner Home Page

6.9 Change Schedule

6.10 Attempt Test

6.11 Test Question

6.12 Tutor Homepage
6.13 Checking Attendance
7. Limitations and Future Enhancements

Limitations

1. Limited awareness of driving schools.

2. Limited practice for tests for learners license.

Future Enhancements

Better training facilities and hence more requirements.

8. Conclusion
Hereby, we declare that the functionality implemented
in this system was performed by understanding all the
modules.

This project aims to provide live auction mechanism

which was fulfilled to a greater extent. All the UML
designs where prepared before implementation and the
coding was done accordingly. After the coding was
completed, comprehensive testing was performed
and the results were provided in the report. Unit
Testing of all modules were done and later Integration
Testing was also performed.

9. Bibliography

Web Tutorials:

www.w3schools.com
www.tutorialspoint.com
www.stackoverflow.com