Dean Fortin – Massachusetts WIC 23 July 2014

System Testing Objectives  Verify hardware  Verify software  Verify hardware/software interaction  Verify system to system interaction  Verified against defined requirements

System Requirements  Functional Issue benefits to participants Redeem benefits at vendors Pay vendors for purchases  Non-functional Accomplish task within specified time Operate with specified number of users  Documentation

WIC EBT Requirements  Universal MIS-EBT Interface Specification  WIC EBT Operating Rules  WIC EBT Technical Implementation Guide  Federal Register – Implementation Rules  NUPC Requirements

System Design/Development  Project Kickoff Meeting Team concept with one goal Schedule milestones Open Communications Accountability  Joint Application Design Sessions Requirements breakdown Interface specification adjustment Refine schedule

Testing Process  Use Cases and Test Cases  Unit Testing  Integration Testing within each system  Functional Testing within each system  Testing Integration of Unfinished Systems Schedule, communication, accountability Special testing tools and utilities  Interface Test Scripts

Using Test Results  Get results from each level of testing  Incorporate feedback into the development process Weekly meetings ○ Each contractor (including WIC office) ○ Project Managers ○ Developers, Operations, Vendors, etc. Daily touch point  Formal test results documented

Communicating with FNS  Monthly EBT status call Plans Results Status  Weekly call as Pilot approaches Plans Results Status Approval