Bus Tracker Project

Description

What’s the goal of the project?

Design and develop a software ecosystem who’s purpose is to solve the problem of limited information about the various bus routes.

To be more specific, passengers usually need information about bus routes in general or a specific bus route they are interested in. The information might be:

• The list of running buses, what's their route and where they are right now.
• The exact route of the bus, in order to find those he is interested in.
• The current position of the bus inside it's route.
• The bus estimated time of arrival to it's destination or to passenger's current location.

What’s the scope of the project?

The above are abstract references to various functionalities (grouped like views).

• Driver
  • List of all bus (drivers that have active path)
  • Specific Bus Info (active path/position etc)
  • Driver's profile
• Passenger
  • Passenger's profile
  • Favourite routes
  • Interesting routes (routes that currently the passenger is interested in receiving notifications)
• Route
  • Official Routes (named ex Athens-Volos)
  • Custom routes (created by bus drivers)
• Common Services
  • About Us
  • Contact Us
  • Bug Report

Deliverables

There are four instances at this ecosystem:

• A backend that stores all the exchanged information
• An administration application (dashboard)
• A bus mobile application (business/closed)
• A passenger mobile application (free/opened)
• A web app for the presentation of the entire ecosystem (Basically an extensive aboutUs) (maybe)

What are the requirements/prerequisites for this project in order to gain value?

Need to get in contact with bus company's drivers in order to create a demo on realistic environment.

Schedule

The project started at 19 February 2017 and will (for now) end at 30 June 2017

Each sprint will last two weeks (starts at Sundays and ends after two Saturdays).

Final sprint lasts three weeks.

Schedule can be found at the below trello board (private): https://trello.com/b/c4ebNtw5

Research/Training

• https://developer.android.com/training/index.html
• https://developers.google.com/maps/documentation/android-api/
• https://www.udacity.com/course/material-design-for-android-developers--ud862
• https://developer.android.com/training/design-navigation/screen-planning.html

Technologies

The technologies that are going to be used at each instance (see deliverables) Backend:

• DB
  • MongoDB
• main-app
• Node.js
• Loopback

Admin's dashboard:

• React
• Redux
• Grommet UI

Driver's mobile App:

• Stick with android defaults
• Loopback SDK (maybe)

Passenger's mobile App:

• Stick with android defaults
• Loopback SDK (maybe)

Presentation Web App (maybe):

• CMS or react based front-end application.