Summary of Interface problems discovered
First of all, at the beginning of each scenario, we were not provided with the task description. As a result, we had no choice but to “blindly” follow the steps in the scenario. In addition, since we did not have a clear goal in mind for every task, we were not able to answer most of the questions until we have “completed” one walkthrough. The scenarios themselves also lack certain details. For example, in the login step, username and password were not specified in the scenario. This leads us to the first interface issue that we encountered.
The first interface issue we encountered during our walkthrough was the inability to know whether we had logged in correctly as we were given no indication of which user was logged in. We encountered this on the first step of the walkthrough when we asked the question “Will the user understand the …show more content…
There is no box to add a date and time and while we were willing to accept that there might just be a feature that uses a timestamp, we all agreed that a pharmacist could perhaps have an interaction and then get really busy and record that interaction at a later time or date. This is outside of the scope of the cognitive walkthrough but something we also talked about while discussing this issue, if we clicked the edit button will we be allowed to edit the time or just the interaction note?
Similarly to the previous item, we had another discrepancy with the interaction screen. We didn’t think that on step 6 of scenario 2 that the user would be able to understand that the drug box was clickable as there are two buttons on the side that afford clicking so why not add a third one for viewing to help the user out instead of assuming they will know to click the drug box.
Another interface problem concerns the consistency of action buttons in pop-up
First of all, at the beginning of each scenario, we were not provided with the task description. As a result, we had no choice but to “blindly” follow the steps in the scenario. In addition, since we did not have a clear goal in mind for every task, we were not able to answer most of the questions until we have “completed” one walkthrough. The scenarios themselves also lack certain details. For example, in the login step, username and password were not specified in the scenario. This leads us to the first interface issue that we encountered.
The first interface issue we encountered during our walkthrough was the inability to know whether we had logged in correctly as we were given no indication of which user was logged in. We encountered this on the first step of the walkthrough when we asked the question “Will the user understand the …show more content…
There is no box to add a date and time and while we were willing to accept that there might just be a feature that uses a timestamp, we all agreed that a pharmacist could perhaps have an interaction and then get really busy and record that interaction at a later time or date. This is outside of the scope of the cognitive walkthrough but something we also talked about while discussing this issue, if we clicked the edit button will we be allowed to edit the time or just the interaction note?
Similarly to the previous item, we had another discrepancy with the interaction screen. We didn’t think that on step 6 of scenario 2 that the user would be able to understand that the drug box was clickable as there are two buttons on the side that afford clicking so why not add a third one for viewing to help the user out instead of assuming they will know to click the drug box.
Another interface problem concerns the consistency of action buttons in pop-up