IS480 Team wiki: 2013T2 Tappers/Documentation/User Testing
Home | The Team | Project Overview | Project Management | Project Documentation | Learning Outcomes |
Design & Prototype | Diagrams | User Testing | Resources | Meeting Minutes |
Please see the full document here: Tappers' Test Plan
User Testing 1
Date : 28 January
Venue: Lien Centre for Social Innovation, SMU Admin Building, Level 9
Users: Jenny HUQ, Shirley PONG, Jared THAM, Mumtaz
User Testing 1 Execution Plan : UT1 Execution Plan
User Testing Test Document: Click Here
User Testing Post Test Questionaire: Click Here
Consolidated User Testing Document Feedback
Consolidated Questionaire Feedback
Contents
Heuristics and Severity Ratings
Heuristics | Severity Ratings |
---|---|
1. Visibility of system status 2. Match between system and the real world 3. User control and freedom 4. Consistency and standards 5. Error prevention 6. Recognition rather than recall 7. Flexibility and efficiency of use 8. Aesthetic and minimalist design 9. Help users recognize, diagnose, and recover from errors 10. Help and documentation Not related to any heuristic |
0 = Not a real usability problem 1 = Cosmetic problem only 2 = Minor usability problem 3 = Major usability problem 4 = Usability catastrophe |
Problem 1
Name | Edit Button is difficult to find | ||
Sources | Mumtaz, Jenny, Shirley | ||
Heuristic | 7. Flexibility and efficiency of use | Severity | 1 = Cosmetic problem only |
Description:
| |||
Proposed Solution:
|
Problem 2
Name | Add comment box to Event registration form | ||
Sources | Mumtaz | ||
Heuristic | 7. Flexibility and efficiency of use | Severity | 1 = Cosmetic problem only |
Description:
| |||
Proposed Solution:
|
Problem 3
Name | Rename the button “Add contacts” to "Invite Contact" for an event | ||
Sources | Mumtaz, Jenny | ||
Heuristic | 7. Flexibility and efficiency of use | Severity | 1 = Cosmetic problem only |
Description:
| |||
Proposed Solution:
|
Problem 4
Name | 4. Inconsistent navigation bar | ||
Sources | Mumtaz | ||
Heuristic | 7. Flexibility and efficiency of use | Severity | 1 = Cosmetic problem only |
Description:
| |||
Proposed Solution:
|
Problem 5
Name | Search column is not visible | ||
Sources | Jenny | ||
Heuristic | 7. Flexibility and efficiency of use | Severity | 1 = Cosmetic problem only |
Description:
| |||
Proposed Solution:
|
Problem 6
Name | Create event does not work | ||
Sources | Jenny | ||
Heuristic | 1. Visibility of system status | Severity | 3- Major Usability Problem |
Description:
| |||
Proposed Solution:
|
Problem 7
Name | Add a confirmation popup before deleting an event | ||
Sources | Mumtaz, Jenny | ||
Heuristic | 7. Flexibility and efficiency of use | Severity | 1 = Cosmetic problem only |
Description:
| |||
Proposed Solution:
|
Problem 8
Name | Spelling mistakes | ||
Sources | Jenny | ||
Heuristic | 7. Flexibility and efficiency of use | Severity | 1 = Cosmetic problem only |
Description:
| |||
Proposed Solution:
|
Problem 9
Name | 7. Add a confirmation popup before deleting an event | ||
Sources | Mumtaz, Jenny | ||
Heuristic | 7. Flexibility and efficiency of use | Severity | 1 = Cosmetic problem only |
Description:
| |||
Proposed Solution:
|
Problem 10
Name | 7. Add a confirmation popup before deleting an event | ||
Sources | Mumtaz, Jenny | ||
Heuristic | 7. Flexibility and efficiency of use | Severity | 1 = Cosmetic problem only |
Description:
| |||
Proposed Solution:
|