IS480 Team wiki: 2013T2 D'PENZ User Testing
Home | Our Team | Project Overview | Project Management | Project Documentation |
Use Cases | Architectural & Deployment Diagram | Prototypes | User Testing | Presentation Slides | Meeting Minutes |
Contents
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
Changes to be implemented
- 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)
- We will include a help function to aid new users in navigating around the system (Change will be implemented after acceptance)
- "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.