Gathering user Data

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.

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

The user will see a page with a heading similar to the previous page. In the middle of the screen will be a series of input fields labeled as so:

1. Name will be a single text input. We will not be separating first and last names.
2. To the right of the name input will be a class year select input. It will have the next four class years as possible selections.
3. On a new row will be another select input to collect information about the school that the student attends. This select can easily be edited later to accommodate new schools.
4. Next to the school input field will be a Student number field. Somewhere near this field will be a prompt linking students to locations where they can find their student numbers.
5. On a new row will be a text input for collecting an email address.
6. There will be a “tel” input on the final row collecting a phone number. This field will be optional, and can be used later to recover login issues.

Below the form, there will be a checkbox for agreeing to the terms of service and a submit button.

All users will have to do is fill in these fields with the appropriate information, agree to the terms of service, and then click submit. The information will then be sent to the server, where it will be stored in a private database.

One of the later features we may implement is a validity checker, which will query university databases and confirm the data users provide. But for now, no validation is necessary.

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?

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.

Relative priority of feature (high, medium, low)