We need to see the overall picture of a student’s behavior history so that appropriate interventions can be created and monitored to support the student. There may be differences to the contents of the graphs/charts beneath the graphs when users have our products vs. integrating data from elsewhere.
Design:
Using Powerschool
User Story
As a teacher user, I need to see a full picture of the student’s history of behavior so that I can provide the student with appropriate tools and intervention plans to help them reach their potential in this area.
UI
To view the number and frequency of incident reports, user clicks on Behavior Tab.
Acceptance Criteria
Follow same rules for top section containing the student demographics, Academic Needs, Other Details and the Year Selector drop down explained in Overview.
Powerschool Integration
Mapping (See Behavior Mapping | Powerschool)
Use INCIDENT_Student_ID
Using RethinkEd
User Story
As a teacher user, I need to see a full picture of the student’s history of behavior so that I can provide the student with appropriate tools and intervention plans to help them reach their potential in this area.
UI
Acceptance Criteria