Maintain Student InformationBrief D

Maintain Student Information
Brief Description
This use case allows the Registrar to maintain student information in the registration system. This includes adding,
modifying, and deleting Students from the system.
Flow of Events
Basic Flow
This use case starts when the Registrar wishes to add, change, and/or delete student information in the system.
1. The system requests that the Registrar specify the function he/she would like to perform (either Add a Student,
Update a Student, or Delete a Student)
2. Once the Registrar provides the requested information, one of the sub flows is executed.
If the Registrar selected “Add a Student”, the Add a Student subflow is executed.
If the Registrar selected “Update a Student”, the Update a Student subflow is executed.
If the Registrar selected “Delete a Student”, the Delete a Student subflow is executed.
Add a Student
1. The system requests that the Registrar enter the student information. This includes:
- name
- date of birth
- social security number
- status
- graduation date
2. Once the Registrar provides the requested information, the system generates and assigns a unique id
number to the student. The student is added to the system.
3. The system provides the Registrar with the new student id.
Update a Student
1. The system requests that the Registrar enter the student id.
2. The Registrar enters the student id. The system retrieves and displays the student information.
3. The Registrar makes the desired changes to the student information. This includes any of the
information specified in the Add a Student sub-flow.
4. Once the Registrar updates the necessary information, the system updates the student information.
Delete a Student
1. The system requests that the Registrar enter the student id
2. The Registrar enters the student id. The system retrieves and displays the student information.
3. The system prompts the Registrar to confirm the deletion of the student.
4. The Registrar verifies the deletion.
5. The system deletes the student from the system.
 Copyright IBM Corp. 2004 Page 11
Section 1: Course Registration Requirements
Alternative Flows
Student Not Found
If, in the Update a Student or Delete a Student sub-flows, a student with the specified id number does not
exist, the system displays an error message. The Registrar can then enter a different id number or cancel the
operation, at which point the use case ends.
Delete Cancelled
If, in the Delete A Student sub-flow, the Registrar decides not to delete the student, the delete is cancelled
and the Basic Flow is re-started at the beginning.
Special Requirements
None.
Pre-Conditions
The Registrar must be logged onto the system before this use case begins.
Post-Conditions
If the use case was successful, the student information is added, updated, or deleted from the system. Otherwise, the
system state is unchanged.
Extension Points
None.
 Copyright IBM