Part 4 - Iowa Medicaid Enterprise

More documents

Recommendations

Info

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsIf a test case does not pass review, the responsible tester updates the test case to reflect the changes notedduring the review. The test case is once again reviewed to ensure that the modifications are correct.When a DSD document contains use cases that require multiple cooperating systems, those use cases arereserved for the system test phase and tested up to the boundary of the component during unit testing.Using ReqTrace, Team Noridian maintains the new MMIS requirements and use case traceability. Thetest cases are further integrated into ReqTrace where the test case management occurs. When creatingtest cases with ReqTrace, the testers can draw the information from ReqTrace and create thetraceability link from requirements to test cases. The Team can then maintain traceability and ensureproper test case coverage. Furthermore, when requirements are changed, test cases are flagged and arelinked to the change requirements so that the relationship between software, requirements, and testcases is constantly synchronized.A test process must be repeatable. This must be considered throughout the test case construction phase.During iterative design and development, test case refinement and detailing continues as the codedevelops. Test case construction is completed when all requirements can be validated through test cases.Traceability reports helps to determine whether all the requirements are mapped to test cases to completevalidation. When mapping is complete, test case construction is also complete.Test case design is focused on verifying the requirements and determining if the requirements are met.The use cases are the starting point for test case design. Use cases are broken down into manageableand testable test cases so that clear steps are available to validate all test conditions required. Thisapproach, using use cases as a source for test cases, covers all of the requirements that need to bedelivered to the Department.Each test case must meet the following guidelines and goals:• Test cases must be traceable to the requirements: The test case clearly shows the requirement orrequirements that the test case addresses• Test cases must provide clear test instructions: Instructions are clear and precise• Test cases must identify clear prerequisite test conditions: The prerequisite conditions required tosuccessfully execute the test cases and to validate the requirement are defined• Test cases must be written to be tester independent: Any tester can read and execute the test case.• Test cases must provide explicit input and output definition: The input data required to satisfy theoutput to be achieved is explicitly stated• Test cases must clearly state the expected results: The expected results of the test, and the actualresult of the test after it has been executed, are stated so that the two results can be easily compared• Test cases must identify boundary conditions: The test conditions used to test the system withextreme values in the valid range• Test case must identify any required external interfaces: The test case clearly identifies and tests all ofthe interfaces associated with the test case• Test cases must include negative testing: Tests the conditions which the application should not acceptand validate the output• Determine data requirements: Identify the data requirements for the test cycle. Establish internal testdata for test cycles until the converted data is made available for system testing. Test cases must also:• Be reusable at various phases• Have unique identifiers• Be maintainable for the lifetime of the software• Provide a clear list of the environment and profile in which test cases are executed• Follow the test case naming convention: ---8 | 138
RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsA good test program reuses common building blocks wherever possible. This also applies to test cases.Test cases developed for the unit test phases may become the building blocks for Module and Integrationtest cases by combining multiple unit test cases in a chain across multiple systems. Furthermore, testcases used in unit, module and integration testing may be reused for acceptance testing and regressiontesting.The sample test case template to be used by all test personnel for the new MMIS project is shownin Figure 8-80.Figure 8-80. Test Case Template. Team Noridian has pre-built templates for use cases to rapidlyimplement our test program.Conducting TestsThe objective of this step is to determine whether the new MMIS project meets RFP requirements andperforms as per the documented design specifications. Test execution is started after completing theconstruction of test cases and identifying the data to be used for that test phase. Additionally, a TestReadiness Review (TRR) is held prior to the start of each formal test phase to verify that all entry criteriadocumented in the test plan for the test phase have been successfully met.8 | 139
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:
Page 147 and 148: RFP MED-12-001 | Technical Proposal
Page 197: RFP MED-12-001 | Technical Proposal
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

Create successful ePaper yourself

Delete template?

Save as template?