This is an old revision of the document!
−Table of Contents
Gathering user Data
Feature
This feature is fairly straight forward. Our registration page will have inputs for a student's name, email address, student number, the school they attend, phone number, and their expected graduation year.
Prerequisites
In order to reach this page, the user must not be already registered with the web application. They will have began at the main landing page, and then have clicked on a link saying something to the effect of “I'm a new user and want to register.”
See the login feature's page for more details: http://cswiki.wlu.edu/dokuwiki/doku.php/courses/cs335/spring2019/chemtutor/requirements/login
What a User Sees
Describe what a user sees: what are the input fields, what are the results displayed, what order are they in
What a User Does
Describe the options for what a user can do. Be specific. (May be tied with fields in earlier section.)
What is required of the user? Any input that needs to validated? Any constraints? (Perhaps a user must fill in two fields or only one of two fields.)
Behavior of the Application/Feature
When a user enters input or clicks a button, what are the possible outcomes?
Examples: if user enters erroneous input, what happens? if user does one of three options, what happens in each of those cases?
Example Use Cases
Describe some typical situations of what a user can/will do.
May want to put this earlier, but may not make sense unless you explain the other stuff.
Priority
Relative priority of feature (high, medium, low)