13.07.2015 Views

Part 4 - Iowa Medicaid Enterprise

Part 4 - Iowa Medicaid Enterprise

Part 4 - Iowa Medicaid Enterprise

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

RFP MED-12-001 | Technical Proposal<strong>Iowa</strong> <strong>Medicaid</strong> <strong>Enterprise</strong> System Service Procurement | MMIS and Core MMIS OperationsConversion Testing. Team Noridian's data conversion test approach uses a state-of-art automationframework and based on using predefined Microsoft Excel data conversion mapping templates. Dataconversion mapping describes the source to target mapping rules to move the legacy data into the eCAMSdatabase format. Team Noridian's automated testing framework eliminates the opportunity for humanerror in data conversion testing by creating automated testing scripts to validate the data conversionprocess was completed successfully.The plan for data conversion testing will be included as part of the conversion plan, executed by TeamNoridian's test team, and the results provided to the Department for review and approval. Team Noridianrecognizes the value of testing using converted data to ensure that the testing activities and results reflecttrue to life examples of the operating MMIS. This will assist in the Departments review and approval oftesting results.Data Certification LetterRFP Section 6.3.2.3.2.1.7Preparation for UAT is vitally important given the number of resources from the Department,business services contractors, Team Noridian, and other contractors that will be involved duringthis event. Documentation, software, processes, and systems must be ready prior to the beginningof UAT. Team Noridian's testing process provides the necessary checkpoints and visibility toverify readiness for UAT. The thoroughness of our process gives us confidence in certifyingreadiness for UAT. Team Noridian will provide a letter to the Department certifying that all data,user manuals, testing facilities, and security accesses necessary to perform UAT.The following provides an overview of the entry and exit criteria for UAT and our UATrelated processes.Entry Criteria• UAT Test Plan has been reviewed and approved• Results from each Integration test have been delivered and approved• All requirements have been addressed through test scenarios and test scripts and is reflected in the RTM• The MMIS systems successfully meet the requirements of the Contract• User Acceptance Test environment (including required interfaces) has been configured, verified, andis available to begin testing• All planned test cases have been created and documented• Required converted test data is in place (except for that which will be created from other test cases)• Team Noridian has provided a letter certifying that all data, user manuals, testing facilities andsecurity accesses necessary to perform UAT have been providedExit Criteria• 100% of the planned Integration Test cases have been executed• All discovered defects logged into Bugzilla• No known Severity 1 or Severity 2 defectsAs each test is executed, the tester collects evidence of the test (i.e., test results). Depending on the natureof the test, evidence may be collected to demonstrate pre-conditions of the test, conditions at each stepduring the test, and conditions after the test has been completed. This evidence is then compared to theexpected results as recorded in each test case document.When the evidence is compared to the expected result at each validation point within the test case, anassessment of the result is made in terms of pass or fail. Additionally, when the test case is executed tocompletion or completed as far as permitted by the system, a pass or fail determination is made for the8 | 153

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!