IS480 Team wiki: 2016T1 Folium User Testing UT2
Contents
Sponsor User Test 2
Venue: SIS Meeting Room 4.7
Date: 10 Aug 2016, Wednesday
Time: 7.00pm
Duration: 2 hrs
Number of Participant(s): 2
- Prof MOK Heng Ngee (Sponsor)
- Prof Hady Wirawan LAUW (Sponsor)
Objectives
- Gathering sponsors’ feedback on whether existing functions’ design align with their expectations.
- Identifying potential risks & usability issues and structuring mitigation actions accordingly.
Scope for Sponsor User Test 2
- Queue Management
- Grader Independent of Tomcat
- Debug Checking
- Shutdown Server
- Allow user to submit a Zip or Single File
- Central Repository
Features Tested and Results
S/N | Tested Feature | Follow-up Actions | In-Charge |
---|---|---|---|
I. | Queue Management
Let administrator and users see Queue contents, delete items in Queue (admin can delete anything, users can only delete their own submission). Currently, all that is visible is the number of items in the Queue when a user logs in. No one knows what is in the Queue, and whose items are these. A user who had submitted something in the Queue also cannot resubmit a new item even after he has come up with a better solution. It will be good if he can view the Queue and delete his previous submission even before it gets graded. |
|
|
II. | Grader Independent of Tomcat
Make all graders independent of Tomcat - each grader machine should be a command line Java app that connects to the DB. |
|
|
III. | Debug Testing
1. If a particular submission has “put”/ “print” statements, the results won’t appear. |
1. Need to do more research on the heap space error. |
1. Zhang Qian |
IV. | Shutdown Server
Allow admin to temporarily hut down website and not allow further submissions. This can be time-controlled or manual. |
|
|
V. | Allow user to submit a Zip or Single File
Allow users to choose individual files to submit for each question. Grader will only grade submitted solutions and not alter the scores for unsubmitted questions. |
|
|
VI. | Central Repository
Central repository for all submission for each question. |
|
|
General Feedback
- System design should align with that of common platforms used by students like, file submission function of e-learn, so as to ensure coherent user experience with similar platforms.
- System should ensure coherent performance in different environmental settings like, different browsers such that the system may be deployed to suit the needs of large population.
- Should have taken into consideration of extreme situations like, server crash and start planning mitigation actions accordingly.