Maharashtra State Board of Technical Education, Mumbai

Matoshri Aasarabai Polytechnic, Eklahare, Nashik

Certificate
This is to certify that following students has successfully completed the Project entitled
“College Bus Management System ” under my supervision, in the partial fulfillment of
Diploma in Computer Engineering of Maharashtra State Board of Technical Education,
Mumbai.

Bhushan Chandrakant Dhikale [Seat No: 454547]

Kartik Kamlakar Shelke [Seat No: 454536]

Pranav Bhaurao Bhaskar [Seat No: 4545443]

Saurabh Kalu Dangale [Seat No: 454544]

Date:-

Place:-

Project Guide Head of Department Principal

(Ms. N.R. Jadhav) (Prof. V.A. Sonawane) (Dr. S. J. Bagul)

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

1
 Maharashtra State Board of Technical Education, Mumbai

Maharashtra State Board of Technical Education, Mumbai

Examiner's certificate
This is to certify that
Bhushan Chandrakant Dhikale [Seat No: 454547]

Kartik Kamlakar Shelke [Seat No: 454536]

Pranav Bhaurao Bhaskar [Seat No: 4545443]

Saurabh Kalu Dangale [Seat No: 454544]

Students of Diploma in Electronics and Telecommunication Engineering was examined in

Project presentation entitled
“College Bus Management System”
on / / 2023
at
Department of Computer Engineering
Matoshri Aasarabai Polytechnic, Eklahare, Nashik
Academic Year-2022-23
Internal Examiner External Examiner

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

2
 Maharashtra State Board of Technical Education, Mumbai

ACKNOWLEDGEMENTS

I would like to express my special thanks of gratitudetomy Project guide and source of inspiration Ms. N.R.

Jadhav for his valuable guidance to make my project towards perfection.

I am also extremely grateful to our HOD Prof. V.A. for their various suggestions and all staff
member of Computer Engineering department for their constant encouragement and kind help during
my project for providing all facility &help for smooth progress of project work. I would also like to
express sincere gratitude towards our Principal Dr. S. J. Bagul for being supportive and always encouraging.
“I always pray to god to shower his blessing on me without nothing is possible to be done.”
Last but not least , the backbone of my success & confidence lies solely on blessing of my parent and
my best friends.

Thanking You.

Bhushan Chandrakant Dhikale [Seat No: 454547]

Kartik Kamlakar Shelke [Seat No: 454536]

Pranav Bhaurao Bhaskar [Seat No: 4545443]

Saurabh Kalu Dangale [Seat No: 454544]

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

3
 Maharashtra State Board of Technical Education, Mumbai

INDEX

i
Acknowledgement ii
Abstract iii
1 Introduction 1
2 Literature Survey 3
3 Problem Statement 9
3.1 Objectives of Project 9
3.2 Gantt Chart (Schedule of Project / Feasibility Analysis) 10
4 Methodology 12
4.1 Block Diagram - Description 12
4.2 Circuit Diagram – Operation 14
4.3 Power Supply Design 16
4.4 Selection Criteria 18
Software Implementation – Software used, Algorithm, Flowchart, PCB
4.5 21
Design
4.6 Sample Calculation 28
5 Result & Discussion 35
6 Conclusion 40
7 Future Scope 41
7.1 Advantages 41
7.2 Disadvantages 41
7.3 Applications 41
7.4 Future Scope 42
References 44

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

4
 Maharashtra State Board of Technical Education, Mumbai

ABSTRACT
The modern world is guided by the change in the technology day by day. Mostly the relevant changes in
technologies are enhancing the modern business techniques. Different technologies have been developed in the
world for making people’s life easier and better day by day. Android is the latest and a rapid growing
technology available for all the users or users in today’s market. An enormous increase in the end user
acceptance has been experienced in the past few years. The project is based on the latest GPS technology which
enables college management team a better way to keep eye on the activity of the college buses and manage
schedule as well as provide real time bus location for the students using bus service.The College Bus
Management System is Web & Android system aimed at students, college administration to maintain bus
facility. The system takes student information as input source and attempts to maintain the bus services. It
allows flexibility during these processes.The system generates exhaustive reports related to the Bus
Management i.e. Fees paid, dues, rout no. & bus stop.To overcome the problems of manual bus management
system, We have developed Web & Android Based college bus management System.College bus management
System is based on Android & Web, which can be implemented on any Android Phone.The reports highlight
various bus services and features of the bus, which can be subjected to improvements especially for the college
administration to improve bus transport system.The system requires comparatively small amount of resources
such as memory, input/output devices and disk space.The system overall keeps approach in highlighting key
features of the bus services. It provides the facility of tracking the particular college bus’s location in the google
map. They can also view the bus details such as bus schedule and they reach the bus on time.

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

5
 Maharashtra State Board of Technical Education, Mumbai

1.INTRODUCTION

The mobile phone industry is one of the fastest and most dynamic business sectors today. The need to
communicate efficiently and instantaneously is always an undying necessity. The market sector and the ever-
growing and demanding consumers always want to have more, and they want it better than ever. Having a
mobile phone for us makes life easier. Communication is always a part of daily life, and we cannot avoid it. The
invention of mobile phone has gone tremendous leaps in innovation and new applications. Originally, it was
intended to be a telephone that can be carried wirelessly at greater distances. Advances in communications,
upgrades in radio frequency and developments on the internet had given mobile phones more sophisticated but
easy to use in applications.Android has become very popular in the world since it is an open source and there
are no extra fees for Java Virtual Machine (JVM).

In today’s world, the time is more important for students.Being a product of high technology, mobile
phones are more widely used and are becoming more and more popular.Nowadays, buses are used rapidly as a
transportation system in the different organization, e.g., school, college, university, business firm, banks, etc.In
almost every college, they provide their bus transportation facility. Under this, updating & maintaining daily bus
records such as Route,bus no.,bus name, bus timing, driver contact,drive name and bus details. So, they need to
keep a record of their vehicle or bus running /driving and the driver of that bus or vehicle. This record contains
bus and the bus driver’s details and they need to keep bus departure, arrival and delay time. They need to keep
track of that record in a notebook or register manually.

This process is so time-consuming and it needs extra manpower. There is another problem related to
students and staff is that they don’t know the real-time location of the bus for which they are waiting for and the

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

6
 Maharashtra State Board of Technical Education, Mumbai

time it will take to reach their bus stop. And parents also don’t know the location of the bus so, they need to
wait. When bus is late then there is a late remark for staff that is traveling through the bus. There is another
problem regarding vehicle maintains. To know there are a vehicle needs maintains is so hard.We develop
College Bus Management System. This system developed on Android Platform using java programming
language.The objective of this work is to implement an intelligent college bus management system based on
current challenges and problems that is determining the person who is getting into the bus, the time of getting
into the bus and the place where he is getting into the bus provided for student bus management system. College
Bus Management System Application is a Web And Android application to help campus members detect the
current location of the bus in real-time.It is based on client-server technology along with the use of database.
One Android user (College Bus Driver) sends real time location of the bus with additional date and time
information to the server. The information provided by that user is stored in the database of the server. And
other android users can get the information through the server. The login page is available on the user app for
the college administrator.

The administrator can keep the record of the bus such as bus no., bus schedule, route info, driver contact,
etc. on the database. The administrator also has the permission to manipulate the bus record as per the needs.
Student need to login. Student can search for the bus present on the particular stop. Students get updated on the
bus location at certain time interval so that they don’t have to wait for the bus being unknown whether the bus is
coming or has gone. our system handles all the data about current location of bus and by using this data the real
time tracking of bus can be done and this information is then given to remote user who want to know the real
time bus information.

For development purpose some technologies like GPS (Global Positioning System) and Google maps
are used. The system includes server-client based application, which gives real time location of bus on Google
Maps.In this proposed system through GPS we will get the bus running distance, distance will be getting from
the map API. We can track the bus from where it is coming and where is its next stop so student, staff, parents
do not need to wait they can track the bus in the mobile application. Security head needs to give the daily report
of transportation to the concerned authority, this report is generated through this system it will be sent to the
Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

7
 Maharashtra State Board of Technical Education, Mumbai

concerned authority. After some distance for maintains of the vehicle this system will notify to maintain
department that particular bus needs maintenance. And using the QR Code, we will get the attendance of
students and staff on time so that if the bus was late then the staff cannot get late remark and if a student is not
in the bus after a certain stop parent will get notified that their child was not in the bus .Information about the
bus acquired by integrating the GPS device and biometric device in the bus.This will help to reduce man power
and time for this work. There are many systems are available to bus tracking and monitoring student in bus.This
system will be easy to access because there is no any manual work needs to do, making system smart which
works automatically. This system also monitors student who are traveling through the bus,View students details.
We fix QR Code scanner for monitoring. This report will send to the central system.From this all collected
information we are generating report for higher authority so they will check transport status. If there is any
mistake or error, they will take action. It also improves data security no one will be change data.

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

8
 Maharashtra State Board of Technical Education, Mumbai

2.LITERATURE SURVEY

This part of the project describes the theoretical background of this project,Following researchers
previously worked on modeling of organizations which is discussed below:

1. Jindan Zhu et al. discussed that many popular mobile applications require the continuous monitoring and
sharing of a mobile User’s location. However, exploiting a user’s location leads to disclosing sensitive
information about the Users daily activity. Several location privacy-preserving schemes have been
proposed, but it remains challenging for a user to achieve visibility of the associated threats as well as to
control the impact of those threats. This paper presents an adaptive location privacy-preserving system
(ALPS) that allows for a user to control the level of privacy disclosure with different quality of location-
based service (LBS). We have identified key attack models on location tracking using powerful map-
matching algorithms, and then defined a scheme that allows a user to control the privacy of tracking
Information. We have implemented ALPS on Android OS and evaluated the implementation extensively
via trace-based simulation, showing the effectiveness of user-controllable privacy preservation. [1]

2. RobiGrgurina et al. learned a student project developing a simple application for Android mobile phone.
The focus of this work was on the processes and development environment that was based on open source
software and we used within the project. Before this project we have never developed mobile
programming. In the beginning of the project we didn’t know what kind of application we wanted to
develop and we needed some time to decide. We were overwhelmed with possibilities. System
requirements were defined during the brainstorming session. During application development and test we
found out that some specifications needed extra clarification because everyone had a different interpretation
of the specifications. Also we left out some details that could improve user experience like displaying
current result. This experience was very useful because we learned something new and got insight into the

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

9
 Maharashtra State Board of Technical Education, Mumbai

entire process of creating applications. We understand the importance of formal processes for effective
teamwork as is for example in our case insufficiency defined requirements have slower our development
and testing by increasing the otherwise. [2]

3. Supriya et.al projected a real-time college bus tracking application for android smartphones which
provides the exact location of the college bus in Google Maps by providing information such as bus details,
stops, routes, etc. It is a realtime system as the current location of the bus is updated every second in the
form of latitude and longitude values which is received by the students through their application on Google
maps. It will estimate the time required to reach a particular stop on its route. The application uses
clientserve technology. When students and faculty members open the application the location of the bus is
visible in Google Maps. Students can track the location of their bus from any location through their login.
But students and faculty members must make sure that their location service is active. It provides the exact
location of the college bus, if the driver’s phone cannot access the internet or if they do not have network
coverage, the location of the bus can be obtained using the average speed of the bus that moves on a fixed
route. Admins can send a message to the driver and the students in any case of an emergency. [3]

4. G.Kiran et.al introduced an android application where the hardware unit is also used along with the
software unit to track college buses. The hardware unit consists of a global positioning system module and
an Arduino microcontroller. The Global System for Mobile communications (GSM) is inserted to a
subscriber identity module card which is connected to the power supply. Using the commands dumped into
the microcontroller, it takes the latitude and longitude values of the current position from the global
positioning system and passes it on to the global system for mobile communications. The global system for
mobile communications will be connected to the server by general packet radio service. Thus, the values
get stored in the database on the server. Then, the location is fetched from the stored database on the server.
This location is transferred as a Google Map which is visible to the user. The position of the bus is
refreshed every thirty seconds and stored on the server database. [4]

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

10
 Maharashtra State Board of Technical Education, Mumbai

5. The authors Komal Satish Agarwal et al proposed RFID Based Intelligent Bus Management and
Monitoring System. They concluded that by implementing this system various problems like
underutilization of bus fleet and long waiting time at the bus stops will be reduced. It can improve the
quality of the public transportation service effectively [5].

6. The authors M.A.HANNAN et al, proposed the Intelligent Bus Monitoring and Management System.
The experimental results show that the system is intelligent enough and able to provide important
information to the authorities for monitoring and management of the bus system [6].

7. The authors Anuradha Vishwakarma et al, proposed GPS and RFID Based Intelligent Bus Tracking and
Management System. In their proposed model they have developed AISFBRM- the autonomous
informative services for bus route map that is flexible, affordable, customizable and accurate [7].

8. The authors Shital M.Dharrao et al, recommended the Intelligent Bus stand Monitoring and Control
Using Combination of GSM,GPS& IR Sensors. The proposed system provides real time information to
monitor bus stand activity done by bus stand management as well as prospective passenger. Proposed
system is more efficient and cost effective, it is possible to implement commercially [8].

9. The authors Sunil Praneel et al, proposed Wireless Sensor Enabled Public Transportation System. The
research focuses on the actual RFID hardware implementation such as the passive tags and the reader that
is used to track the University Bus as it moves from one station to another station [9].

10. The authors Ben Ammar Hatem et al, suggested the Bus Management System Using RFID In
WSN. In their proposed model, they concluded that it is expected that integration of RFID and WSN will
provide new opportunities for applications related to the identification of object over a large area. Possible
applications are parking solution, agriculture
3.PROBLEM STATEMENT
Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

11
 Maharashtra State Board of Technical Education, Mumbai

To make an efficient use of Web & Android Technology. Provide solution with least hardware
requirement.“Web & Android Based Attendance System” is software developed for maintaining the college bus
management system.Nowadays, many colleges are still using the traditional way of using paper and files to keep
record of the bus route and schedule as well as provides information through notices which is not effective. So,
there is need of a systematic way of keeping records as well as providing information as per the need. Also
Students even don’t know about the proper timing of the bus. Some students wait for the bus being unaware of
that the bus had already been missed and they are late for the class. Therefore, the smart system is necessary
which provides real time information of bus to remote user. So we proposed a new system which overcome the
drawback of college transportation system.

3.1 Motivation:

In most educational institutions the Bus Management System is taken manually. It is not only time consuming,
but it is also unsecure and unreliable and it can be lost.All Details will be available soon via software.Students
will get to know about the buses location. Students can pay the fair via app.The objective of this proposed
system is to develop an application which will help to provide security for college and school going children’s.
This allows parents and management to check the status of secure smart college and school bus by using Iota.
The proposed system will provide various facilities like speed control, che, missing children’s, accident
emergencies, inappropriate drop, panic button, logistic management etc. which are helpful for child security.The
objective of this work is to implement an college bus management system based on current challenges and
problems that is determining the person who is getting into the bus, the time of getting into the bus and the place
where he is getting into the bus provided for college bus management system.

3.2 Scope:

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

12
 Maharashtra State Board of Technical Education, Mumbai

The aim of the project is to build a simple, effective Web & Android Based college bus management
System.The scope of the project is the system on which the software is installed, i.e. the project is developed as
a desktop application, and it will work for a particular institute. But later on the project can be modified to
operate it online.The purpose of developing Attendance System app is to computerized the tradition way of
getting bus information.Any colleges/schools/travelling agencies can make use of this application providing
information about the live location of the vehicles.This system would provide basic set of features such as
adding or updating routes and locations in the database.It also greatly reduces the amount of paper resources
needed.This is an android mobile app. It’s built to be used for school/college faculty so that they may take bus
details on their phones

3.3 Need:

Nowadays there is no limit to the kind of crimes committed in the world. Many of these include abducting
school children. Many school children’s lives were at risk because of the lack of proper safety. To ensure the
safety of each and every child we need to improve the safety measures around them. One of such a safety
measure could be bus surveillance.Everywhere around the world, children’s safety has become a major priority
for both the parents and also the college administration. Every parent thinks about the safety of his/her kid. Then
why not think about the safe transportation facility that could be provided by the schools? The major concerns
of both the parents and the administration are about the route that the buses take, student’s attendance on the
bus, and also the speed that the bus travels with. Another concern that the school administration might face is
the usage of fuel by the driver. The proposed system improves the safety of the children along with giving the
parents and the administration of peace of mind.With this project, we tend to give every child that security and
peace of mind to every parent. It is executed to give a real-time location along with an emergency alert text
message in any immediate circumstance caused. Through this framework we can get real-time monitoring of the
college bus along with a route planning.Provide a simpler method to store and access information related to
buses and students.provide a simple interface which will be easily used without much training. Reduce
paperwork and make all related information accessible easily.

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

13
 Maharashtra State Board of Technical Education, Mumbai

3.4 Objectives:

The objectives are as follows:

1) Time saving activity.
2) Easy to manage historical data in database.
3) Eliminate paperwork and save time.
4) To Increase security.
5) To make the college transportation system more efficient.
6) To eliminate paper work and increase the level of accuracy.
7) To increase speed of service with the use of technology.
8) Administrator can track the activity of the college bus by sitting at any location using internet.
9) Administrator can modify the bus schedule that is stored in the database.
10) Students can know the current location of the college bus online.
11) Provides the list of the schedule of the bus stops with its time on the user’s phone.
12) Keeps the individual record of buses with their history of movement activity.
Provides the information of the bus regarding bus no, driver name, driver contact, etc

4.PROPOSED SYSTEM

Proposed System

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

14
 Maharashtra State Board of Technical Education, Mumbai

We tried to implement a system which overcomes the limitations of the existing approach.The Bus
Management System is a desktop system aimed at students, college administration to maintain bus facility.The
system takes student information as input source and attempts to maintain the bus services. It allows flexibility
during these processesThe reports highlight various bus services and features of the bus, which can be subjected
to improvements especially for the college administration to improve bus transport system.The system requires
comparatively small amount of resources such as memory, input/output devices and disk space.We are
expecting to find the location of the bus and let the users know the location.so that one can manage their time
efficiently and reach their stop just before the bus arrives or take an alternate means of transport if they miss the
bus or they are running late.
System Architecture:

Fig:System Architecture
The system architecture diagram shows that when the user opens the application, they will need to log in
or register if they do not have an account. Once they successfully log in, they will see the home page which will
display their current location on a map as well as the current location of their assigned bus. The current location

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

15
 Maharashtra State Board of Technical Education, Mumbai

of their assigned bus will be obtained by getting the longitude and latitude values of the bus from the database
with is updated from the global positioning system and the location of the bus is displayed on the user’s map.
The driver’s details such as their name and number will also be retrieved and displayed to the user, in case they
need to contact the driver. Once the location is displayed on the map, the estimated time for the bus to reach the
user’s location will also be displayed. This will record the time it took the bus previously to reach the user’s stop
from its current location. The user can also set an alarm if they want to be notified when the bus is at a specific
stop or a certain amount of time before the bus reaches their stop.

H/W& S/W REQUIREMENT

System Necessity

Hardware:
1. Processor – i3
2. Hard Disk – 5 GB
3. Memory – 1GB RAM
4. SmartPhone
Software:
1.Operating System:Windows XP and later versions 2.Front
End:XML,HTML,CSS
3.Programming Language: Android
4.Database:MySql

SOFTWARE REQUIREMENT SPECIFICATION

a) Purpose:
Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

16
 Maharashtra State Board of Technical Education, Mumbai

This document describes a system capable of Monitoring College bus management

system.Nowadays there is no limit to the kind of crimes committed in the world. Many of these include
abducting school children. Many school children’s lives were at risk because of the lack of proper safety.
To ensure the safety of each and every child we need to improve the safety measures around them. One
of such a safety measure could be bus surveillance.Everywhere around the world, children’s safety has
become a major priority for both the parents and also the college administration. Every parent thinks
about the safety of his/her kid. Then why not think about the safe transportation facility that could be
provided by the schools? The major concerns of both the parents and the administration are about the
route that the buses take, student’s attendance on the bus, and also the speed that the bus travels with.
Another concern that the school administration might face is the usage of fuel by the driver. The
proposed system improves the safety of the children along with giving the parents and the administration
of peace of mind.With this project, we tend to give every child that security and peace of mind to every
parent. It is executed to give a real-time location along with an emergency alert text message in any
immediate circumstance caused.
b) Document Convention:

FONT STYLE SIZE

Heading Calibri (body) bold 16

Sub-Heading Calibri (body) bold 16

Others Calibri (body) regular 14

c) Intended Audience and Reading Suggestions:

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

17
 Maharashtra State Board of Technical Education, Mumbai

This document is useful for the School,College,Univercities.This project can be used in

schools.It can be implemented in colleges.Easy to manage historical data in database.Eliminate duplicate
data entry and errors in time and attendance entries. Eliminate paperwork and save time.

d) Project Scope:
The aim of the project is to build a simple, effective web based & android based college bus
management system.The aim of the project is to build a simple, effective Web & Android Based college
bus management System.The scope of the project is the system on which the software is installed, i.e.
the project is developed as a desktop application, and it will work for a particular institute. But later on
the project can be modified to operate it online.The purpose of developing Attendance System app is to
computerized the tradition way of getting bus information.Any colleges/schools/travelling agencies can
make use of this application providing information about the live location of the vehicles.This system
would provide basic set of features such as adding or updating routes and locations in the database. It
also greatly reduces the amount of paper resources needed.This is an android mobile app. It’s built to be
used for school/college faculty so that they may take bus details on their phones

1) Overall Description:
To make an efficient use of Web & Android Technology. Provide solution with least hardware
requirement.“Web & Android Based Attendance System” is software developed for maintaining the
college bus management system.Nowadays, many colleges are still using the traditional way of using
paper and files to keep record of the bus route and schedule as well as provides information through
notices which is not effective. So, there is need of a systematic way of keeping records as well as
providing information as per the need. Also Students even don’t know about the proper timing of the
bus. Some students wait for the bus being unaware of that the bus had already been missed and they are
late for the class. Therefore, the smart system is necessary which provides real time information of bus
to remote user. So we proposed a new system which overcome the drawback of college transportation

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

18
 Maharashtra State Board of Technical Education, Mumbai

system.We tried to implement a system which overcomes the limitations of the existing approach.The
Bus Management System is a desktop system aimed at students, college administration to maintain bus
facility.The system takes student information as input source and attempts to maintain the bus services.
It allows flexibility during these processes.The system generates exhaustive reports related to the Bus
Management i.e. Fees paid, dues, rout no. & bus stop. The reports highlight various bus services and
features of the bus, which can be subjected to improvements especially for the college administration to
improve bus transport system.The system requires comparatively small amount of resources such as
memory, input/output devices and disk space.We are expecting to find the location of the bus and let the
users know the location.so that one can manage their time efficiently and reach their stop just before the
bus arrives or take an alternate means of transport if they miss the bus or they are running late.

a) Product Perspective:
College Bus Management System: It is a web application .To develop an application that is cost
efficient.To reduce project completion time and cost.To make an efficient use of Web & Android
Technology. Provide solution with least hardware requirement. “college bus management system” is
software developed for maintaining the bus system management of the student on the daily basis in
the collage.

b) Product features:
It will help for the School,College.This project can be used in schools .It can be used in
hospitals.It can be implemented in colleges.In this process every institution wasted lots of paper just
for keeping the record. With such small reasons, our natural resources are depleting at the enormous
rate and it can be possible that our descendants don’t able to get those resources.College bus
management system is an android application built on Java that can be used for managing bus
services in a school,college or instiution. With the help of this application, one can book his slot for
daily ride on the institution bus. Faculties or Teachers can check ride details of a student boarding a

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

19
 Maharashtra State Board of Technical Education, Mumbai

bus. This application is connected to database which is hosted using mysql. It can also be used for
scaling any attempts to use the bus even after not paying the bus service fee

c) User class and characteristics:

1) Admin (Web):
 Login: -By using admin login page admin can create, delete, modify an Data In the Login
registration portal users can register themselves and then can login through the login
portal. Every user has to register before login and have to set a password so they could
access the event management system wherever or whenever they want. Registering will
save the login credentials in the database and verify every time a user logins through the
login portal.This module is used to login for administrator, it have whole rights to
monitor and manage the entire project, through this module, new information can be
insert, update, view and delete.
 Add Bus.
 View Bus.
 Delete Bus.
 Approve Students.
 Add Students.
 View Students.
 Delete Students.
 View Pending fees students.
 Update Fees.
 View all complaints.

2) Students (Android):

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

20
 Maharashtra State Board of Technical Education, Mumbai

 Registration
 Login.
 Mark present on particular stop.
 View current bus location
 View bus details, drivers details, timetable of bus.
 Add complaints.
 Show QR code.

3) Driver (Android):
 Login.
 View bus stop.
 View present student on stop.
 Scan QR Code(view Summery/Students details)

d) Operating Environment:
Operating environment for the college bus management System: is as listed below.
1. Internet Connection
2. Operating System Windows, Linux (Ubuntu)

e) Design and Implementation Constraints:

a) Frontend:
1. The system shall be web application.
2. The language used will be HTML,CSS

b) Backend:
1. The Desktop application should be developed by using Framework.
Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

21
 Maharashtra State Board of Technical Education, Mumbai

2. The backend language is Android.

2) Functional requirements:
1. REQ-1: The system shall be able to build student’s profile.
2. REQ-2: The system should be able maintain the student’s record.
3. REQ-3The system will predict a student bus fee record on the basis of the previous present
record.
4. REQ-4:To make the college transportation system more efficient.
5. REQ-5:To eliminate paper work and increase the level of accuracy.
6. REQ-6:To increase speed of service with the use of technology.
7. REQ-7:Administrator can track the activity of the college bus by sitting at any location using
internet.
8. REQ-8:Administrator can modify the bus schedule that is stored in the database.
9. REQ-9:Students can know the current location of the college bus online.
10. REQ-10:Provides the list of the schedule of the bus stops with its time on the user’s phone.
11. REQ-11:Keeps the individual record of buses with their history of movement activity.
12. REQ-12:Provides the information of the bus regarding bus no, driver name, driver contact, etc.

3) Non-functional requirements:
a) Performance requirements:
1. The system gives advice or alerts user immediately.
2. The System gives accurate results.
3. Interactive, minimal delays, safe info transmission

b) Safety requirements:
1. Nobody will be harm while developing the system.

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

22
 Maharashtra State Board of Technical Education, Mumbai

2. Easy to use.
3. System embedded with management procedures and validation procedures

c) Security requirements:
1. The system keeps all Students information’s with high security.
2. Identify all user, authenticate/verify user credentials, authorize user/third party, audit for user’s
usability, backup, server clustering, system policies

d) Software quality attributes:

5. Predictability
6. Accuracy
7. Maintainability
8. Usability
9. Modifiability
10. Interoperability
11. Efficiency

4) External interface:
a. User interface:

1. The developed web application for Web based and android based attendance system. To
develop an website that is cost efficient for college.
2. Front End:HTML,CSS
3. Back End:Android

b. Hardware interface:

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

23
 Maharashtra State Board of Technical Education, Mumbai

4. Processor – i3
5. Hard Disk – 5 GB
6. Memory – 1GB RAM

c. Software interface:

1.Operating System:Windows XP and later versions 2.Front

End:XML,HTML,CSS
3.Programming Language: Android
4.Database:MySql

d. Communication interface:

This project supports all types of web browsers.Active internet connection

5) Analysis Model

Waterfall Model:

SLDC Model:

1. Planning:
It is performed by the senior members of the team with inputs from the customer, the sales
department, market surveys and domain experts. This information is then used to plan the basic project
approach and to conduct product feasibility study in the economical, operational and technical areas.
Planning for the quality assurance requirements and identification of the risks associated with the project
is also done in the planning stage

2. Defining:

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

24
 Maharashtra State Board of Technical Education, Mumbai

Next step is to clearly define and document the product requirements and get them approved
from the customer or the market analysts.

3. Designing:
Based on the requirements specified in SRS, usually more than one design approach for the product architecture
is proposed and documented. This is reviewed by all the important stakeholders and based on various
parameters as risk assessment, product robustness, design modularity, budget and time constraints, the best
design approach is selected for the product.A design approach clearly defines all the architectural modules of
the product

4. Building:
The actual development starts and the product is built. The programming code is generated. If the
design is performed in a detailed and organized manner, code generation can be accomplished without
much hassle.The programming language is chosen with respect to the type of software being developed

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

25
 Maharashtra State Board of Technical Education, Mumbai

5. Testing:
This stage is usually a subset of all the stages as in the modern SDLC models, the testing activities are
mostly involved in all the stages of SDLC. However, this stage refers to the testing only stage of the product
where product defects are reported, tracked, fixed and retested, until the product reaches the quality standards
defined in the SRS.
6. Deployment:
Once the product is tested and ready to be deployed it is released formally.

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

26
 Maharashtra State Board of Technical Education, Mumbai

MATHEMATICAL MODEL
System Description:

S= I, O,F,DD,NDD, Failure, Success

Where,
S=System
I= Input
O=Output
F=Failure
S=Success

I is Input of system
Input I = set of Inputs
Where,
I= {I1,I2 ,I3,I4,I5 }
Where,
I1={ Admin}
I2= {Students}
I3= {Bus}
I4= {Drivers}
I5= {Bus Admin}

F is Function of system
F = set of Function
Where,
F1={Login }
F2={Registration }

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

27
 Maharashtra State Board of Technical Education, Mumbai

F3={Approve Students }
F4={Add Bus }
F5={Add Students }
F6={ Add Complains }
F7={ View Bus }
F8={View Students }
F9={ View Complains }
F10={Delete Students }
F11={Delete Bus }
F12={Post Complaiant}
F13={View Location }
F14={Update Fees }
F15={View Details}
F16={Show QR Code }
F17={Scan QR Code }

O is Output of system
Output O1 = { Web & Anroid Application for College bus management system}
 Success Conditions: Product working Soothly.Develop Anroid Application for College bus
management system successfully.
Failure Conditions: if internet connection Unavailable.

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

28
 Maharashtra State Board of Technical Education, Mumbai

Venn Diagram:

Fig. 1: Venn diagram

Where,

I1={ Admin}
I2= {Students}
I3= {Bus}
I4= {Drivers}
I5= {Bus Admin}
F1={Login }

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

29
 Maharashtra State Board of Technical Education, Mumbai

F2={Registration }
F3={Approve Students }
F4={Add Bus }
F5={Add Students }
F6={ Add Complains }
F7={ View Bus }
F8={View Students }
F9={ View Complains }
F10={Delete Students }
F11={Delete Bus }
F12={Post Complaiant}
F13={View Location }
F14={Update Fees }
F15={View Details}
F16={Show QR Code }
F17={Scan QR Code }
O1 = { Web & Anroid Application for College bus management system}

DFD/UML

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

30
 Maharashtra State Board of Technical Education, Mumbai

UML Diagram

A diagram is the graphical presentation of a set of elements, most often rendered as a connected graph of vertices
and arcs . you draw diagram to visualize a system from different perspective, so a diagram is a projection into a
system. For all but most trivial systems, a diagram represents an elided view of the elements that make up a
system. The same element may appear in all diagrams, only a few diagrams , or in no diagrams at all. In theory, a
diagram may contain any combination of things and relationships. In practice, however, a small number of
common combinations arise,which are consistent with the five most useful views that comprise the architecture
ofa software-intensive system. For this reason, the UML includes nine such diagrams:
 DFD Digram
 Class Diagram
 Object Diagram
 Use case Diagram
 Sequence Diagram
 Collaboration Diagram
 State chart Diagram
 Activity Diagram
 Component Diagram
 Deployment Diagram

DFD DIAGRAM

Data objects represented by labeled arrows and transformation are represented by circles also called as
bubbles. DFD is presented in a hierarchical fashion i.e. the first data flow model represents the system as a
whole. Subsequent DFD refine the context diagram (level 0 DFD), providing increasing details with each
subsequent level. The DFD enables the software engineer to develop models of the information domain &
functional domain at the same time. As the DFD is refined into greater levels of details, the analyst perform an
implicit functional decomposition of the system. At the same time, the DFD refinement results in a
corresponding refinement of the data as it moves through the process that embody the applications.A context-

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

31
 Maharashtra State Board of Technical Education, Mumbai

level DFD for the system the primary external entities produce information for use by the system and consume
information generated by the system. The labeled arrow represents data objects or object hierarchy

The context diagram is the most abstract data flow representation of a system. It represents the entiresystem as a
single bubble and. The various external entities with which the system interacts and thedata flows occurring
between the system and the external entities are also represented. The namecontext diagram is well justified
because it represents the context in which the system is to exist i.e.the external entities (users) that would
interact with the system and specific data items they would bereceiving from the system

1) DFD level 0

Fig: DFD Level 0

2) DFD level 1

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

32
 Maharashtra State Board of Technical Education, Mumbai

Fig: DFD Level 1

3) DFD level 2

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

33
 Maharashtra State Board of Technical Education, Mumbai

Fig: DFD Level 2

4) CLASS ER DIAGRAM

A Class is a category or group of things that has similar attributes and common behavior. A Rectangle is the
icon that represents the class it is divided into three areas. The upper most area contains the name, the middle;
area contains the attributes and the lowest areas show the operations. Class diagrams provides the representation
that developers work from. Class diagrams help on the analysis side, tooClass is nothing but a structure that
contains both variables and methods. The Class Diagram shows a set of classes, interfaces, and collaborations
and their relating ships. There is most common diagram in modeling the object oriented systems and are used to
give the static view of a system. It shows the dependency between the classes that can be used in our
system.The interactions between the modules or classes of our projects are shown below. Each block contains
Class Name, Variables and Methods.

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

34
 Maharashtra State Board of Technical Education, Mumbai

Fig: Class diagram

5) ACTIVITY DIAGRAM
Activity diagram are the flowcharts, showing the flow of control from activity to activity. Activity diagrams
represent the business and operational work flows of a system

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

35
 Maharashtra State Board of Technical Education, Mumbai

6) COLLABORATION DIAGRAM

A collaboration diagram is an introduction diagram that emphasizes the structural organization of the objects
that
send
and
receive

messages. Graphically a collaboration diagram is a collection of vertices and arcs.A Collaboration Diagram also
called a communication diagram or interaction diagram, is an illustration of the relationships and interactions

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

36
 Maharashtra State Board of Technical Education, Mumbai

among software objects. The concept is more than a decade old although it has been refined as
modeling paradigms have evolved

Fig: Collaboration diagram

7) STATE CHART DIAGRAM

The state diagram shows the states of an object and represents activities as arrows connecting the states. The
Activity Diagram highlights the activities. Each activity is represented by a rounded rectangle-narrower and
more oval-shaped than the state icon. An arrow represents the transition from the one activity to the next. The
activity diagram has a starting point represented by filled-in circle, and an end point represented by bulls eye
Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

37
 Maharashtra State Board of Technical Education, Mumbai

Fig: State Chart diagram

8) USECASE DIAGRAM

A use case diagram in the Unified Modeling Language(UML) is a type of behavioral diagram defined by and
created from a use-case analysis. its purpose is to present a graphical overview ofthe functionality provided by a
system in terms of actors, their goals(represented as usecases),and any dependencies between those use cases.
Use case diagrams are formally included in two modeling languages defined by the OMG:the unfied modeling
language(UML) and the systems modeling language.A Use case is a description of set of sequence of actions

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

38
 Maharashtra State Board of Technical Education, Mumbai

Graphically it is rendered as an ellipse with solid line including only its name. Use case diagram is a
behavioral diagram that shows a set of use cases and actors and their relationship. It is an association between
the use cases and actors. An actor represents a real-world object.Use case diagrams model behavior within a
system and helps the developers understand of what the user require. The stick man represents what’s called an
actor.Use case diagram can be useful for getting an overall view of the system and clarifying who can do and
more importantly what they can’t do.Use case diagram consists of use cases and actors and shows the
interaction between the use case and actors

 The purpose is to show the interactions between the use case and actor.
 To represent the system requirements from user’s perspective.
 An actor could be the end-user of the system or an external system

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

39
 Maharashtra State Board of Technical Education, Mumbai

Fig: Usecase diagram

9) ER DIAGRAM
Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

40
 Maharashtra State Board of Technical Education, Mumbai

The Entity-Relationship (ER) model was originally proposed by Peter in 1976 [Chen76] as a way to unify the
network and relational database views. Simply stated the ER model is a conceptual data model that views the
real world as entities and relationships. A basic component of the model is the Entity-Relationship diagram
which is used to visually represents data objects. Since Chen wrote his paper the model has been extended and
today it is commonly used for database design For the database designer, the utility of the ER model is:

 it maps well to the relational model. The constructs used in the ER model can easily be transformed into
relational tables
 it is simple and easy to understand with a minimum of training. Therefore, the model can be used by the
database designer to communicate the design to the end user.
 In addition, the model can be used as a design plan by the database developer to implement a data model
in a specific database management software.

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

41
 Maharashtra State Board of Technical Education, Mumbai

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

42
 Maharashtra State Board of Technical Education, Mumbai

NP HARD ANALYSIS

NP Hard analysis
The algorithm in which every operation is uniquely defined is called deterministic algorithms.The algorithm in
which every operation may not have unique result, rather there can be specified set of possibilities for every
operation, such algorithms are called Non deterministic algorithms. Non deterministic means no particular rule
is followed to make guess. The algorithms are classified into groups depending on their computing time:

Figure : P-NP Class

 P Class:
This group consists of all algorithms whose computing times are polynomial time that is there
computing time is bounded by polynomials of small degree. Eg. insertion sort, merge sort, quick sort
have polynomial computing time.

 NP Class:

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

43
 Maharashtra State Board of Technical Education, Mumbai

This group consists of all algorithms whose computing time is non-deterministic polynomial time. Eg.
Traveling salesman problem. The NP class problem can be classified into two groups:

 NP Hard Problems:
Normally optimization problems are NP-Hard problems. All NP complete problems are NP hard but
some NP hard are not NP complete. A problem is NP hard if and only if its at least as hard as NP
complete problem.

 NP complete problems:
Normally decision problems are NP-Complete problems. Non deterministic polynomial time complete
problems. The diagnosis is made through the visual analysis of tissue samples by pathologists. However,
this analysis is susceptible to intra- and inter-pathologists variability in addition to being a complex and
time-consuming task. To deal with these challenges, image processing methods are developed for
application on historical images obtained through the digitization of the tissue samples. To do so,
feature extraction and classi_cation techniques are investigated to aid pathologists and make it possible a
faster and more objective diagnosis de_nition. This process continuously goes till end and goal is being
achieved. Thus problem is comparable with Knapsack Problem.
The complexity of software is O (O (n) = O (n))which is again compatable with Knapsack.

Input:
Bus Admin
Students
Driver
Bus

SOFTWARE TESTING

The Testing Spectrum

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

44
 Maharashtra State Board of Technical Education, Mumbai

The term implementation has different meanings ranging from the conversation of a basic application to
a complete replacement of a computer system. The procedures however, are virtually the same.
Implementation includes all those activities that take place to convert from old system to new. The new
system may be totally new replacing an existing manual or automated system or it may be major
modification to an existing system. The method of implementation and time scale to be adopted is found
out initially. Proper implementation is essential to provide a reliable system to meet organization
requirement.

Software Testing

1) Unit Testing
Unit testing, also known as component testing refers to tests that verify the functionality of a specific
section of code, usually at the function level. In an object-oriented environment, this is usually at the
class level, and the minimal unit tests include the constructors and destructors. These types of tests are
usually written by developers as they work on code (white-box style), to ensure that the specific
function is working as expected. One function might have multiple tests, to catch corner cases or other
branches in the code. Unit testing alone cannot verify the functionality of a piece of software, but rather
is used to assure that the building blocks the software uses work independently of each other. In our
project we will test following modules separately.In computer programming, unit testing is a software
testing method by which individual units of source code, sets of one or more computer program modules
together with associated control data, usage procedures, and operating procedures, are tested to
determine whether they are fit for use. Intuitively, one can view a unit as the smallest testable part of an
application. In procedural programming, a unit could be an entire module, but it is more commonly an
individual function or procedure. In object-oriented programming, a unit is often an entire interface, such
as a class, but could be an individual method. Unit tests are short code fragmentscreated by programmers
or occasionally by white box testers during the development process. It forms the basis for component
Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

45
 Maharashtra State Board of Technical Education, Mumbai

testing. Ideally, each test case is independent from the others. Substitutes such as method stubs, mock
objects, fakes, and test harnesses can be used to assist testing a module in isolation. Unit tests are
typically written and run by software developers to ensure that code meets its design and behaves as
intended
Module for unit testing will be
• Pre-process Image.
• Image Decomposition.
• Feature Extraction.
• Object Recognition.
• Web Information retrieval.

 Benefits
The goal of unit testing is to isolate each part of the program and show that the individual parts
are correct. A unit test provides a strict, written contract that the piece of code must satisfy. As a
result, it affords several benefits.

 Find problems early

Unit testing finds problems early in the development cycle. In test-driven development (TDD),
which is frequently used in both extreme programming and scrum, unit tests are created before
the code itself is written. When the tests pass, that code is considered complete. The same unit
tests are run against that function frequently as the larger code base is developed either as the
code is changed or via an automated process with the build. If the unit tests fail, it is considered
to be a bug either in the changed code or the tests themselves. The unit tests then allow the
location of the fault or failure to be easily traced. Since the unit tests alert the development team
of the problem before handing the code off to testers or clients, it is still early in the development
process.

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

46
 Maharashtra State Board of Technical Education, Mumbai

 Facilitates Change
Unit testing allows the programmer to refactor code or upgrade system libraries at a later date,
and make sure the module still works correctly (e.g., in regression testing). The procedure is to
write test cases for all functions and methods so that whenever a change causes a fault, it can be
quickly identified. Unit tests detect changes which may break a design contract.

 Simplifies Integration
Unit testing may reduce uncertainty in the units themselves and can be used in a bottom-
up testing style approach. By testing the parts of a program first and then testing the sum of its
parts, integration testing becomes much easier.

 Documentation
Unit testing provides a sort of living documentation of the system. Developers looking to learn
what functionality is provided by a unit, and how to use it, can look at the unit tests to gain a
basic understanding of the unit's interface (API).Unit test cases embody characteristics that are
critical to the success of the unit. These characteristics can indicate appropriate/inappropriate use
of a unit as well as negative behaviors that are to be trapped by the unit. A unit test case, in and
of itself, documents these critical characteristics, although many software development
environments do not rely solely upon code to document the product in development.

2) Integration Testing
Integration testing is any type of software testing that seeks to verify the interfaces between components
against a software design. Software components may be integrated in an iterative way or altogether.
Normally the former is considered a better practice since it allows interface issues to be localized more
quickly and fixed. Integration testing works to expose defects in the interfaces and interaction between
Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

47
 Maharashtra State Board of Technical Education, Mumbai

integrated components (modules). Progressively larger groups of tested software components

corresponding to elements of the architectural design are integrated and tested until the software works
as a system. To combine the modules below and combine test full system.Integration testing (sometimes
called integration and testing, abbreviated I&T) is the phase in software testing in which individual
software modules are combined and tested as a group. It occurs after unit testing and before validation
testing. Integration testing takes as its input modules that have been unit tested, groups them in larger
aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output
the integrated system ready for system testing.

• Image Decomposition.
• Feature Extraction.
• Object Recognition.
• Web Information retrieval

 Purpose
The purpose of integration testing is to verify functional, performance, and
reliability requirements placed on major design items. These "design items", i.e., assemblages
(or groups of units), are exercised through their interfaces using black-box testing, success and
error cases being simulated via appropriate parameter and data inputs. Simulated usage of
shared data areas and inter-process communication is tested and individual subsystems are
exercised through their input interface. Test cases are constructed to test whether all the
components within assemblages interact correctly, for example across procedure calls or process
activations, and this is done after testing individual modules, i.e., unit testing. The overall idea is
a "building block" approach, in which verified assemblages are added to a verified base which is
then used to support the integration testing of further assemblages.Software integration testing is
performed according to the software development life cycle (SDLC) after module and functional
tests. The cross-dependencies for software integration testing are: schedule for integration
Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

48
 Maharashtra State Board of Technical Education, Mumbai

testing, strategy and selection of the tools used for integration, define the cyclomatical
complexity of the software and software architecture, reusability of modules and life-cycle and
versioning management.Some different types of integration testing are big-bang, top-down, and
bottom-up, mixed (sandwich) and risky-hardest. Other Integration Patterns are: collaboration
integration, backbone integration, layer integration, client-server integration, distributed services
integration and high-frequency integration.
 Big Bang
In the big-bang approach, most of the developed modules are coupled together to form a
complete software system or major part of the system and then used for integration testing. This
method is very effective for saving time in the integration testing process. However, if the test
cases and their results are not recorded properly, the entire integration process will be more
complicated and may prevent the testing team from achieving the goal of integration testing.A
type of big-bang integration testing is called "usage model testing" which can be used in both
software and hardware integration testing. The basis behind this type of integration testing is to
run user-like workloads in integrated user-like environments. In doing the testing in this manner,
the environment is proofed, while the individual components are proofed indirectly through
their use. Usage Model testing takes an optimistic approach to testing, because it expects to have
few problems with the individual components. The strategy relies heavily on the component
developers to do the isolated unit testing for their product. The goal of the strategy is to avoid
redoing the testing done by the developers, and instead flesh-out problems caused by the
interaction of the components in the environment. For integration testing, Usage Model testing
can be more efficient and provides better test coverage than traditional focused functional
integration testing. To be more efficient and accurate, care must be used in defining the user-like
workloads for creating realistic scenarios in exercising the environment. This gives confidence
that the integrated environment will work as expected for the target customers.

 Top-down And Bottom-up

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

49
 Maharashtra State Board of Technical Education, Mumbai

Bottom-up testing is an approach to integrated testing where the lowest level components are
tested first, then used to facilitate the testing of higher level components. The process is repeated
until the component at the top of the hierarchy is tested.All the bottom or low-level modules,
procedures or functions are integrated and then tested. After the integration testing of lower
level integrated modules, the next level of modules will be formed and can be used for
integration testing. This approach is helpful only when all or most of the modules of the same
development level are ready. This method also helps to determine the levels of software
developed and makes it easier to report testing progress in the form of a percentage.Top-down
testing is an approach to integrated testing where the top integrated modules are tested and the
branch of the module is tested step by step until the end of the related module.Sandwich testing
is an approach to combine top down testing with bottom up testing.

3) GUI Testing
GUI testing is a process to test application's user interface and to detect if application is functionally
correct. GUI testing involves carrying set of tasks and comparing the result of same with the expected
output and ability to repeat same set of tasks multiple times with different data input and same level of
accuracy. GUI Testing includes how the application handles keyboard and mouse events, how different
GUI components like menu bars, toolbars, dialogs, buttons, edit _elds, list controls, images etc. reacts to
user input and whether or not it performs in the desired manner. Implementing GUI testing for your
application early in the software development cycle speeds up development improves quality and
reduces risks towards the end of the cycle. GUI Testing can be performed both manually with a human
tester or could be performed automatically with use of a software program. To test whether .net and java
GUI is properly managed as per ow in use case diagram. To test all controls of In GUI testing check
weather .Net module GUI is been Working properly.

4) Validation Testing

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

50
 Maharashtra State Board of Technical Education, Mumbai

The process of evaluating software during the development process or at the end of the development
process to determine whether it satisfies specified business requirements.Validation Testing ensures that
the product actually meets the client's needs. It can also be de_ned as to demonstrate that the product
fulfills its intended use when deployed on appropriate environment.

Software Verification And Validation

In software project management, software testing, and software engineering, verification and
validation (V&V) is the process of checking that a software system meets specifications and that it
fulfills its intended purpose. It may also be referred to as software quality control. It is normally the
responsibility of software testers as part of the software development lifecycle. Validation checks that
the product design satisfies or fits the intended use (high-level checking), i.e., the software meets the
user requirements.This is done through dynamic testing and other forms of review.Verification and
validation are not the same thing, although they are often confused. Boehm succinctly expressed the
difference between
 Validation: Are we building the right product?
 Verification: Are we building the product right?

According to the Capability Maturity Model (CMMI-SW v1.1)

 Software Verification: The process of evaluating software to determine whether the products of a given
development phase satisfy the conditions imposed at the start of that phase.
 Software Validation: The process of evaluating software during or at the end of the development process
to determine whether it satisfies specified requirements.
In other words, software verification is ensuring that the product has been built according to the
requirements and design specifications, while software validation ensures that the product meets the

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

51
 Maharashtra State Board of Technical Education, Mumbai

user's needs, and that the specifications were correct in the first place. Software verification ensures that
"you built it right". Software validation ensures that "you built the right thing". Software validation
confirms that the product, as provided, will fulfill its intended use.
From testing perspective:
 Fault – wrong or missing function in the code.
 Failure – the manifestation of a fault during execution.
 Malfunction – according to its specification the system does not meet its specified functionality.
Both verification and validation are related to the concepts of quality and of software quality assurance.
By themselves, verification and validation do not guarantee software quality; planning, traceability,
configuration management and other aspects of software engineering are required.Within the modeling
and simulation (M&S) community, the definitions of verification, validation and accreditation are similar:
 M&S Verification is the process of determining that a computer model, simulation, or federation
of models and simulations implementations and their associated data accurately represent the
developer's conceptual description and specifications.
 M&S Validation is the process of determining the degree to which a model, simulation, or
federation of models and simulations, and their associated data are accurate representations of the
real world from the perspective of the intended use(s).
 Accreditation is the formal certification that a model or simulation is acceptable to be used for a
specific purpose.

The definition of M&S validation focuses on the accuracy with which the M&S represents the real-world
intended use(s). Determining the degree of M&S accuracy is required because all M&S are approximations of
reality, and it is usually critical to determine if the degree of approximation is acceptable for the intended use(s).
This stands in contrast to software validation.

 Classification of Methods
In mission-critical software systems, where flawless performance is absolutely necessary, formal
methods may be used to ensure the correct operation of a system. However, often for non-mission-

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

52
 Maharashtra State Board of Technical Education, Mumbai

critical software systems, formal methods prove to be very costly and an alternative method of software
V&V must be sought out. In such cases, syntactic methods are often used.
 Test Cases
A test case is a tool used in the process. Test cases may be prepared for software verification and
software validation to determine if the product was built according to the requirements of the user. Other
methods, such as reviews, may be used early in the life cycle to provide for software validation.
Black-Box Testing
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 virtually to 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.
 Test Procedures
Specific knowledge of the application's code/internal structure and programming knowledge in general
is not required. The tester is aware of what the software is supposed to do but is not aware of how it does
it. For instance, the tester is aware that a particular input returns a certain, invariable output but is not
aware of how the software produces the output in the first place.
 Test Cases
Test cases are built around specifications and requirements, i.e., what the application is supposed to do.
Test cases are generally derived from external descriptions of the software, including specifications,
requirements and design parameters. Although the tests used are primarily functional in nature, non-
functional tests may also be used. The test designer selects both valid and invalid inputs and determines
the correct output, often with the help of an oracle or a previous result that is known to be good, without
any knowledge of the test object's internal structure.
 Test Design Techniques
Typical black-box test design techniques include:

o Decision table testing

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

53
 Maharashtra State Board of Technical Education, Mumbai

o All-pairs testing
o Equivalence partitioning
o Boundary value analysis
o Cause–effect graph
o State transition testing
o Use case testing
o Domain analysis
o Combining technique

White-Box Testing
White-box testing (also known as clear box testing, glass box testing, transparent box testing,
and structural testing) is a method of testing software that tests internal structures or workings of an
application, as opposed to its functionality (i.e. black-box testing). In white-box testing an internal
perspective of the system, as well as programming skills, are used to design test cases. The tester
chooses inputs to exercise paths through the code and determine the appropriate outputs. This is
analogous to testing nodes in a circuit, e.g. in-circuit testing (ICT). White-box testing can be applied at
the unit, integration and system levels of the software testing process. Although traditional testers tended to
think of white-box testing as being done at the unit level, it is used for integration and system testing
more frequently today. It can test paths within a unit, paths between units during integration, and
between subsystems during a system–level test. Though this method of test design can uncover many
errors or problems, it has the potential to miss unimplemented parts of the specification or missing
requirements.
White-box test design techniques include the following code coverage criteria:

1. Control flow testing

2. Data flow testing
3. Branch testing

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

54
 Maharashtra State Board of Technical Education, Mumbai

4. Statement coverage
5. Decision coverage
6. Modified condition/decision coverage
7. Prime path testing
8. Path testing

White-box testing is a method of testing the application at the level of the source code. These test
cases are derived through the use of the design techniques mentioned above: control flow testing, data
flow testing, branch testing, path testing, statement coverage and decision coverage as well as
modified condition/decision coverage. White-box testing is the use of these techniques as guidelines
to create an error free environment by examining any fragile code. These White-box testing
techniques are the building blocks of white-box testing, whose essence is the careful testing of the
application at the source code level to prevent any hidden errors later on. [1] These different
techniques exercise every visible path of the source code to minimize errors and create an error-free
environment. The whole point of white-box testing is the ability to know which line of the code is
being executed and being able to identify what the correct output should be.

Levels

1. Unit testing. White-box testing is done during unit testing to ensure that the code is working as intended,
before any integration happens with previously tested code. White-box testing during unit testing
catches any defects early on and aids in any defects that happen later on after the code is integrated with
the rest of the application and therefore prevents any type of errors later on.
2. Integration testing. White-box testing at this level are written to test the interactions of each interface
with each other. The Unit level testing made sure that each code was tested and working accordingly in
an isolated environment and integration examines the correctness of the behaviour in an open

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

55
 Maharashtra State Board of Technical Education, Mumbai

environment through the use of white-box testing for any interactions of interfaces that are known to the
programmer.
3. Regression testing. White-box testing during regression testing is the use of recycled white-box test
cases at the unit and integration testing levels.

Basic Procedures
White-box testing's basic procedures involves the tester having a deep level of understanding of the
source code being tested. The programmer must have a deep understanding of the application to know
what kinds of test cases to create so that every visible path is exercised for testing. Once the source code
is understood then the source code can be analyzed for test cases to be created. These are the three basic
steps that white-box testing takes in order to create test cases:

1. Input involves different types of requirements, functional specifications, detailed designing of

documents, proper source code, security specifications. This is the preparation stage of white-box
testing to layout all of the basic information.
2. Processing involves performing risk analysis to guide whole testing process, proper test plan, execute
test cases and communicate results. This is the phase of building test cases to make sure they thoroughly
test the application the given results are recorded accordingly.
3. Output involves preparing final report that encompasses all of the above preparations and results.

System Testing
System testing of software or hardware is testing conducted on a complete, integrated system to evaluate
the system's compliance with its specified requirements. System testing falls within the scope of black-
box testing, and as such, should require no knowledge of the inner design of the code or logic. As a rule,
system testing takes, as its input, all of the "integrated" software components that have
passed integration testing and also the software system itself integrated with any applicable hardware
system(s). The purpose of integration testing is to detect any inconsistencies between the software units
Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

56
 Maharashtra State Board of Technical Education, Mumbai

that are integrated together (called assemblages) or between any of the assemblages and the hardware.
System testing is a more limited type of testing; it seeks to detect defects both within the "inter-
assemblages" and also within the system as a whole.

 Testing The Whole System

System testing is performed on the entire system in the context of a Functional

Requirement Specification(s) (FRS) and/or a System Requirement Specification (SRS). System testing
tests not only the design, but also the behavior and even the believed expectations of the customer. It is
also intended to test up to and beyond the bounds defined in the software/hardware requirements
specification(s).

FEASIBILIT STUDY

Feasibility Study
A key part of the preliminary investigation that reviews anticipated costs and benefits and recommends a course of
action based on operational, technical, economic, and time factors. The purpose of the study is to determine if the
systems request should proceed further.

Technical Feasibility: The system being developed is economic. It is cost effective in the sense that it has
eliminated the registered work completely. The system is also time effective because the calculations are automated
which are made at the end of the paper or as per the student requirement. The result obtained contains fewer errors
and are highly accurate as the data is required.

Economic feasibility: The technical requirement for the system is economic and it does not use any other
additional Hardware and software.

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

57
 Maharashtra State Board of Technical Education, Mumbai

Behavioural Feasibility: The system working is quite easy to use and learn due to its simple but attractive
interface. User requires no special training for operating the system.

PROJECT PLAN

5.1 Project Estimate

5.1.1 Reconciled Estimate
The Constructive Cost Model (COCOMO) is an algorithmic software cost
estimationmodel developed by Barry Boehm. The model uses a basic regression formula, with parameters
that are derived from historical project data and current project characteristics.It is a method for evaluating
the cost of a software package. According to him software cost estimation should be done through three
stages:

1. Basic COCOMO Model

2. Intermediate COCOMO Model

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

58
 Maharashtra State Board of Technical Education, Mumbai

3. Complete/Detailed COCOMO Model

 Basic COCOMO:
Computes software development effort and cost as a function of program size expressed in
estimated DSIs.
There are three modes within Basic COCOMO:
 Organic Mode:
Development projects typically are uncomplicated and involve small experienced teams. The
planned software is not considered innovative and requires a relatively small amount of DSIs
(typically under 50,000).
 Semidetached Mode:
Development projects typically are more complicated than in Organic Mode and involve teams
of people with mixed levels of experience. The software requires no more than 300,000 DSIs. The
project has characteristics of both projects for Organic Mode and projects for Embedded Mode.
 Embedded Mode:
Development projects must fit into a rigid set of requirements because the software is to be
embedded in a strongly joined complex of hardware, software, regulations and operating
procedures.
The basic COCOMO estimation model is given by the following expressions:
Effort = a1 x (KLOC)a2PM
Tdev=b1 x(Effort)b2 Months

Where,

 KLOC is the estimated size of the software product expressed in Kilo Lines of Code,

 a1, a2, b1, b2 are constants for each category of software products,

 Tdev is the estimated time to develop the software, expressed in months,

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

59
 Maharashtra State Board of Technical Education, Mumbai

 Effort is the total effort required to develop the software product, expressed in person months
(PMs).

 Intermediate COCOMO:
An extension of the Basic model that computes software development effort by adding a set of "cost
drivers," that will determine the effort and duration of the project, such as assessments of personnel
and hardware.

 Detailed COCOMO:
An extension of the Intermediate model that adds effort multipliers for each phase of the project to
determine the cost drivers impact on each step.
Example: A distributed Management Information System (MIS) product for an organization having
offices at several places across the country can have the following sub-components:

 Database part
 Graphical User Interface (GUI) part
 Communication part

COST ESTIMATE
It is the most frequently used technique for evaluating the e_ectiveness of the proposed
system more commonly kwon as cost/bene_t analysis.It determine the bene_t savings that are
expected from the proposed system compare them with cost. The system is economically feasible
since it would not entail additional hardware.thereby savings on the costs the manpower involved in
economical feasible study we do some calculations.

PHASES COST/HOUR HOURS COST

ESTIMTION
Requirement 30/- 20H 600
Gathering
Design Code 50/- 30H 1500
Code 50/- 20H 1250
Developement

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

60
 Maharashtra State Board of Technical Education, Mumbai

Testing 40/- 40H 2400

Implemention 60/- 10H 400

TIME ESTIMATE

Phases Time
Analysis 20H
Design 30H
Coding 20H
Testing 30H
Documentatio 20H
n
Maintenance 40H
Total time 160H

5.2 Risk Management

NP-hard (non-deterministic polynomial-time hard), in computational complexity theory is a

class of problems that are informally, quote ;at least as hard as the hardest problems in NP
quote ;. A problem H is NP-hard if and only if there is an NP-complete problem L that is
polynomial time Turing-reducible to H (i.e., LTH). In other words, L can be solved in
polynomial time by an oracle machine with an oracle for H. Informally, we can think of an
algorithm that can call such an oracle machine as a subroutine for solving H, and solves L in
polynomial time, if the subroutine call takes only one step to compute. NP-hard problems
may be of any type: decision problems, search problems, or optimization problems. If there
is a polynomial algorithm for any NP-hard problem, then there are polynomial algorithms for
all problems in NP and hence P = NP; If P NP, then NP-hard problems have no solutions in
polynomial time, while P = NP does not resolve whether the NP-hard problems can be
solved in polynomial time.

RISK IDENTIFICATION
1. Have top software and customer managers formally committed to sup- port theproject?

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

61
 Maharashtra State Board of Technical Education, Mumbai

 No
2. Are end-user enthusiastically committed to the project and the sys- tem/product to bebuilt?
 No
3. Are requirements fully understood by the software engineering team and its customers?
 Yes
4. Have customers been involved fully in the definition ofrequirements?
 No
5. Do end-users have realisticexpectations?
 Yes
6. Does the software engineering team have the right mix ofskills?
 Yes

7. Are project requirements stable?

 Yes
8. Is the number of people on the project team adequate to do thejob?
 Yes
9. Do all customer/user constituencies agree on the importance of the project and on the
requirements for the system/product to bebuilt?
 Yes
RISK ANALYSIS:
There are quite different types of risk analysis that can be used. Basically, risk analysis is used to
identify the high-risk elements of a project in software engineering. Also, it provides ways of detailing
the impact of risk mitigation strategies. Risk analysis has also been found to be most important in the
software design phase to evaluate criticality of the system, where risks are analyzed and necessary
counter measures are introduced. The main purpose of risk analysis is to understand risks in better
ways and to verify and correct attributes. A successful risk analysis includes important elements like
problem definition, problem formulation, data collection.

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

62
 Maharashtra State Board of Technical Education, Mumbai

Risk analysis is useful in many situations:

I. When you're planning projects, to help you anticipate and neutralize possible problems.
II. When you're deciding whether or not to move forward with a project.
III. When you're improving safety, and managing potential risks in the workplace.
IV. When you're preparing for events such as equipment or technology failure, theft, staff sickness,
or natural disasters.
V. When you're planning for changes in your environment, such as new competitors coming into
the market, or changes to government policy.

RISK MANAGEMENT ANALYSIS:

If there is a possibility that the achievement of a goal is harmed, prevented from occurring or suffers
negatively due to the occurrence of uncertain events, we call it the risk.These so-called uncertain events
can be caused by different factors. An efficient risk management analysis should be able to attend to
every one of them to be able to identify them promptly in each of the listed cases:

Personnel risks:
Caused by a lack of Knowledge about technology and training to perform functions. There is a
possibility that errors are intentional, this is the result of the dubious conduct.
The main risks from personal issues are:
 Unintentional; resulting in omission or negligence.
 Cannot perform task because lack of ability.
 Lack of time management.

Process Risks:
The occurrence of internal process deficiencies like inadequate performance indicators, inefficient
controls, modeling failures and an inability to abide by the current laws.

Systems risks:
Arising from inadequate, poorly structured or defective IT systems. Some examples:
 Intermittent networks

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

63
 Maharashtra State Board of Technical Education, Mumbai

 Server crash
 Physical damage to data storage components
 System obsolescence
 Improper maintenance
 Power outage from internal causes
 System slowdown
 Security holes

RISK MANAGEMENT W.R.T NP HARD ANALYSIS:

1. In rural area most of the time Internet will not be available so our system may not work.
2. If reviews not available and false review are there then systems results will fails.
3. If provide wrong input then system will show wrong output or it may fail.

RISK IDENFICATION:
1. System may get fail during review database.
2. Results may get fail.

RISK ANALYSIS:
The risks for the Project can be analyzed within the constraints of time and quality

I RISK PROBABIL IMPACT

D DESCRIPTI ITY
ON
SCHEDU QUALI OVERA
LE TY LL
1 Internet Low Low High High
connection
not available
2 False review Low Low High High
3 Incorrect Low Low High High
input
Table 1.1

PROBABILITY VALUE DESCRIPTION

High Probability of occurrence is >75%

Medium Medium Probability of occurrence 26-75%

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

64
 Maharashtra State Board of Technical Education, Mumbai

is
Low Low Probability of occurrence is <25%
Table 1.2

5.3 Team Organization

Team consists of 4 members and proper planning mechanism are used and roles of each member are
defined.

Team structure :
The team structure for the project is identified. There are total 4 members in our team and roles are
depend. All members are contributing in all the phases of project. Management reporting and
communication: Well planning mechanisms are used for progress reporting and inter/intra team
communication are identified as per requirements of the project.
Management Reporting :
1. Status Reports
2. Risk Reports
3. Resource Reports

Management Reporting And Communication

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

65
 Maharashtra State Board of Technical Education, Mumbai

1.Feedback: Provides a feedback, which ensures to the user that the organization (which develops the
software) understands the issues or problems to be solved and the software behavior necessary to address
those problems.
2. Decompose problem into components: Organizes the information and divides the problem into its
component parts in an orderly manner.
3. Validation: Uses validation strategies applied to the requirements to acknowledge that requirements are
stated properly.
4. Input to design: Contains sauciest detail in the functional system requirements to devise a design
solution.
5. Basis for agreement between the user and the organization: Provides a complete description of the
functions to be performed by the system. In addition, it helps the users to determine whether the spiced
requirements are accomplished.
6.Estimating costs and schedules: Determines the requirements of the system and thus enables the
developer to have a 'rough' estimate of the total cost and schedule of the project.

Advantages

1. It saves lots of time.

2. It is easy to use and fast to implement.
3. User Friendly GUI
4. Reduction of paper work
5. The system eliminates the use of paperwork needed for attendance marking and monitoring.
6. There is no need for laptop or computer in every class to run the system as the system is run on mobile
so no need of extra efforts and resources.
7. The app is easy to install and use.
8. This system is very easy to implement.
9. The same system can be used for many applications with minute changes.
10. Very easy to maintain.

Application:

 School
 College
 Companies
 Big Organisations.
 used in bus monitoring and controlling systems

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

66
 Maharashtra State Board of Technical Education, Mumbai

 used as library login system.

 used as student attendance monitoring system.
 used in Electronic transportation system.

FUTURE SCOPE

Future Scope:
The users suggest that the future researches may improve the current project. More features may also be added
to the system through future researches to improve and enhance the capabilities of the system. Future researches
may also create a mobile application on iOS or android due to which the system will be more easily accessible
and may accommodate and support more users that use different mobile platforms.

CONCLUSION
Conclusion:

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

67
 Maharashtra State Board of Technical Education, Mumbai

The proposed system is implemented practically in the bus and the working is monitored and observed that it
has maximum functional capability.This application will make it easier for users to students to track the real-
time location of their buses.This ensures that the user arrives on time to the university and does not get delayed
trying to find a bus or wondering if they missed their bus. It is useful to first-year students who might not know
the bus might arrive that their stop and lets them know if they have missed their bus in which case they can find
other buses that might pass by their stop.This system only gives the latitude and longitude of the place, in future
we are trying to implement the system which gives the name of the place.

REFERANCE

1) Jindan Zhu,1 Kyu-Han Kim,2 Prasant Mohapatra,1 and Paul Congdon2 “An Adaptive Privacy-
Preserving Scheme for Location Tracking of a Mobile User” 2013 IEEE International Conference on
sensing, Communication and networking.

2) RobiGrgurina, Goran Brestovac and TihanaGalinacGrbac, “Development Environment for Android

Application Development: an Experience Report”, MIPRO 2011, May 23-27, 2011.

3) Supriya Sinha, Pooja Sahu, Monika Zade, Roshni Jambhulkar and Prof. Shrikant V. Sonekar. Real Time
College Bus Tracking Application for Android Smartphone. In: International Journal Of Engineering
And Computer Science, ISSN: 2319-7242, Volume 6 Issue 2 Feb. 2017, pp 20281-20284.M. Young,
The Technical Writer’s Handbook. Mill Valley, CA: University Science, 1989.

4) G.Kiran Kumar, C.B.Aishwarya, A. Sai Mounika. College Bus Tracking Android Application using
GPS. In: International Journal of New Innovations in Engineering and Technology, Volume 4 Issue 4 –
April 2016, ISSN: 2319-6319

5) Komal Satish Agarwal, Kranthi Drive “RFID Based Intelligent Bus Management and Monitoring
System”. International Journal of Engineering & Technology, ISSN: 2278-0181, Vol.3 Issue 7, July-
2014.

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

68
 Maharashtra State Board of Technical Education, Mumbai

6) M.A. Hannan, A.M.Mustapha, A. Hussain, H.Basri “Intelligent Bus Monitoring and Management
System”. World Congress on Engineering and Computer Science 2012 Vol II, October 24-26.

7) Anuradha Vishwakarma, Agarja Jaiswal, Ashwini Neware, Shruthi Ghime, Antara Marathe, Reshmi
Deshmukh “ GPS and RFID Based Intelligent Bus Tracking and Management System ”. International
Research journal of Engineering and Technolgy,Vol. 03, Issue: 03, March-2016.

8) Shital M. Dharro, Vijay d. Choudary, Kantilal P. Rane “International Bus Stand Monitoring and Control
Using Combinnation of GSM, GPS&Ir Sensor”. International Journal of Innovative Research in Science,
Engineering and technology,Vol. 4,Issue 7, july 2015.

9) Sunil Prannel narayan, Mansour H. Assaf, Shalvindra Krishneel Prasad “ Wireless Sensor Enabled
public transportation System”. International Journal of Communications, Network and System Sciences,
2015,8,187-196.

Matoshri Aasarabai Polytechnic, Nashik Department of Computer Engineering

69