CS 466 - Project: Usage scenarios v2.0

Due: 2017-04-06 1:30p

Revisiting the scenarios

The design process is inherently one of iteration and refinement. In our first pass at usage scenarios, many of you aimed at too high a level or you missed a number of opportunities to really flesh out the requirements of your application. So, we are going to iterate and take a further crack at writing scenarios.

In your scenarios you should be walking through the actual usage of your app. However, this should be at the task level, not the interface level (because the interface hasn't been designed yet). Examples:

• "The artistic director likes Color Explorer for picking color schemes" (Too high level, doesn't actually talk about any actual tasks)
• "The artistic director pulls out Color Explorer, adjusts the RGB sliders to get the right base color and then hits the 'Complement' button to find the color's compliment" (Too low level, assumes an existing interface)
• "The artistic director pulls out the Color Explorer, enters in an RGB color and then uses the app to get the compliment of the color" (Good. The task is specific, provides some requirements, but doesn't specify how it should happen)

Be imaginative! Try to imagine the various ways someone might use the app, and the ways it might respond. Imagine that things do not go perfectly every time. If you are relying on users using your app at regular intervals, what if they don't? What if they enter bad values? Make a mistake? Change their mind? Do not forget novice users and how you will support them (if at all).

Deliverables

I would like a minimum of five scenarios, but I am also expecting to see all of the requirements for your app spelled out in the scenarios. If there is something your app does, it should be described in a scenario. These are your design documents. You do not need to make all new scenarios; many of you should be able to reuse some of your scenarios. Some of you will want to start fresh.

I would then like one unified analysis of all of your scenarios. The analysis should come directly from the scenarios, and I would like you to number the scenarios and reference them in the analysis. The analysis should again consist of

• users: who are your users
• context of use: what situations are they in when they use the app
• tasks: what activities do the user perform
• information objects: what pieces of information are produced/manipulated/stored by the application

Note that this is all about what the user is trying to accomplish.

Please make this a PDF and submit it on Canvas. I only need one copy. Again, make sure that the first page has your names and the project name on them.

Evaluation