The uPortal team's focus is the evaluation of the uPortal product. We will be engaging in a process similar to that pursued by the other teams, but at the same time acknowledging the unique aspects of the service a portal offers to its users. Our objective will be to have something concrete to report at the Fluid Summit at the end of September. It will therefore be necessary to carefully scope our activities, selecting chunks of functionality we can investigate an report on. The goal is for the subgroups for Sakai, Moodle and uPortal to come together with our first phase evaluations in Toronto to look across the work to identify pain points that may be improved through the creation of components.
Project Plan & Timelines
Complete a short list of personas
Create a short list of scenarios
Select target implementations of uPortal and acquire courtesy (guest?) accounts
Review and freeze heuristic principles and walkthrough objectives
Finalize Report Template
Determine accessibility measures and tools (screenreader?)
Assign evaluation activities (usability, accessibility, walkthrough)
Evaluation (usability, accessibility, walkthroughs, create raw individual reports)
Screen Reader Evaluation (including report)
Write Summary Report (synthesize individuals)
Personas give us the ability to emulate representative users of the service. While a persona may not have exactly the same characteristics as any actual user, it provides us with a benchmark of goals, desires, needs, intentions, and behaviour of a population we want to serve. All persona descriptions should be backed up by research data derived from observations of real populations. They should not be simply imagined stereotypes.
A set of example personas can be found in the uPortal pages of the JA-SIG wiki. The Sakai Personas created for the Sakai walkthroughs may also be useful in the uPortal investigations.
We chose to focus on personas with intermediate experience/skills in Sakai for the Sakai walk-throughs, as that is the stage we hypothesized most users would be in. In the portal environment, it may make sense to focus on newer users. In the spirit of reuse and commonality we will attempt to use the Sakai Personas for the uPortal walkthroughs.
|uPortal Content Management Scenarios|
|uPortal Content Management Scenarios|
Target Instance of uPortal for Evaluation
Evaluations will be performed on existing uPortal implementations selected by the team. In most cases it will be necessary to obtain courtesy accounts for the target services; in some cases demo accounts may suffice. Please add suggestions to the following list.
uPortal Reporting Template
We will use the same Report Template as is used in the Sakai walk-throughs. There may be minor extensions to the template to cover the needs of each product.
uPortal Evaluation Plan
- Heuristic Overview of the portal and selected channels/portlets
- Use MyUBC (https://my.ubc.ca/ , contact Unlicensed user Paul Zablosky for login), Unicon 2.6 instance of uPortal set up by Unlicensed user Gary Thompson (http://22.214.171.124/uPortal/), or even another test uPortal instance you have access to if it contains channels/portlets we want to evaluate. See #Target Instance of uPortal for Evaluation for suggestions.
- Begin with a general heuristic overview of the portal. Some of the things to explore include modes, behaviors and content explosions, portlet modes and window states, personalization and customization, and how all of these things affect novice, occasional, and expert users, as discussed in the Content Management - uPortal Usability and Accessibility document.
- Suggested Channels/Portlets for Heuristic Overview: Announcements, News, [please add more typical channels/portlets here]
- done individually be each team member
- "traditional" heuristic-style
- Use UX Walkthrough Heuristics
- Cognitive walkthroughs
- Scenario Walkthroughs: use https://my.ubc.ca/ (contact Paul Zablosky for login) or Unicon 2.6 instance of uPortal set up by Gary Thompson (URL not yet available), or even another test uPortal instance you have access to if it contains channels/portlets we want to evaluate. See #Target Instance of uPortal for Evaluation for suggestions.
- Pick a scenario or scenarios from uPortal Content Management Scenarios page and check it off there as complete which you finish it. This page may be updated with information on which uPortal instance to use; if not, you may need to try to select the best uPortal instance for your scenario. If you are unsure, start with MyUBC and then move on to the Unicon 2.6 instance.
- Some of the goals are buried inside the portlet applications, and may be inaccessible. Also some of the clickpoints take you right out of the portal. If you are unable to complete a scenario due to not having access to an outside system, just concentrate what happened to get you that far. Paul interactions which cause you to leave the portal are key points for portal usability/accessibility.
- Can be done individually, but preferably should be done in groups -- 2+
- Walkthrough specific "likely" (identified) activities as the user -- uses personas
- Walkthrough each scenario again based on description of how disabled person would complete this task differently
- Keyboard only
- Screen reader
- Technical evaluation
- individually or in a group -- need specific skill set?
- review code 'under the covers' of the portal and selected channels/portlets against guidelines
uPortal UX Walkthrough Results
Results from the uPortal UX Walkthroughs completed prior to the summit can be found on the uPortal Pre-Summit UX Walkthrough Results page, and results from those completed after the summit can be found on the uPortal Post-Summit UX Walkthrough Results page.