Bus tracking system
Bus tracking system
Bus tracking system
Objectives
1. Realtime Bus Tracking: To implement GPSenabled tracking that
provides accurate, realtime location updates of buses for passengers
and operators.
2. Route and Schedule Management: To optimize bus routes and
schedules dynamically, based on traffic conditions and other factors,
ensuring efficient time management and reducing delays.
3. Passenger Notifications and Alerts: To enhance the passenger
experience by providing timely notifications regarding bus arrival
times, delays, route changes, and other relevant updates.
4. Data Analytics and Reporting: To generate actionable insights
through data analytics on bus performance, route efficiency, and
passenger usage patterns, aiding operators in making datadriven
decisions for improving service.
5. Enhanced Operational Efficiency: To streamline bus operations by
automating tracking, scheduling, and data collection processes,
thereby reducing manual work and improving accuracy.
Scope
1. System Development:
Creation of a webbased platform with GPS integration, enabling
realtime bus tracking and updates accessible from mobile and
desktop devices.
Implementation of passenger and operator interfaces to cater to
different user needs.
2. Features Covered:
For Passengers: Realtime bus location tracking, route information,
and notification services.
For Operators: Tools for route optimization, schedule management,
and access to data analytics dashboards.
4. Stakeholders Supported:
Includes functionalities for passengers, bus operators, and
administrative staff, enabling each group to access relevant data and
tools to improve overall bus service efficiency and user satisfaction.
1.4 overview of frontend
Technologies Used:
- HTML: For structuring the web pages and presenting content.
- CSS: For styling the interface, ensuring it is visually appealing and responsive
across different devices.
- JavaScript: For dynamic content updates, user interactivity, and handling real-
time updates using AJAX.
- React (or Angular/Vue.js): For building a reactive and efficient user interface
that handles the real-time data flow smoothly.
- Bootstrap: To ensure responsive design across various screen sizes and
devices.
- Map Integration: Using Google Maps API or Mapbox for real-time bus location
tracking and visualization.
1.5 Backend
The back-end of the Bus Tracking System is responsible for processing real-time
data, managing user requests, handling databases, and ensuring secure and
reliable communication between the system and its users. This part of the
system is crucial for enabling GPS tracking, route optimization, and data
analytics. It serves as the backbone that supports front-end functionalities,
managing data flow, processing requests, and integrating with external services
like GPS APIs.
- Database Management:
- MySQL: A relational database for storing structured data like user
information, bus schedules, and route data.
- Redis: A caching solution for storing frequently accessed data (like real-time
bus locations) to improve response times.
- Communication Protocols:
- RESTful APIs: For communication between the front-end and back-end,
allowing secure and structured data exchange.
- WebSocket: For real-time communication, enabling quick updates on bus
locations without needing to refresh the front-end.
- Security Tools:
- OAuth 2.0: For secure user authentication and authorization.
- SSL/TLS Encryption: To secure all data transferred between clients and
servers.
1. Request Handling:
- The system receives requests from users (e.g., checking bus location) via the
front-end interface. These requests are processed by the server, which
interacts with the database and GPS services to retrieve or update the
necessary data.
3. Real-Time Updates:
- WebSockets enable the server to send real-time location updates and alerts
directly to the front-end without needing to poll the server continually,
enhancing efficiency and responsiveness.
- Server-Side Software:
- PHP for handling server-side logic and API requests.
- MySQL for database management, storing user data, route
information, and GPS data.
- Python (optional) for data analytics and processing.
- Client-Side Software:
- JavaScript (React, Angular, or Vue.js) for the front-end interface.
- HTML5 and CSS3 for content structure and styling.
- Google Maps API or Mapbox for real-time mapping.
- Other Tools:
- Web server software like Apache or Nginx.
- Notification services, e.g., Firebase for real-time notifications.
2.5 Hardware Requirements
- Server Hardware:
- High-speed processors (minimum 1.4 GHz or higher).
- Storage: At least 1 TB for data storage and backups.
- RAM: Minimum 8 GB for handling multiple simultaneous requests.
- Network Infrastructure:
- High-bandwidth internet connection to support real-time data
transfer.
- Routers and network switches for secure, reliable connectivity.
- GPS tracking devices installed in each bus, capable of transmitting
location data to the central server.
2.6 Feasibility Study
The Waterfall Model is chosen for BTS development due to the clear
requirements and structured phases involved. Key phases include:
1. Entities:
- Bus: Stores information on each bus, including bus ID, current
location, and status.
- Route: Contains route details, such as route ID, start point, end
point, and associated bus stops.
- Stop: Represents each bus stop, with stop ID, name, location, and
connections to routes.
- User: Represents both passengers and operators, storing user ID,
name, contact information, role, and notification preferences.
- Notification: Stores alert details, such as notification ID, type,
timestamp, and recipient ID.
- Tracking Data: Logs real-time bus location updates, including
timestamp, latitude, longitude, and speed.
2. Relationships:
- Bus to Route: A one-to-many relationship where each bus is
assigned to one route, but each route can have multiple buses.
- Route to Stop: A one-to-many relationship, with each route
consisting of multiple stops.
- User to Notification: A one-to-many relationship where users
receive multiple notifications based on their preferences.
- Bus to Tracking Data: A one-to-many relationship, as each bus
generates continuous tracking data updates over time.
3.3 Data Flow Diagrams (DFD)
- External Entities:
- Passengers: Interact with the system to view bus locations, check
routes, and receive notifications.
- Operators: Manage routes, monitor bus performance, and receive
alerts through the system’s dashboard.
- GPS System: Sends real-time bus location data to the BTS.
- Main System:
- Interacts with external entities to provide real-time bus tracking,
manage routes, and handle notifications.
2. Processing:
- Location Processing: The system updates the bus location on the
map in real time.
- Route Calculation: Based on real-time data and user inputs, the
system calculates optimal routes.
- Notification Processing: Checks for any relevant updates and sends
alerts based on user preferences.
3. Data Output:
- Real-Time Map Display: Updates the front-end with current bus
locations and routes.
- User Notifications: Sends alerts and notifications to passengers
and operators.
- Operator Reports: Provides analytics and reports to operators,
accessible through the dashboard.
3.4 Database Design
1. Bus Table:
- Fields: `bus_id`, `route_id`, `current_location`, `status`
- Primary Key: `bus_id`
- Foreign Key: `route_id`
2. Route Table:
- Fields: `route_id`, `start_point`, `end_point`, `total_stops`
- Primary Key: `route_id`
3. Stop Table:
- Fields: `stop_id`, `route_id`, `stop_name`, `location`
- Primary Key: `stop_id`
- Foreign Key: `route_id`
4. User Table:
- Fields: `user_id`, `name`, `contact`, `role`, `notification_pref`
- Primary Key: `user_id`
5. Notification Table:
- Fields: `notification_id`, `user_id`, `message`, `timestamp`
- Primary Key: `notification_id`
- Foreign Key: `user_id`
This design approach ensures that the system is modular, allowing for
scalability, easy maintenance, and efficient data processing. Each
module can be updated or replaced independently, providing
flexibility for future enhancements.
Chapter 4 CONCLUSION
The Bus Tracking System (BTS) offers a comprehensive solution to the
limitations of traditional bus services, which are often plagued by
uncertainties in schedules and inefficiencies in operations. Through
GPS tracking, real-time updates, and robust data management, the
BTS enhances both the passenger experience and operational
efficiency, supporting data-driven decision-making and facilitating
more reliable and accessible public transportation.
Key Benefits
Future Directions
4. Sustainability Initiatives:
- The BTS could incorporate features that track fuel consumption or
emissions, supporting eco-friendly initiatives and enabling operators
to make sustainable decisions that reduce the environmental impact
of their services.
Final Thoughts