Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 53 Current »

We need a way to set up the Rating Scale collection method so Users who select it can create the parameters for data collection using the this method.

Design: https://www.figma.com/file/6YgiTKZKFelfsc6fjYFIHQ/Behavior-Tracking?type=design&node-id=9-4968&mode=design&t=k7PDs4LflkZXp2jG-0


Select Behavior / Measurement Tool

User Story:

As a teacher or admin user who is setting up behavior tracking I need a select/ create a behavior to increase and decide on attaching it to an existing plan so that I then select Rating Scale as my data type.

UI:

  • To enter a behavior, user clicks on Select behavior field and selects from the behavior bank items or custom enters a behavior.

  • User selects increase or decrease in the field labeled “Do you want the student to increase or decrease this behavior?” for the desired outcome of the behavior.

  • User selects if the behavior is part of an existing field by clicking on the field labeled “Is this part of an existing plan? If so, which one?”. (Required field)

  • To delete the draft user clicks on Delete button or closes out of the modal.

  • To go to the next slide, user clicks on Continue

  • To view more information about the Rating Scale data type, user clicks on or hovers over the information icon next to Rating Scale.

  • To select Rating Scale as the data type, user clicks inside circle next to Rating Scale.

  • To advance to the next screen, user clicks on Continue.

  • To return to previous slide, user clicks Go back.

Acceptance Criteria:

Given I am a User with access to Behavior Support OR MTSS Intervention (all tools or Behavior Tracking enabled) and permission to view Behavior Support> Add/Edit Behaviors:

  • I will be able to create behavior tracking.

Create Behavior Tracking image contents:

  • Given a behavior is part of the behavior bank, then we will pre-fill the Define Behavior box.

  • Given a behavior is not part of the behavior bank, then the user is required to enter a definition of the behavior in the Define Behavior box.

  • Given user selects Increase from the drop down, then the following data types are available:

    • Frequency

    • Duration

    • Interval

    • Frequency and Duration

    • Checklist

    • Rating Scale

  • Behavior Tracking becomes active after a unique behavior, data method, and intensity selection (if applicable- Frequency, Duration, Frequency& Duration combined) have been selected and the user selects Continue.

Rating Scale Information Icon (See images: Younger Student, Older Student)

  • Given Rating Scale is selected for a younger student (Pre-K to Grade 5) and the user hovers/clicks over the icon, then the message reads:

    • A rating of the behavior occurrence. Example: Always, Sometimes, Never

  • Given Rating Scale is selected for an older student (Grade 6 to Grade 12) and the user hovers/clicks over the icon, then the message reads:

    • A rating of the behavior occurrence. Example: Always, A lot, Sometimes, A little, Never


Error State: Existing Behavior Tracking

User Story:

As an Admin or Educator who as set up Behavior Tracking many times, I need to be alerted if I am repeating a behavior and data collection method for a specific student so that I can keep everything straight for that student.

UI:

  • Given user has an active behavior tracking using Rating Scale for a specific behavior already in place, then we will show this message.

  • To delete the draft of behavior tracking, user selects Delete button or clicks on X to close.

  • To continue with the set up for this behavior, user clicks on a different data collection method.

Acceptance Criteria:

  • Given user select Continue button when the Behavior Tracking is lacking in the following combination of criteria, then we will show the error message:

    • unique behavior, data method, and intensity selection (if applicable- Frequency, Duration, Frequency& Duration combined)

  • Given user selects Continue button when the behavior Tracking DOES have the combination of unique behavior, data method and intensity selection (if applicable), then they DO NOT see the error message.

  • At this time, users will NOT be create an additional active behavior tracking using Rating Scale where the only difference is the selection of goal criteria that includes a different selection of (K-5: Always, Sometimes, Never and 6-12: Always, A lot, Sometimes---See Goal section below for more information.)


Baseline / No Baseline Selected

User Story:

As an Admin or Educator user who is setting up Behavior Tracking, I need options of recording my existing baseline data, entering baseline data I am taking right now, or skipping baseline data recording altogether so that I the process of setting up Behavior Tracking is easy.

UI:

  • User sees the select baseline screen.

  • To select either Yes, or No the user clicks on the drop down field and makes selection.

 

  • To record baseline data from either a selection of Yes, or No in the drop down, user clicks on Record Baseline button.

 

 

Data Express Flow

  • User enters baseline information for quick summary or detailed summary and then clicks I am done recording baseline button.

  • User sees prompt to return to Behavior Tracking to continue set up for Goal/Objectives.

  • User selects Yes and is returned to Behavior Tracking on the Goal/Objective scree.

  • User sees Behavior Tracking Goal/Objective screen

Skip Baseline Flow

  • To continue with Behavior Tracking Set up WITHOUT entering Baseline data, user clicks Continue Button.

Acceptance Criteria:

  • Baseline Selection screen contains dropdown where the default selection is Select. (See image: Default View)

  • User’s options in the dropdown include:

    • Yes

    • No

  • Given user selects either Yes or No from the drop down, we will show the same message and Record Baseline button. (See images: No Selected and Yes Selected)

    • Message reads: Visit Data Express to record you Baseline data.

Data Express Flow (See image: User enters baseline)

  • Given the user clicks on Record Baseline, then we take them to Record Baseline in Data Express landing on the Behavior Tab with the Behavior Listed along with the Data Collection Method.

    • Given the user has not yet set up the goal, then the Goal will read: No Goal has been added for this behavior.

    • User is then prompted to return to Behavior Tracking to continue set up for Goal/objectives once Baseline is concluded. (See image: Set up Goal)

    • Given user selects Yes, then we return them to Behavior Tracking with the Goal/Objective screen showing. (See images: Return to Behavior Tracking-Younger Student and Return to Behavior Tracking-older student)

    • Given the student for which the behavior tracking is being created is in grades K-5, then we will show the image: Return to Behavior Tracking-Younger Student.

    • Given the student for which the behavior tracking is being created is in grade 6-12, then we will show the image: Return to Behavior Tracking-Older Student.

Skip Baseline Flow

  • Given user does not select Record Baseline button but instead selects Continue button, they are taken to set goal slide for either younger or older student. (See image: Continue without Baseline).


Goal / No Objectives

User Story:

As an educator who is creating Behavior Tracking without objectives, I need to see an uncluttered creation screen so that I can select to customize the goal or keep it hidden from view so that I don’t get confused or overwhelmed by unnecessary information.

UI:

  • To select goal criteria, user clicks on fields for Step 1 Set Goal and makes selections.

  • To select No for objectives, user clicks on field for Step 2 Set Objectives and selects No from drop down.

Acceptance Criteria:

  • Goal Statement reads: At Least [X%] of opportunities which include a rating of [user selects criteria; different for younger and older-see below ] per [time period select A] for [integer select] consecutive [time period select B].

    • X% field ranges from 0% to 100%

    • time period select fields A and B contains text: minute, hour, session, day

    • integer select contains numbers ranges from 1 to 99

  • Given user select a time period in Time Period Select A field, it does not need to be the same selection in Time Period Select B field.

  • Given user selects No for including Objectives, then we will show the Goal box at the bottom of the page with the same information that is contained in the goal the user set.

User Selects Criteria

Older Student (Grades 6-12)

  • The drop down contains the following (Single Select):

    • Always

    • A lot or Always

    • Sometimes or Always or A lot

  • The default setting is: A lot or Always

  • Given user selects Always as the criteria for meeting the goal, then only data recordings of Always will be counted as meeting the goal criteria.

  • Given user selects A lot or Always as the criteria for meeting the goal, then data recordings of Always or A lot will be counted as meeting the goal.

  • Given user selects Sometimes, or Always or A lot as the criteria for meeting the goal, then only data recording of Sometimes or Always or A lot will be counted as meeting the goal.

Younger Student (Grade K-5)

  • The drop down contains the following: (Single Select):

    • Always

    • Sometimes or Always

  • The default setting is: Always

  • Given user selects Always as the criteria for meeting the goal, then only data recordings of Always will be counted as meeting the goal criteria.

  • Given user selects Sometimes or Always data recordings of Sometimes or Always will be counted as meeting the goal.

Goal with Objectives

User Story:

As an educator who is creating Behavior Tracking with objectives, I need to understand the connection between the goal and the objectives so that I can focus on creating a meaningful behavior tracking quickly and easily.

UI:

  • To include objectives, user clicks on Set Objectives field and selects Yes.

  • To edit objective(s), user clicks on the editable fields and selects desired responses.

  • To advance to the next screen, User clicks on Continue button.

Acceptance Criteria:

  • Goal Statement reads: At Least [X%] of opportunities which include a rating of [user selects criteria; different for younger and older] per [time period select A] for [integer select] consecutive [time period select B].

  • The fields for [time period select A] and [time period select B] for the goal populate throughout the objectives and cannot be changed within the objective.

    • Given user edits the goal for the fields [time period select A] and/or [time period select B], then those edits will populate throughout the objectives.

  • Given the user does not make a selection for field [user selects criteria: different for younger and older] , then the default of Always for younger students and A lot or Always will populate for each of the objectives and is not editable in the objectives.

    • Given the user edits the selection for field [user selects criteria: different for younger and older] within the goal statement, then their selection will populate throughout the objectives.

  • Users may change the following fields in the objectives but with constraints:

    • [X%]

    • [integer select]

For objective 1 (using days for time period select A and B as example):

  • At least [custom enter % less than or equal to goal] of opportunities per day for [custom enter integer lower than or equal to what is selected in the goal] consecutive days.

  • Users may do the following for objective 2

    • At least [custom enter less than or equal to goal and greater then or equal to first objective] of opportunities per day for [custom enter integer lower than or equal to what is selected in the goal BUT greater than or equal to what is selected in the first objective] consecutive days.

  • Given user has additional objectives, they follow this same pattern for each additional objective until the final objective.

    • The final objective is a repeat of the goal.

      • Mastery criteria for the behavior is triggered when user has completed all objectives in order and fulfilled the conditions of the goal.


Done Screen

User Story:

As an Admin or Teacher who is creating Behavior Tracking, I need to know that all steps of the Behavior Tracking Set up are complete so that I can begin tracking the behavior and/ or continue setting up Behavior Plan.

UI:

  • User sees Done screen with Success message.

 

Acceptance Criteria:

  • See Section 6 Done from Frequency for functionality of buttons.

Active Status (See: View/Edit Behavior Tracking)


Error Message: This is a View / Edit Flow

User Story:

As an admin or educator who is currently tracking data for a behavior and chooses to edit behavior tracking, I need to know if my edits will affect my data collection so that I will not mistakenly lose valuable data.

UI:

Entry path: Program Tools> Behavior> Behavior Tracking>View Behaviors > Classrooms > View

  • User selects Edit button.

Changing Goal

De-selecting Objectives

Changing Objectives

Acceptance Criteria:

  • These Error messages apply to all data types.

Changing goal

  • IF the user clicks edit and tries to change the goal and there is data that exists for the goal, then the user will see the error message: There is data for this goal. If you make changes and save or continue, you will lose the data for the saved goal.

  • If they save and exit or continue, they will lose data attached to old goal.

 

De-selecting Objectives

  • If the user clicks edit and tries to change to not track objectives and there is data that exists for the objectives, then the user will see error message: There is data for the objective(s). If you no longer track the objectives, you will lose data for the saved objectives.

  • If they save and exit or continue, they will lose data for the objectives.

 

Changing Objectives

  • If the user clicks edit and tries to change an objective and there is data that exists for the objective, then the user will see error message: Objective cannot be saved because there is data already collected for it.

  • If they save and exit or continue, they will lose data for the objective.


Future Development for Rating Scale and Self-Monitoring Connection---Save for later

User Story

As an admin or educator who compare the student and teacher recordings for the same behavior across tools (Rating Scale and Self-Monitoring), I need to know that both assessments are being calculated the same way

UI

  • Show SM create screen

  • Show BT Create Screen

Acceptance Criteria

Self-Monitoring Impact:

  • The student sees: Yes, At Times, No and these options need to match: Always, Sometimes, Never

  • We currently default calculate student’s responses of Yes for the younger students and Always or A lot for the older students as meeting the goal criteria-teacher/admin user will need to select their criteria in SM and we need a way to have it match Behavior tracking so graphs can be created to compare the teacher/student responses.

Younger Students:

  • Yes in Self-Monitoring = Always in Behavior Tracking

  • At times in Self-Monitoring = Sometimes in Behavior Tracking

  • No in Self-Monitoring = Never in Behavior Tracking

  • No labels