Use Cases

My task to provide some thoughts on use cases:
I am leaning toward using our top level principles - Perceivable, Operable,
Understandable, and AT friendly - as the primary structure for the use
cases. Within each area we could address specific input/output modalities.
They are easy to define and relate closely to the requirements we need to
write. We also need to address the principles in the 2 interfaces (for lack
of a better word) - UI and Rendered Content. That said, the use cases still
need a human face. Individuals with a disability should be used to frame the
input/output modality specifics for given tasks.

How do we create a finite set of perhaps 10 (a totally arbitrary number) use
cases?
Or,  how do we combine the intersections given:
4 principles times 2 interfaces times 7 disability types times 6 tasks = 288
intersections
to result in 10 use cases?

Functional performance (Disability types) [1]
1. Full use without Vision
2. Full use without Hearing
3. Full use with Low Vision without Audio
4. Full use without Color perception
5. Full use without Speech
6. Full use with limited reach, strength or dexterity
7. Full use with cognitive, language or learning disabilities

Goals/tasks: The user can
- change rendering (scale font/image/window, expand/collapse structure)
- navigate the content (structure and active elements)
- complete and submit forms
- search the content  (rendered and conditional)(how to search compound
document content?)
- interact with the content  (ajax, compound documents (media, flash, svg,
etc.)) Note: forms could be included here
- interact with and modify the UI

Are there other tasks? These are very broad and could be more focused -
resulting in more tasks.

[1] http://teitac.org/wiki/Proposal_for_blended_categories

Jim

Received on Tuesday, 27 February 2007 21:52:35 UTC