Sample use cases

From MWCSWiki

Jump to: navigation, search

Contents

Amazon.com

Register (good)

Synopsis: An anonymous user creates a unique identity with the system, to be used to identify this user in this and future sessions.

Actor: Anonymous User

Precondition: The user is not logged on.

Sunny Day flow:

  1. From the main amazon.com home page, a "Create login" button is visible.
  2. The user clicks this button.
  3. The user is presented with a "create a user id" page, and is instructed to enter (and re-enter, for accuracy) their e-mail address and password.
  4. The user enters their e-mail address and password, re-typing their e-mail address a second time to ensure accuracy. (See Rainy Day #1) When entering text in the password field, a dummy character appears for each keystroke rather than the actual character pressed.
  5. The system presents a "successful registration" page. <Include Login>

Rainy Day #1

  1. If the e-mail addresses do not match, the system presents a message indicating this, and prompts again for e-mail address and password. <Go to Sunny Day step 3.>

Register (overspecified)

Synopsis: An anonymous user creates a unique identity with the system, to be used to identify this user in this and future sessions.

User: Anonymous User

Precondition: The user is not logged on.

Sunny Day flow:

  1. From the main amazon.com home page, a red "Create login" button is visible in the upper right-hand corner of the screen, to the immediate right of the "Welcome back!" button.
  2. The user clicks this button.
  3. A new page load occurs, refreshing the browser with new contents.
  4. The "create a user id" page appears that displays the message "Welcome to Amazon.com!" prominently at the top. The user is given three 40-character text boxes, vertically aligned, which have the phrases "e-mail address," "retype e-mail address," and "password", respectively, appearing in boldface to the immediate left of each box. These boxes should be centered immediately beneath the "Welcome to Amazon.com!" banner.
  5. The user clicks in the top text box and is presented with a blinking cursor in the box. This indicates that the box is active and they can type text into it. The user enters their e-mail address. Then, by either pressing the "tab" key or by using the mouse to get a blinking cursor in the second box, they re-type their e-mail address a second time. Finally, by either pressing "tab" again or using the mouse to highlight the third text box, they enter a password of their choosing. (See Rainy Day #1)
  6. A new page load occurs, refreshing the browser with new contents.
  7. The system presents a "successful registration" page. <Include Login>

Rainy Day #1

  1. If the e-mail addresses do not match, the system presents a message indicating this, and prompts again for e-mail address and password. <Go to Sunny Day step 2.>


Banner

Force Add Student (underspecified)

Synopsis: A professor enables a student to enter an otherwise closed section of a course.

User: Course Instructor

Preconditions: A course section is closed (full.) A student, not currently enrolled in the section, has expressed interest in enrolling in it. The user is logged in to the system.

Sunny Day flow:

  1. The user chooses the "Registration Overrides" option.
  2. The user chooses a term.
  3. The user chooses a student.
  4. The user selects the "Force Add" function for up to three of their sections.
  5. After the force add operation completes (including student involvement), the course's "remaining enrollment" will be negative.
  6. If any student in the section drops the course, the "remaining enrollment" will return to 0.

Force Add Student (good)

Synopsis: A professor enables a student to enter an otherwise closed section of a course.

User: Course Instructor

Preconditions: A course section is closed (full.) A student, not currently enrolled in the section, has expressed interest in enrolling in it. The user is logged in to the system.

Sunny Day flow:

  1. From the main Banner page, the user chooses the "Registration Overrides" option from the "Faculty & Advisors" menu.
  2. The user is prompted to choose a term. <Include "Select Term">
  3. The user is presented with a new page, and prompted to specify a particular student. <Include "Select Student">
  4. The user is presented with a new page, containing three pairs of lists. In each pair, one of the lists -- the "function list" -- lets the user choose a registration override function (such as "Force Add" or "Repeat.") The second list in each pair -- the "section list" -- lets the user select one of the course sections that they are currently assigned to teach. The initial (selected) entries in each list of all three pairs is the entry "None."
  5. For any or all of the three pairs of lists, the user may replace "None" in the function list with "Force Add" and "None" in the selection list with one of their assigned sections. This initiates a separate force add operation for that student for each of the pairs that was not left blank. (Also see Rainy Day #1 and #2.)
  6. The user presses a "Submit" button that is immediately visible. (See Rainy Day #3.)
  7. The user is returned to the student selection page (go to step 3), and presented with a message that indicates the operation was successful.
  8. When the student in question next accesses the system, navigates to the course add screen (see "Course Add"), and enters the CRN number for this section, he/she will be permitted to enroll for it, even though the section is closed. (See Rainy Day #4.)
  9. After the student enrolls, the next time the user views their detailed or summary class list for this section (see "View Detailed Class List" and "View Summary Class List"), the "remaining enrollment" entry will be negative. This is because the "current enrollment" will exceed the "maximum enrollment."
  10. If, after the force add operation has succeeded, any student in the section (the student who force-added, or any other) drops the course, the "remaining enrollment" will return to 0. However, another student may enroll for the course, bumping the "remaining enrollment" back into the negative range. This is because the "force add" operation has effectively increased the maximum enrollment possible for the course. (Multiple force add operations on the same course will continue to increase the maximum enrollment possible.)

Rainy Day #1:

  1. If the user chooses "Force Add" from the function list in one of the pairs, but leaves the section list entry as "None," no operation will take place. Similarly, if the user leaves the function list as "None" and chooses an entry from one of the section lists, no operation will take place.

Rainy Day #2:

  1. Note that if the user makes a selection for both the function list and the section list of any of the pairs, the operation corresponding to those selections will take place when the Submit button is pressed. This is true even if the pair(s) in question are not the first pair in the list, nor contiguously chosen.

Rainy Day #3:

  1. If the user navigates away from the page without pressing "Submit," no operation will take place.
  2. The next time the user returns to this screen, any selections they have made to any of the function lists or section lists will be lost, and appear again as "None."

Rainy Day #4:

  1. Until the student manually adds the course (via "Course Add") after the user has completed the force add operation, the student will not be enrolled for the course.
  2. The force add operation will remain in effect for 72 hours after the operation completes, at which time the system state will revert to what it was before the operation took place. (This includes the fact that the effective maximum enrollment for the section will revert to what it was previously.)
Personal tools