Decrease Duration and Frequency | Create Behavior | Data Tracking | MTSS Suite

We need a way to set up the Frequency and Duration as a combination data collection method so Users who select it can create the parameters for data collection using the this method.

 

 

Design: https://www.figma.com/file/gdwMnbpudJxuzVrORrOGvd/Ed-Member-Site-UX?node-id=28422%3A235770&t=wbeRLWvz9ZmCD1uo-0


 

Section 1: Select Behavior

User Story

As a teacher or admin user who is setting up behavior tracking I need a select/ create a behavior to decrease and decide on attaching it to an existing plan so that I then select Frequency & Duration 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.

 

(Create Behavior Tracking)
  • To go to the next slide, user clicks on Continue

  • To view more information about Frequency & Duration (Increase Behavior) data type, user clicks on or hovers over the information icon next to Frequency and Duration.

  • To select Frequency & Duration as the data type, user clicks inside circle next to Frequency and Duration.

 

  • 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 Decrease from the drop down, then the following data types are available:

    • Frequency

    • Duration

    • Interval

    • Frequency and Duration

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

  • Frequency & Duration Information Icon (See image: Hover/Click)

    • Given user hovers/clicks on Frequency & Duration icon then the message reads:

      • The combination of the number of times (Frequency) and the length of time (Duration) a behavior occurs.


Error State: Existing Active 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 Frequency & Duration (Decrease Behavior) for a specific behavior already in place, then we will show this message.

 

 

 

 

 

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 (See image: Error Message)

      • Error message reads: There is already an active Behavior Tracking for this behavior name and data method. Please select a different data type or delete.

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


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.

 

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.

  • Skip Baseline Flow

    • Given user does not select Record Baseline button but instead selects Continue button, they are taken to set goal slide


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

See Settings for contents of fields for the goal statement.

 


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

The goal reads:

  • No more than [3] [minutes] and [5] times per [day] for [2] consecutive [days].

  • The following fields in red auto-populate and are locked in the objectives. (They are shown as grayed out in the image.)

    • No more than [2] [minutes] and [5} times per [day] for [2] consecutive [days].

  • The auto-populated fields shown in red (grayed-out in the image) can be changed in the goal statement and then the edits will populate through the objectives.

 

  • User can change the non-grayed out fields in the objectives but with constraints based on the goal statement.

  • The goal reads:

    • No more than [3] [minutes] and [5] times per [day] for [2] consecutive [days].

    • We auto-populate the calculation in each objective for the above fields by equally distributing the increments and end with the last objective being the same as the goal. The increments decrease with each objective.

    • Given the user edits an objective(s), then each successive objective needs to be equal to or no more than the previous one for these fields but does not become less than the goal.

 


Done

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.

 


 

Error messages--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.