...
For Task 2, we expect the user to perform the same sequence of actions as they would have done with the first iteration prototype.
The "View My Full Schedule" option now lets the user both expand and contract the schedule.
For Task 3, we expect the user to click on the "Swap Dates" tab. Here, the user can either choose to "Propose a Swap" or "Respond to Swap Proposals."
Clicking on "Propose a Swap" pulls up a list of the user's carpooling groups. The user should select the group for which they need to swap a date.
This then leads to a form that asks the user to first select the pick-up date of theirs that they cannot make. Then, the user must check off ALL possible times that they could potentially swap with. There is an option for the user to consult their full schedule before submitting. The reminder to check over the responses attempts to improve the safety of the interface.
For Task 4, we expect the user to see a notification on the "Swap Dates" tab after logging into the home screen.
After clicking on the tab, we expect the user to find another notification on the "Respond to Swap Proposals" button.
After clicking on the button, the user will find a list of their carpooling groups, with a notification on the group in which someone had requested a swap.
Clicking on a group will lead to a form asking whether the user can accept the swap. An expandable schedule is available for reference.
Clicking on "I agree" leads to a similar result as that of the first iteration prototype. However, we attempted to make the instructions clearer and left an expandable schedule for convenience.
Clicking on "Submit" again leads to a similar result as that of the first iteration prototype. This time, we made it clear what the user's and the swap proposer's new driving dates were and included a link to the updated schedule.
For Task 5, the workflow is exactly the same as that of the first iteration prototype. The only change was the labels on the buttons.
Observations from User Tests
...