PROJECT REPORT

ON

DESIGN AND DEVELOPMENT OF DRIVER MANAGEMENT SYSTEM

(Monthly Basis Driver Module)

FOR

Indian Drivers Private Limited

BY

Mr. Abhiram A. Sadhu

(Seat No: )

AT

SAVITRIBAI PHULE PUNE UNIVERSITY

MASTER OF COMPUTER APPLICATION

PIMPRI CHINCHWAD EDUCATION TRUST’S

PIMPRI CHINCHWAD COLLEGE OF ENGINEERING

SECTOR NO. 26, PRADHIKARAN, NIGDI, PUNE-411044

2016-2019
 Index

Chapter Chapter Name

No.
1 INTRODUCTION
1.1 Company Profile
1.2 Existing System and Need for System
1.3 Scope of Work
1.4 Operating Environment – Hardware and Software
1.5 Detail Description of Technology Used
2 PROPOSED SYSTEM
2.1 Proposed System
2.2 Objectives of System
2.3 User Requirement
2.4 Work Flow Diagram
3 ANALYSIS & DESIGN
3.1 Class Diagram
3.2 Use Case Diagrams
3.3 Activity Diagram
3.4 Sequence Diagram
3.5 Component Diagram
3.6 Deployment Diagram
3.7 Module Hierarchy Diagram
3.8 Module Specifications
3.9 Input and Output Screens
3.10 Table specifications:
3.10.1 Entity Relationship Diagram (ERD)
3.10.2 Data Dictionary
3.10.3 Table Design
3.11 Test Procedures and Implementation
4 USER MANUAL
4.1 User Manual
5 DRAWBACKS AND LIMITATIONS
6 PROPOSED ENHANCEMENTS
7 CONCLUSION
8 BIBLIOGRAPHY(References)
9 ANNEXURES:
ANNEXURE 1 : Source Code / Algorithms /
Pseudo Code
1.1 Company Profile:

Indian Drivers represent as a Professional Car Driver Management Company

engaged in providing Car drivers to individuals and corporates. Indian Drivers
started its business activities in the year 2009 having corporate registered office
at Sadashiv Peth, Pune. Company providing car driver services on Daily,
Monthly and Annual basis or as per customer requirement.

Indian Drivers having registrations of more than 8000 car drivers in Pune
region, which are growing month on month. Indian Drivers started its
business activities with a vision to create employment opportunities to car
drivers without any cost part as a social responsibility.

Indian Drivers not only take the responsibility to provide reliable

drivers but also involved into payroll management of provided
drivers i.e. Salaries, advances, statutory compliances etc.

Indian Drivers served more than 40,000 customers all over Pune and
Pimpri Chinchwad which consists Individuals, SMEs and Large
corporates. Company management have been working 24*7 for applying
thoughts, conducting survey, create and innovate new mantras for
corporate and individual driver management. Routine business activities
are managed by qualified staff members in professional manner which
consists multiple division viz.HR, Accounts, Sales, Relationship etc.
As mobile technology is becoming more adaptable, the trend of using smart
devices is growing like wildfire, and there is in fact no stoppage. Looking at
market need & scenario Indian Drivers Launched mobile application for
Customer and Drivers.

The Entire on demand/ Hourly basis car driver requirements taken care by
technology platform which is managed by our group Firm ID Software
solutions. This application has three parts viz. Admin app, Customer
mobile app and Driver application. Customer app enable app user to add
booking/trip i.e. Local / Outstation as per their requirement whereas Driver
application help driver to choose booking as per his convenience. Indian
Drivers manages and monitor entire activities on admin application for
smooth running of the business.
1.2 Existing System and Need for System

Existing System

• Customer needs to make a call to Indian Drivers for Driver Booking.

There was no guaranteed confirmation of driver allotment.

• Staff needed to call the driver for customer booking.

• There were issues with the start and stop time of trip.
Need for System:

 “Design and Development of Driver management System” will help

users and help desk of the company to manage the bookings and
reports dynamically over a server.

 It will be easier and transparent for customers to find a permanent

driver on their desired needs and also for the driver to select desired
duty.

 This system is allowing the direct interaction of drivers and customers

which means there is no need to perform any manual tasks to find a
driver.
1.3 Scope of Work

 To make drivers available to customers on their desired needs.

 To maintain drivers’ scheduling as per the need of customer.
 To provide reliable drivers to the customers at reasonable fare.
 To provide clear and fixed fare calculations.
1.4 Operating Environment –Hardware & Software:
Hardware Requirement
Client & Server

Component Minimum Recommended

Processor 1 GHz Pentium4 and more

RAM 2 GB 4 GB

Hard disk 20GB 30GB

Software Requirement:
Component Minimum Recommended

O/S Windows 7 and above Any

HTML,
AngularJS,
Development NodeJS
tools PostgreSQL Database
1.5 Detail Description of Technology Used

Angular JS
AngularJS is a JavaScript-based open-source front-end web framework mainly
maintained by Google and by a community of individuals and corporations to
address many of the challenges encountered in developing single-page applications.
It aims to simplify both the development and the testing of such applications
by providing a framework for client-side model-view-controller (MVC)
and model-view-view model (MVVM) architectures, along with components
commonly used in rich Internet Applications.

Node JS
Node JS is an open-source, cross-platform JavaScript run-time
environment that executes JavaScript code outside of a browser. JavaScript is
used primarily for client-side scripting, in which scripts written in JavaScript
are embedded in a webpage's HTML and run client-side by a JavaScript
engine in the user's web browser. Node.js lets developers use JavaScript to
write command line tools and for server-side scripting—running scripts
server-side to produce dynamic web page content before the page is sent to
the user's web browser. Consequently, Node.js represents a "JavaScript
everywhere" paradigm, unifying web application development around a
single programming language, rather than different languages for server side
and client side scripts.
PostgreSQL
PostgreSQL, often simply Postgres, is an open source object-relational
database management system with an emphasis on extensibility and
standards compliance. It can handle workloads ranging from small single-
machine applications to large Internet-facing applications with many
concurrent users.
PostgreSQL is developed by the PostgreSQL Global Development Group, a
diverse group of many companies and individual contributors. It is free and
open-source, released under the terms of the PostgreSQL License,
a permissive software license.

Strongloop:
Strongloop is the (IBM) company that has built an API Platform which
features the open source Loopback framework. Loopback enables you to
quickly compose APIs and runs on top of the express framework. It could've
been named Strongloop Loopback Starter. In addition to the loopback
framework, the Strongloop API Platform also includes the Arc graphical UI,
which has tools for building, profiling, and monitoring Node Apps. You could
create your API using Loopback & then monitor & profile that API using Arc.
Both are a part of the strongloop platform.
2.1 Proposed System
In the proposed System we will provide automation to all the manually
process performed by customer and driver.

 Admin can manage all the activities through web portal.

 Admin can allocate driver to customer booking.
 Registration of new driver will be done by admin.
 Transparency of fare charges for the customers.
 Calculation of fare will be made automatically as per the time
and distance travelled.
 Booking History of Driver as well as customer will be available.
 If driver fails to have minimum amount in his account, the recharge
of minimum amount will be made from admin.
 Booking Report and Driver Transactions Report will also be
displayed.

2.2 Objective of the Project

 To make drivers available to customers according to their
requirements.
 To have clear and perfect fare calculations.
 To maintain information of an experienced and professional driver.
 To provide new driver if the allotted driver is unavailable.
2.3 User Requirement

 User Friendly: Any individual with basic knowledge of computer can

easily execute web-based driver management system functionalities.
 Fast & Secure: Web based driver management system make it extremely
fast and secure.
 Unlimited User Support: Once a user is assigned a role in the system,
user can perform all the functionalities of role assigned. All the
information about customer and driver should be available on same
platform.
 Validations & Verifications: It should give the error message if the data
is invalid. If user input invalid data then it verifies the data with the
database and gives error message.
2.4 Work Flow Diagram
3.10.1 Entity Relationship Diagram
3.10.2 Data Dictionary:
Sr. Siz
Field Name Datatype Constraint Table name Description
No e
character Driver Account
1 account_number 10 Not Null driver_details
varying Number
double company2_custo Driver's advance
2 advance_amount 20 Not Null
precision mer_bills amount
Primary
3 agent_id bigint 10 agent Agent's ID
Key
Date of
agreement_end_ company2_custo
4 date 50 Not Null agreement to be
date mer_details
ended
How many
agreement_numb company2_custo
5 integer 10 Not Null ageements have
er mer_details
been done
agreement_start_ company2_custo Start of
6 date 50 Not Null
date mer_details agreement
double company2_bill_ Total amount in
7 amount 20 Not Null
precision details bill details
Primary
8 analysis_id bigint 10 analysis ID of analysis
Key
character Driver's bank
9 bank_name 10 Not Null driver_details
varying name
Primary company2_bill_
10 bd_id bigint 10 ID of Bill details
Key details
company2_custo
11 bill_date date 50 Not Null Date of Bill
mer_bills
company2_custo
12 bill_from_date date 50 Not Null Gross bill date
mer_bills
company2_custo
13 bill_to_date date 50 Not Null Gross bill date
mer_bills
character company2_custo Company or
14 bill_type 10 Not Null
varying mer_bills personal bill
15 car_type character 10 Not Null permanent_drive Type of car
Sr. Siz
Field Name Datatype Constraint Table name Description
No e
varying r_request
Primary company2_custo ID of Customer
16 cb_id bigint 10
Key mer_bills Bill
double company2_custo
17 cgst 20 Not Null CGST
precision mer_bills
character company2_custo Name of
18 company_name 10 Not Null
varying mer_details Company
company2_custo Foreign company2_custo ID of Customer
19 bigint 10
mer_id Key mer_bills Bill
contact_person_ character company2_custo Email of
20 10 Not Null
email varying mer_details customer
contact_person_ character company2_custo Name of
21 10 Not Null
name varying mer_details customer
Foreign
22 conuser_id bigint 10 agent Id of conusers
Key
Company Police
23 cpv boolean 10 Not Null driver_details
Verification
ID of a person
Foreign
24 created_by bigint 10 agent who has created
Key
the booking
Name of person
created_by_nam character permanent_drive
25 10 Not Null who has created
e varying r_request
the booking
timestam Date on which
26 created_date p with 50 Not Null agent booking has been
time zone created
Primary company2_custo
27 cust_id bigint 10 ID of Customer
Key mer_details
Primary company2_custo ID of Customer
28 cust_rate_id bigint 10
Key mer_rate defined Rate
character The batch of
29 driver_batch 10 Not Null driver_details
varying driver
Autogenerated
30 driver_code bigint 10 Not Null driver_details
Driver code
Sr. Siz
Field Name Datatype Constraint Table name Description
No e
Primary
31 driver_id bigint 10 driver_details ID of Driver
Key
Foreign driver_job_reque
32 driver_job_id bigint 10 Driver job detail
Key st
character company2_custo
33 driver_name 10 Not Null Name of Driver
varying mer_details
permanent_drive
34 duty_hours bigint 10 Not Null Hours of duty
r_request
character
emergency_num Emergency
35 varying(1 15 Not Null driver_details
ber number
5)
character
36 free_address 10 Not Null driver_details Address of driver
varying
character company2_custo
37 gstin_number 10 Not Null GST number
varying mer_details
character company2_custo
38 hsa_number 10 Not Null Duty number
varying mer_details
character
39 ifsc_code 10 Not Null driver_details IFSC code
varying
character Is the vehicle
40 is_luxury 10 Not Null driver_details
varying luxury
Foreign company2_custo
41 item_id bigint 10 ID of Item
Key mer_rate
character
42 item_name 10 Not Null company2_items Name of Item
varying
double
43 item_value 20 Not Null company2_items Value of Item
precision
Primary Company Police
44 items_id bigint 10 company2_items
Key Verification
Primary driver_job_reque
45 job_request_id bigint 10 Id of job request
Key st
character company2_custo
46 landline 10 Not Null Landline number
varying mer_details
47 micr_code character 10 Not Null driver_details MICR
Sr. Siz
Field Name Datatype Constraint Table name Description
No e
varying
character
48 month 10 Not Null analysis Months
varying
double company2_custo
49 monthly_salary 20 Not Null Monthly Salary
precision mer_details
character permanent_drive Home, Office,
50 nature_of_duty 10 Not Null
varying r_request School
double company2_custo
51 net_amount 20 Not Null Net Amount
precision mer_bills
52 nt_date date 50 Not Null driver_details NT date
Foreign Duty hours if
53 outstation_duty boolean 2 analysis
Key outstation
Primary permanent_drive Id of permenent
54 pdr_id bigint 10
Key r_request driver request
permanent_addre character Permenent
55 10 Not Null driver_details
ss varying Address of driver
Police
56 pv boolean 10 Not Null driver_details
Verification
double company2_bill_
57 quantity 20 Not Null Quantity of items
precision details
double company2_bill_
58 rate 20 Not Null Defined Rate
precision details
double company2_custo Received amount
59 received_amount 20 Not Null
precision mer_bills of customer
received_bill_dat company2_custo Date of bill
60 date 50 Not Null
e mer_bills received
character company2_custo
61 remark 10 Not Null Remark on bills
varying mer_bills
character company2_custo
62 reverse_charge 10 Not Null Reverse travelling
(1) mer_bills
character permanent_drive
63 salary_budget 10 Not Null Budget of salary
varying r_request
double company2_custo
64 sgst 20 Not Null SGST
precision mer_bills
Sr. Siz
Field Name Datatype Constraint Table name Description
No e
character company2_custo
65 status 10 Not Null Status
varying mer_bills
double company2_custo Total of Sub
66 sub_total 20 Not Null
precision mer_bills amounts
double company2_custo
67 total 20 Not Null Total
precision mer_bills
double
68 total_overtime 20 Not Null analysis Total Overtime
precision
double
69 total_time 20 Not Null analysis Total time period
precision
70 tr_date date 50 Not Null driver_details TR date
character company2_bill_
71 unit 10 Not Null Unit
varying details
Updated by
Foreign
72 updated_by bigint 10 agent user/customer/dri
Key
ver
timestam
73 updated_date p without 50 Not Null agent Date on updated
time zone
timestam
company2_custo Value defined by
74 value p without 50 Not Null
mer_details customer
time zone
double company2_custo
75 vehicle_name 20 Not Null Name of Vehicle
precision mer_rate
character company2_custo
76 vehicle_type 10 Not Null Type of Vehicle
varying mer_details
character company2_custo
77 weekly_off 10 Not Null Weekday of leave
varying mer_details
character company2_custo
78 year 10 Not Null null
varying mer_details
3.10.3 Table Specification
Agent
Table Name Agent
Description This table stores information about agents.

Sr. Field Name Datatype Size Constraint

No.
1 id bigint 10 Primary Key
2 conuser_id bigint 10 Foreign Key
3 created_by bigint 10 Not Null
4 created_date timestamp with time 50 Not Null
zone
5 updated_by bigint 10 Not Null
6 updated_date timestamp without time 50 Not Null
zone

Analysis
Table Name Analysis
Description This table stores analysis details.

Sr. Field Name Datatype Size Constraint

No.
1 id bigint 10 Primary Key
2 month character 10 Not Null
 varying
3 year bigint 10 Not Null
4 total_time double precision 10 Not Null
5 total_overtime double precision 10 Not Null
6 outstation_duty boolean 1 Not Null
company2_customer_details
Table Name Company2_customer_details
Description This table stores the information customers opted the
monthly booking.

Sr. Field Name Datatype Size Constraint

No.
1 id bigint 10 Primary Key
2 conuser_id bigint 10 Foreign Key
3 agreement_number integer 10 Not Null
4 landline character varying 10 Not Null
5 contact_person_name character varying 10 Not Null
6 contact_person_email character varying 10 Not Null
7 vehicle_name character varying 10 Not Null
8 vehicle_type character varying 10 Not Null
9 gstin_number character varying 10 Not Null
10 hsa_number character varying 10 Not Null
11 duty_hours integer 10 Not Null
12 weekly_off character varying 10 Not Null
13 agreement_start_date date 20 Not Null
14 agreement_end_date date 20 Not Null
15 company_name character varying 10 Not Null
16 created_by bigint 10 Nullable
17 created_date timestamp with time 50 Nullable
zone
18 updated_by bigint 10 Nullable
19 updated_date timestamp without 50 Nullable
time zone
20 monthly_salary double precision 10 Not Null
21 driver_name character varying 10 Not Null
company2_customer_rate
Table Name Company2_customer_rate
Description This table stores the budget rate of a customer

Sr. Field Name Datatype Size Constraints

No.
1 id bigint 10 Primary Key
2 company2_customer_id bigint 10 Foreign Key
3 item_id bigint 10 Foreign Key
4 value double 10 Not Null
precision
5 unit character 10 Not Null
varying

company2_items
Table Name Company2_items
Description This table stores the hourly charges for a transaction.

Sr. No. Field Name Datatype Size Constraints

1 id bigint 10 Primary Key
2 item_name character 10 Not Null
varying
3 item_value double precision 10 Nullable
4 created_by bigint 10 Nullable
5 created_date timestamp with 50 Nullable
time zone
6 updated_by bigint 50 Nullable
7 updated_date time without 50 Nullable
time zone
company2_bill_detail
Table Name Company2_bill_detail
Description This table stores the customer bill details

Sr. Field Name Datatype Size Constraints

No.
1 id bigint 10 Primary Key
2 bill_id bigint 10 Foreign Key
3 item_id bigint 10 Foreign Key
4 amount double precision 10 Not Null
5 created_by bigint 10 Nullable
6 created_date timestamp with 50 Nullable
time zone
7 updated_by bigint 10 Nullable
8 updated_date timestamp without 50 Nullable
time zone
9 quantity double precision 10 Not Null
10 rate double precision 10 Not Null
11 unit character varying 10 Not Null

company2_customer_bills
Table Name Contact
Description This table stores the customer bill

Sr. Field Name Datatype Size Constraints

No.
1 id bigint 10 Primary Key
2 company2_customer_id bigint 10 Foreign Key
3 bill_date date 10 Foreign Key
4 total double precision 10 Not Null
5 created_by bigint 10 Nullable
6 created_date timestamp 50 Nullable
 with time zone
7 updated_by bigint 10 Nullable
8 updated_date timestamp 50 Nullable
without time
zone
9 sub_total double precision 10 Not Null
10 cgst double precision 10 Not Null
11 sgst double precision 10 Not Null
12 status character varying 10 Not Null
13 bill_from_date date 50 Not Null
14 bill_to_date date 50 Not Null
15 reverse_charge character(1) 1 Not Null
16 advance_amount double precision 10 Not Null
17 net_amount double precision 10 Not Null
18 bill_type character varying 10 Not Null
19 received_bill_date date 50 Not Null
20 received_amount double 10 Not Null
precision
21 remark character varying 10 Not Null

permanent_driver_request
Table Name Permanent_driver_request
Description This table stores the information about permanent
driver requests

Sr. Field Name Datatype Size Constraints

No.
1 id bigint 10 Primary Key
2 customer_id, bigint 10 Foreign Key
3 status character varying 10 Not Null
4 created_by bigint 10 Not Null
5 created_date timestamp with 50 Not Null
time zone
6 updated_by bigint 10 Nullable
7 updated_date timestamp 50 Nullable
without time zone
8 remark character varying 10 Not Null
9 created_by_name character varying 10 Not Null
10 car_type character varying 10 Not Null
11 duty_hours bigint 10 Not Null
12 salary_budget character varying 10 Not Null
13 nature_of_duty character varying 10 Not Null
14 weekly_off character 10 Not Null
varying[]

driver_details
Table Name Driver_details
Description This table stores the information about drivers

Sr. Field Name Datatype Size Constraint

No.
1 id bigint 10 Primary Key
2 conuser_id bigint 10 Foreign Key
3 is_luxury character varying 10 Not Null
4 permanent_address character varying 10 Not Null
5 account_number character varying 10 Not Null
6 ifsc_code character varying 10 Not Null
7 micr_code character varying 10 Not Null
8 created_by bigint 10 Not Null
9 created_date timestamp with 50 Not Null
time zone
10 updated_by bigint 10 Nullable
11 updated_date timestamp without 50 Nullable
time zone
12 bank_name character varying 10 Not Null
13 pv boolean 1 Not Null
14 cpv boolean 1 Not Null
15 emergency_number character varying 10 Not Null
(15)
16 tr_date date 50 Not Null
17 nt_date date 50 Not Null
18 driver_batch character varying 10 Not Null
19 free_address character varying 10 Not Null
20 driver_code bigint 10 Not Null
21 remark character varying 10 Nullable

driver_job_request
Table Name Driver_job_request
Description This table stores the information about drivers job
request

Sr. Field Name Datatype Size Constraint

No.
1 id bigint 10 Primary Key
2 driver_job_id bigint 10 Foreign Key
3 driver_id bigint 10 Foreign Key
4 remark character varying 10 Nullable
5 created_by bigint 10 Not Null
6 created_date timestamp with 50 Not Null
time zone
7 updated_by bigint 10 Nullable
8 updated_date timestamp 50 Nullable
without time
zone
9 created_by_name character 10 Not Null
varying
10 status character 10 Not Null
varying
3.1 Class Diagram
3.2 Use Case Diagram
1. Use Case Diagram For User
3.4 Sequence Diagram
1. Sequence Diagram for User
3.3 Activity Diagram
1. Activity Diagram for User

3.5 Component Diagram:

3.6 Deployment Diagram
3.7 Module Hierarchy Diagram:
3.8 Module Specification:
3.11 User Interface Design
Login Screen:

Home Page
Add Driver
New Driver Update after PV and CPV:
Add Customer:
Monthly Driver Request

Monthly Driver Request New Booking:

Monthly Driver Request Searching:
Data Reports:
Analysis 1:

Analysis 2:
Analysis 3:
Analysis 4:
Analysis 5:
Driver Transaction History:
3.11Test Procedures and Implementation
 1. Test plan identifier

Test plan for Design and development of Driver Service

Administration Portal 1.0

2. Reference

The test plan is prepared based on project documents and in

consideration with documents required to cover all the test cases
for the project.
Documents that are used for reference:
1. Requirements specifications
2. Detail design document

3. Introduction

The aim of this document is to develop a test plan for the driver
service administration portal. The objectives of the test plan are to
define the activities for performing testing process, define the test
deliverable documents and to identify the schedule and staff
require for various activities in testing.

4. Features to be tested

The following list describes the features to be tested:

 Registration
 Driver Booking
 Analysis
 Job report

5. Approach
 This section describes the overall approach of the testing which ensures
that each feature and the combination of the features are adequately
tested.

The levels of testing that are performed through this test plan are:-

5.1 Unit testing

Unit testing is a method to verify the individual units of source code are
working properly. The purpose of unit testing is to isolate each part of the
program and show that the individual parts are correct. This process is
applied to all the modules of my project. The Basic modules Booking of
Driver and registration is thoroughly testing and that test cases are shown
below.

5.2 Integration testing

Integration testing is used for checking the interface between two
components.

It is used for checking for different modules are working with each other in
correct way.

To identify the error, appear in the two different interfaces this type of testing
is used. Example: Booking of Driver and booking history.

6. Pass/Fail criteria
The system should satisfy all the functional requirements, in the SRS
document. Each feature to be tested will be evaluated against its requirement
as stated in the SRS Document. The pass or fail of a test depends on whether
the system meets with all the particular post conditions. Test cases executed
on the Automation will pass if they meet the specific requirements as
mentioned in the SRS Document.

7. Suspension criteria and resumption requirements

7.1 Suspension criteria
If the system contains one or more critical defects like the defects in the GUI
editor the entire system should be suspended.
The testing may also be suspended if the hardware and software components
required are not available on time.
The failed test cases should be recorded along with the description for
failure.

7.2 Resumption requirement

When a new version of the system is transmitted to the test group after a
suspension of testing has occurred, all previous tests will be rerun to ensure
program changes have not inadvertently affected other portions of the
program.

8. Test deliverables
The following documents are available for test deliverables
1. Test plan
2. Test case
3. Test input and output data
9. Schedule
 Sr. No. Test Name Dates
1 Unit Testing- 07/03/2019
Black Box Testing to 15/03/2019

2 Integration Testing 21/03/2019

to 26/03/2019

3 System Testing

Add Customer

ADD_CUST_DMS_01:
To check the functionality of adding customer.
Fill the valid details of user and click on ADD CUSTOMER button
System will generate the message “Customer added successfully”.
ADD_CUST_DMS_02:
To check the functionality of adding customer.
 Fill the Invalid details of user and click on ADD CUSTOMER button.
System will generate the message “Please fill out this field”

Monthly Driver Request

MNTH_DRV_DMS_01: To check the functionality of Monthly Driver

Booking.
Fill the valid details of monthly driver request and click on ADD REQUEST
button.
System will generate the message “Request posted successfully”

MNTH_DMS_02: To check the functionality of Monthly Driver

Booking.
Fill the Invalid details of monthly driver request and click on ADD
REQUEST button
System will generate the message “Please fill this field”
.

1.Test Case for Adding Customer

Test Case ID: ADD_CUST_DMS_01 Test Designed by: Abhiram Sadhu
Test Priority (Low/Medium/High): High Test Designed date: 12/03/19
Module Name: Adding Customer Test Executed by: Abhiram Sadhu

Test Title: To validate the add customer module Test Execution date: 16/03/19
with Proper validation
Description: To check the validation of adding customer Module in the application
Pre-conditions: Application should be properly installed and registration page should be
open.
Test Case Id Steps to be Test Data Expected Actual Pass/ Remark
executed Result Result Fail

VALID INPUT DATA

ADD_CUST_D 1.Enter Name Abhiram User User is Pass

MS_01 Sadhu should navigated
8007899492 navigate to to next
2.Enter Mobile the next page.
page
3. Enter the Abhiramsadhu without
Email Id 1@gmail.com error and
will
display the
4.Enter Status Active message”
Customer
added
5. Landmark Akurdi Successful
ly”
6.Customer
R
Type

7.Address Akurdi
INVALID INPUT DATA

ADD_CUST_D 1.Enter Name Fgdfjdfl Applicatio Applicatio Pass

MS_02 n should n displays
display the the
2.Enter Mobile 9879898f99 message message
”Please ”Please
3. Enter the
enter valid enter valid
#abc@gmail.co
details and details and
 Email Id m try Again” try Again”

4.Enter Status Active

5. Landmark Dehu

6.Customer A
Type

Dehu
7.Address

Monthly Driver Request Test Case

Test Case ID: MNTH_DRV_DMS_01 Test Designed by: Abhiram Sadhu
Test Priority (Low/Medium/High): High Test Designed date: 25/03/2019
Module Name: Monthly Driver Request
Module Test Executed by: Abhiram Sadhu
Test Title: To validate the Monthly Driver
Request with Proper validation Test Execution date: 28/3/2019
Description: To check the validation of Monthly Driver Request in the application
Pre-conditions: Application should be properly installed and login page should be open.
Test Case Id Steps to be Test Data Expected Actual Pass/ Remark
executed Result Result Fail

VALID INPUT DATA

MNTH_DRV_ 1.car type Automatic User User is Pass

DMS_01 should navigated
navigate to to next
2.Duty hours 11 the next page.
page
3.Salary budget 12000 without
error.

4.Weekly off Saturday

5.nature of Home to office

duty
6 Remark
Fluent English
INVALID INPUT DATA

MNTH_DRV_ 1.car type Manual It should It display

DMS_02 display message
message “Invalid
2.Duty hours 13 “Invalid Details”,
Details”, and
and navigate to
navigated to monthly
3.Salary budget 14000
monthly driver
driver request
request page.
4.Weekly off NA page.

5.nature of Home to office

duty
 6 Remark NA

4.1 User Manual

Although the user interface of the system is constructed in such a way
that person with particular access can use the system if he has the basic
knowledge of operating keyboard and mouse operation of a computer.

All pages of the application contain the descriptive links and the
buttons that will help the user to perform the required operation.

The following section provides the details, which can be very useful for
using the system. The Description is much in detail so that any user can
use it very easily.
1.2 Operations Manual / Menu Explanation

Step 1: Login with proper credentials.

Step 2: Select the desired tile from dashboard
Step 3: Let’s take an example of new booking.
Step 4: After clicking on new booking we get the following popup.
Step 5: Fill the details and click add request the booking will be saved.
Another Example will be Analysis reports:
Step 6: In booking analysis report enter from date and to date and click
search:
Step 7: In search analysis report by user enter the same along with user name
or number.
Step 8: Select desired year and quarter from another drop box.
5. Drawback and Limitations
Drawback

 There is a manual process of interviewing the driver by

customer and company.
 There are agents in the company, who have to visit
customers opted for monthly drivers at their house or
working places.
 The PostgreSQL is not a distributed database that’s why
manual backups are necessary.

Limitations

 PostgreSQL isn’t distributed database.

 Google API key’s need to be updated each month.
 Company users and help desk can use this system.
 Adding new city requires changes in database directly.
6. Proposed Enhancement

The system can be enhanced in future. More features can be added to the
system such as

 It will provide a facility to pay using different online

payment modes.
 Distributed databases and parallel processing will be
adopted.
 New cities will be added in simpler way.
7. Conclusion

I feel very glad to conclude this report. This is my first experience to

perform such as professional work. I learnt lot from this project and
specially how to apply the technical skills at different stages of software
development.

I have got the opportunity to learn about “Driver Management System”

conceptual and practical knowledge of software engineering, system
analysis and real time experience of project implementation

After testing process I conclude that the system was developed

according to user requirement.
8 BIBLIOGRAPHY

Bibliography

Books:
1“UML” – by Mahesh Martha.
2“Build Your Own Database Driven Website Using PHP”.
3“MySQL” – by Kevin Yank

Website:
1. www.getbootstrap.com.
2. www.w3schools.com.
3. www.tutorialspoint.com.
9. ANNEXURES:
Source Code
Monthly Driver Request Code:
<div class="panel panel-default" style="overflow-x: auto" ng-
init="getPdriver()">
<div class="panel-heading">
<div class="row">
<div class="col-sm-6">
<div class="col-sm-3">
<button class="pull-right btn btn-labeled btn-primary"
style="padding-top: -2px;
padding-bottom: -2px;" ng-
click="backToSearchCriteriaMDR()">
<span class="btn-label"><i class="fa fa-chevron-left"></i>
</span> Back
</button>
</div>
</div>
<div class="col-sm-6">
<div class="col-sm-8">
</div>
<div class="col-sm-4">
<button class="pull-right btn btn-labeled btn-primary" style=""
ng-click="addRequest()">
 <span class="btn-label"><i class="fa fa-plus"></i>
</span>New Request</button>
</div>
</div>
</div>
</div>
<table ng-table="tableParams3" class="table table-striped table-bordered
ng-table-rowselected" show-filter="true">
<tr ng-repeat="customer in $data | orderBy:'-createdDate'" ng-
show="$data.length > 0">
<td title="'Customer Name'" filter="{ custName: 'text'}"
sortable="'custName'" ng-click="requestDetailsPopup(customer)"
style="text-transform: capitalize;text-align:
left;">{{customer.custName}}</td>
<td title="'Mobile'" filter="{ mobile: 'text'}" sortable="'mobile'" ng-
click="requestDetailsPopup(customer)" style="text-transform:
capitalize;text-align: left;">{{customer.mobile}}</td>
<td title="'Address'" filter="{ address: 'text'}" sortable="'address'" ng-
click="requestDetailsPopup(customer)" style="text-transform:
capitalize;text-align: left;">{{customer.address}}</td>
<td title="'Status'" filter="{ status: 'text'}" sortable="'status'" ng-
click="requestDetailsPopup(customer)" style="text-transform:
capitalize;text-align: left;">{{customer.status}}
</td>
<td title="'Remark'" filter="{ remark: 'text'}" sortable="'remark'" ng-
click="requestDetailsPopup(customer)" style="text-transform:
capitalize;text-align: left;">{{customer.remark}}
</td>
 <td title="'Created By'" filter="{ createdByName: 'text'}"
sortable="'createdByName'" ng-click="requestDetailsPopup(customer)"
style="text-transform: capitalize;text-align:
left;">{{customer.createdByName}}
</td>
<td title="'Created Date'" filter="{ date: 'text'}" sortable="'date'" ng-
click="requestDetailsPopup(customer)" style="text-transform:
capitalize;text-align: left;">{{customer.date}}</td>
<td title="'Car Type'" filter="{ cartype: 'text'}" sortable="'cartype'"
ng-click="requestDetailsPopup(customer)" style="text-transform:
capitalize;text-align: left;: capitalize;text-align:
left;">{{customer.carType}}</td>
<td title="'Duty Hours'" filter="{ dutyhours: 'text'}"
sortable="'dutyhours'" ng-click="requestDetailsPopup(customer)"
style="text-transform: capitalize;text-align: left;: capitalize;text-align:
left;">{{customer.dutyHours}}</td>
<td title="'Weekly Off'" filter="{ weeklyOffDays: 'text'}"
sortable="'weeklyOffDays'" ng-click="requestDetailsPopup(customer)"
style="text-transform: capitalize;text-align: left;: capitalize;text-align:
left;">{{customer.weeklyOffDays}}</td>
<td title="'Salary Budget'" filter="{ salbudget: 'text'}"
sortable="'salbudget'" ng-click="requestDetailsPopup(customer)"
style="text-transform: capitalize;text-align: left;: capitalize;text-align:
left;">{{customer.salBudget}}</td>
<td title="'Nature Of Duty'" filter="{ natureofduty: 'text'}"
sortable="'natureofduty'" ng-click="requestDetailsPopup(customer)"
style="text-transform: capitalize;text-align: left;: capitalize;text-align:
left;">{{customer.natureOfDuty}}</td>
<td title="'Edit'" style="text-align:left">
<button class="btn btn-sm btn-info" ng-
click="updateRequest(customer.id)"><em class="fa fa-pencil-square-
o"></em></button>
 </td>
</tr>
<tr ng-show="$data.length == 0">
<td>No record found</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</table>
</div>