Difference between revisions of "IS480 Team wiki: 2013T2 D'PENZ User Testing"
Line 353: | Line 353: | ||
Date: 7 February 2014<br> | Date: 7 February 2014<br> | ||
Purpose: Evaluate usability of system: Home page, Create + Edit + Search Projects, Create + Edit + Search Suppliers, Edit PAF Template, View Audit Log, Approval<br> | Purpose: Evaluate usability of system: Home page, Create + Edit + Search Projects, Create + Edit + Search Suppliers, Edit PAF Template, View Audit Log, Approval<br> | ||
− | |||
Time: 12pm-7pm<br> | Time: 12pm-7pm<br> | ||
User: 30 SMU students <br> | User: 30 SMU students <br> |
Revision as of 21:20, 12 February 2014
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
Round-up of Evaluation
- Overall, the app is easy to use and navigate around.
- More instructions could be provided so that users know what to do.
- The user interface is simple, which is well-liked by testers.
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
Comments from UT1
S/N | Function | Description | Suggestion |
---|---|---|---|
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. |
2 | View Project Details | It is not clear which fields can or cannot be edited. | Fields that cannot be edited should be greyed out. |
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. |
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. |
5 | Home Page | There should be a toggle button to see all projects. | Add a toggle button. |
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. |
7 | Add New User | It will be good to have a function to add new users. | See previous. Comments: 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. |
Changes to be implemented
(All changes to be implemented after acceptance)
- Remove the search section and replace it with a search bar at the top, with results displayed on a different page.
- View project details: grey out fields that cannot be edited.
- Project dates: spell out the month in full.
- Indicate the currency of the project budget.
- Add a toggle button for procurement staff to see all projects.
- Shift audit log button to view project details page.
User Testing 2
Date: 30 December 2013
Purpose: Evaluate usability of system including new functions: Edit PAF, Submit Supplier Information, Audit Log, changes since previous user test
Time: 2.15pm-2.45pm
User: Tam Chee Hong
Location: Skype (Screen sharing with our client as we are still using internal IP)
Browser: Internet Explorer
Role: Procurement staff
Comments from UT2
S/N | Function | Comments | Suggestion |
---|---|---|---|
1 | Search bar | What fields will the search bar search for? -Searches under all fields (including project description) |
Good. |
2 | Audit Log | Project log is good. We might need other kinds of logs too. |
Have logs for change of template, log in/log out (system-wide log) |
3 | Edit PAF Template | For basic information, the field type should be a drop-down list. | Change field type to dropdown list instead of getting users to enter the type (e.g. Integer, Date) |
4 | Edit PAF Template | Field types: most people won’t understand what does integer or text stand for, it’s confusing | Use simpler words like “numbers” or “words”, “paragraph”, “attachment” |
5 | Edit PAF Template | How many roles can I create under privilege? Can I create new privileges in future from the admin panel? How do I identify if someone is under procurement or not? | Allow changing of privileges from the admin panel. |
6 | Edit PAF Template | Customizable field sequence is nice | -- |
7 | Edit PAF Template | Assigned to & functional owner should be a dropdown list. | Change assigned to & functional owner to dropdown list. |
8 | Edit PAF Template | Project status should not be hardcoded. | Allow admin to add project status from admin panel. |
7 | Edit PAF Template | Assigned to & functional owner should be a dropdown list. | Change assigned to & functional owner to dropdown list. |
8 | Submit Supplier Information | We should cater for suppliers who sell products across multiple domains | Use tags to list out the products the suppliers provide. |
9 | Submit Supplier Information | Rating be tagged to the project instead of the supplier itself. | Don’t allow input of rating when a new supplier is created. Instead, when the project closes, procurement staff should do a rating of the supplier. |
Changes to be implemented
Function | Changes |
---|---|
Audit Log |
|
Edit PAF Template |
|
Submit Supplier Information |
|
Admin Panel (Future Implementation) |
|
User Testing 4
Note: This is the first testing we have done with people who are not from our client's company. Our testers will be similar to new hires of the company who do not have any experience with the Procurement workflow management system before.
Date: 7 February 2014
Purpose: Evaluate usability of system: Home page, Create + Edit + Search Projects, Create + Edit + Search Suppliers, Edit PAF Template, View Audit Log, Approval
Time: 12pm-7pm
User: 30 SMU students
Location: SIS CR 3-2 & SIS SR 3-2
Browser: IE8 - IE11
Role: Procurement, Functional Owner, Approver