Skip to content

Bus Koi

Project Overview

Users of the system are the passengers who are willing to avail tickets online and without any physical presence. This system shall provide a solution for long distant transportation throughout the country. Through such a project, the purpose was to develop a system that shall enhance the overall experience of the passengers with comfort and convenience. As in, people will obtain a more enhanced experience from pre-journey period to the very end of the journey. Moreover, the system covers some safety measures and precautionary features during the travel period.

Features

  • e-Ticketing
  • Live Tracking
  • Schedule Maintenance
  • Record Keeping

UML Diagrams

  1. Use Case Diagram Placeholder


  2. Data Flow Diagram Placeholder

    Info

    First the customer shall sign-up for the Bus Koi App, providing various information. While doing so, the passenger shall provide Emergency Contact numbers which will be stored in the emergency_numbers database, and can also be updated by the user as passenger himself, moreover the process Emergency_Contact_Number returns the existing contact numbers to the passenger. Here. Via the e-Ticketing App process the user can get the ticket information and can avail ticket.

    Through the e-Ticketing App process, the passenger first give information and based upon those information, the process then extracts relevant information and returns them to the passenger.

    The Authority gets the Ticket purchase information though e-Ticketing web and consequently deliver bill. The Authority can also update the Schedule of the transports through Schedule_Update_process via Schedule_database.

    Via the location_database, and through Track_Location the customer can track the location of his desired transport. The Transport will provide its live location by the GPS, which is stored and updated in the location database.

    Through the Accident Detection process, if any accident occurs to the Transport, the nearest Police Station & Hospital shall be sent Alert Message and consequently update the accident database.

    Via emergency_numbers database, the Accident Detection process can access the emergency numbers; thus allowing to send alert message to the passengers’ close people.

  3. Class Diagram Placeholder

    Info

    The Passenger Class is connected to the Ticket class which has composition relationship and schedule class as association relationship more the Passenger class has a composition relationship with the Passengers’_Emergency_Contact_Numbers class, while the Authority class is connected to the both Ticket class and Schedule class for the Ticketing system and maintains the corresponding schedule to the transports via Association relationship.

    Bus_Passengers’_Emergency_Contact_Numbers has an aggregation relationship with the Accident class.

    The Schedule class has a relationship with Ticket and Accident class, having a Composition relationship with both of them. The Schedule class is also connected to the Accident class as Aggregation relationship and Bus class as Composition relationship. The Accident class has an Aggregation relationship with the Hospital and Police_Station class; While, the Bus class is connected with Schedule and Live_Tracking class through Composition relationship.

Warning

Here I am showing only 2 features of them:

  • e-Ticketing
  • Live Tracking

API Tree

Placeholder

Architecture And Tools Used In App

* MVVM Architecture
* Retrofit
* Material Design
* Recyclerview
* Google Maps API

Video Demo

1. e-Ticketing

2. Live Tracking

Screenshots of BusKoi App (Passenger)

1. Navigation Drawer

2. Ticket Purchasing

1
2
2
3
4
5
6

3. Live Tracking Bus

1
2

4. Ticket History

1

5. Sign In and Sign Up

SignIn
SignUp

Screenshots of BusKoi Driver App (Driver)

1. Navigation Drawer

2. Share Location

1
2
3
4

3. Sign In