FY23.2.x: Technical Design (Slate+Advising)

Executive Summary

The purpose of this document is to provide the full details of the technical solution to be used for the build of the Slate+Advising solution. Everything that is needed by the developer(s) to produce the required data model, forms and workflows will be included in this specification.

Technical Components

The following sections will detail the technical components within each functional area that are required to successfully implement this project.

Data Management

Technical Requirements

The following technical requirements must be delivered for a successful implementation of this application component:

• Incoming Data
  • Create scheduled exports based on last modification date for the required data points in the following systems
    • SIS
      • Extended details for student records
    • Lenel
      • Student photos
  • Create source formats and scheduled imports for all data noted above
• Reports and queries
  • Audit queries to validate imported data
  • Determine best reports for leadership view of advising status

Student Relationship Management

Technical Requirements

The following technical requirements must be delivered for a successful implementation of this application component:

• Custom form(s) to collect information from students as required to support requests and process flows and store in the student profile
  • Placeholder for specific forms and processes 
    • E.g., program change requests, leave of absence requests, others?

Communications & Outreach

Technical Requirements

The following technical requirements must be delivered for a successful implementation of this application component:

• For Advisors
  • Message templates for common referral communications
    • Health Hold
    • Admissions Hold
    • ISSO for New Students
    • ISSO For Continuing Students

Security & Access Management

Technical Requirements

The following technical requirements must be delivered for a successful implementation of this application component:

• Define role-based security model and assign users to appropriate groups based on role
  • Include program-level grouping to further segment access based on student population