This page is for use by clients who are in the implementation phase. This describes the standard iterative approach that Regent follows during implementation for SBL file development.
Iteration 1 - Student/Bio/Demo Data
In this iteration, student biographic, demographic, high school and test score data elements are incorporated onto the SBL. In addition it is appropriate to start making use of the additionalInformation element in order to bring in UDF values.
An Iteration 1 SBL includes the following elements:
<student> (main element)<demographic><highschool><additionalinformation> (User-Defined-Field UDF Values)<userDefinedTestScore><address><phone><email><parentspouse><portal>
Iteration 2 - Academic Information / Program / Course Data
In this iteration the focus is to introduce academic information, program data and course data on the SBL file. Development efforts should first be focused on introducing the Student's Current Program and Course Data. Initial conversations, design and development on SBL Program Change logic is initiated during this iteration.
An Iteration 2 SBL includes all elements from Iteration 1 along with additional elements for capturing program and course data.
<student> (main element)<academicInformation><demographic><highschool><additionalinformation><userDefinedTestScore><address><phone><email><parentspouse><portal><courseData><studentBreak> (available but not-in-use)
Iteration 3 - Program Changes / R2T4 / SAP / Course Adjustment
In this iteration the primary focus is on properly defining Program Changes on the SBL file. In addition, R2T4, SAP and Course Adjustment nodes are added if applicable.
An Iteration 3 SBL includes all elements from Iteration 1 and 2 along with additional elements used to capture R2T4, SAP and Course Adjustment data.
<student> (main element)<academicInformation><demographic><highschool><r2t4><sap><additionalinformation><userDefinedTestScore><address><phone><email><parentspouse><portal><courseData><courseAdjustment><studentBreak> (available but not-in-use)