Part 4 - Iowa Medicaid Enterprise

More documents

Recommendations

Info

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS Operations• Batch scheduler configured as agreed per the test plan• All claim input methods verified to be operating correctly• Printing facilities online• Imaging system onlineThe environment readiness review is a key part of the each test phase readiness review that will beexecuted prior to test commencement. This very same process will also be executed for everyenvironment set up for the new MMIS, including the production environment itself.Test PlansRFP Sections 6.3.2.3.2.1.1, Requirements a andb; Requirements a through qTest plans describe the systematic approach thatis followed during each test phase. The first stepin every test phase is a test planning activity. Ourview is that the test plan is the basis forcommunicating the test process for all partiesinvolved in each test phase. The test planprovides background information on the softwarebeing tested, the test objective, and specific teststo be performed. It provides specific informationabout the testing process and procedures thatneed to be followed for each test phase.Team Noridian test plans will address theprocesses and procedures for unit, module, rules,integration (End-to-End), and ORT (parallel,load and stress test, beta, disaster recovery andbusiness continuity test). Prior to submission ofthe test plan for the Departments approval, TeamNoridian will establish the expectations of foreach plan and obtain concurrence on the scopeand content. This approach has shown toeliminate unrealized expectations and reduce thetime to obtain approval from the Department.Team Noridian's iVision360 methodologyincludes a standard test plan that has been refinedover time through our experience and lessonslearned on our previous MMIS projects. Figure8-78 provides the test plan table of contents forthe new MMIS project.All of the test plan content required by the RFPis captured in Team Noridian's standardtest plan; however, the terminology may notexactly match. For this reason, we are includingFigure 8-79 to provide a mapping of the RFP testplan deliverable requirements to the section ofTeam Noridian's standard test plan.Figure 8-78. Team Noridian’s Standard Test PlanTable of Contents. Team Noridian’s test plancaptures the required information to plan andschedule each phase of testing.8 | 136
RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsRFP Deliverable RequirementPlan for use of regression testing during all testing phases of the system.Plan and schedule for each business process area and associated systemmodules and subsystems as well as for the integrated testing.Plan for analyzing difference between the legacy MMIS and the LouisianaReplacement MMIS during parallel testing and how those differences will bereported.Plan for identifying and documenting test situations and expected test results.An organization plan showing contractor personnel responsible for testing.Plan for managing the testing effort, including strategies for dealing with delaysin the testing effort, back-up plan, back-up personnel, and related issues.Procedures for tracking, documenting, and correcting deficiencies discoveredduring each phase of testing.Strategy and methodology for dealing with the situation where unit tests,Module tests, Rules test, Integration tests, Load and Stress tests, useracceptance tests, parallel tests, or operations readiness tests failed to producethe desired results.Plan for updating system or user documentation based on test results.Procedures for notifying the Department of problems discovered in testing,progress, adherence to the test schedule, and so forth.A plan for documenting and reporting test results to the Department for reviewincluding test scenarios used, anticipated and actual outcomes, anddiscrepancies identified.Specific procedures for backing up, restoring, and refreshing all permanent datastores in the test environments.Migration procedures describing the steps needed to move or copy softwarefrom system test libraries to the test environments.Migration procedures describing the steps needed to move or copy softwarefrom the User Acceptance test environment to production.Team Noridian Content SectionSection 3.5: Plans for Regression TestingSection 2: Approach to Testing for each Test PhaseSection 7: Test SchedulesSection 2: Approach to Testing for each Test PhaseSection 4: Test Execution and ReportingSection 4: Test Execution and ReportingSection 1.1: Organization PlanSection 1.2: Roles and ResponsibilitiesSection 3.6: Strategies for Delays and Contingency PlanSection 4.4: Defect Creation and Resolution ProcessSection 3.6: Strategies for Delays and Contingency PlanSection 4.5: Test Reporting and ResultsSection 3.7: Plan for Updating System or User Documentation Based on TestResultsSection 4.5: Test Reporting and ResultsSection 4.5: Test Reporting and ResultsSection 6.1: Back-up, Restore, and Refresh ProceduresSection 6.2: Back-up, Restore, and Refresh ProceduresSection 6.2: Back-up, Restore, and Refresh ProceduresFigure 8-79. Mapping of RFP test plan requirements to Team Noridian's standard test plan. TeamNoridian's test plan is based on standards to enable repeat of past successes and process improvementfrom lessons learned.Test Cases and ScriptRFP Section 6.3.2.3.2.1.2A test case is a set of test inputs, execution conditions, and expected results developed for a particular testobjective. Test case construction begins with review of the established test objectives and the detailedsystem design (DSD) document, which details the use case and use case stories with its business rules anddatabase field information, created during the iterative design and development. Test construction is animportant step to ensure that all required test cases are identified and all system functionality requirementsare tested. Test construction uses the requirements and use cases developed as the source for generating testcases. A use case provides high level details of the requirements to be addressed to perform a given task.Each use case corresponds to one or more test cases. All test cases undergo review as need arises. Duringreview, each test case is examined in detail to ensure that the test steps, input conditions, output, andvalidation points are correct. The review may include the following Team members:• Testing Manager• Programmer / Analysts• Business Analysts• Testers8 | 137
Page 1 and 2:
RFP MED-12-001 | Technical Proposal
Page 3 and 4:
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146: RFP MED-12-001 | Technical Proposal
Page 195: RFP MED-12-001 | Technical Proposal
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Page 405 and 406:
Page 407 and 408:
Page 409 and 410:
Page 411 and 412:
Page 413 and 414:
Page 415 and 416:
Page 417 and 418:
Page 419 and 420:
Page 421 and 422:
Page 423 and 424:
Page 425 and 426:
Page 427 and 428:
Page 429 and 430:
Page 431 and 432:
Page 433 and 434:
Page 435 and 436:
Page 437 and 438:
Page 439 and 440:
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
Page 451 and 452:
Page 453 and 454:
Page 455 and 456:
Page 457 and 458:
Page 459 and 460:
Page 461 and 462:
Page 463 and 464:
Page 465 and 466:
Page 467 and 468:
Page 469 and 470:
Page 471 and 472:
Page 473 and 474:
Page 475 and 476:
Page 477 and 478:
Page 479 and 480:
Page 481 and 482:
Page 483 and 484:
Page 485 and 486:
Page 487 and 488:
Page 489 and 490:
Page 491 and 492:
Page 493 and 494:
Page 495 and 496:
Page 497 and 498:
Page 499 and 500:
show all

Part 4 - Iowa Medicaid Enterprise

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?