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 45 Next »

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:

  • We need to update Settings for Rating Scale since user will select which rating(s) count toward meeting the criteria--as per Tracey. See section: Goal / No objectives below.

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.

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:

  • Users may do the following for objective1

    • At least [custom enter less than or equal to goal] of opportunities per day for [custom enter] 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] 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.

    • The final objective shows the highest percentage of opportunities per [unit selected in goal] for the number of consecutive [unit selected in goal].

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

  • Given user edits the goal statement, those changes will populate in the final objective.


Done Screen

User Story:

UI:

Acceptance Criteria:


Error Message: This is a View / Edit Flow

User Story:

UI:

Acceptance Criteria:


Section 4 Goal selection

UI:

  • User sees timeline.

Set Goal:

  • To edit the goal the User selects choices from drop downs

  • To edit the Customized Goal Statement the User clicks inside the Goal statement text box and enters additional information before and/or after the hard coded sentence.

  • To go back to previous slide, User clicks on Go back button.

  • To continue to track objectives, User clicks on Continue.

  • To save and exit the modal, the user clicks on Save and exit.

 

 

  • Select No

    • If the User does not want to track objectives, the User selects No from drop down or leaves it as the default.

    Select Yes

    • To track objectives, the User selects Yes.

     

    Selecting Yes shows the goal the User set in Goal Selection section.

    Selecting Yes opens 3 objectives fields.

    • To select mastery criteria for each of the objectives, the User selects from the drop down fields.

    • To customize objective definition, the User clicks inside text field and types.

    • To remove an objective, the user clicks on the x next to the objective.

    • To add a new objective, the User clicks on +Add new objective.

     

    • To go back to previous slide, User clicks on Go back button.

    • To continue to track objectives, User clicks on Continue.

    • To save and exit the modal, the user clicks on Save and exit.

     

Business Rules: (copy of old specs)

  • Set goal is required.

  • We will show a default mastery criteria based on the account settings.

  • The format of the mastery criteria is dependent on the data collection type

  • The goal sentence is based on the data collection type. It will be formatted as:

    • Increase: STUDENT NAME will increase BEHAVIOR NAME to INSERT MASTERY CRITERIA.

  • If the user updates the mastery criteria, the hard-coded goal definition sentence will update as well.

  • The mastery criteria will populate a hard-coded sentence in the goal definition box. This sentence cannot be edited. However, custom text may be entered before and/or after this sentence.

 

Timeline:

  • Timeline has Select Tool and Record Baseline colored in blue with white check mark.

  • Set Goal in Timeline is outlined in blue.

Buttons:

  • Back takes user to Baseline selection for Rating Scale.

  • Continue takes user to Track behaviors for Rating Scale.

  • Save and exits, saves the behavior tracking as a draft and exits the modal.

  • Timeline has Select Tool, Record Baseline, Set Goal colored in blue with white check mark and Track objectives outlined in blue.

 

Select No for tracking objectives.

  • Track objectives field contains:

    • No

    • Yes

  • Default selection is No.

  • Selecting Save & Go Back button goes to Goal Selection screen.

  • Selecting Save & Continue goes to Set Self-Monitoring Screen.

Select Yes to track objectives:

  • 3 objectives will appear as the default.

  • If the User clicks the X next to an objective, the objective is removed.

  • If the User clicks on +Add new objective, a field for a new objective will appear.

  • For each objective, the user must enter a mastery criteria.

  • If a User does not create mastery criteria, then the objective cannot be used for behavior tracking.

  • The objective definition box will include a hard-coded sentence based on the mastery criteria. The user may not change this sentence, but may add custom text before and/or after this sentence.

  • If objectives are selected, the user must include at least 1 objective.

  • Rating Scale only has Increase Behavior.

  • Increase Behavior

    • The mastery criteria must increase for each objective. Meaning, the criteria for objective 1 cannot be higher than the criteria for objective 2.

    • The mastery criteria for the last objective must be equal to the mastery criteria for the goal.

    • By default, each objective criteria will be evenly distributed in an increasing fashion from the first objective to the last. For example, if my goal is to increase time on task to 30 minutes & I have included 3 objectives, my first objective will be to increase to 10 minutes, my second objective will be to increase to 20 minutes, & my 3rd objective will be to increase to 30 minutes.

    • This logic will continue & the mastery criteria will update as I add and remove objectives.

    • Once I begin editing the mastery criteria for any objective, the system will no longer update the criteria for any other objective.

  • Decrease Behavior

    • The mastery criteria must decrease for each objective. Meaning, the criteria for objective 1 cannot be lower than the criteria for objective 2.

    • The mastery criteria for the last objective must be equal to the mastery criteria for the goal.

    • By default, each objective criteria will be evenly distributed in increments of 10 in a decreasing fashion from the first objective to the last. For example, if my goal is to decrease tantrums to 0 minutes & I have included 3 objectives, my first objective will be to decrease to 20 minutes, my second objective will be to decrease to 10 minutes, & my 3rd objective will be to decrease to 0 minutes.

    • This logic will continue & the mastery criteria will update as I add and remove objectives.

    • Once I begin editing the mastery criteria for any objective, the system will no longer update the criteria for any other objective.

  • The format of the mastery criteria is dependent on the data collection type

  • The objective definition sentence is based on the data collection type. It will be formatted as:

    • Increase: STUDENT NAME will increase BEHAVIOR NAME to INSERT MASTERY CRITERIA.

    • Decrease: STUDENT NAME will decrease BEHAVIOR NAME to INSERT MASTERY CRITERIA.

  • If the user updates the mastery criteria, the hard-coded objective definition sentence will update as well.

  • If User clicks on +Add new objective, an objective 4 section is added.

  • User can have up to 5 objectives.

  • Additional objectives follow same rules for increase and decrease behavior.

 

Buttons:

  • To continue to Done screen for Rating Scale, the User selects the Continue button.

  • To return to the goal selection screen for Rating Scale, the User selects Go Back.

  • To save the work and exit the modal, user clicks on Save and exit button.


Done Screen

UI:

  • User sees Done screen with Success message.

 

 


Business Rules:

  • Timeline includes blue fill-in with white checkmarks for all items.

  • If the User has successfully completed all the previous screens for Rating Scale then they will see the Success message.

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

Active Status (See: View/Edit Behavior Tracking)


Updated Design To Set Goal and Objectives: User Feedback

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

  • Rating Scale is an option when user selects Increase behavior.

  • Rating Scale does not have intensity.

  • Given user has selected increase behavior, they will see Rating Scale as a choice.

    • Given user has selected Rating Scale, they will not see intensity level in set up Behavior Tracking. (See: Select Behavior Section 2: Data Collection-Select Measurement Tool)

  • Given user as set goal and selected No for Objectives, then we will show the goal statement. (See Frequency Section: Updated Design to Set Goal and Objectives: User Feedback Look for Selecting No for Objectives in Acceptance Criteria.

    • The user selects No first, then we show the Goal statement.

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 customize objective statement(s) criteria, user clicks on fields and makes a selection.

  • To view a customized objective statement, user clicks on Show Objective Statement.

  • To Hide and objective statement, user clicks on Hide Objective Statement.

Acceptance Criteria

  • Follow same rules for Checklist when editing objective criteria and objective statements. See section: Updated Design To Set Goal and Objectives: User Feedback

  • No labels