CMPS183, Fall 2011, Section 01: Scenarios - Template

For the scenarios phase, you need to turn in a series of scenarios. Each scenario should include:

  1. A textual description of the scenario
  2. Paper prototypes or storyboards showing mockups of the sequence of screens encountered during the scenario

Textual Scenarios

There are many possible ways to write scenarios. For this class, your scenarios should be written in prose, and should involve named people (e.g., "Mary", "John", not "User A" or "the user") performing concrete actions with the Web application. Be as specific as you can, since the process of filling in the details leads to questions whose answers yield an improved understanding of the system.

Requirements Engineering by Kotonya and Sommerville, states that scenarios typically include the following information:

  • A description of the state of the system prior to entering the scenario (that is, the scenario's precondition)
  • The normal flow of events in the scenario
  • Exceptions to the normal flow of events
  • Information about other activities that might be going on at the same time
  • A description of the state of the system after completion of the scenario (the scenario's postcondition)

Ideally, each scenario should cover a different function of the Web application, and together the scenarios should encompass the majority of the Web application's behavior.

Each scenario should have a title (typically the heading of that section) and then the textual description of the scenario.

Paper Prototype / Storyboard

Sketches for your paper prototype or storyboard may be neatly hand-drawn, or created on the computer. The intent is not to have you quickly implement the term project and then take screen shots of the already working project. Instead, the sketches are intended for use in discussions with your customer on how the functionality of the site will look and behave. It should be easy to create and modify these sketches based on feedback you receive from your customer.

The title for each sketch should describe which aspects of the scenario it implements. The sketches and the scenario text should be consistent.

Turning in the Project

The scenarios you produce for this assignment must be placed on your project Web site, and also printed out and attached in a 3-ring binder (your project notebook). Each team is responsible for acquiring a 3-ring binder, and ensuring your project documents are 3-hole punched so they can be placed in the binder.