Child pages
  • A Community Process for Requirements Gathering
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

A Community Process for Requirements Gathering (Strawman)

There are three types of requirements gathering that would be useful during the life cycle of the Sakai product:

  1. Functional Visions - These would be stories that would capture, at a high level, innovative teaching and learning strategies (grounded in teaching and learning theory/research) that could be facilitated by Sakai.  They would be tool/technology agnostic "pie-in-the-sky" narratives who's goal would be to provide a "functional target" at which future development could be aimed.  The ultimate goal would be to get teaching, learning, and research needs out ahead of development efforts.  Functional Visions would be used most often during the "R&D" and "Incubation" stages.
  2. Use Cases - These would be more specific descriptions of how users want/need to use particular tools or workflows that would cut across tools/capabilities.  Although teaching/learning/research (TLR) focused, they would be more practical in nature and more grounded in usability practices then teaching and learning theory.  Use cases might be used most often during the transition from "incubation" to "development".
  3. Tool Requirements - These would be at the "nitty gritty" level and would be focused on near-term improvements to existing tools.  The might range from purely usability issues (e.g. button is poorly located) to more functional issues (e.g. instructors need to be able to edit this item after it is released).  Tool requirements would generally be dealt with in the "maintance" stage.

  • No labels