HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T1 Bumblebee Project Documentation User Acceptance Test"

From IS480
Jump to navigation Jump to search
 
(48 intermediate revisions by 3 users not shown)
Line 25: Line 25:
  
  
 
+
===<div style="color: #ffffff; font-size:0%">User Testing 1, 17 September 2012</div>===
 
 
 
 
 
 
 
 
==<div style="color: #ffffff; font-size:0%">Objectives</div>==
 
 
{| class="wikitable" cellpadding="15"
 
{| class="wikitable" cellpadding="15"
 
|-
 
|-
| style="background:#ffffff;; color: #000000; font-weight: bold; text-indent: 2px; width: 32%; font-size:22px; text-align:lrft; border: 1px solid #ffffff" valign="top" | <b><u>User Testing 1 (17 September 2012)</u>
+
| style="background:#ffffff;; color: #000000; font-weight: bold; text-indent: 2px; width: 32%; font-size:22px; text-align:lrft; border: 1px solid #ffffff" valign="top" | <b>User Testing 1, 17 September 2012</b>
Objectives</b>
 
 
|-
 
|-
 
| style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |
 
| style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |
Line 40: 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
  
• Identify any potential concerns to address regarding application usability, presentation, and navigation.
+
• 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
  
• Get feedback on the usefulness and accuracy of the functions developed.
 
  
• To match client expectations on the system developed.
+
Click [[Media:BumblebeeUserTesting1Report.pdf‎|here]] to download our report
  
 
|-
 
|-
Line 56: Line 64:
 
|-
 
|-
 
|}
 
|}
<div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation_User_Acceptance_Test#Top|Back to Top]]</u></font></div>
 
  
==<div style="color: #ffffff; font-size:0%">Methodology</div>==
+
===<div style="color: #ffffff; font-size:0%">User Testing 2, 25 October 2012</div>===
 
{| class="wikitable" cellpadding="15"
 
{| class="wikitable" cellpadding="15"
 
|-
 
|-
| style="background:#ffffff;; color: #000000; font-weight: bold; text-indent: 2px; width: 32%; font-size:22px; text-align:lrft; border: 1px solid #ffffff" valign="top" | <b>Methodology</b>
+
| style="background:#ffffff;; color: #000000; font-weight: bold; text-indent: 2px; width: 32%; font-size:22px; text-align:lrft; border: 1px solid #ffffff" valign="top" | <b>User Testing 2, 25 October 2012</b>
 
|-
 
|-
 
| style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |
 
| style= "background:#000000; 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"  |
 
| style= "background:#FBB917; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |
===User Testing Environment===
 
  
Computer platform : Intel Pentium Processor
+
'''The goals and objectives of usability testing:'''
  
Screen resolution : 1028 x 768
+
• Record and document general feedback and first impressions
 
 
Operating System : Windows XP
 
  
Set-up required : Computer date format (English (Australia)) of d/MM/YYYY
+
• Identify any potential concerns to address regarding application usability, presentation, and navigation
  
===Participants===
+
• Get feedback on the usefulness and accuracy of the functions developed
  
The participants will attempt to complete a set of scenarios presented to them and to provide feedback regarding the usability and acceptability of the application.
+
• To match client expectations on the system developed
  
1. Kevin Choy, SATS Airline Relations Manager - Person-in-charge for this project.
 
  
2. Goh Wei Xuan, SATS Airline Relations Manager
+
'''User Testing Conclusion:'''
  
===Procedure===
+
• Client was satisfied with the system
  
====Instructions====
+
• Current result seems close and better than the actual result under manual scheduling. However, close monitor of result with client is highly needed to ensure that the result is indeed valid
  
These instructions were given to our clients:
+
• Team will consistently send the latest file to client for independent testing
  
1. Each user will be accompanied by 1 facilitator.
 
 
2. Users are encouraged to verbalize their movements, purpose, and problems.
 
 
3. Facilitators will record mistakes and questions made by users during testing.
 
 
4. To start the test, click on the file named “START.bat” found in folder named “SATS_Bumblebee_Beta_v5”.
 
 
5. All sample files needed for testing are found in:  SATS_Bumblebee_Beta_v5/data
 
 
6. Database used to store imported data is also found in ROOT folder.
 
 
7. Users are allowed to change their input(s) to verify data validity.
 
 
8. Users are to complete the tasks stated below. After completing each task, users have to answer the test questions pertaining to the specific task.
 
 
====Tasks====
 
 
These are the task descriptions given to clients:
 
 
Below are tasks for users to complete.
 
 
1. Bootstrap/import files(s)
 
 
This task is for user to import data from excel files such as Flight Schedule Departure, Flight Schedule Arrival, Staff Records, etc. into the application. The application will then use these data for simulation purpose in the later step.
 
 
2. Add staff costs
 
 
This task is to record various costs in hiring staff into the application.
 
 
3. Add uncertainties
 
 
This task is to record the mean and standard deviation of different uncertainties that will affect the initial schedule prepared by the application. Simulation period = 7 days (represents the number of days the data is to be generate).
 
 
4. Run simulation
 
 
Run simulation to start assigning staff to different job assignments.
 
 
5. View staff schedule (in Gantt Chart)
 
 
This allows user to view and compare between a staff’s planned and actual working time.
 
 
6. Add airline requirements
 
 
Airlines have several different requirements on number of CSA and CSO needed.
 
 
This task is to record the individual requirements into the database. The input data will be used for simulation purpose in the later step.
 
 
7. Generate result
 
 
This task is to view the result generated in PDF format.
 
 
===Team Roles===
 
 
Overall in-charge (Yosin Anggusti)
 
 
- Provide training overview prior to usability testing
 
 
- Defines usability and purpose of usability testing to participants
 
 
Facilitators (Glorya Marie, Suriyanti)
 
 
- Evaluate on the application and user interaction with the application, rather than evaluating on the user
 
 
- Facilitator will observe and enter user behavior and user comments.
 
 
- Responds to participant’s requests for assistance
 
 
Test Observers (Yosin Anggusti)
 
 
- Silent observers
 
 
- Assists the data logger in identifying problems, concerns, coding bugs, and procedural errors
 
  
 +
Click [[Media:BumblebeeUserTesting2Report.pdf‎|here]] to download our report
  
 
|-
 
|-
Line 171: Line 102:
 
|-
 
|-
 
|}
 
|}
<div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation_User_Acceptance_Test#Top|Back to Top]]</u></font></div>
 
  
==<div style="color: #ffffff; font-size:0%">Reporting Results</div>==
+
===<div style="color: #ffffff; font-size:0%">Heuristic Evaluation, 12-15 November 2012</div>===
 
{| class="wikitable" cellpadding="15"
 
{| class="wikitable" cellpadding="15"
 
|-
 
|-
| style="background:#ffffff;; color: #000000; font-weight: bold; text-indent: 2px; width: 32%; font-size:22px; text-align:lrft; border: 1px solid #ffffff" valign="top" | <b>Usability Metrics</b>
+
| style="background:#ffffff;; color: #000000; font-weight: bold; text-indent: 2px; width: 32%; font-size:22px; text-align:lrft; border: 1px solid #ffffff" valign="top" | <b>Heuristic Evaluation, 12-15 November 2012</b>
 
|-
 
|-
 
| style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |
 
| style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |
Line 182: Line 112:
 
| 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"  |
  
===Critical Errors===
+
'''The goals and objectives of usability testing:'''
Critical errors are deviations of results from the actual result. These errors will cause the task to fail. Facilitators are to records there critical errors.
 
  
===Non-Critical Errors===
+
• Record and document general feedback and first impressions
Non-critical errors are usually procedural, in which the participant does not complete a task in the most optimal means (e.g. excessive steps, initially selecting the wrong function, attempting to edit an un-editable field).
 
These errors may not be detected by the user himself. Facilitators have to record these errors independently.
 
  
===Scenario Completion Time===
+
• Identify any potential concerns to address regarding application usability, presentation, and navigation
The time to complete each scenario, not including subjective evaluation durations, will be recorded.
 
  
  
|-
+
'''Heuristic Evaluation Conclusion:'''
  
|-
+
• Users have no problem in navigating around the system in general
| style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |
 
|-
 
|}
 
<div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation_User_Acceptance_Test#Top|Back to Top]]</u></font></div>
 
  
==<div style="color: #ffffff; font-size:0%">Reporting Results</div>==
+
• There is a need for more instructions from pages to pages
{| class="wikitable" cellpadding="15"
 
|-
 
| style="background:#ffffff;; color: #000000; font-weight: bold; text-indent: 2px; width: 32%; font-size:22px; text-align:lrft; border: 1px solid #ffffff" valign="top" | <b>Reporting Results</b>
 
|-
 
| style= "background:#000000; 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"  |
 
 
 
Task 1: Bootstrap/ Import File(s)
 
{| class="wikitable" cellpadding="15"
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 50%; font-size: 13px;" valign="top"  | <b>Bootstrap/import file(s)</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 25%; font-size: 13px;" valign="top"  | <b>Concern</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 25%; font-size: 13px;" valign="top"  | <b>Recommendations</b>
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 50%; font-size: 13px;" valign="top"  | Critical Errors
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | --
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | --
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 50%; font-size: 13px;" valign="top"  | Non-Critical Errors
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | - Window to get bootstrap data blocked the “Bootstrap Data” page.
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | - @Homepage: give system name instead of “Welcome..”
 
- “Bootstrap”change it to: “import”
 
- Texts are not cleared after bootstrap is started
 
- 1% progress bar is not implemented
 
- Have everything in process view (e.g. Breadcrumb)
 
- While importing, disable all browse  and bootstrap buttons.
 
 
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 50%; font-size: 13px;" valign="top"  | Scenario Completion Time
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | 4 minutes
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | --
 
|-
 
|}
 
  
  
 +
Click [[Media:BumblebeeHeuristicEvaluationReport.pdf‎|here]] to download our report
  
 
|-
 
|-
Line 245: Line 134:
 
|-
 
|-
 
|}
 
|}
<div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation_User_Acceptance_Test#Top|Back to Top]]</u></font></div>
 
  
==<div style="color: #ffffff; font-size:0%">Subjective Evaluations</div>==
+
===<div style="color: #ffffff; font-size:0%">User Testing 3, 22 November 2012</div>===
 
{| class="wikitable" cellpadding="15"
 
{| class="wikitable" cellpadding="15"
 
|-
 
|-
| style="background:#ffffff;; color: #000000; font-weight: bold; text-indent: 2px; width: 32%; font-size:22px; text-align:lrft; border: 1px solid #ffffff" valign="top" | <b>Subjective Evaluations</b>
+
| style="background:#ffffff;; color: #000000; font-weight: bold; text-indent: 2px; width: 32%; font-size:22px; text-align:lrft; border: 1px solid #ffffff" valign="top" | <b>User Testing 3, 22 November 2012</b>
 
|-
 
|-
 
| style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |
 
| style= "background:#000000; 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"  |
 
| style= "background:#FBB917; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |
Subjective evaluations regarding ease of use and satisfaction will be collected via questionnaires. There are 2 participants, thus results from both participants will be combined or averaged whenever it is necessary.
 
  
Each of the two participants contributes 50% to their answers. Not all sections are answered, thus not all questions have a total of 100% weight.
+
'''The goals and objectives of usability testing:'''
  
{| class="wikitable" cellpadding="15"
+
• Record and document general feedback and first impressions
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 50%; font-size: 13px;" valign="top"  | <b>Navigation Impression</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 25%; font-size: 13px;" valign="top"  | <b>Agree</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 25%; font-size: 13px;" valign="top"  | <b>Neutral</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 25%; font-size: 13px;" valign="top"  | <b>Disagree</b>
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 50%; font-size: 13px;" valign="top"  | It is easy to find my way around the system
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | --
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | --
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | 50%
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 50%; font-size: 13px;" valign="top"  | It is easy to remember where to find things
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | --
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | 50%
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | --
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 50%; font-size: 13px;" valign="top"  | The system is well-suited to first-time users
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | --
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | --
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | 50%
 
|-
 
|}
 
Comment(s):
 
 
 
-‘Back’ button at simulation is missing
 
 
 
- Have a flow. Not sure which button to select?
 
 
 
- Need more instructions for first time users.
 
 
 
{| class="wikitable" cellpadding="15"
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 50%; font-size: 13px;" valign="top"  | <b>Look and Feel</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 25%; font-size: 13px;" valign="top"  | <b>Agree</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 25%; font-size: 13px;" valign="top"  | <b>Neutral</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 25%; font-size: 13px;" valign="top"  | <b>Disagree</b>
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 50%; font-size: 13px;" valign="top"  | The interface design is simple
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | 100%
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | --
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | --
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 50%; font-size: 13px;" valign="top"  | The size and layout of the application is optimal
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | --
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | 100%
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | --
 
|-
 
|}
 
 
 
{| class="wikitable" cellpadding="15"
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 50%; font-size: 13px;" valign="top"  | <b>Functions</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 25%; font-size: 13px;" valign="top"  | <b>Agree</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 25%; font-size: 13px;" valign="top"  | <b>Neutral</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 25%; font-size: 13px;" valign="top"  | <b>Disagree</b>
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 50%; font-size: 13px;" valign="top"  | Each function has a clear purpose
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | 50%
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | 50%
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 25%;font-size: 13px;" valign="top"  | --
 
|-
 
|}
 
 
 
Comment(s):
 
 
 
- Must be more explicit on description
 
 
 
{| class="wikitable" cellpadding="15"
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 5%; font-size: 13px;" valign="top"  | <b>Bootstrap/import file(s)</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 5%; font-size: 13px;" valign="top"  | <b>Agree</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 40%; font-size: 13px;" valign="top"  | <b>Neutral</b>
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 5%; font-size: 13px;" valign="top"  | <b>Disagree</b>
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 5%; font-size: 13px;" valign="top"  | The function works well
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 5%;font-size: 13px;" valign="top"  | 100%
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 40%;font-size: 13px;" valign="top"  | --
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 40%;font-size: 13px;" valign="top"  | --
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 5%; font-size: 13px;" valign="top"  | The function takes reasonable amount of time
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 5%;font-size: 13px;" valign="top"  | 100%
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 40%;font-size: 13px;" valign="top"  | --
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 40%;font-size: 13px;" valign="top"  | --
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 5%; font-size: 13px;" valign="top"  | The function provides right amount of information
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 5%;font-size: 13px;" valign="top"  | 100%
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 40%;font-size: 13px;" valign="top"  | --
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 40%;font-size: 13px;" valign="top"  | --
 
|-
 
|-
 
| style= "background:#000000; color: #ffffff; padding: 10px 4px 0 15px; width: 5%; font-size: 13px;" valign="top"  | The result/outcome of the function is right
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 5%;font-size: 13px;" valign="top"  | 100%
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 40%;font-size: 13px;" valign="top"  | --
 
| style= "background:#ffffff; color: #000000; padding: 10px 4px 0 15px; width: 40%;font-size: 13px;" valign="top"  | --
 
|-
 
|}
 
  
Comment(s):
+
• Identify any potential concerns to address regarding application usability, presentation, and navigation
  
- “Bootstrap” should be changed to “import”
+
• Get feedback on the usefulness and accuracy of the functions developed
  
- Disable ‘browse’ button when bootstrapping
+
• To match client expectations on the system developed
  
  
 +
'''User Testing Conclusion:'''
  
|-
+
• Client was satisfied with the system.
| style= "background:#000000; color: #000000; padding: 10px 4px 0 15px; font-size: 13px;" valign="top"  |
 
|-
 
|}
 
<div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation_User_Acceptance_Test#Top|Back to Top]]</u></font></div>
 
 
 
==<div style="color: #ffffff; font-size:0%">Reporting Conclusions</div>==
 
{| class="wikitable" cellpadding="15"
 
|-
 
| style="background:#ffffff;; color: #000000; font-weight: bold; text-indent: 2px; width: 32%; font-size:22px; text-align:lrft; border: 1px solid #ffffff" valign="top" | <b>Reporting Conclusions</b>
 
|-
 
| style= "background:#000000; 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"  |
 
  
Client was satisfied with the system. However, there are more to be improved in terms of the presentation and navigation of the application.
+
Results are reasonable
  
Client, especially another participant gained better and clearer understanding on what the application delivers after testing the application.
+
A video as user manual will be done to aid user in using the software
  
• 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 [[Media:BumblebeeUserTesting2Report.pdf‎|here]] to download our report
 
|-
 
|-
  
Line 396: Line 172:
 
|-
 
|-
 
|}
 
|}
<div style = "text-align:right;"><font ="color:#000000; size:"12px;"><u>[[IS480_Team_wiki:_2012T1_Bumblebee_Project_Documentation_User_Acceptance_Test#Top|Back to Top]]</u></font></div>
 

Latest revision as of 11:57, 4 December 2012

Bao.png
Home Project Overview Project Documentation Project Management Learning and Growth
Diagrams User Interface User Manual User Testing Meeting Minutes Presentations


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


User Testing Conclusion:

• Client was satisfied with the system

• Current result seems close and better than the actual result under manual scheduling. However, close monitor of result with client is highly needed to ensure that the result is indeed valid

• Team will consistently send the latest file to client for independent testing


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


Heuristic Evaluation Conclusion:

• Users have no problem in navigating around the system in general

• There is a need for more instructions from pages to pages


Click here to download our report

User Testing 3, 22 November 2012

User Testing 3, 22 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

• 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.

• Results are reasonable

• A video as user manual will be done to aid user in using the software


Click here to download our report