BOHS-Part+C

**__Part C__**

 * Scenarios and Requirements (Mar. 16 – 5%)**

Each team will generate a series of scenarios that reflect user interaction, as informed by the user study (min 1 scenario per group member).

The collection of scenarios should reflect the full complexity of the technology and usage context in question (e.g., it should hit on all the important people, activities, context and technologies you've noted...)

While scenarios may be forward looking (e.g., describing features or functions that don't yet exist, but should) the scenarios should be partially based in actual use patterns (e.g., actual problems that do exist at present...) In other words, the scenarios must reflect at least in part what the current situation is and not be complete conjectures on what could be.

Each scenario will be broken down to requirements, prioritized from "must" to "would be nice" using the MoSCoW approach from text and lecture notes.