Scenarios are a method for requirements elicitation where engineers write detailed descriptions of how people interact with the system being developed. In the process of writing down how the system should behave once it is fully implemented, many details need to be resolved, and resolving these questions leads to an improved understanding of the system, and its requirements. Scenarios also make the intended behavior more visible, since they are easy to understand by both stakeholders and engineers. This increased visibility can expose disagreements among customers and engineers concerning the system's behavior, and thereby lead to resolution of the conflict.
The scenarios document should contain a table of contents, and then 5-10 pages of scenarios (do not exceed 10 pages of scenarios). If you are unable to cover all of your project's functionality in 10 pages, focus on the most important capabilities. Note that length is not necessarily correlated with quality; a long document with redundant scenarios would receive a lower grade than a short, concise document with a well chosen set of scenarios.
Scenarios will be graded based on their internal consistency (are the scenarios contradictory), and how well they represent the important functional aspects of the project (do the scenarios address substantive issues, or trivial functionality). Poor grammar and spelling can contribute to a lower grade, so proofread your work.
For more information on this assignment, please read the template.
Last updated: