1. September Interface Kickoff Sunflower Project Statewide Management and Reporting Tool Update September 02, 2009

2. 2 Overview of Interface Test Overview: The objective of Interface Test is to verify that correct data is passed between Agency systems and SMART All new Agency SMART interfaces and spreadsheet uploads will be tested Interfaces are logically grouped into stages for testing Data conversion activities are excluded from Interface Test The DISC mainframe will be used as a conduit between Agency systems and SMART A primary contact on the Interface Team will be identified for each interface

3. 3 Project Update Interface Facts: The file naming standard is: XX.TOSMRT.AP02.XXXX.DYYMMDD.THHMMSS.in XX.FMSMRT.AP02.DYYMMDD.THHMMSS.out DA.GBSMRT.GL15.DYYMMDD.THHMMSS.out Date/Time will be used in the file naming standard as the file numbering solution Transmittal sheets will not be required except for interfaces requiring manual effort

4. 4 Roles and Responsibilities Development Team are Responsible for: Completing interface builds on schedule for interface testing Researching and resolving assigned defects Coordinating with DISC to establish mainframe file numbering and archiving procedures Maintaining defect status and resolution in Phire Working with assigned tester to troubleshoot defects Unit testing defect fixes Coordinating with the Database Administrator to migrate defect fixes to interface environment once they have been resolved

5. 5 Roles and Responsibilities Finance Team are Responsible for: Completing Functional Designs Providing support for interface team members Providing support for development team members Providing configuration values, creating configuration insert scripts, and manually configuring the Interface Test environment as needed Assisting with the resolution of functional issues Processing change request forms Determining the necessity of a change request Providing support for the spreadsheet uploads

6. 6 Roles and Responsibilities The Interface Team is Responsible for: Developing test scripts and conditions Executing test scripts in SMART Validating the expected results of an interface test Providing outbound error files to the DISC mainframe Logging System Investigation Requests (SIRs) for errors SIR Tracking Coordinating the schedule of SMART processes Providing agencies with configuration values required for testing Validating that Entry and Exit Criteria are met

7. 7 Interface Test Strategy SIR Tracking: The interface team will log and track SIRs in Phire SIRs will be assigned to the Development, Tech Arc, Security, and Finance teams The team leads will be responsible for assigning team members to resolve the defects Team leads can reassign SIRs to the appropriate team as needed The technical team will work with the finance team to resolve functional issues Request for code migrations must be logged in Phire Approval must be given by the development leads for code migrations Approval to close the SIR must be given by the interface team SIRs will be reviewed in the weekly interface test status meeting

8. 8 Interface Test Strategy Agency Error Notification: SMART will provide system generated error files to the Agencies via the DISC Mainframe Error files will contain the invalid data and a description of the error Error files will have the same file name as the inbound file, including the date/time stamp, except the file extension will be.err Error files will not be produced for outbound SMART interfaces Message logs containing statistical information will also be provided to Agencies via the DISC Mainframe Message logs will have the same file name as the inbound file, including the date/time stamp, except the file extension will be.log Agencies will actively check the DISC Mainframe for error files

9. 9 Interface Test Strategy Interface Test Filenames: All test files will have a “T” before the file direction Inbound files will have the following format: XX.TTOSMRT.AP02.XXXX.DYYMMDD.HHMMSS.in Outbound files will have the following format: XX.TFMSMRT.AP01.DYYMMDD.HHMMSS.out The filename for error files will be the same as the related interface but with a ‘.err’ suffix The filename for message log files will be the same as the related interface but with ‘.log’

10. 10 Interface Test Strategy Test Structure: The test stage structure is based on the time dependencies and logical grouping of interfaces within SMART Interface Test will consist of 6 successive stages Agencies are required to complete testing in the order of the test stages An Agency will only participate in stages which test interfaces used by that Agency Spreadsheet uploads will be tested in Cycle 6

11. 11 Interface Test Strategy Test Structure: Stage 1 – Outbound Configuration Interfaces (9/1/09 – 10/12/09): o Confirms that the outbound interface files are successfully processed in Agency systems o Provides SMART chartfield and vendor values to agencies for use in future testing stages o The initial download for INF01 – Vendor Outbound and INF15 – Chartfield Extract will occur on the first day of the testing period o Incremental updates (for INF01 only) will then be performed to provide deltas to the agencies o The outbound interface files in Stage 1 will not be segregated by agency

12. 12 Interface Test Strategy Test Structure: Stage 2 – Inbound Interfaces (10/5/09 – 11/18/09): o Confirms that the inbound interface files load successfully, without errors o Provides transactions which will be used for stage 3 testing o Confirms that agencies can properly process SMART data received in Stage 1 Stage 3 – Outbound Interfaces/Return Processing (10/26/09 – 11/25/09): o Confirms that the outbound interface files are successfully processed in Agency systems o Processes transactions used in stage 2 and returns the transactions to agencies where applicable

13. 13 Interface Test Strategy Test Structure: Stage 4 – Inbound Error Processing (11/30/09 – 1/15/10): o Confirms that the inbound interfaces detect errors in files sent from Agency systems o Uses SMART Commitment Control functionality to detect budget checking errors as appropriate Stage 5 – Additional Inbound Interfaces (11/15/09 – 1/15/10): o Confirms that the inbound interface files are successfully processed in SMART o Tests interfaces used by a very small group of agencies with special needs. Stage 5 (cont) – SHARP Interfaces (11/15/09 – 1/15/10): o Confirms that the SHARP inbound interface files are successfully processed in SMART

14. 14 Interface Test Strategy Test Structure: Stage 6 - Agency-Defined Testing, Spreadsheet Uploads, Regression Testing, and Direct Connect Testing (1/15/09 – 3/15/09): o Validates Agency-defined conditions for inbound or outbound testing o Allows Agencies to perform regression test as needed o Validates the Direct Connect integration between SMART and vendor websites o Agencies will not be involved in Direct Connect testing o Confirms that the Spreadsheet Upload interfaces are processed successfully in SMART

15. 15 Key Dates Activity/MilestoneStart dateFinish Date Agency performs connectivity testing7/15/098/31/09 Agency attends Interfacing Testing workshop (Task ID 227)8/18/09 Stage 1: SMART Outbound Configuration Interfaces – Agency receives outbound files 9/1/0910/12/09 Stage 2: SMART Inbound Interfaces – Agency provides inbound files 10/5/0911/18/09 Stage 3: SMART Outbound Interfaces (Return Processing) – Agency receives outbound files 10/26/0911/25/09 Stage 4: Error Processing (Inbound) – Agency provides inbound files 11/30/091/15/10 Stage 5: Additional Inbound Interface Test – Agency provides inbound files 11/30/091/15/10 Stage 6: Agency-Use Interface Test using Agency conditions; spreadsheet upload testing; and regression testing (as needed) – Agency receives and provides files as needed 1/15/103/15/10 Completion of Interface TestN/A3/15/10