Difference between revisions of "IS480 Team wiki: 2012T1 Bumblebee Project Documentation User Acceptance Test"
Yosin.a.2009 (talk | contribs) |
Yosin.a.2009 (talk | contribs) |
||
| Line 34: | Line 34: | ||
| style= "background:#FBB917; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top" | | | style= "background:#FBB917; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top" | | ||
| − | The goals and objectives of usability testing: | + | '''The goals and objectives of usability testing:''' |
• Record and document general feedback and first impressions | • Record and document general feedback and first impressions | ||
| Line 44: | Line 44: | ||
• To match client expectations on the system developed. | • To match client expectations on the system developed. | ||
| − | User Testing Conclusion: | + | '''User Testing Conclusion:''' |
• Client was satisfied with the system. However, there are more to be improved in terms of the presentation and navigation of the application. | • Client was satisfied with the system. However, there are more to be improved in terms of the presentation and navigation of the application. | ||
Revision as of 10:07, 28 November 2012
 |
| Home | Project Overview | Project Documentation | Project Management | Learning and Growth |
| Diagrams | User Interface | User Manual | User Testing | Meeting Minutes | Presentations |
Contents
User Testing 1, 17 September 2012
| User Testing 1, 17 September 2012 |
|
The goals and objectives of usability testing: • Record and document general feedback and first impressions • Identify any potential concerns to address regarding application usability, presentation, and navigation. • Get feedback on the usefulness and accuracy of the functions developed. • To match client expectations on the system developed. User Testing Conclusion: • Client was satisfied with the system. However, there are more to be improved in terms of the presentation and navigation of the application. • Client, especially another participant gained better and clearer understanding on what the application delivers after testing the application. • There are critical errors on the logic/formula for staff utilization rate and staff working hours that can be further improved to increase the accuracy of the calculation. • Non-critical errors will also be solved. Click here to download our report.
|
User Testing 2, 25 October 2012
| User Testing 2, 25 October 2012 |
|
The goals and objectives of usability testing • Record and document general feedback and first impressions • Identify any potential concerns to address regarding application usability, presentation, and navigation • Get feedback on the usefulness and accuracy of the functions developed • To match client expectations on the system developed Click here to download our report
|
Heuristic Evaluation, 12-15 November 2012
| Heuristic Evaluation, 12-15 November 2012 |
|
The goals and objectives of usability testing • Record and document general feedback and first impressions • Identify any potential concerns to address regarding application usability, presentation, and navigation.
|
User Testing 3, 22 November 2012
| User Testing 3, 22 November 2012 |
|
Click here to download our report.
|
