HeaderSIS.jpg

IS480 Team wiki: 2013T2 D'PENZ User Testing

From IS480
Jump to navigation Jump to search

Dpenz logo.jpg

Neophase Home.png Home DPENZ Team Icon 2.png Our Team DPENZ Overview Icon.png Project Overview DPENZ Project Management Icon.png Project Management DPENZ Project Documentation Icon.png Project Documentation


Use Cases Architectural & Deployment Diagram Prototypes User Testing Presentation Slides Meeting Minutes



Heuristic Evaluation

Note: This was done on our system coded in JSP.
Date: 22 October 2013
Purpose: To test if our system is intuitive enough to be used by people who have not used procurement systems before.

Results from HE

Data Pilot Participant Participant 1 Participant 2 Participant 3
Participants Dpenz HE Shanaaz1.jpg Dpenz HE Derrick.jpg Dpenz HE Meizhen.jpg Dpenz HE Joel.jpg
Name Shanaaz Derrick Meizhen Joel
Age 23 22 22 27
Location SIS Level 4 SIS Level 4 SIS Level 4 SIS Level 4
Web Browser Google Chrome Google Chrome Google Chrome Google Chrome
Quantitative Data
Prior experience with Procurement systems) No No No No
Ease of editing a project
(Scale of 1 - 5 [highest])
5 4 5 5
Ease of searching for a project
(Scale of 1 - 5 [highest])
5 3 4 5
Ease of learning & using the interface
(Scale of 1 - 5 [highest])
5 4 5 4
Ease of navigating around the system
(Scale of 1 - 5 [highest])
5 3 4 4
Able to quickly find information needed
(Scale of 1 - 5 [highest])
5 4 3 3
Pathway for Manage Projects
(Scale of [not completed] 0 - 2 [easily completed])
2 2 1 2
Pathway for Search Projects
(Scale of [not completed] 0 - 2 [easily completed])
2 1 2 2
Pathway for Edit Project - Procurement Staff
(Scale of [not completed] 0 - 2 [easily completed])
2 1 2 2
Pathway for Edit Project - Functional Owner
(Scale of [not completed] 0 - 2 [easily completed])
2 2 2 2
Time taken to complete Manage Projects 2 min 25 sec 1 min 1 min
Time taken to complete Search Projects 1 min 3 min 30 sec 1 min 2 min
Time taken to complete Edit Project (Procurement Staff) 1 min 2 min 1 min 1 min
Time taken to complete Edit Project (Functional Owner) 2 min 3 min 1 min 1 min
Number of times participants asked for help 1 2 2 2
Number of bugs found in system 0 0 1 0
Qualitative Data
What does the participant think is required for a procurement workflow management system? Good user interface and experience that is understood by all the departments involved. Probably a centralised platform so that whoever is in-charge can manage the procurements I am not too sure about how a procurement workflow management system is like. Knowing the total number of projects on hand. Knowing important deadlines. Knowing who are the people involved.
Anything the participant like about our system? I like the simple UI and easy navigation through the pages. The UI looks rather professional. Simple and easy to navigate. Not too much of information on one page. The layout.
Anything the participant dislike about our system? Not that I can think of at the moment. It was pretty easy and sleek. Personal opinion is that there's too many information loaded on one page. - No help function.
Anything to be changed to provide an improved user experience? 1. It would be better if the search results appear on top of the User's current projects.
2. When I change the assigned user and save, I would like to see a confirmation message.
Maybe to provide those "changes have been saved" notifications. 1. If there is more than one table to be shown in a page, probably could use a different color for each table so that it is easier to identify and would not look as if there are too much of information in a page.
2. Color contrast can be improved.
Add a help function.


Changes to be implemented

  1. Instead of displaying search results under Other Projects section (where users still have to scroll down), we will place the Search Results in the same tab as the Search fields (Change implemented)
  2. We will include a help function to aid new users in navigating around the system (Change will be implemented after acceptance)
  3. "Save Edits" button in the project details page will be placed both at the top and bottom of the page (Change will be implemented after acceptance)



User Testing 1

Note: This is the first testing we have done with on our system coded with ASP.NET.

Date: 29 November 2013
Purpose: Evaluate usability of functions: Home page, Search project, View & Edit Project Details

Time: 5pm-6pm
User: Tam Chee Hong
Location: Skype (Screen sharing with our client as we are still using internal IP)
Browser: Google Chrome
Role: Procurement staff


Results & Changes

S/N Function Description Suggestion Comments
1 Search Projects There are too many functions in one page (Home page) which leads to a lot of scrolling. Also, search function may not be used often since I can already see the projects that I'm working on. Remove the search section and replace it with a search bar at the top. Search results could be displayed on a different page. We agree that a search bar will be less obstructive and intuitive as users are used to search bars in websites. We will implement this change after acceptance.
2 View Project Details It is not clear which fields can or cannot be edited. Fields that cannot be edited should be greyed out. We are currently using disabled fields to show that a field cannot be edited. This shows only when users hover over the fields. Hence, we agree that greying out the disabled fields will be clearer for users and we will implement this change after acceptance.
3 View Project Details The start date is in a format like 01/03/2013, and it is confusing as it is not clear which is the month and which is the date. Spell out the month in full. Change to be implemented after acceptance.
4 View Project Details Projects are submitted from various countries, hence it is important to know the currency of the project budget. Indicate the currency of the project budget Change to be implemented after acceptance.
5 Home Page There should be a toggle button to see all projects. Add a toggle button. This button would probably be of interest only to Procurement staff. Change to be implemented after acceptance.
6 Audit Log It's funny that the audit log has it's own page when it should be for specific projects Shift audit log button to view project details page. Change to be implemented after acceptance.
7 Add New User It will be good to have a function to add new users. See previous. This function will be considered as an additional request and we will further evaluate if we have enough resources to add it to our scope.

User Testing 2

Will be conducted after acceptance.