Our code prototype may be seen at:
http://zbt.mit.edu.ezproxy.canberra.edu.au/nextride/myrides.html
and downloaded at: NextRide.zip
The page is meant to be a mobile html5 page, however because only one of our team members has a smart-phone the prototype was developed and tested on the desktop but restricted to 900x640 pixels (iPhone 4s resolution). It works best in Chrome.
When the splash page is loaded all the stored data is cleared and new random data is generated, do not be alarmed. The core interactions happen on the "to House", "to Campus" and "Me" page
Our scenarios from GR2:
- Charles is planning on going to campus today. He woke up at 11and needs to be on campus by 3pm, but besides that he doesn’t really care when he goes. He’s willing to give people a ride and leave whenever is more convenient for others. He is going to check to see when people have requested a ride. He sees that 2 people have requested a ride at 2, and then schedules a ride then. His car seats 5 (including him).
- Alexis is on campus and he needs to get to the house, Saferide and the T have both stopped running for the night, its too cold to walk and he wants to get a ride but he would not mind getting a cab. he’s flexible on when he is leaving but he knows he can’t leave in the next 30 min.
- Jorge needs to get to campus before 1pm. It’s 11am right now and he doesn’t care when he goes as long as he gets a ride before one. Jorge looks at the available rides and reserves himself a spot on a ride in Yifan’s car at 12:30pm.