btots web beta testing kickoff meeting february 2, 2012

BTOTS Web Beta TestingKickoff Meeting

February 2, 2012

Welcome Parent Infant Program to the

exciting world of BTOTS!

BTOTS Web Beta Testing Basics

• Purpose• Goals• Timeline• Using BTOTS Web during beta testing• Major controls• User interface in BTOTS Web• Data verification• Data migration clean-up

BTOTS Web Beta Testing Kickoff Meeting, February 2, 2012

Purpose

• Validate that the system is right– Validate that the system is capturing the right information (i.e., is it

capturing the right data in the right way)• Verify the system is correct

– Verify the system is working as designed (i.e., is it allowing you to enter and work with the data as intended by the developers)

• Capture system performance information– Is the system usable with the intended load of users

• Confirm compatibility with EI program processes– Ensure that each program’s internal processes are compatible


Beta Testing Goals

Beta Testing Goals1.Identify and prioritize defects

– Defects vs. bugs– Over 370,000 lines of code

(~7,400 single spaced pages)

2.Resolve critical defects before release– Ensure that critical issues have been resolved– Have a plan for resolving non-critical issues

3.Improve system usability– Identify areas of confusion or slow data entry– Have a plan for improving trouble spots


Project Goals•Complete •High Quality•Maintainable•Usable•High Value

Timeline


Timeline


2. Beta Testing Finish: Status: In-progressActivities Responsible Deadline Status Provider kickoff training MDSC & Baby

WatchFeb 2nd, 1 – 3 pm

Done

USDB training USDB, Baby Watch, MDSC

Before pre-deploy 1st Session Complete

Beta checklists Baby Watch Start of beta testing Done Beta testing Providers February 6, 2012

Load testing MDSC & Providers

Week of Mar 5th

Report Server Optimization MDSC March 5, 2012 Data verification checklist

createdMDSC March 6, 2012

Data verification complete Providers Deploy -1 week

Timeline

Beta TestingThrough first of April

Pre-deployFirst of April

•Beta checklists complete•Critical issues resolved•Critical reports in place•Data verification passes•Load testing passes•Data Entry Training


DeploymentMid-April

•Data clean-up complete•Provide supportProvider TrainingDeploy + 2 Months

•Non-critical issues resolved•Additional online help•Additional staff training

* Estimated dates based on pre-conditions being met

Getting Started

• Provider Beta Testing– List of beta tester emails and

reset codes will be provided

• Beta Tester Accounts– “Password Reset” Email will be

sent to each beta test account– Follow the instructions to enter

a new password


Password Reset Email

Reset Password Page

Getting Started

• https://btots.health.utah.gov• Login to your account

– Dashboard (successful)– Account not verified (contact support)

• Beta Test User Accounts– Administrator Accounts– Data Entry Accounts

• Browser Support– Firefox, Chrome, Safari,

Internet Explorer (preferably IE 9.0)– If unable to continue try one of the

other preferred browsers (bold above)


Account not verified message

Dashboard after Login

Navigating BTOTS Web


Account Information – account links and logout



Section Tabs – dropdown menus for major actions



Quick Links – common actions and quick child locator



Child Identifier – identifying information for the child



Child Actions – next steps for the child (previously on the left)



Edit Links – click to edit child information



Family Units – family groupings or households

Other Contact

f

Primary Family

Family 1

a b c

Additional Family

Family 2

d e


Multiple Tabs•Each child folder is opened in a new tab (or window)Keyboard Use•Press “Alt” key for shortcuts(Firefox, Chrome, Safari)•“Spacebar” for checkboxes and radio buttonsPrivacy Screen•Displayed after no activity


Privacy Screen

Multiple Tabs

Shortcuts

Major Controls

Auto-complete•Partial matchesSortable Tables•Click table header to sortDate Picker•Arrow keys•Today’s date (“t”)•Default date•Pop-up


Auto-complete

Sortable Tables

Date Picker

Major Controls

Person Picker•Matches with existing people in the system•Mechanism to add a new person to the system


12

3

Data Verification & Data Cleanup

Data Verification

Data Cleanup•A few children from each program are in an invalid state (e.g., activation dates don’t line up correctly due to multiple transfers)•We will be providing you with child ID’s to fix in BTOTS Classic during beta testing


Beta Testing Procedures

• Three tracks:– Admin [early intervention (EI) and Parent-Infant Program

(PIP)]– EI data entry– PIP data entry

• How beta testers will communicate with BWEIP• How BWEIP will communicate with beta testers• Compatibility of internal program processes with

BTOTS Web


Admin Beta Testing Track

• BWEIP point-of-contact is Chris Wnek• Focus will be on areas/tasks that EI and PIP

administrators will use– Some examples:

• Setting up user accounts• Entering employee records• Comprehensive System of Personnel Development


EI Data Entry Beta Testing Track

• Assigned BWEIP point-of-contact or BTOTS Helpline • Focus on areas/tasks that EI data enterers and non

administrative staff will use– Some examples:

• EI-only referrals• PIP referrals• Assessments• IFSPs• Service visits• Exits and deactivations


PIP BVI/PIP DHH Data Entry

Beta Testing Track• Assigned BWEIP point-of-contact or BTOTS Helpline• Focus on areas/tasks that non administrative PIP

staff will use– Examples: • PIP referrals• PIP-specific vision and hearing information• PIP visits


Beta Testing Schedules

• Six-week schedule for each beta testing track– Schedule for each week will be posted Monday morning as

an Excel file on the BWEIP website and also emailed to beta testers • utahbabywatch.org > For EI Providers > BTOTS > BTOTS Web beta

• Each week, the beta tester will:– Attempt each activity in the schedule and add information

to the Excel file such as child IDs and notes/comments– Save the Excel file as his or her name, e.g., “JohnDoe,” on

his or her computer– Email the Excel file to the program’s assigned BWEIP point-

of-contact


Beta Testers’ Communication with BWEIP

• Support link on beta test site– Use for reporting bugs, software problems, misspellings,

incorrect drop-down lists

• Email or call your BWEIP point-of-contact– Use if you have procedural questions

• BTOTS Helpline (1-801-584-8222)– Use the helpline if your BWEIP point-of-contact is

unavailable when you need assistance


Compatibility of Program Processes with BTOTS Web

• During beta testing, programs will be able to assess how changes in the user interface in BTOTS Web (compared to that in BTOTS Classic) may affect their internal processes– For example, the data entry process for parent/guardian

vs. non parent/guardian referrals will differ in BTOTS Web (whereas it was identical in BTOTS Classic)

– How will this data entry change impact how programs handle parent/guardian vs. non parent/guardian referrals?• There may be no change for some programs but not others• Programs will need to determine whether internal processes will

be affected by how data entry occurs in BTOTS Web


Provider Questions?

Provider Concerns?

btots web beta testing kickoff meeting february 2, 2012

Documents

beta testing finish

system usable

right data

beta test accountfollow

right information

slow data entryhave

right wayverify

mdscbefore pre