Technical Requirements (Slate+SPS)

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+SPS 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
    • Slate+Admissions
    • Slate+Academics
  • Create source formats and scheduled imports for all data noted above
  • Create manual formats and processes for importing any data not managed in source systems
    • None currently identified
• Managing Data
  • Create forms for adding/editing any manually sourced data points
• Reports and queries
  • Audit queries to validate imported data
  • Determine best reports for leadership view of faculty status

Security & Access Management

Technical Requirements

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

• Import users for launch
  • System Admins
  • Leadership
  • Admin Staff
• 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

Communications & Outreach

Technical Requirements

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

• For Admin Staff
  • Message templates for common communications
    
    • Define common messages
    • General message templates for ad-hoc announcements via email