Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Warning
titleThis Work is Still In Progress

These models are still a work in progress, and are actively being worked on. While discussion and comments are welcome, please treat this material as such.

User and behaviorial User and behavioral models are a great way to make sense of a lot of user research data. 

There are a variety of models we can use to help us in our understanding of our findings and share out our learning with the community.  We are focusing on Personas to model users and Use Cases (.ppt) to model behaviorial behavioral goals, needs and wants.

On this page:

Table of Contents

Personas 
Anchor
personas
personas

Persona Scales were used to identify and describe personas.  We identified 6 Faculty, 4 Student and 2 Instructional staff personas based on 20 Contextual Inquiries with users in these roles (across UC Berkeley, York University & University of Toronto).  Our research is an iterative process.  We were unable to meet with System Administrators and Institutional Staff in this iteration although we recognize them as an important user group.

The next step was to create rough draft personas based on the persona scales. The personas created at that time have evolved to become the Fluid Personas for Course Administration & Content Management.

For privacy, contextual Inquiry participant initials are used to identify the people on whom each persona was based.  Multiple initials mean several participants have been rolled up into the same persona (because they have similar goals, needs & characteristics).  The personas describe these archetypes, including their characteristics, goals and distinctions from one another. 

Faculty

 
Student

Instructional Support Staff

Check out the personas that emerged from the research:

Fluid Personas

Use Cases
Anchor
use_cases
use_cases

...

A variety of models are being worked on with use cases as the focus.  They will inform the Fluid component roadmap along with each component's functional requirements. 

Affinity Diagramming Diagramming

 

 

See all affinity diagrams...

Use Case Frequency Matrix Matrix

The Frequency Matrix allows us to understand who's doing what and how often. 

Completed Use Case Frequency Matrix

Samples from matrix:

Component Identification 

Components identified through the research and modeling activities...

Coming soon!

Use Case Priority Matrices

...

We will create a priority matrix for each component on the Fluid Roadmap.  Here's what one might look like (borrowed from a previous Sakai project):

Image Removed|width=300pixelsImage Added
 
This matrix was created for the Sakai project.  Colors indicate the functional area of the use case.  Low-low is the bottom left corner.  As you move up Y axis or over on the X axis the measurement gets higher.