HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2015T2 Starteur User Testing 2"

From IS480
Jump to navigation Jump to search
Line 79: Line 79:
 
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:20px; border:1px solid #999" | Participant 2
 
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:20px; border:1px solid #999" | Participant 2
 
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:20px; border:1px solid #999" | Participant 3
 
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:20px; border:1px solid #999" | Participant 3
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:20px; border:1px solid #999" | Participant 4
 
 
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:20px; border:1px solid #999" | Overall Mean
 
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:20px; border:1px solid #999" | Overall Mean
 
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:30px; border:1px solid #999" | Remark
 
! style="font-family: Roboto Lt; text-align: center; bold;background: #34495e;color:#ecf0f1; width:30px; border:1px solid #999" | Remark
Line 88: Line 87:
 
| style="text-align:center" | 1
 
| style="text-align:center" | 1
 
| style="text-align:center" | 1
 
| style="text-align:center" | 1
| style="text-align:center" | 3
+
| style="text-align:center" | 1
| style="text-align:center" | 1.5
 
 
| style="text-align:center" | Nil
 
| style="text-align:center" | Nil
  
 
|-
 
|-
| style="text-align:center" | Task 2
+
| style="text-align:center" | Task 2a
| style="text-align:center" | 2
 
 
| style="text-align:center" | 1
 
| style="text-align:center" | 1
 
| style="text-align:center" | 1
 
| style="text-align:center" | 1
| style="text-align:center" | 4
 
 
| style="text-align:center" | 2
 
| style="text-align:center" | 2
 +
| style="text-align:center" | 1.33
 
| style="text-align:center" | Nil
 
| style="text-align:center" | Nil
  
 
|-
 
|-
| style="text-align:center" | Task 3
+
| style="text-align:center" | Task 2b
 
| style="text-align:center" | 1
 
| style="text-align:center" | 1
| style="text-align:center" | 2
 
| style="text-align:center" | 2
 
| style="text-align:center" | 4
 
| style="text-align:center" | 2.25
 
| style="text-align:center" | Nil
 
 
|-
 
| style="text-align:center" | Task 4
 
 
| style="text-align:center" | 1
 
| style="text-align:center" | 1
| style="text-align:center" | 2
 
 
| style="text-align:center" | 1
 
| style="text-align:center" | 1
 
| style="text-align:center" | 1
 
| style="text-align:center" | 1
| style="text-align:center" | 1.25
 
 
| style="text-align:center" | Nil
 
| style="text-align:center" | Nil
  
 
|-
 
|-
| style="text-align:center" | Task 5
+
| style="text-align:center" | Task 3
 +
| style="text-align:center" | 1
 
| style="text-align:center" | 2
 
| style="text-align:center" | 2
 
| style="text-align:center" | 2
 
| style="text-align:center" | 2
| style="text-align:center" | 1
+
| style="text-align:center" | 1.67
| style="text-align:center" | 4
 
| style="text-align:center" | 2.25
 
 
| style="text-align:center" | Nil
 
| style="text-align:center" | Nil
  
|-
 
| style="text-align:center" | Task 6
 
| style="text-align:center" | 1
 
| style="text-align:center" | 1
 
| style="text-align:center" | 2
 
| style="text-align:center" | 1
 
| style="text-align:center" | 1.25
 
| style="text-align:center" | Nil
 
  
 
|-
 
|-
| style="text-align:center" | Task 7
+
| style="text-align:center" | Task 4
| style="text-align:center" | 1
 
| style="text-align:center" | 4
 
 
| style="text-align:center" | 2
 
| style="text-align:center" | 2
| style="text-align:center" | 1
 
| style="text-align:center" | 2
 
| style="text-align:center" | Nil
 
 
|-
 
| style="text-align:center" | Task 8
 
 
| style="text-align:center" | 2
 
| style="text-align:center" | 2
 
| style="text-align:center" | 2
 
| style="text-align:center" | 2
 
| style="text-align:center" | 2
 
| style="text-align:center" | 2
| style="text-align:center" | 1
 
| style="text-align:center" | 1.75
 
 
| style="text-align:center" | Nil
 
| style="text-align:center" | Nil
 
|-
 
| style="text-align:center" | Task 9
 
| style="text-align:center" | 3
 
| style="text-align:center" | 3
 
| style="text-align:center" | 3
 
| style="text-align:center" | 2
 
| style="text-align:center" | 2.75
 
| style="text-align:center" | Don't have to go to a new page to see which co-educator is attached to batch
 
 
|-
 
|-
 
</div>
 
</div>
Line 178: Line 137:
 
|-
 
|-
 
| style="text-align:center" | 1
 
| style="text-align:center" | 1
| style="text-align:center" | Text size
+
| style="text-align:center" | Additional search functionalities
| style="text-align:center" | Layout of the pages is simple and easy to see, <br> However, the text is quite faint and the font size can be bigger. <br> Bigger font size<br> Current layout is nice but text can be bigger.<br> Bigger font size.  
+
| style="text-align:center" | It might be presumptuous but if Starteur launches and we have alot of users. It will get difficult to identify an educator or Starteur user and help them in time. So being able to search for them and pull out their account details would be good. <br> It will easier for us to be able to search for certain accounts or details  <br> Clean, simple layout.  
  
 
|-
 
|-
 
| style="text-align:center" | 2
 
| style="text-align:center" | 2
| style="text-align:center" | Phrasing
+
| style="text-align:center" | Additional analytical features
| style="text-align:center" | "Batch" is a little too definitive as teachers may only request a certain group of students to take the test. Consider changing to something less definitive and more generic.
+
| style="text-align:center" | It would be good if we have charts that state how many educators/Starteur accounts we have/increased each month. Then we can decide and use it to make business decisions. <br> I like the layout and the numbers shown but maybe more colours? <br>I need to know how much subscriptions or purchases we have and some form of visuals would be good
 
 
|-
 
| style="text-align:center" | 3
 
| style="text-align:center" | Success Messages
 
| style="text-align:center" | Application is simple to use and straightforward but I would like to know where I am at in terms of the steps in using the application. <br> I think it would be good if I can know whether some stuff I am doing is correct or not.  
 
 
 
|-
 
| style="text-align:center" | 4
 
| style="text-align:center" | Lack of information hierarchy
 
| style="text-align:center" | Everything is there on the page but I don't know where to look or what to focus on for certain stuff<br>I like the layout cause it is not confusing but it would be good if things are presented in a way that I can see certain important information.
 
 
 
|-
 
| style="text-align:center" | 5
 
| style="text-align:center" | Validation
 
| style="text-align:center" | Do you have certain password restrictions? <br> Any password limits and email verification?
 
 
 
|-
 
| style="text-align:center" | 6
 
| style="text-align:center" | Any thing you will like to see in the application?
 
| style="text-align:center" | A report for my cohort as well? It would be very insightful<br> It will be useful if I send the reminder myself. Because then I know how many days have passed since the reminder has been sent and send it again if necessary. I can control the frequency.<br> Allow me to send an email straight from this application. <br>
 
Include a report for a cohort so that I can submit it for analysis with the other Year Heads. <br>
 
 
|}
 
|}
 
</div>
 
</div>
 
  
 
===User Study Summary===
 
===User Study Summary===

Revision as of 12:41, 15 February 2016

Starteur.jpg

HOME

ABOUT US

PROJECT OVERVIEW

PROJECT MANAGEMENT

DOCUMENTATION

Use Cases Technical Diagrams Design Documents Meeting Minutes User Testings Project Documents

Venue

  • Location: Reactor ARC
  • Date: 13 Feb 2016
  • Time: 1pm

Objectives

  • Verify that functionalities built are in line with user requirements
  • Determine if the user interface is intuitive
  • Identify usability problems
  • Identify additional functionalities that user may require

Participants

  • Number of participants: 3
  • Roles of participants: Management team of Reactor Industries (Finance, Customer Service, Trainer)


Photo 2015-08-23 13-51-48.jpg insert photo of participant

Tasks

  • Each of the users was given a list of tasks to complete. Click here to download tasklist.
  • Before and after completing all the tasks, users are given a survey questionnaire to complete.

Survey Results

Collated Task Score

UAT2 results.jpg


Task Participant 1 Participant 2 Participant 3 Overall Mean Remark
Task 1 1 1 1 1 Nil
Task 2a 1 1 2 1.33 Nil
Task 2b 1 1 1 1 Nil
Task 3 1 2 2 1.67 Nil


Task 4 2 2 2 2 Nil
# Issue Collated feedback
1 Additional search functionalities It might be presumptuous but if Starteur launches and we have alot of users. It will get difficult to identify an educator or Starteur user and help them in time. So being able to search for them and pull out their account details would be good.
It will easier for us to be able to search for certain accounts or details
Clean, simple layout.
2 Additional analytical features It would be good if we have charts that state how many educators/Starteur accounts we have/increased each month. Then we can decide and use it to make business decisions.
I like the layout and the numbers shown but maybe more colours?
I need to know how much subscriptions or purchases we have and some form of visuals would be good

User Study Summary

  • Overall, users find the application easy to use, and the layout simple. intuitive to perform certain functions as it fits with other learning management systems that they have been using.
  • In general, users are satisfied with most functions, except for a few
  • User feedback for important features are fairly useful

User Study Takeaways

  • A consistency in usability for different users. Consider that different users have different capabilities in using such a system.
  • With users' feedback, we identified areas of improvement on these functions. Eg. Add or Remove a co-educator
  • Allow us to evaluate the usefulness of these features and future functions. Consideration on improvising the features and removing features that are redundant to users. Eg. Sort & Filter. Most feedback has been accounted for in our implementation plan, which will then be confirmed into subsequent development.