...
One user was our original User B in GR1. His requests were part of the requirements of the project, but we still presented the GR3 debriefing to him. His tests included his original request to find energy consumption broken down by the hours, and he felt the user interface intuitive enough to quickly find out the information. He was also given some other tasks, for example, schedule a transaction. His overall feedback is that the interface is easy to learn, and information is presented well.
...
- When he tried to adjust the Air Conditioner setting, the soft-keyboard blocked the screen. He couldn't see where the cursor was or whether the backspace was actually deleting the old value
- After schedule a transaction from the Reserves tab, the screen returned to the device tree view. It's not obvious how to view the just scheduled transaction
- He was pressing on the device name itself, while trying to bring up the device settings page. Currently using the Edit Setting button is the only way to get to the page. We should consider supporting context menus as well, which will pop up when user presses a device name. .
The second user is a female home owner. She is a typical user among the targeted user population of the application. She was verbally introduced the purpose of the application, and given about ten minutes to play around it. After that we asked her to do the following specific tasks:
- Find today's total energy consumption
- Find which device used most for the day
- Compare today's usage with the past 30 days
- Sell power from a specific device at a given future time
Reflection
Risk Assessment
...