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

Overview

This is the creation process in setting up a Check-In/Check-Out (CICO) tool for a student, designed to monitor target behaviors. Users must define the behaviors for tracking, either from the behavior bank or by creating new behaviors. Additionally, the user can interact with action buttons to print data sheets, record or view data, and manage the status of the tool.

Figma

https://www.figma.com/design/6tpmUIqjsH6mk6mQ7ifeEG/Checkin-Checkout?node-id=565-3410&t=IGlfAUOgDaGtsOAu-1

Feature

Project 223101: MTSS | Check In/Check Out

User Story

As a user, I need to create a Check-In/Check-Out tool for a student by selecting or entering target behaviors, so that I can effectively track and manage the student's progress on the defined behaviors.

UI Description

  1. Page Heading: "Create Check-In, Check-Out Tool"

  2. Student Name Display: The student's first and last name is shown below the heading to ensure the user knows which student they are configuring the tool for.

  3. Step Indicator:

    • Current Step displays as dark grey in the indicator. The indicator displays the other step as light grey.

    • Behaviors pill container (current step)

    • Data Settings pill container

  4. Behaviors Screen:

    • Users must enter at least one target behavior and has the option to enter up to three target behaviors.

    • Display dropdown menu input fields with labels

      • Target Behavior #1

        • Required Field

    • Add Target Behavior Button: User selects ‘Add Target Behavior’ button to add additional Target Behavior and Description input fields. The button is hidden when the user has three target behavior and description input fields displayed on the screen. User can remove addition fields by selecting the ‘Delete’ icon.

      • Target Behavior #2 (Optional)

        • Optional Field

      • Target Behavior #3 (Optional)

        • Optional Field

    • Dropdown menu input field values:

      • Search bar at the top of the dropdown menu to search for behaviors

      • For each target behavior, a dropdown allows the user to select from the existing behavior bank or choose "Other" to enter a new behavior.

        • Behaviors included in the Student Behavior Bank and Admin Settings Behavior Bank

        • Custom input field displays as text input field with ‘Other’ as placeholder text that the user types over.

    • Behavior descriptions are text fields where users can describe the behavior being tracked.

      • Required fields that display to the right of each ‘Target Behavior’ dropdown menu selection

      • Labels for text area fields: ‘Behavior Description’

      • Support multiple lines of text.

  5. Continue Button:

    • User selects ‘Continue’ button to proceed to the next screen of the CICO tool creation process.

    • Validation Warning Errors display on input field labels and containers if the user does not enter details in the required fields.

  6. Action Buttons:

    • Print Data Sheets: Opens a modal to print either blank or pre-filled data sheets.

    • Record Data: Takes the user to the Data Express CICO page to enter student data.

    • View Data: Navigates user to Data Express > View Data and displays the recorded data for the student.

    • Delete:

      • Displays instead of Change Status button during tool creation, just like Behavior Tracking setup

      • Deletes the CICO tool and returns the user to the Student Dashboard > Behavior Support > CICO screen

  7. Discussion Panel:

    • User will be able to add team members or admin to the discussion and send discussion messages. (Utilize Existing Discussion Panel functionality)

User Interaction and Validation Notes

  1. Behavior Setup:

    • The user must define at least one behavior for the CICO tool to progress.

    • Selecting ‘Other’ in the Target Behavior dropdown menu allows the user to enter a new behavior. This new behavior is automatically added to the student’s behavior bank once the form is submitted.

    • The user should be able to add up to three Target Behavior input fields and Description input fields using the ‘Add Target Behavior’ button.

    • The user should be able to remove Target Behavior #2 and/or Target Behavior #3 by selecting the ‘Delete’ icon.

  2. Data Entry Validation:

    • All required fields must be completed for the user to proceed.

    • If the user attempts to continue without completing the required fields, validation error messages will prompt the completion of the missing fields.

      • Target Behavior Validation: Input field label turns red, container is red, helper text below field: ‘Behavior Required’.

      • Behavior Description Validation: Input field label turns red, container is red, helper text below field: ‘Description Required’

  3. Action Buttons:

    • Print Data Sheets:

      • Verify that the user can open the 'Create Data Sheets' modal to print either blank or pre-filled data sheets and the number of pages to print.

      • Verify that the 'Print Data Sheets' button is active for a Check-In/Check-Out tool in Active, Mastered, or Archived statuses. 

      • Verify that the 'Print Data Sheets' button is inactive for a Check-In/Check-Out tool in Draft Status. 

    • Record Data:

      • Verify that the 'Record Data' button is active for a Check-In/Check-Out Tool that is in Active Status

      • Verify that the 'Record Data' button on an Active status Check-In/Check-Out tool navigates the user to Data Express on the Check-In/Check-Out tab with the specific Check-In/Check-Out tool displayed on the screen. 

      • Verify that the 'Record Data' button is inactive for a Check-In/Check-Out tool in the statuses: Draft, Mastered, Archived

    • View Data:

      • Verify that the 'View Data' button is inactive until at least one data entry is recorded for the Check-In/Check-Out tool 

        • This logic applies to all statuses: Draft, Active, Mastered, Archived

      • Verify that the 'View Data' button is active when at least one data entry has been recorded for the Check-In/Check-Out tool

        • This logic applies to statuses: Active, Mastered, Archived

    • Delete (during creation):

      • Verify that when the user is on the Behaviors screen of the Create Check-In/Check-Out tool, the 'Delete' button displays in the header and is active. 

      • Verify that upon selecting the 'Delete' button, the warning confirmation pop-up displays to the user:

        • Heading: 'Delete Tool?'

        • Description Text: 'This action cannot be undone.'

        • Cancel: Cancels the action and returns the user to the Behaviors screen of the Create Check-In/Check-Out tool

        • Delete: Deletes the tool and returns user to the Student Dashboard > Behavior Support > Check-In/Check-Out screen.

Workflow Description

  1. The user navigates to the "Create Check-In/Check-Out Tool" screen, sees the student’s name, and starts entering behaviors.

  2. The user must define at least one target behavior and its description. If the user selects "Other," they can input a new behavior, which gets added to the student’s behavior bank.

  3. Once behaviors are entered, the user can proceed by clicking the "Continue" button.

  4. If any required fields are missing, the user is alerted and prompted to complete them before continuing.

  • No labels