|
|
# **Report: Wireframe Iteration 1**
|
|
|
|
|
|
**Purpose**
|
|
|
|
|
|
The purpose of this test is to assess the usability of the prototype's interface, focused on the following aspects:
|
|
|
|
|
|
- **Visibility** : Are menu items placed in accordance with their importance, and is the wording of each item appropriate for its function?
|
|
|
- **Feedback** : Is the user given sufficient information as to what is happening when they input data or make mistakes?
|
|
|
- **Consistency** : Does moving through menus and inputting user data follow a consistent pattern such that the user does not get confused by changes in how the program operates?
|
|
|
- **Error handling** : If the user inputs erroneous data, does the program provide sufficient and appropriate leeway to change the data after the mistake is done?
|
|
|
|
|
|
**Methodology**
|
|
|
|
|
|
Participants engaged in one-on-one test and interview sessions with our testers, first being administered a short batch of specific tasks to be performed in the interactive prototype while they were encouraged to verbalize any doubts they had about functionality. Observations were noted down, then after the tests were completed, they were followed up with a batch of questions regarding the user's interaction with the program.
|
|
|
|
|
|
|
|
|
## **Problem statements and Solutions**
|
|
|
|
|
|
Going through the observations and answers to questions, we've reduced each one to a problem statement that can be addressed, loosely grouped within categories. For each one, solutions should be filled in and voted on by project team members before beginning work on the next iteration.
|
... | ... | |