A Project Report

On
“Employee Transport Management System”

Submitted By:
VIJAYRAJ SINGH PUNWAR
(BCA Third Year)

Submitted To
Vikram University, Ujjain (M.P.)
In Partial Fulfilment of the requirements for the award of
the degree of Bachelor Of Computer Application (BCA)
2022-23
Under Guidance of:
PROF. HEMANT PRAJAPATI
(Department of Computer Science)
Balkavi Bairagi Mahavidyalaya Kanawati,
Neemuch (M.P.) - 458441
 Acknowledgement

We would like to utilize this opportunity to give

thanks to all people who so ever helped us in the
completion of this project activity as all of us know very
well that doing something creative requires lot of courage,
motivation, moral support and a lot of other support We
have undertaken the opportunity of the completion of this
project entitled “Employee Transport Management
System" we are proud to state that we are successful in
accomplishing the set target in the completion of this
project work there were many hands of support without
which the project work could not be a success

First of all we would like to express our heartfelt

gratitude Mr. Hemant Prajapati (HOD of Computer
department BKBM Neemuch) and all over lecturers for
there valuable guidance and tremendous support We are
also highly grateful to Mr. Hemant Prajapati For giving as
an opportunity to undertake the project work in their
organization and also for providing us all the useful
resources till of our project the most important I would
like to thank my parents for their moral and financial
support without it was not possible to accomplish this
success thanking you all for our heart.
 DECLARATION

I am VIJAYRAJ SINGH PUNWAR of Balkavi

Bairagi Mahavidhyalaya, declares that the dissertation
project report submitted by me under the guidance of
Hemant Prajapati Sir is a Bonafede work of the partial
fulfillment of the requirement of BCA Third Year project
work. I have incorporated all the suggestions provided by
guide time to time. .

I further that to the best of my knowledge this

dissertation contains my original work and does not contain
any part of any work which has been submitted for the
award of any degree either in this university or in any other
university/Deemed University/Institute etc. without proper
citation and I shall be fully responsible for any plagiarism
found at any stage.

Name of the guide Name of student

Signature of the guide Signature of student

 Certificate of Attendance

The project entitled “Employee Transport Management

System" developed by VIJAYRAJ SINGH PUNWAR in
the college and he and she has put at least 200 hours of
laboratory work with the guide to complete this project
during the stipulated period of the project at Balkavi
Bairagi Mahavidhyalaya.

Place: Signature of Guide:

Date: Signature of principal /Director

 Self-Certificate

This is to certify that VIJAYRAJ SINGH

PUNWAR student of BCA(Third Year) of Balkavi
Bairagi Mahavidhyalaya has successfully completed the
project work entitled “Employee Transport Management
System" under the guidance of Hemant Prajapati Sir is a
Bonafede piece of work carried out at Balkavi Bairagi
Mahavidyalaya Kanawati. .

The project entitled “Employee Transport Management

System" developed by VIJAYRAJ SINGH PUNWAR in
the college and he and she has put at least 200 hours of
laboratory work during the tenure with the guide to
complete this project. All the prescribed certificates are
attached after the completion of all the formalities of the
project work as per schedule, including internal
examination.

Place: Signature of Guide:

Date: Signature of principal

/Director
 TABLE OF CONTENTS

1: INTRODUCTION
1.1 Background
1.2 Objectives
1.3 Purpose, Scope, and Applicability
1.3.1 Purpose
1.3.2 Scope
1.3.3 Applicability
1.4 Achievements
1.5 Organization of Report
2: SYSTEM ANALYSIS
2.1 Problem Definition
2.2 Requirements Specification
2.3 Planning and Scheduling
2.4 Software and Hardware Requirements
2.5 Preliminary Product Description
2.6 Conceptual Models
3: SYSTEM DESIGN
3.1 Basic Modules
3.2 Data Design
3.2.1 Schema Design
3.2.2 Data Integrity and Constraints
3.3 Procedural Design
3.3.1 Logic Diagrams
3.3.2 Data Structures
3.3.3 Algorithms Design
3.4 User interface design
3.5 Security Issues
3.6 Test Cases Design
4: IMPLEMENTATION AND TESTING
4.1 Implementation Approaches
4.2 Coding Details and Code Efficiency
4.2.1 Code Efficiency
4.3 Testing Approach
4.3.1 Unit Testing
4.3.2 Integrated Testing
4.3.3 Beta Testing
4.4 Modifications and Improvements
4.5 Test Cases
5: RESULTS AND DISCUSSION
5.1 Test Reports
5.2 User Documentation
6: CONCLUSIONS AND FUTURE WORK
6.1 Conclusion
6.1.1 Significance of the System
6.2 Limitations of the System
6.3 Future Scope of the Project
PREFERENCES
8:GLOSSARY
 1
Introduction
1.1 Background
• Pickups and drop-offs are an essential service that organisations provide transport for
employees.
• Transportation manager can view, manage and track all trip activity.
• If not managed well, it can be a problem rather than being a solution.
• The main job of the transporter is to provide transport service to employees.
• The Employee transportation solution will provide an application platform to organise all the
pick and drop related services.
• Using this system user can computerize transport office work like billing, tracking payments,
creating report etc.
• The employee transport service application to be designed, will provide a smooth flow of
services between the admin and the users, where the admin will be the management of an
organisation and the user will be the employees.
• The admin panel needs to login into the application, the admin will have many functions by
which he/she can modify the pick-ups and drop-offs related services.
• These functions include add driver where he can add the driver, add vehicle where he can add
vehicles to the employees, Admin can view bookings and manage time slot.
• On the other end, the employee’s first needs to register into the system by filling up basic
registration details.
• After successful registration, employee can login by using their login credentials.
• Once the user logs in into the system, he/she can view available time slots and employee can
select a time slot according to their shift timings.
• All these features will provide a hassle-free pick and drop management system for an
organisation.

1.2 Objective
• The objective of project to achieve the goal of safe, sufficient, reliable and sustainable
transportation for employees. And To bring safety and convenience for employees in their
commute, make them feel valued, and encourage them to commit to the companies they work
for, many companies are choosing employee transportation solutions.

1.3 Purpose, Scope and Applicability

13.1 Purpose
• Purpose of the project is to provide the safe and reliable charter in motor coaches and buses
that ensure that workers arrive to the site safely and minimize potential delays.
 This project allows the user to choose the service from their convenience. This project ensures
the data shared by user is secure.

1.3.2 Scope
• The scope of this project is to centralized and manage the transportation system for employees.
• This system is a web-based application. People can register through the online form Then, they
will get the detail about the transport.

1.3.3 Applicability
• It is used by employees who work in organization for pickups and drop-offs.

1.4 Achievements
• This project helped me to study and understand the working of how we can predict the
risk factor of individual. .
. At the time of selection of project very little was known to us about the mentioned system
However we learnt a lot about this while working on our project.
. We also lemt how to use this system for for our benefits and liking as per we desirenin
any respective field.

1.5 Organization of Report

This report is divided into seven s.
• l gives a brief introduction of the project covered. It contains basic information about
Employee Transport Management that is used for the project.
• 2 covers the list of components both hardware and software.it also includes the approximate
time taken for the completion of the said project.
• 3 provides us with necessary diagrams like logic diagrams, block diagrams,

flowchart, etc.
4 includes the respective test cases.
5 gives us the test report.
6 finally deals with the future scope of the project.
 2
SYSTEM ANALYSIS
2.1 Problem definition
• Transport Management System (TMS) has design to manage the booking and maintenance of
growing transport*
• Problem occurs when transports have mechanical problems are rented, vehicles that have
been double booked and there have been cases when the wrong vehicle has been rented
when it has been returned and not serviced.
• The current system has redundancy, where data cause by the manual system which uses
paper to fill the information.
• Data is also not being kept in the secure location. Information lost is common by using
manual system.
• The efficient planning and management of an organization’s transport system is the key to
providing a proficient transport network.

2.2 Requirements and Specifications

• For making Employee Transport Management it is important to select a platform that

provides innovative user interface, enhance security and provide many built-in features that
can that makes coding easier. The web framework which will be used the project is
ASP.NET C#.ASP.NET is a web application framework developed and marketed by
Microsoft to allow programmers to build dynamic web sites. It allows you to use a featured
programming language such as C# to build web application easily.
• Along with ASP.NET C# we need Microsoft SQL Sever Management Studio for storing and
retrieving data from database.

2.3 Planning and Scheduling

Gantt Chart

Task Start Date End Date Duration

Requirement Gathering 10-09-2020 25-09-2020 15
Requirement Analysis 26-09-2020 15-10-2020 20
Design 16-10-2020 17-11-2020 35
Coding 18^11-2020 20-12-2020 90
Testing 21-12-2020 20-01-2021 21-01- 66
Evaluation 2021 25-02-2021 25
 10-09-2020 30-09-2020 20-10-2020 09-11-2020 29-11-2020 19-12-2020 08-01-2021 28-01-2021 17-02-2021

Requirement Gathering

Requirement Analysis

Design Coding Testing

Evaluation

2.4 Software and Hardware Requirements

• Software
o ASP.NET C# o Microsoft
SQL Server
• Hardware
o 4GB RAM and above o
CORE i3 and above

2.5 Preliminary Product Description

• A Employee transport management system is specialized software for planning,
executing and optimizing the pickups and drop-offs of employee.

2.6 Conceptual Model

ER diagram
UPDATE DATA
 3: SYSTEM DESIGN

3.1 Basic modules

• Login: It is used by the user to login his/her account.

• Logout: It is used by user to logout off his/her account.
• Register: It is used to register his/her account.
• About: It is used to inform the reader about the website and its operation.
• Services: It is used to provide services to the user.
• Contact us: User can contact admin or owner of the website.
• Feedback: User can give the feedback about the website.

3.2 Data Design

3.2.1 Schema Design

Register Table:

SS Results gl Messages
UName UEmail UPhno UUsemame U Password UConfirm Password UUserinfo
1 | Admin j admin@gmajl.com 7858455521 admin 12345 12345 Admin
2 Nidhi nidhi @gmatl com 8585858578 nidhi123 123 123 User

Login Table:
IS Results gl Messages
UUsemame U Password

1 I admin

2 nidhi 123 123

3.2.2 Data Integrity and Constraints

For Register Table:
create table [dbo].[User_Register](
[UName] fvarchar](50) NULL,
[UEmail] [varchar](50) NULL,
 [UPhno] [bigint] NULL,
[UUsername] [varchar](50) NULL,
[UPassword] [varchar](50) NULL,
[UConfirmPassword] [varchar](50) NULL,
[UUserinfo] [varchar](50) NULL)
For Login Table: create
table User_Login(
[UUsername] [varchar](50) NULL,
[UPassword] [varchar](50) NULL,)

3.3 Procedural Design

3.3.1 Logic Diagram • Use

case diagram

Activity diagram
• Class diagram
3.4 User Interface Design

Q V *a*fau* K [5 o»»"W»» * +
o O fjp I CyPRIVANKA/PROJ£CT/hom»*20p»gt Wml

Upgrade the way

•am
.1
P Sejuhfci anyth'**)
 Q ley,* □X

^•6 Test Cases Design

• Test Case for Register Page:
TCOI Name: Admin Email: Registration Registration Passwords doesn’t
admin@gmail.com Ph. no: Successful Failed match
7858455521 Username: admin
Password: 12345 Confirm
Password: 123

TC02 Registration Registration Email is not in proper

Name: Nidhi Email: Successful Failed format
nidhLgmail.com Ph. no:
8585858578 Username: nidhi
123 Password: 123 Confirm
Password: 123
TC03 Registration Registration Successful
Successful Successful
Name: abc
Email: abcl23@gmail.com Ph. no:
123456789 Username: abc!23
Password: abc@123 Confirm
Password: abc@123

Test Case for Login Page:

Expected Result
Test Case Id Description

TCOT Username: INidhi

Password: 123
TC02 Username: #abc
Password: abc@123
TC03 Username: nidhil23
Password: 123

4 Implementation and Testing

Implementation Approaches
 Phase 1: Creating basic layout
Phase2: Concentrating on Layout/ User Interface
Phase 3: Working on client side
Phase 4: Working on Security
Phase 5: Testing
The project is implemented in Visual Studio with the help ofASP.NET C# framework and
languages are C# and SQL Server Database Management System

4.2 Coding Details and Code Efficiency

4.2.1 Code Efficiency

For Register Page:

protected void Buttonl_Clickl(object sender, EventArgs e)
{
SqlCommand cmd = new SqlCommand("SPJnsert", con); con.Open();
cmd.CommandType = CommandType.StoredProcedure;
cmd.Parameters.AddWithValue("@Name", TextBoxl.Text);
cmd.Parameters.AddWithValue("@Email", TextBox2.Text);
cmd. Parameters. Add WithVaIue("@Phno", TextBox3.Text);
cmd.Parameters. Add With Value("@Username", TextBox4.Text);
cmd.Parameters.Add With Value("@Password", TextBox5.Text);
cmd.Parameters.AddWithValue("@ConfirmPassword", TextBox6.Text);
int i = cmd.ExecuteNonQuery();
con.Close();

string message = "Register Successful! !!!"; string title = "Message from

Web";

if (i > 0)
{
Message Box.Show(message, title);
}
}
}
}

For Login Page:

protected void Button I_Click(object sender, EventArgs e)
{
 string sConn =
System.Configuration.ConfigurationManager.ConnectionStrings["sConn"].ToString();
SqlConnection objConn = new SqlConnection(sConn);
objConn.Open();
try
{
string usid = uid.Text;
string Drop = DropDownListl .Selectedltem.Value;
SessionfUUsername"] = uid; // taking userid in session and passing in default2.aspx

SqlCommand cmd = new SqlCommand(); // SqlCommand cmd= new SqlCommand();

SqlDataReader reader; // SqlDataReader reader=cmd.ExecuteReader()

if (Drop = "Admin")
{

cmd = new SqICommand("select * from register where Username-" + usid + and

Password—" + upass.Text + objConn);
reader = cmd.ExecuteReaderQ;

}
else
{
cmd = new SqICommand("select * from register where Username-" + usid + and
Password-" + upass.Text + objConn);
reader = cmd.ExecuteReader();
}
i f (reader.HasRows)
{
Label 1.Text = "Login Success......!!";
Label 1 .ForeCoIor = System.Drawing.Color.ForestGreen;
cmd.DisposeQ;
cmd.CommandTimeout = 900;
// objConn.Close():
cmd.Dispose();

if (usid == "Admin")
{
Response.Redirect("MainLogin.aspx", false);
Context. Application Instance.CompleteRequestO;
}
else
 {
Response.Redirect(”MainLogin.aspx”, false);

else { '
LabeI2.Text = "Authentication Error!! ( Username Or Password is Incorrect)
LabeI2.ForeCoior = System.Drawing.Color. White*
}

}
catch (Exception ex)
{
Response. Write(ex.Message);
}
/*
string message = "Login Successful!!!!";
string title = "Title":
MessageBox.Show(message, title):
*/

string user = this.uid.Text; string pass =

this.upass.Text;

if (user — "admin" && pass = "12345")

{
Response.Redirect("Admin.aspx");
}
}

protected void DropDownListl_SeIectedIndexChanged(object sender, EventArgs e)

}
}

4.3 Testing Approach

4.3.1 Unit Testing

Unit Testing is a type of software testing where individual units or components of a software are
tested; The purpose is to validate that each unit of the software code performs as expected. Unit
Testing is done during the development (coding phase) of an application by the developers.
 Following modules were tested under Unit Testing:
* Register Page:
• Register page was tested by entering valid as well as invalid input of user
• By clicking on Register button the message box will be displayed as “Register
Successful”.
• Textbox, Required Field Validator, Button were used to enter user details.
• Login Page:
• Login page was tested by entering valid as well as invalid input for username
and password.
• After entering valid username and password the user will be directed to Main page.
• Button, Textbox, Required Field Validator were used to enter username and
password. Drop Down List was used to select whether user wants to login or admin.
• Red color indicates Authentication Error!! “Username or Password is incorrect”.

.3.2 Integrated Testing

Integration testing is the phase in software testing in which individual software modules are combined
and tested as a group.

• Home Page is connected with various pages such as Symptom, Types, Precautions, Causes,
Doctor Details, Register, Login and About Us.
• Register Page is connected to Login Page. After successful registration, the user will be directed
to Login Page.
• Login Page and Main Login Page are connected. After successful login user will be directed to
Main Login Page.
• Main Login Page is connected with Prediction Page. User can click on Predict button which is
inside Main Login Page, after that the user will be directed to Predict page. Inside Predict page
the user can enter the data and predict the result.
• After Admin logins inside, admin can check the data entered by the user.

4.3.3 Beta Testing

Beta testing is the final round of testing before a product is finally released to a wide
audience.

4.3.4 System Testing

System Testing is a level of testing that validates the complete and fully integrated software product.
• The entire Prediction System is checked as a one unit.
• Right from verification and validation at login page to proper and systematic display of
services.
 Display of the Predicted result is shown after
user enters all the input attributes,
Calculation of all the data entered by the user
is maintained and managed by the
admin. The data is displayed on admin page.

4.3.5 White Box Testing

White Box Testing is a software testing method in which the internal structure/ design/
implementation of the item being tested is known to the tester.
• By applying break points in the code, statement and branch coverage of white box
testing was achieved

• If-else Statement in the code were tested by giving valid as well as invalid data.

4.3.6 Black Box Testing

Black Box Testing is a software testing method in which the internal structure/ design/
implementation of the item being tested is not known to the tester.
• Boundary value testing was performed on username and password textbox of login
page, quantity text box of stock maintenance by entering valid and invalid input.
• Equivalence class testing was performed on login, Stock Maintenance Page.

4.4 Modifications and Improvements

4.5 Test Cases

Testing is the process of executing a program with the intent of finding out errors. A good test
case is the one that high probability of finding an as yet undiscovered error. A successful test is the
one that uncovers as a yet undiscovered error. Software Testing is critical element of software quality
assurance and represents the ultimate of specification, design and code generation.
Testing is the process of executing the program with intent of finding error. Testing begins in
small and progresses to large.
4.5.1. Unit testing:
• Unit testing is the first level of testing.
• It is the process of ensuring individual components of a piece of software at the code level are
functional.
• Unit testing can be conducted manually, but automating the process will speed up delivery
cycles and expand test coverage.
• Unit testing will also make debugging easier because finding issues earlier means they take
less time to fix than if they were discovered later in the testing process.
4.5.2 Integration Testing:
In integration testing, components are tested as group through integration
testing to ensure whole segments of an application behave as expected.
These tests are often framed by user scenarios, such as logging into an
application or opening files.
It ensures the working of different components working as a module, together.

4.5.3 White Box Testing

Here, testing of a software solution's internal structure, design, and coding
happens. In this type of testing, the code is visible to the tester. It focuses on
verifying the flow of inputs and outputs through the application, design and
usability, strengthening security. White box testing is also known as Clear Box
testing, Open Box testing, Structural testing, Transparent Box testing, Code-Based
testing, and Glass Box testing.
• Statement coverage: This technique requires every possible statement in the
code to be tested at least once during the testing process of software
engineering.

• Branch Coverage: This technique checks every possible path (if-else and other
conditional loops) of a software application.

4.3.4 Black Box Testing

It is defined as a testing technique in which functionality of the Application Under
Test (AUT) is tested without looking at the internal code structure,
implementation details and knowledge of internal paths of the software. This
type of testing is based entirely on software requirements and specifications. We
just focus on inputs and output of the software system without bothering about
internal knowledge of the software program.

• Equivalence Partitioning: It is a software test design technique that involves

dividing input values into valid and invalid partitions and selecting representative
values from each partition as test data.

• Boundary Value Analysis: It is a software test design technique that involves

the determination of boundaries for input values and selecting values that are at
the boundaries and just inside/ outside of the boundaries as test data.

• Cause-Effect Graphing: It is a software test design technique that involves

identifying the cases (input conditions) and effects (output conditions), producing
a Cause-Effect Graph, and generating test cases accordingly.
 5 RESULTS AND DISCUSSION

5.1 Test Reports

For Login;
SR NO. CASE DESCRIPTION EXPECTED RESULT ACTUAL RESULT

MESSAGE IN GREEN
1 VALID CREDENTIALS SAME AS EXPECTED
COLOUR

INVALID CREDENTIALS SAME AS EXPECTED

MESSAGE IN RED
2
COLOUR

5.2 User Documentation

6 CONCLUSIONS AND FUTURE WORK

6.1 Conclusion
6.1.1 Significance of the System
6.2 Limitations of the System
6.3 Future Scope of the Project
 7 Glossary
Cloud Computing- An emerging computing paradigm where data and
services reside in massively scalable data canters, and can be
ubiquitously accessed from any connected devices over the internet.

Collect freight- Freight payable to the carrier at the port of discharge or

ultimate destination. The consignee does not pay the freight charge if
the cargo does not arrive at the destination.
Electronic data interchange- Inter-company, computer-to-computer
transmission of business information in a standard format. An EDI
transmission consists only of business data, not any accompanying
verbiage or free-form messages.

Consigner- The party who originates a shipment of goods (shipper); the

sender of a freight shipment, who is usually the seller.

Enterprise resource planning system- A class of software for planning

and managing “enterprise-wide” the resources needed to take customer
orders, ship them account for them and replenish all needed goods
according to customer orders and forecasts. Often includes electronic
commerce with suppliers. Examples of ERP systems are the application
suites from SAP, Oracle,

Dynamics AX and others-

Integrated Testing -Integration testing is the phase in software testing in

which individual software modules are combined and tested as a group.

Black Box Testing-It is defined as a testing technique in which functionality

of the Application Under Test (AUT) is tested without looking at the
internal code structure.
White Box Testing-Here, testing of a software solution's internal structure,
design, and coding happens. In this type of testing, the code is visible to
the tester.
Unit Testing- Unit testing is the first level of testing. It is the process of
ensuring individual components of a piece of software at the code level
are functional.