Skip to content

C.R.U.D. Students

Jump to bottom
doccz edited this page Feb 11, 2011 · 25 revisions

7. C.R.U.D. Students

Return to Use Case List

Brief Description:

  • Create, Read (display all information), Update, and Delete a student

Actor:

  • Admin
  • Super user

Dependencies:

  • Create: Student cannot exist already. If they do, then the admin can only update.
  • Read: Student must exist
  • Update: Student must exist
  • Delete: Student must exist
  • The admin must be logged-in to the system.

Event Flows:

CREATE
Basic Event Flow: Successful create 1. The admin selects the Create Student button 2. The admin inputs the student's information 3. The admin submits the student's information 4. A message indicating a successful create displays 5. (Event Flow Ends)

Alternate Event Flows: Unsuccessful create (incorrect input)
1. This event flow begins after steps 1-4 from the Basic Event Flow are completed.
2. An error message displays (perhaps we should do a red asterisk next to each field that is incorrect)
3. (Event Flow Ends)

UPDATE
Basic Event Flow: Successful update 1. The admin selects the Update Student button 2. The admin inputs the NSHE# 3. The student's information is displayed with input fields for editing 4. The admin enters input into fields they want to update 5. The admin selects the submit button 6. A message indicating a successful update displays 7. (Event Flow Ends)

Alternate Event Flow: Unsuccessful update - NSHE# does not exist
1. The admin selects the Update Student button
2. The admin inputs the NSHE#
3. An error message indicating that no student with said NSHE# exists
4. (Event Flow Ends)

READ
Basic Event Flow: Successful read/look-up 1. The admin selects the Read Student button 2. The admin inputs the NSHE# 3. All the student's information is displayed. 4. (Event Flow Ends)

Alternate Event Flow: Unsuccessful read/look-up - NSHE# does not exist
1. The admin selects the Read Student button
2. The admin inputs the NSHE#
3. An error message indicating that no student with said NSHE# exists
4. (Event Flow Ends)

DELETE
Basic Event Flow: Successful delete 1. The admin selects the Delete Student button 2. The admin inputs the NSHE# 3. All the student's information is displayed along with a Delete button 4. The admin selects the Delete button 5. There will be a message displaying: "Are you sure (Y/N)? [] Yes [] No" 6. The admin selects "Yes" 7. A message indicating a successful delete displays 8. (Event Flow Ends)

Alternate Event Flow: Unsuccessful delete - NSHE# does not exist
1. The admin selects the Delete Student button
2. The admin inputs the NSHE#
3. An error message indicating that no student with said NSHE# exists
4. (Event Flow Ends)



Document Contributors: Greg Carter, Suzanna Ho, and Danny Kovene

Return to Use Case List

Clone this wiki locally