This is a draft in progress.

Discussion about terminology and what components might emerge.

Terminology Definition

Definition

Problem/Pain

Problem description.

Scenarios

Sarah Windsor - Primary Persona
Scenarios to come.

Ed McClellan, Undergraduate
Scenarios to come.

Blue Sky Vision

Terminology Component Ideas

Use of Icons

Example Confusing Terms use in Specific Applications

Moodle

Sakai

uPortal

Summit Post-it Page

At the Fluid Summit, pain points represented on post-it notes were grouped into problem spaces (such as Feedback), then into (usually very high level) potential components such as the ones below. Each problem area was then rated as to whether it affected 1, 2, or 3/All of the Fluid applications (Sakai, uPortal, Moodle). Each potential component was then rated on the following matrix, which indicated how severe the pain point it helped solve was for users, as well as how frequently the pain point was encountered. It helped us determine how high a priority it was, with 1 being the highest priority and 3 being the lowest.

high severity

1

2a

low severity

2b

3

 

high frequency

low frequency