html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <style>
.hidable
Unknown macro: {display}
</style>
<script>
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. function showhide(section){
var ele=document.getElementById(section);
if(ele.style.display!="block") {
ele.style.display="block";
document.getElementById(section+"show").innerHTML = "Hide";
} else
Unknown macro: { ele.style.display="none"; document.getElementById(section+"show").innerHTML = "Show"; }}
</script>
GR3 - Paper Prototyping
1. Scenario given to the users
Two people arrive at the aquarium without a visit plan. They have limited time available. This web-based system is available through a mobile device to accomplish the some specific tasks:
2. Description of the initial prototype
uhfiefijwoiefj
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <a href="javascript:showhide('design1');" id="design1show">Show this prototype</a>
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <div id="design1" class="hidable">
2.1 Tasks requested to the user:
1. Buy 2 tickets
2. Find the location of the little blue penguins
3. Find the schedule of events about penguins
4. User finds a very interesting red fish in a tank and wants to get more details about that specie (added for the last user test of the first round)
2.2 Prototype functionality:
The following table presents all the screens used in this prototype desing.
 |
AUHIUADHGVIUH |
 |
AUHIUADHGVIUH |
 |
AUHIUADHGVIUH |
 |
AUHIUADHGVIUH |
 |
AUHIUADHGVIUH |
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. </div>
3. First Round Prototype testing
3.1 User 1:
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <a href="javascript:showhide('design2');" id="design2show">Show this user test</a>
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <div id="design2" class="hidable">
User 1 - Observations:
Task 1:
clicks Tickets
clicks text box, enters informations, tabs to go to next text box
repeats until form is finished, grabs ticket
Task 2:
hit floor 2 look around
hit floor 3 look around
hit overview
hit floor 1
go to search type in ‘penguin’
go back to map
hit floor 2 and find it
Task 3:
floor 1
click triangular symbol
click round symbol
tap outside to close all bubbles
click triangular symbol, see info about session
“It was hard to not confuse triangles and circles, they look alike”
Task 4:
click on circles and triangles to read bubbles
“I expect the bubbles to close automatically when I click a different location”
click on section
“I would like if it at least said the name of the section”
User 1 - Changes made to the prototype after this test:
 |
- Added "today button" to save the typing time if this is the case (more common case)
- Information about the payment method was separated to avoid confusion
|
 |
- The map legend was deleted because its meaning was not clear for the users. Showing now events more clearly
|
 |
The name "events" is used instead of "related staff sessions" which was not a clear term |
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. </div>
3.2 User 2:
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <a href="javascript:showhide('design3');" id="design2show">Show this user test</a>
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <div id="design3" class="hidable">
User 2 - Observations:
Task 1:
Click tickets
Starts filling out information
(The user thinks expiration date is for the tickets)
(The user realizes it’s for the credit card when he reads ‘security code’)
Picks Boston first, then changes to California (his home town)
Click Buy
Task 2:
Search for ‘penguin’
Clicks on ‘look on map’
“I know I have to head over to that triangle now”
Task 3:
Search for ‘penguin staff session”
“I can go it’s 4pm”
“I don’t know if the number of current attendees means there is no space left”
“I’ll now head over”
Task 4:
(Confused, don’t know if to search)
Go to floor
Click on one of the symbols
“It should keep the titles for each one and more info should be on the legend”
“Legend is hard to find”
“Bubbles should be larger”
“Hover over should show titles”
Jeremy Comments:
Regarding ticket screen, “there is no info on the top”, “cc info and ticket information
should be separated”
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. </div>
3.3 User 3:
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <a href="javascript:showhide('design4');" id="design2show">Show this user test</a>
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <div id="design4" class="hidable">
User 3 - Observations:
Task 1:
“It’s touchscreen?”
Click tickets
Click ‘Today?’
Enter info
Click Buy
“Does it give me a QR code or something?”
Task 2:
“I’m not sure if this map is for the inside of the building, or how to get here in Boston”
Click Map
Click ‘lookup on map’
“touch the penguin?”
“is this supposed to be floor 2?”
“there is no gps...”
“I’m distracted by these icons jumping slightly”
Task 3:
(A home button is clearly needed for all screens)
Press floor 1
(Map now shows “events” instead of “sessions”)
“I thought the legend would list all things”
Task 4:
Click floor 2
“I would walk go to map from home”
User 3 - Changes made to the prototype after this test:
 |
- The ticket confirmation screen explicitly says that the confirmation number will remain in the screen so that the user is sure the information will remain there
- The ticket drawing was eliminated to avoid redundant information
|
 |
- Added price in the screen. This price box is automatically updated when the user changes the number of tickets
|
 |
- Improved display of events over the map.
- Added home button.
|
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. </div>
3.4 User 4:
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <a href="javascript:showhide('design5');" id="design2show">Show this user test</a>
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <div id="design5" class="hidable">
User 4 - Observations:
Task 1:
Click tickets
Click ‘Today?’
Fills in form
Click ‘Buy’
“What is the price?!”
“Are there guest types?”
“I don’t know my confirmation number...”
Task 2:
Click search
‘Penguin’
Click ‘lookup on map’
“Does it mean I’m here?”
“Where am I?”
“Are there directions?”
Task 3:
“I want to go Home”
“There is no Home button”
Type “floor 1 events” in search
Click on ‘Map’
Click on floor 1
“expected to see a list of events on the left”
Task 4: (Find info regarding red fish)
Click on floor 2
Click on floor overiew
Click on section
(list of animal pictures show up)
“Is it a long list? It will be hard to find...”
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. </div>
3.5 Usability issues:
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <a href="javascript:showhide('design3s');" id="design2show">Show</a>
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <div id="design3s" class="hidable">
|
Being in the main screen, it was not obvious how to:
- Find events schedule
- Type "Penguin event" in search box?
- Are events in the maps?
- What is it possible to search for using the search option?
|
|
For Buying tickets:
- The price is not displayed!
- Better way to input the date, need of "today button"
- Confusing what information is for the user or the credit card identification
|
|
- Once the transaction was finished, the user felt afraid of losing the confirmation number
- Some users didn't understand why the tickets was shown graphically and if there is any different with the confirmation number
|
|
Regarding the map feature:
- The legend for types of information in the map was confusing. Is this a list?
- ALL users expected the map to show your current location, but this will require some technology installed in the building.
- Lack of home button.
|
|
Search result layout:
- Good results in general
- Lack of home button
|
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. </div>
4. Description of the second prototype
uhfiefijwoiefj
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <a href="javascript:showhide('design6');" id="design1show">Show this prototype</a>
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <div id="design6" class="hidable">
4.1 Tasks requested to the user:
For the second round of user testing, we used the same set of tasks but including the task that was added for the last user of the first round (find information about an unknown specie). The tasks are as follows:
1) Buy 2 adult tickets and 1 kid ticket.
2) Find the Little blue penguins and go there.
3) Find the events (times-location) related to penguins today.
4) You saw a interesting red fish. You want to get information about it and find out its name. The only information you have is your current location.
4.2 Prototype functionality:
The following table presents the different screens in this prototype as well as an explanation of how to use each one.
SCREEN |
USE |
 |
AUHIUADHGVIUH |
 |
AUHIUADHGVIUH |
 |
AUHIUADHGVIUH |
 |
AUHIUADHGVIUH |
 |
AUHIUADHGVIUH |
 |
AUHIUADHGVIUH |
 |
AUHIUADHGVIUH |
 |
AUHIUADHGVIUH |
Finally, the following diagram presents the interaction between all the screens:
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. </div>
3. Second Round of Prototype Testing
3.1 User 1:
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <a href="javascript:showhide('design7');" id="design2show">Show this user test</a>
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <div id="design7" class="hidable">
User 1 - Observations:
User 3 - Usability issues:
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. </div>
3.2 User 2:
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <a href="javascript:showhide('design8');" id="design2show">Show this user test</a>
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <div id="design8" class="hidable">
User 2 - Observations:
User 3 - Usability issues:
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. </div>
3.3 User 3:
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <a href="javascript:showhide('design9');" id="design2show">Show this user test</a>
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. <div id="design9" class="hidable">
User 3 - Observations:
User 3 - Usability issues:
html: Security restricted macro is not allowed. An edit restriction is required that matches the macro authorization list. </div>