Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

Design:


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 Checklist 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

Image RemovedImage Added
  • To view more information about the Checklist data type, user clicks on or hovers over the information icon next to Checklist.

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

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

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

Image RemovedImage Added

Acceptance Criteria:

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.

Checklist Information Icon (See image: Information Icon)

  • Given user hovers over/clicks on the Checklist information icon, they will see the checklist definition.

  • Checklist definition reads:

    • A response of Yes or No to the question: Did the behavior occur?

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 Checklist 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.

Baseline Selection

User Story

UI

Acceptance CriteriaAs 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.

Image Added

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

Image Added

Image AddedImage Added

Data Express Flow

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

Image Added
  • 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.

Image Added
  • User sees Behavior Tracking Goal/Objective screen

Image Added

Skip Baseline Flow

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

Image Added
  • User sees Set Goal Screen

Image Added

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.

    • 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 image: Return to Behavior Tracking)

Skip Baseline Flow

Section 2: Baseline Selection

UI:

  • User sees timeline.

UI: Select No

  • To select No, the User clicks on down arrow in selection field and selects No or leaves it as the default state.

  • To Save and Record baseline in Data Express, user clicks on Record baseline button.

  • To go back to previous screen (Select data type), User selects Go Back button.

Select Yes:

  • To select Yes, the User clicks on down arrow in selection field and selects Yes.

  • The user is prompted to go to Data Express and select summary to include baseline data.

  • To Record baseline in Data Express, user clicks on Record baseline button and completes the baseline for the Checklist.

  • To return to previous screen, User clicks on Save & Go Back button.

  • To advance to the next section, User clicks on Save & Continue Button.

Business Rules:

  • If User has selected a tool, then Select tool will be filled in with blue and white checkmark in timeline.

  • If User has selected a tool, then Record Baseline is outlined in blue in timeline.

  • Default setting for Baseline selection is No.

  • Selecting Save & Go Back takes User to previous screen. (Select measurement tool)

  • If User Selects Yes or No, then Record baseline button is shown. (See Frequency Baseline for further explanation)

    • If the User selects Checklist, they are taken to Checklist in data express.

    • Selecting Go Back button takes User to Select Type screen.

  • If the user selects Yes in baseline field, then both the message “Visit Data Express and select summary to include your baseline data” and the Record Baseline button are shown. (See Image: Yes Baseline)

  • If User Selects Yes for Baseline, then Record baseline button takes User to record baseline data in Data Express for Checklist

  • Selecting Save & Continue button takes Users to Set Goal section.

  • Selecting Save & Go Back button takes User to Select Measurement Tool screen.


Section 3: Return from Recording Baseline

UI:

  • User sees timeline and success message.

  • User sees completed summary view.

Business Rules:

  • If User completes Baseline in Data express and returns to Create Behavior Tracking, the Timeline shows completion of Recorded Baseline with filled-in blue circle and white checkmark and success message.

  • If the User completed checklist in Data express, they see summary view.

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 definition 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.

  • 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.

  • 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.

  • 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.

Select No

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

  • 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 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.

Business Rules: (copy of old specs)

  • Users must select a goal.

  • 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.

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

    • Checklist only has Increase.

  • 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:

  • Go Back takes user to Baseline selection for Duration.

  • Continue takes user to Track behaviors for Duration.

  • 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.

  • Track objectives field contains:

    • No

    • Yes

    • Tracking objectives is optional.

  • Default selection is No.

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

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

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.

  • Checklist only has increase behavior as an option.

  • 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 additional objective section is added.

  • User can have up to 5 objectives.

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


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 for checklist, then they will see the Success message.

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

 

Active Status (See: View/Edit Behavior Tracking)

  • If the User has completed all parts of creating Behavior tracking and has recorded data, Print data sheets, Record Data, View Data, Change status are active buttons.

    • Print Data sheets button

    • Record Data button

      • If User sets up behavior tracking forChecklist and selects Record Data button, they are taken to Data express.

  • View Data button takes user to view data for checklist.


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

  • Checklist is an option when user selects Increase behavior.

  • Checklist does not have intensity.

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

    • Given user has selected Checklist, 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

Acceptance Criteria

  • Follow rules for including Objectives for all Data types. (See: Frequency Look for: Select Yes for Objectives in Acceptance Criteria. It is in the bottom section- Updated Design to Set Goal and Objectives: User Feedback.

  • See also Section Locking Fields from Frequency.

  • 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.

      • Note: User could have recorded data that exceeded the goal--Example entry: 90% of opportunities per day for 2 consecutive days.