Difference between revisions of "IS480 Team wiki: 2013T2 Zora Testing"
(6 intermediate revisions by the same user not shown) | |||
Line 55: | Line 55: | ||
==Test Outcome== | ==Test Outcome== | ||
− | + | ===Heuristic Evaluation 1=== | |
<b>Testers are the expert evaluators. They used the following heuristic and severity ratings, as shown below, to evaluate our application</b><br> | <b>Testers are the expert evaluators. They used the following heuristic and severity ratings, as shown below, to evaluate our application</b><br> | ||
{| class="wikitable centered" | {| class="wikitable centered" | ||
Line 109: | Line 109: | ||
[[Image:Zora_Testing20.JPG |thumb|500px|left]] | [[Image:Zora_Testing20.JPG |thumb|500px|left]] | ||
<br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br> | <br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br><br> | ||
− | + | ||
+ | ===User Test 1=== | ||
<b>Steps taken to conduct user testing 1</b> | <b>Steps taken to conduct user testing 1</b> | ||
<br> | <br> | ||
Line 423: | Line 424: | ||
|} | |} | ||
− | + | ===User Test 2=== | |
<b>Results obtained from the testing conducted</b> | <b>Results obtained from the testing conducted</b> | ||
Line 1,276: | Line 1,277: | ||
|} | |} | ||
− | + | ===User Test 3=== | |
− | In this user test, we did the testing on 9 participants, of which 5 participants are the same person from user test 2. This is so that we are able to do comparison between the qualitative and quantitative results gathered from user test 2 with the results that we gathered in this user test 3. Due to the space constraints, we will be showing the results gathered from the 4 new participants. If you want to view more results from user test 3, please click on this -> | + | In this user test, we did the testing on 9 participants, of which 5 participants are the same person from user test 2. This is so that we are able to do comparison between the qualitative and quantitative results gathered from user test 2 with the results that we gathered in this user test 3. Due to the space constraints, we will be showing the results gathered from the 4 new participants. If you want to view more results from user test 3, please click on this -> [[Media:User Test 3 Analysis.pdf|<font color="#069" face="">''' |
+ | View Full Analysis. '''</font>]] | ||
<b>Results obtained from the testing conducted</b> | <b>Results obtained from the testing conducted</b> | ||
Line 1,298: | Line 1,300: | ||
|- | |- | ||
− | ! colspan=" | + | ! colspan="5" style="background: #A9F5E1;" | General Data |
|- | |- | ||
Line 1,324: | Line 1,326: | ||
|- | |- | ||
|Browser | |Browser | ||
− | |||
|Google Chrome | |Google Chrome | ||
|Google Chrome | |Google Chrome | ||
Line 1,679: | Line 1,680: | ||
|} | |} | ||
+ | <h3>Response Plan (Implement)</h3> | ||
{| class="wikitable centered" width="95%" | {| class="wikitable centered" width="95%" | ||
− | !style = "width: | + | !style = "width: 10%; background:#66CCCC; color:black;"|'''S/N''' |
− | !style = "width: | + | !style = "width: 22%; background:#66CCCC; color:black;"|'''Functionality''' |
− | !style = "width: | + | !style = "width: 22%; background:#66CCCC; color:black;"|'''Feedback''' |
− | !style = "width: | + | !style = "width: 23%; background:#66CCCC; color:black;"|'''Proposed Solution''' |
− | !style = "width: | + | !style = "width: 23%; background:#66CCCC; color:black;"|'''Proposed Decision''' |
− | !style = " | + | |
+ | |- | ||
+ | ! colspan="5" style="background: #A9F5E1;" | Claim | ||
+ | |- | ||
|- | |- | ||
− | | | + | |1 |
− | | | + | |Submit Claim |
− | + | |Tedious to record receipt numbers of the claim receipts by HR | |
− | + | |Have an addition field "Receipt No." for employee to key in their own receipt number and HR will just validate instead of having to input it herself | |
− | + | |Implement | |
− | | | ||
− | |||
− | | | ||
− | |||
− | |||
− | |||
− | | | ||
− | |||
|- | |- | ||
− | | | + | |2 |
− | | | + | |Validate Claim |
− | + | |Did not know need to update the edited amount before continuing to validate the claim | |
− | | | + | |To include a "message" whenever the edit button is click to remind the user that update button must be hit before the changes can be made |
− | + | |Implement | |
− | |||
− | |||
− | |||
− | | | ||
− | |||
− | | | ||
− | |||
|- | |- | ||
− | | | + | |3 |
− | | | + | |Approve/Reject Claim |
− | + | |Admin accept/reject the status not obvious | |
− | | | + | |Make it bigger and more striking colour |
− | + | |Implement | |
− | | | + | |
− | + | |- | |
− | | | + | |4 |
− | + | |Edit Payment Method | |
− | | | + | |Have a back button to generate claimslip |
− | + | |Implement "Go to Generate Claimslip" button below the edit payment method page | |
+ | |Implement | ||
|- | |- | ||
− | | | + | |5 |
− | | | + | |Generate Claimslip |
− | + | |No need claimslip for employee | |
− | | | + | |Take out the employee's copy of claimslip in the PDF generated |
− | + | |Implement | |
− | | | ||
− | |||
− | |||
− | |||
− | |||
− | | | ||
− | |||
|- | |- | ||
− | | | + | |6 |
− | | | + | |Generate Claimslip |
− | + | |Make the slip bigger | |
− | | | + | |Make the slip bigger |
− | + | |Implement | |
− | | | + | |
− | + | |- | |
− | | | + | |7 |
− | + | |Generate Claimslip | |
− | + | |More space for signature | |
− | | | + | |Spread the claim slip to have more space and include a date space to input date |
− | + | |Implement | |
+ | |||
+ | |- | ||
+ | ! colspan="5" style="background: #A9F5E1;" | Leave | ||
+ | |- | ||
|- | |- | ||
− | | | + | |1 |
− | | | + | |Record Leave |
− | + | |Not obvious that employee's name is able to be selected by keying the alphabet | |
− | | | + | |Enable filtering for user's to type employee's name |
− | + | |Implement | |
− | | | + | |
− | + | |- | |
− | * | + | |2 |
− | + | |Emailing for all Leave | |
− | | | + | |Leave approval emails did not CC HR personnel |
− | + | |CC HR personnel for all leave emails | |
+ | |Implement | ||
+ | |||
+ | |- | ||
+ | |3 | ||
+ | |Approve/Reject Leave | ||
+ | |Never state day duration in email (e.g. half day) | ||
+ | |State day duration of leave taken in email | ||
+ | |Implement | ||
+ | |||
+ | |- | ||
+ | ! colspan="5" style="background: #A9F5E1;" | Remuneration | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |1 | ||
+ | |Input worker timesheet | ||
+ | |Full name of workers should be shown for worker input timesheet page | ||
+ | |Insert full name of workers | ||
+ | |Implement | ||
+ | |||
+ | |- | ||
+ | ! colspan="5" style="background: #A9F5E1;" | Performance & Appraisal | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |1 | ||
+ | |View full appraisal | ||
+ | |Text on "View Appraisal" button is not specific | ||
+ | |Change Button Text to "View Full Appraisal" | ||
+ | |Implement | ||
+ | |||
+ | |- | ||
+ | |2 | ||
+ | |View full appraisal | ||
+ | |Scores displayed are not meaningful to the user | ||
+ | |Display of Remuneration Scores- show total (e.g. 100/100) | ||
+ | |Implement | ||
+ | |||
+ | |- | ||
+ | ! colspan="5" style="background: #A9F5E1;" | Training & Development | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |1 | ||
+ | |Approve/Reject Proposed Training | ||
+ | |UI Changes for select the training to be approve/reject. Accept / Reject button unclear, user wasn't sure she needs to click the button to proceed | ||
+ | |Change the name of the button | ||
+ | |Implement | ||
+ | |||
+ | |- | ||
+ | |2 | ||
+ | |Approve/Reject Proposed Training | ||
+ | |UI Changes for the page that they input the training details. Back button not standardize. No need write "default". Venue nv put "*". Instead of add session, it should be add another training session. Different form of writing time (e.g. 9am vs 0900. Course duration give dropdown for hrs/mins | ||
+ | |Standardize back button. Remove the default wording. Venue is a required. Change value for the button for adding training session. Put the indication that is a 24 hour (so accept numbers only). A dropdown box that have the hr/mins/day/month/year for course duration | ||
+ | |Implement | ||
+ | |||
+ | |- | ||
+ | |3 | ||
+ | |Propose Training | ||
+ | |Need to check if the employee have or didn't have any people under him/her. Nomination of employee | ||
+ | |Do a check if there is no employee under him, it will prompt him a message | ||
+ | |Implement | ||
+ | |||
+ | |- | ||
+ | |4 | ||
+ | |Manage External Training | ||
+ | |Training Status from Completed change to Course Completed | ||
+ | |Change from completed to Course Completed | ||
+ | |Implement | ||
+ | |||
+ | |- | ||
+ | ! colspan="5" style="background: #A9F5E1;" | System Administration | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |1 | ||
+ | |Manage Employee | ||
+ | |Adding the department dropdown list | ||
+ | |Add a table in db + and add a dropdown list | ||
+ | |Implement | ||
+ | |||
+ | |- | ||
+ | ! colspan="5" style="background: #A9F5E1;" | Navigation | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |1 | ||
+ | |General | ||
+ | |Font size could be larger | ||
+ | |Increase Font Size | ||
+ | |Implement | ||
+ | |- | ||
+ | |} | ||
+ | |||
+ | {| cellpadding="0" style="margin: 1em auto 1em auto;" "height: 317px" width="750px" | ||
+ | ! scope="col" width="200" bgcolor="#a7b1aa"| | ||
+ | ! scope="col" width="550" bgcolor="#a7b1aa"|<font color="white">Changes made from User Test 3 Feedbacks</font> | ||
+ | |- align="left" | ||
+ | |bgcolor="#cedad1"|Claims | ||
+ | |bgcolor="#cedad1"| | ||
+ | <b>Before</b> [[Image:Zora UT3 CBefore.JPG|550|center]] | ||
+ | <br/> | ||
+ | <b>After</b> [[Image:Zora UT3 CAfter.JPG|550|center]] | ||
+ | | | ||
+ | |- align="left" | ||
+ | |bgcolor="#cedad1"|Leave | ||
+ | |bgcolor="#cedad1"| | ||
+ | <b>Before</b> [[Image:Zora UT3 LBefore.JPG|550|center]] | ||
+ | <br/> | ||
+ | <b>After</b> [[Image:Zora UT3 LAfter.JPG|550|center]] | ||
| | | | ||
− | *N | + | |- align="left" |
+ | |bgcolor="#cedad1"|Training & Development | ||
+ | |bgcolor="#cedad1"| | ||
+ | <b>Before</b> [[Image:Zora UT3 TDBefore.JPG|550|center]] | ||
+ | <br/> | ||
+ | <b>After</b> [[Image:Zora UT3 TDAfter.JPG|550|center]] | ||
+ | | | ||
+ | |} | ||
+ | |||
+ | {| cellpadding="0" style="margin: 1em auto 1em auto;" "height: 317px" width="750px" | ||
+ | ! scope="col" width="200" bgcolor="#a7b1aa"| | ||
+ | ! scope="col" width="550" bgcolor="#a7b1aa"|<font color="white">Quantitative Feedback - User Test 2 versus User Test 3</font> | ||
+ | |- align="left" | ||
+ | |bgcolor="#cedad1"|Ease of Use | ||
+ | |bgcolor="#cedad1"| | ||
+ | [[Image:Zora_Ease_of_use_analysis.png|400px|center]] | ||
+ | <br/> | ||
+ | | | ||
+ | |- align="left" | ||
+ | |bgcolor="#cedad1"|Overall Layout | ||
+ | |bgcolor="#cedad1"| | ||
+ | [[Image:Zora_overall_layout_analysis.png|400px|center]] | ||
+ | <br/> | ||
+ | | | ||
+ | |- align="left" | ||
+ | |bgcolor="#cedad1"|Analysis for the same 5 participants from user test 2 | ||
+ | |bgcolor="#cedad1"| | ||
+ | This is the analysis done from user test 2: | ||
+ | [[Image:Zora_UT3_Before_Analysis.png|500px|center]] | ||
+ | Reasons for the time taken: | ||
+ | *Validate Submitted Claim - Most users are not able to locate the "view" claim receipt link | ||
+ | *Edit Payment Method - Confirmation message was not display thus user did not know the payment method had been updated | ||
+ | *Apply Other Leave - Most users was unsure how to upload 2 files as no instruction was stated hence a huge amount of time was spent figuring it out | ||
+ | <br/> | ||
+ | This is the analysis done for user test 3: | ||
+ | [[Image:Zora_UT3_After_Analysis.png|500px|center]] | ||
+ | Reasons for changes in timing: | ||
+ | *Changes that we made and improved on the application was useful | ||
+ | *Live Deployment + user interacting with the system before enables them to familiar with the system | ||
+ | | | ||
+ | |} | ||
+ | |||
+ | <h3>Response Plan (Not Implementing)</h3> | ||
+ | {| class="wikitable centered" width="95%" | ||
+ | !style = "width: 10%; background:#66CCCC; color:black;"|'''S/N''' | ||
+ | !style = "width: 22%; background:#66CCCC; color:black;"|'''Functionality''' | ||
+ | !style = "width: 22%; background:#66CCCC; color:black;"|'''Feedback''' | ||
+ | !style = "width: 23%; background:#66CCCC; color:black;"|'''Reason for Not Implementing''' | ||
+ | !style = "width: 23%; background:#66CCCC; color:black;"|'''Proposed Decision''' | ||
+ | |||
+ | |- | ||
+ | ! colspan="5" style="background: #A9F5E1;" | Leave | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |1 | ||
+ | |Record medical leave | ||
+ | |Did not check for duplicate medical series no | ||
+ | |There is a possibility that 2 person can have the same medical series no. Hence, this will not be checked | ||
+ | |Not Implementing | ||
+ | |||
+ | |- | ||
+ | ! colspan="5" style="background: #A9F5E1;" | Remuneration | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |1 | ||
+ | |Worker payslip | ||
+ | |Timesheet to include dinner breakdown (3h x 2) instead of giving the total ending sum | ||
+ | |Dinner is allocated $3 for each dinner, if necessary. The payslip in the system is mirroring the current payslip they are using | ||
+ | |Not Implementing | ||
+ | |||
+ | |- | ||
+ | |2 | ||
+ | |Input worker timesheet | ||
+ | |User tend to miss out the days but will notice when see days | ||
+ | |The timesheet in the system is mirroring the current worker timesheet they used. Others may not be familiar but the HR personnel who is in charged of inputting the timesheet will be familiar if it is the same format as the one she is using | ||
+ | |Not Implementing | ||
+ | |||
+ | |- | ||
+ | ! colspan="5" style="background: #A9F5E1;" | Performance & Appraisal | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |1 | ||
+ | |Create Employee Appraisal | ||
+ | |Radio button too small. Cannot click properly | ||
+ | |Radio buttons are controlled by system and browser. Customization of radio buttons would not enable usage on mobile devices | ||
+ | |Not Implementing | ||
+ | |||
+ | |- | ||
+ | ! colspan="5" style="background: #A9F5E1;" | Training & Development | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |1 | ||
+ | |Manage External Training | ||
+ | |Suggest user can type "UOB" for cheque no. (so allow text and no.) | ||
+ | |Cheque number got nothing to do with the Bank name | ||
+ | |Not Implementing | ||
+ | |||
+ | |- | ||
+ | ! colspan="5" style="background: #A9F5E1;" | System Administration | ||
+ | |- | ||
+ | |||
+ | |- | ||
+ | |1 | ||
+ | |Manage Employee | ||
+ | |Date Cannot go back to earlier than 2014. Wage Type, Hourly, Edit button on the top, cause too much to scroll down. | ||
+ | |The requirement that we had agreed on earlier was to either put in daily wage or monthly wage | ||
+ | |Not Implementing | ||
|- | |- | ||
|} | |} |
Latest revision as of 01:16, 13 April 2014
Home | Project Overview | Project Management | Documentation | |
---|---|---|---|---|
Contents
Test Methodology
Test Plan
Test Cases
Click here to view Login/Logout Test Case file.
Click here to view Remuneration Test Case file.
Click here to view Claim Test Case file.
Click here to view Leave Test Case file.
Click here to view Training & Development Test Case file.
Click here to view Performance Management & Appraisal Test Case file.
Click here to view Administration Test Case file.
Test Outcome
Heuristic Evaluation 1
Testers are the expert evaluators. They used the following heuristic and severity ratings, as shown below, to evaluate our application
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 = I don't agree that this is a usability problem 1 = Cosmetic problem only 2 = Minor usability problem 3 = Major usability problem 4 = Usability catastrophe |
Images taken during the evaluation
Results obtained from the evaluation conducted
User Test 1
Steps taken to conduct user testing 1
Post-Test
Identify:
- Goals of the test
- Scope of the test
- Participant Profile
Decides on:
- Testing set up (venue, time etc.)
Prepare:
- Testing items and documents
Recruit Testers
- Testers to read the study script
During-Test
- Give user informed form to testers
- Give task instructions to testers
- Give interview form to testers
- Observe and fill up Observation Form
- Give Questionnaire to testers to fill up while testing
Post-Test
- Consolidate Feedbacks
- Analyze Results
- Maintain a Response Plan
- Implement feedback in UT1 and test again in upcoming UT2
Results obtained from the testing conducted The following table shows the summary results for quantitative data analysis in terms of the number of time taken for various functions, clicks, bugs and question asked:
Category | Pilot Participant | Participant 1 | Participant 2 | Participant 3 |
---|---|---|---|---|
Navigation/Login/Overall look |
|
|
|
|
Remuneration |
|
|
|
|
Claims |
|
|
|
|
Leave |
|
|
|
|
User Test 2
Results obtained from the testing conducted The following table shows the summary results for quantitative data analysis in terms of the number of time taken for various functions, clicks, bugs and question asked:
Category | Pilot Participant | Participant 1 | Participant 2 | Participant 3 | Participant 4 |
---|---|---|---|---|---|
Navigation/Login/Overall look |
|
|
|
|
|
Claim |
|
|
|
|
|
Leave |
|
|
|
|
|
Remuneration |
|
|
|
|
|
Performance & Appraisal |
|
|
|
|
|
System Administration |
|
|
|
|
|
Response Plan (Implement)
S/N | Functionality | Feedback | Proposed Solution | Proposed Decision |
---|---|---|---|---|
Claim | ||||
1 | Submit Claim | User tend to click "Add Claim" instead of "Submit Claim" | Will shift the "Add Claim" button to somewhere else" | Implement |
2 | validate Claim & Approve/Reject Claim | User cannot find where to view the claim receipt | Make the "view" link bigger and more distinct | Implement |
Leave | ||||
1 | Apply Leave | User is unsure of how to upload more than 1 files while applying for leave that require supporting documents | Have a short instruction before the upload file field (i.e. Hold down CTRL button to select multiple options) | Implement |
2 | Apply Leave | User is unsure of what to put in the "Date To" field to apply leave on the same day | When user selects the date in "Date From" field, the same date should be repopulated in the "Date To" field | Implement |
3 | Apply Leave/Record Leave | User tends to type the date instead of choosing the date using the datepicker leading to the wrong format being input | Have a short instruction before the "Date To" and "Date From" field to indicate the date format and give an example of it | Implement |
4 | User should be able to view leave of their colleagues in the same department so that they can plan how to cover up leave | Have a separate "View Leave" page for users to view leave of people from the same department | Make the "view" link bigger and more distinct | Implement |
Remuneration | ||||
1 | View Personal Payslip tab | User feel that it is hard to navigate to view personal payment record link when it is at the bottom | Change the arrangement for the links under remuneration tab | Implement |
2 | View payslip | User finds that the less part of the payslip can be more obvious with a "-" sign | Include the "-" sign in the PDF payslip | Implement |
3 | View payslip | Instead of month only, should include year as well in the payslip | Include the year | Implement |
Performance & Appraisal | ||||
1 | Edit Salary Increment | User does not click the "Save" button when revising the salary increment amont. As a result, the amount approved is not the revised amount. It is not obvious that the "Save" button should be clicked before submitting the form | In the event the increment value is not saved, the user should not be allowed to approve the increment request | Implement |
2 | View Scheduled Salary Increment/Scheduled Bonus | Currently the "Scheduled salary increment" and "Scheduled Bonuses" tables reside on the same page ("View Scheduled Increments/Bonus"). This can be confusing to the user as he/she is unable to distinguish between scheduled salary increments and scheduled bonuses | Change the colours of the tables to differentiate between scheduled salary increments and scheduled bonuses | Implement |
3 | Submit Appraisal | Placement of "Submit Appraisal" and "Clear" buttons. Button placements are different from other modules. Not intuitive and users may get confused | Standardize position of buttons across modules | Implement |
4 | Submit Appraisal | When an appaisal has been submitted successfully, it is not obvious to the user | Display a successful appraisal submission message | Implement |
System Administration | ||||
1 | Manage Leave | Change default no. of leave --> User unsure of change is successful cos there is no popup or anything | Display a successful update message | Implement |
2 | Create/Edit Profile | Remind the user the DOB format to type. User unsure of what to type. The date thing also must select super long ago. super troublesome for them | Display a date format beside the field | Implement |
Navigation | ||||
1 | Navigation | In the navigation bar, users tend to click on menu items which display sub-menus, this results in the menu options being minimize. Selection of sub-menu items require users to hover over the main menu items and then clicking the sub-menus items | Enable the navigation bar to support both hover and click functionality. In both instances, the sub-menu will be displayed and the menu will not be minimized | Implement |
Login | ||||
1 | Error message | Error message for login is black in colour | Error message for login should be red in colour | Implement |
2 | Active status | Account with inactive status can login | Account with inactive status should not be able login | Implement |
Changes made from User Test 2 Feedbacks | |||
---|---|---|---|
Claims | |||
Leave | |||
Remuneration | |||
Performance Management & Appraisal |
Quantitative Feedback Analysis | ||
---|---|---|
Ease of Use | ||
Overall Layout |
User Test 2 Analysis |
---|
Response Plan (Not Implementing)
S/N | Functionality | Feedback | Reason for Not Implementing | Proposed Decision |
---|---|---|---|---|
Leave | ||||
1 | Approve/Reject Leave | People in the department should have the authority of approving/rejecting the leave the user sends | The sponsor of the project mentioned that the line manager should be the only one approving. He should know if anyone in the department rejects to that particular leave on a particular day in case of any project that arises. Hence, according to the business logic, only the line manager should have the authority to approve/reject leave | Not Implementing |
2 | Apply Leave | User takes quite a while to find the leave balance on the "Apply Leave" page | As the task instruction explicitly mention to the tester to check on the leave balance, tester might not know that it can be checked in the "Apply Leave" page. Moreover, it is only 1 out of 5 of the user that mentioned that. However, everyone eventually managed to find the leave balance when they are applying leave | Not Implementing |
Remuneration | ||||
1 | Payslip | Suggestion: For payslip, put signature and date | The payslip is followed closely to the current payslip that the company is using | Not Implementing |
Performance & Appraisal | ||||
1 | Edit Appraisal | User should have the option to edit Appraisal once submitted | Client explicitly mentioned that Appraisals should not be edited once submitted | Not Implementing |
System Administration | ||||
1 | Create/Edit Profile | Creating user profile --> User tend to click Tab. Take note to rearrange input data values. E.g. Put "Given Name" beside "Family Name" cos that is where the cursor go when user click Tab. Do take note of this | Not really important | Not Implementing |
2 | Create/Edit Profile | To input allowance --> amount for which allowance type? If user select more than 1 allowance type, the $500 is for which one? | It suppose to be like this, is a combine amount | Not Implementing |
Login/Logout | ||||
1 | Logout | User takes a few secs to find logout button | Attributed to lack of familiarity with the system user interface. | Not Implementing |
User Test 3
In this user test, we did the testing on 9 participants, of which 5 participants are the same person from user test 2. This is so that we are able to do comparison between the qualitative and quantitative results gathered from user test 2 with the results that we gathered in this user test 3. Due to the space constraints, we will be showing the results gathered from the 4 new participants. If you want to view more results from user test 3, please click on this -> View Full Analysis.
Results obtained from the testing conducted The following table shows the summary results for quantitative data analysis in terms of the number of time taken for various functions, clicks, bugs and question asked:
Response Plan (Implement)
S/N | Functionality | Feedback | Proposed Solution | Proposed Decision |
---|---|---|---|---|
Claim | ||||
1 | Submit Claim | Tedious to record receipt numbers of the claim receipts by HR | Have an addition field "Receipt No." for employee to key in their own receipt number and HR will just validate instead of having to input it herself | Implement |
2 | Validate Claim | Did not know need to update the edited amount before continuing to validate the claim | To include a "message" whenever the edit button is click to remind the user that update button must be hit before the changes can be made | Implement |
3 | Approve/Reject Claim | Admin accept/reject the status not obvious | Make it bigger and more striking colour | Implement |
4 | Edit Payment Method | Have a back button to generate claimslip | Implement "Go to Generate Claimslip" button below the edit payment method page | Implement |
5 | Generate Claimslip | No need claimslip for employee | Take out the employee's copy of claimslip in the PDF generated | Implement |
6 | Generate Claimslip | Make the slip bigger | Make the slip bigger | Implement |
7 | Generate Claimslip | More space for signature | Spread the claim slip to have more space and include a date space to input date | Implement |
Leave | ||||
1 | Record Leave | Not obvious that employee's name is able to be selected by keying the alphabet | Enable filtering for user's to type employee's name | Implement |
2 | Emailing for all Leave | Leave approval emails did not CC HR personnel | CC HR personnel for all leave emails | Implement |
3 | Approve/Reject Leave | Never state day duration in email (e.g. half day) | State day duration of leave taken in email | Implement |
Remuneration | ||||
1 | Input worker timesheet | Full name of workers should be shown for worker input timesheet page | Insert full name of workers | Implement |
Performance & Appraisal | ||||
1 | View full appraisal | Text on "View Appraisal" button is not specific | Change Button Text to "View Full Appraisal" | Implement |
2 | View full appraisal | Scores displayed are not meaningful to the user | Display of Remuneration Scores- show total (e.g. 100/100) | Implement |
Training & Development | ||||
1 | Approve/Reject Proposed Training | UI Changes for select the training to be approve/reject. Accept / Reject button unclear, user wasn't sure she needs to click the button to proceed | Change the name of the button | Implement |
2 | Approve/Reject Proposed Training | UI Changes for the page that they input the training details. Back button not standardize. No need write "default". Venue nv put "*". Instead of add session, it should be add another training session. Different form of writing time (e.g. 9am vs 0900. Course duration give dropdown for hrs/mins | Standardize back button. Remove the default wording. Venue is a required. Change value for the button for adding training session. Put the indication that is a 24 hour (so accept numbers only). A dropdown box that have the hr/mins/day/month/year for course duration | Implement |
3 | Propose Training | Need to check if the employee have or didn't have any people under him/her. Nomination of employee | Do a check if there is no employee under him, it will prompt him a message | Implement |
4 | Manage External Training | Training Status from Completed change to Course Completed | Change from completed to Course Completed | Implement |
System Administration | ||||
1 | Manage Employee | Adding the department dropdown list | Add a table in db + and add a dropdown list | Implement |
Navigation | ||||
1 | General | Font size could be larger | Increase Font Size | Implement |
Changes made from User Test 3 Feedbacks | ||
---|---|---|
Claims |
Before
|
|
Leave |
Before
|
|
Training & Development |
Before
|
Quantitative Feedback - User Test 2 versus User Test 3 | ||
---|---|---|
Ease of Use |
|
|
Overall Layout |
|
|
Analysis for the same 5 participants from user test 2 |
This is the analysis done from user test 2: Reasons for the time taken:
Reasons for changes in timing:
|
Response Plan (Not Implementing)
S/N | Functionality | Feedback | Reason for Not Implementing | Proposed Decision |
---|---|---|---|---|
Leave | ||||
1 | Record medical leave | Did not check for duplicate medical series no | There is a possibility that 2 person can have the same medical series no. Hence, this will not be checked | Not Implementing |
Remuneration | ||||
1 | Worker payslip | Timesheet to include dinner breakdown (3h x 2) instead of giving the total ending sum | Dinner is allocated $3 for each dinner, if necessary. The payslip in the system is mirroring the current payslip they are using | Not Implementing |
2 | Input worker timesheet | User tend to miss out the days but will notice when see days | The timesheet in the system is mirroring the current worker timesheet they used. Others may not be familiar but the HR personnel who is in charged of inputting the timesheet will be familiar if it is the same format as the one she is using | Not Implementing |
Performance & Appraisal | ||||
1 | Create Employee Appraisal | Radio button too small. Cannot click properly | Radio buttons are controlled by system and browser. Customization of radio buttons would not enable usage on mobile devices | Not Implementing |
Training & Development | ||||
1 | Manage External Training | Suggest user can type "UOB" for cheque no. (so allow text and no.) | Cheque number got nothing to do with the Bank name | Not Implementing |
System Administration | ||||
1 | Manage Employee | Date Cannot go back to earlier than 2014. Wage Type, Hourly, Edit button on the top, cause too much to scroll down. | The requirement that we had agreed on earlier was to either put in daily wage or monthly wage | Not Implementing |