We’ll look at all the information sources we’ve gathered so far and evaluate:
- currency: the source is up to date / current
- accuracy: the information is accurate
- clarity: the layout and purpose are clear
- usability: the resource is easy to use (e.g. read / easy to navigate)
- availability: the resource is easy to obtain or find
- operability: the resource works without error (web/apps and compatibility: the resource works on different platforms – browsers, mac/pc, tablet, iphone/android)
- costs associated with the above:
The desk evaluation will be followed by some user testing. We plan to test some of the information sources we have found with users to see how practical they are to use for a number of simple and complex bus journey scenarios. We will be testing among existing users and non users, young people and older folk too.
In addition, we are developing a bus stop survey, mainly using volunteers, but perhaps one that can be crowd-sourced (we provide a link to a website; user finds the relevant stop from a list of stops; user completes a simple form and uploads pics). e.g. it might work like this: What is the state of our bus stops?
The idea is that we measure the condition of the stop and the whether the timetables are present and up to date:
- a picture of the stop in context (so that we may locate it);
- a picture of the stop so that we can clearly see the timetable display panel
- remarks about the condition of the stop and timetable display (damage, legibility, height of the timetable info – condition of the fabric)