CALPADS UAT EOY Kick-off Meeting April 4, 2012 UAT Kick-off 4/4/2012

Introductions and Ground Rules CDE / CSIS Participants IBM Participants Ground Rules Mute phones while listening (*6 to mute and un-mute) Do not place your phone on HOLD Silence cell phones Introduce yourself (name and LEA) when speaking One conversation at a time UAT Kick-off 4/4/2012

Agenda Meeting Objectives UAT Objectives UAT Process and Schedule EOY UAT Training Requirements LEA Activities and Responsibilities UAT Communications Next Steps Questions UAT Kick-off 4/4/2012

Meeting Objectives Provide an overview of the UAT process Provide a review of the UAT schedule and time commitment Inform LEA participants of their roles and responsibility Address questions / concerns from the participants UAT Kick-off 4/4/2012

UAT Objectives Exercise all CALPADS EOY functionality from the LEA’s environment to detect and resolve application defects Execute CALPADS EOY functionality in a “production-like” hardware and software environment to validate readiness for production implementation Confirm EOY functionality meets functional requirements UAT Kick-off 4/4/2012

EOY UAT Process and Schedule EOY UAT will be conducted in a single phase (with different focuses each week) to exercise all EOY functionality EOY UAT will be conducted in the CALPADS Pre-production environment, which is configured identical to the Production environment CALPADS Pre-production environment has been refreshed with CALPADS Production ODS data as of April 11, 2012 UAT user IDs and passwords will be created and communicated via email on the LEA UAT start date UAT Kick-off 4/4/2012

EOY UAT Process and Schedule EOY UAT execution is anticipated to be five weeks in duration (4/16/12 – 5/18/12) During the UAT process, the CALPADS Pre-production environment will be available daily from 6:00 am to 10:00 pm All EOY functionality (all file format submissions, extracts, ODS reports, and snapshot certification reports) will be available when UAT begins, with the exception of the new SCTE file functions UAT Kick-off 4/4/2012

EOY UAT Process and Schedule 4/16-4/20 4/23- 427 4/30-5/4 5/7-5/11 5/14-5/18 EOY UAT Modules/Functions TW1 TW2 TW3 TW4 TW5 EOY 2 Program Participation   EOY 4 Student Waivers EOY 3 Discipline EOY 1 Course Completion Wrap Up Legend Testing Testing continues if needed 8 UAT Kick-off 4/4/2012

EOY UAT Process and Schedule LEAs will be provided UAT test scenarios and the test scenarios will be available on the UAT site UAT test scenarios define business scenarios to exercise EOY functionality UAT Kick-off 4/4/2012

EOY UAT Process and Schedule EOY UAT Execution Log Module Function Business Process Test Scenario ID Test Scenario Pass / Fail Issue Reported? (Y/N) # of Times Executed Last Execution Date Comments 1.0 - Security 1.1 - EOY 2 Roles Assign Roles 1.1.1 Assign EOY 2 Report roles   1.1.2 Assign EOY 2 Certification roles 2.0 - Administration 2.1 - Manage Local Codes Map Local Codes 2.1.1 Map Local EOY 2 Codes to State Course Codes 3.0 - Program Participation / Homeless Students 3.1 - Program Participation Data - Online Add/Maintain Program Paticipation Data 3.1.1 Add a new Program Participation record 3.1.2 Add/Update/Delete Program Participation Records 3.2 - Program Participation Data - Batch Upload File 3.2.1 Submit Student Program (SPRG) File Review submission 3.2.3 View Passed Records 3.2.4 View Rejected Records and resolve errors (Refer to Scenario 3.4.2) Post Data 3.2.5 Post or Exclude data 10 UAT Kick-off 4/4/2012

EOY UAT Process and Schedule EOY UAT Test Scenario Details Test Scenario ID Test Scenario User Documentation Reference Objective Setup & Dependencies Testing Path Expected Outcome 1.1.1 Assign EOY 2 Report roles LEA Admin Manual - Section 2.2.1.1 To grant a user account the appropriate access to Fall 2 report functionality. This test scenario will confirm the Fall 2 Report roles have appropriate access to the Report functionality. Successful Login and access to the Administration User Security links Navigate to Admin --> User Security --> Search/Maintain User 1. Successfully assign the following Program roles to a user account: - Program 2. Validate roles were successfully assigned by successfully accessing the ODS and Snapshot Reports links for the EOY 2 reports 1.1.2 Assign EOY 2 Certification roles To grant a user account the appropriate access to Fall 2 Certification functionality. This test scenario will confirm the Fall 2 Certification roles have appropriate access to the Certification functionality. 1. Successfully assign the following roles to a user account: - EOY 2 Data Collection Certifier 2. Validate roles were successfully assigned by successfully accessing the Certification Status Screens for EOY 2 Snapshots 11 UAT Kick-off 4/4/2012

EOY UAT Process and Schedule LEAs should conduct: 50% scenario based testing 50% unscripted “sandbox” testing LEAs may test at their own pace UAT scenarios will be available on the CALPADS UAT FTP site prior to the start of UAT at: ftp://ftp.cde.ca.gov/calpads-uat/ UAT Kick-off 4/4/2012

EOY UAT Process and Schedule UAT Issue Reporting Process LEA UAT participants should report defects as they are identified by emailing the UAT email account: calpadsuat-sd@cde.ca.gov LEA UAT participants should bring up issues by: Emailing the UAT email account; or Bringing them up during the two UAT Check Point calls NOTE: DO NOT report UAT defects through the CALPADS webform OR through submitted Execution Logs 13 UAT Kick-off 1/25/2012

EOY UAT Process and Schedule When requesting HELP though email, include the following : Subject (include the word “help”) Your name Phone number CALPADS UAT user ID Job # (if applicable) Description of the issue UAT Kick-off 4/4/2012

EOY UAT Process and Schedule When reporting a PROBLEM though email, include the following: Subject Your name Phone number Bread crumb Describe what you were doing, what you expected from the system, and what happened UAT Kick-off 4/4/2012

EOY UAT Process and Schedule System updates to address UAT defects will be released to the CALPADS Pre-production environment on Wednesday evenings. However, Report fixes, which do not require a new system build will be done as defects are found and fixed UAT Release notes will be published on Thursdays following the Wednesday software release UAT Known Issues will be published twice a week – Tuesdays and Thursdays Additional system updates may occur as needed to address critical issues identified during testing UAT Kick-off 4/4/2012

EOY UAT Training Requirements Users from each participating LEA should have attended the EOY training course (includes EOY1, EOY2, EOY3, EOY4) EOY Training will cover: Overview - EOY1, EOY2, EOY3, EOY4 Preparation for all EOYs Data Submission (ODS) for all EOYs Data Certification (Snapshot) for all EOYs 17 UAT Kick-off 4/4/2012 17

LEA Activities and Responsibilities Estimated UAT Time Commitment UAT Activity Time Required Description UAT Training and Meeting Participation 6 Hours Total Attend one hour EOY kickoff meeting Attend one 2 ½ hour training session Attend five 30 minute UAT Check Point meetings UAT Testing 10 – 15 Hours / wk during UAT Anticipate ten to fifteen hours per week to execute test scenarios, conduct unscripted testing, and document test results 18 UAT Kick-off 4/4/2012 18

LEA Activities and Responsibilities Attend EOY Kick Off and Training Attend and participate in UAT Check Point meetings Execute test scenarios and conduct unscripted testing Submit results once a week and report defects (when found) Retest reported defects UAT Kick-off 4/4/2012

UAT Communications CALPADS UAT Email for defect reporting, issues, and questions  calpadsuat-sd@cde.ca.gov UAT Weekly Check Point Meetings WebEx URL: http://csis.webex.com WebEx Phone: 888-426-6840 Participant Code: 4603184 UAT Service Desk Phone: 916-325-9210 UAT Documents posted at ftp://ftp.cde.ca.gov/calpads-uat/ 20 UAT Kick-off 1/25/2012 20

Next Steps Attend EOY Training on April 11, 2012 Await email from CDE confirming start of LEA UAT for April 16, 2012 Login and execute test scenarios and conduct unscripted testing Attend and participate in UAT Check Point meetings Submit results once a week and report defects (when found) 21 UAT Kick-off 4/4/2012 21

Questions UAT Kick-off 4/4/2012