Student Initial Interactions
|
Scenario 1: Student states/explores educational goals |
|||
|
Goal |
|
||
|
Pre-Conditions |
|
||
|
Step # |
Initiating or Other Actor |
Advising System |
|
|
1. |
Student requests specific degree plans |
|
|
|
2. |
|
System retrieves and displays requested information |
|
|
3. |
Student reviews options, makes preliminary selection |
|
|
|
4. |
|
System records preliminary course of study intention |
|
|
Post-Conditions |
|
||
|
Scenario 2: Student declares major |
|||
|
Goal |
|
||
|
Pre-Conditions |
|
||
|
Step # |
Initiating or Other Actor |
Advising System |
|
|
1. |
Advisor requests student records |
|
|
|
2. |
|
System provides records |
|
|
3. |
Advisor requests intended major requirements |
|
|
|
4. |
|
System provides records |
|
|
5. |
Advisor & student compare student’s records with major requirements |
|
|
|
6. |
Advisor approves student request for admission into major, enters appropriate data into system |
|
|
|
7. |
-or- |
System receives approval data for entry into major program, updates data file accordingly |
|
|
8. |
Advisor rejects student request for admission into major because of detected deficiency or lack of student interest in the major after complete description by advisor, enters appropriate data into system |
|
|
|
9. |
|
System receives denial data for entry into major program, updates data file accordingly |
|
|
10. |
Advisor requests data outlining other majors |
|
|
|
11. |
|
System provides requested data |
|
|
12. |
Advisor recommends student review of alternative major fields of study |
|
|
|
Post-Conditions |
|
||
|
Scenario 3: Student declares minor |
|||
|
Goal |
|
||
|
Pre-Conditions |
|
||
|
Step # |
Initiating or Other Actor |
Advising System |
|
|
1. |
Advisor requests student records |
|
|
|
2. |
|
System provides records |
|
|
3. |
Advisor requests intended minor requirements |
|
|
|
4. |
|
System provides records |
|
|
5. |
Advisor & student compare student’s records with minor requirements |
|
|
|
6. |
Advisor approves student request for admission into minor, enters appropriate data into system |
|
|
|
7. |
-or- |
System receives approval data for entry into minor program, updates data file accordingly |
|
|
8. |
Advisor rejects student request for admission into minor because of detected deficiency or lack of student interest in the minor after complete description by advisor, enters appropriate data into system |
|
|
|
9. |
|
System receives denial data for entry into minor program, updates data file accordingly |
|
|
10. |
Advisor requests data outlining other minors |
|
|
|
11. |
|
System provides requested data |
|
|
12. |
Advisor recommends student review of alternative minor fields of study |
|
|
|
Post-Conditions |
|
||
|
Scenario 4: Student and advisor build a Course Schedule |
|||
|
Goal |
|
||
|
Pre-Conditions |
|
||
|
Step # |
Initiating or Other Actor |
Advising System |
|
|
1. |
Advisor submits student’s proposed list of courses to system, along with schedule limitations/boundaries pertaining to student’s needs |
|
|
|
2. |
|
System matches list with available courses, produces list of course availabilities |
|
|
3. |
Advisor & student submit selections from the list of available courses |
|
|
|
4. |
|
System produces schedule |
|
|
5. |
Student and advisor review and approve schedule, request enrollment in courses |
|
|
|
6. |
|
System enrolls student & verifies completion of process |
|
|
Post-Conditions |
|
||
|
Scenario 5: Student adds a class |
||||
|
Goal |
|
|||
|
Pre-Conditions |
|
|||
|
Step # |
Initiating or Other Actor |
Advising System |
||
|
1. |
Student accesses records through KATS (K-State Access Technology System), the online student information system |
|
||
|
2. |
|
System produces current enrollment status from student information data |
||
|
3. |
Student adds class, identifying name, section (if more than one exists) and days/times the class meets |
|
||
|
4. |
|
System verifies availability of desired class and adds it to the student’s semester schedule, and to the class instructor’s student roster |
||
|
5. |
Student receives verification that requested class has been added |
|
||
|
6. |
|
System prints copy of schedule for final verification |
||
|
Post-Conditions |
|
|||
|
Scenario 6: Student drops a class |
|||
|
Goal |
|
||
|
Pre-Conditions |
|
||
|
Step # |
Initiating or Other Actor |
Advising System |
|
|
1. |
Student accesses records through KATS (K-State Access Technology System), the online student information system |
|
|
|
2. |
|
System produces current enrollment status from student information data |
|
|
3. |
Student removes the class from the current semester schedule |
|
|
|
4. |
|
System verifies action by student and any accompanying ramifications (withdrawal date and status, is dropped class on permanent record, is drop request after penalty deadline, etc.), adjusts student’s semester schedule, and notifies the class instructor |
|
|
5. |
Student receives verification that the course has been dropped, along with any ramifications from that action |
|
|
|
Post-Conditions |
|
||
NOTE: When a student changes from one section of a course to another section of that same course, the
"drop-add" process includes both of the above scenarios (Student adds a class, and Student drops a class)
and generally must occur within the first week of the semester, and with the permission of the instructor of
the section to which the student is being added.