Part 4 - Iowa Medicaid Enterprise

More documents

Recommendations

Info

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsThe RTM is published from ReqTrace at various milestones of the project. During DSD, Team Noridianwill maintain the traceability information in ReqTrace. This traceability information will be updatedperiodically and made available to the Department, thereby eliminating the wait for a deliverable fromTeam Noridian to receive the latest traceability information. Team Noridian will provide an up to dateRTM at the completion of DSD, as required by the RFP. The RTM will be a report describing the RFPrequirements and their trace to system use cases. Non-functional requirements that describesupplementary information will also be traced to system components. Eventually as test cases aredeveloped, the RTM will include a trace from RFP requirements and system use cases to test cases.Using the ReqTrace requirements database, Team Noridian maintains IME requirements and use casetraceability. When creating test cases, the testers can draw the information from the ReqTrace and createthe traceability link from requirements to test cases. Team Noridian can then maintain traceability andensure proper test case coverage. Furthermore, when requirements are changed, test cases are flaggedwhich are linked to the change requirements so that the relationship between software, requirements andtest cases is synchronized.As previously described, the use cases will be introduced during requirements validation and furtherdefined and detailed during design. Each use case will then be decomposed into stories. Stories are smallcomponents of work that must be developed to support the use case. To understand how use cases,stories, and test cases relate to each other and to the requirements, it is helpful to view the traceabilitystructure of our approach. Figure 8-37 describes how RFP requirements and derived requirements aretraced to use cases and how use cases are related to stories.Figure 8-37. Requirements Traceability and Relationships. How we trace RFP requirements and derivedrequirements to use cases, and how use cases are related to stories.Figure 8-38 provides an example of an RTM with requirements traced to system use cases and test cases.8 | 64
RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsTest Case Name RFP Requirements Use Case NameSTC-FIN-LG2-LT1-1 - Worker checks data objectsfor providers and other entitiesSTC-FIN-LG2-LT1-2 - Provider information intofinancials interface tablesSTC-FIN-LG2-LT1-3 - Provider information intofinancials base tablesSTC-FIN-LG2-LT1-4 - Provider contact informationinto financials interface tablesSTC-FIN-LG2-LT1-5 - Provider contact informationinto financials base tablesSTC-FIN-LG2-LT1-6 - Update provider informationinto financials base tablesSTC-FIN-LG2-LT1-7 - Provider to customerinformation into financials interface tablesSTC-FIN-LG2-LT1-8 - Provider to customerinformation into financials base tablesSTC-FIN-LG2-LT1-9 - COB-TPL Information intofinancials interface tablesSTC-FIN-LG2-LT1-10 - COB-TPL Information intofinancials base tablesSTC-FIN-LG2-LT1-11 - COB-TPL Contactinformation into financials interface tables4.13.2.6, 4.13.2.7, 4.13.2.15, 4.13.2.16,4.13.2.17,4.13.3.7, 4.13.3.8, 4.13.3.20, 4.13.3.22,4.13.3.234.13.2.6, 4.13.2.7, 4.13.2.15, 4.13.2.16,4.13.2.17,4.13.3.7, 4.13.3.8, 4.13.3.20, 4.13.3.22,4.13.3.234.13.2.6, 4.13.2.7, 4.13.2.15, 4.13.2.16,4.13.2.17,4.13.3.7,4.13.3.8, 4.13.3.20, 4.13.3.22, 4.13.3.234.13.2.6, 4.13.2.7, 4.13.2.15, 4.13.2.16,4.13.2.17,4.13.3.7, 4.13.3.8, 4.13.3.20, 4.13.3.22,4.13.3.234.13.2.6, 4.13.2.7, 4.13.2.15, 4.13.2.16,4.13.2.17,4.13.3.7, 4.13.3.8, 4.13.3.20, 4.13.3.22,4.13.3.234.13.2.6, 4.13.2.7, 4.13.2.15, 4.13.2.16,4.13.2.17,4.13.3.7, 4.13.3.8, 4.13.3.20, 4.13.3.22,4.13.3.234.13.2.6, 4.13.2.7, 4.13.2.15, 4.13.2.16,4.13.2.17,4.13.3.7, 4.13.3.8, 4.13.3.20, 4.13.3.22,4.13.3.234.13.2.6, 4.13.2.7, 4.13.2.15, 4.13.2.16,4.13.2.17,4.13.3.7, 4.13.3.8, 4.13.3.20, 4.13.3.22,4.13.3.234.13.2.6, 4.13.2.7, 4.13.2.15, 4.13.2.16,4.13.2.17,4.13.3.7, 4.13.3.8, 4.13.3.20, 4.13.3.22,4.13.3.234.13.2.6, 4.13.2.7, 4.13.2.15, 4.13.2.16,4.13.2.17,4.13.3.7, 4.13.3.8, 4.13.3.20, 4.13.3.22,4.13.3.234.13.2.6, 4.13.2.7, 4.13.2.15, 4.13.2.16,4.13.2.17,4.13.3.7, 4.13.3.8, 4.13.3.20, 4.13.3.22,4.13.3.232.3.1 Maintain providers or other entities infinancials2.3.1 Maintain providers or other entities infinancials2.3.1 Maintain providers or other entities infinancials2.3.1 Maintain providers or other entities infinancials2.3.1 Maintain providers or other entities infinancials2.3.1 Maintain providers or other entities infinancials2.3.1 Maintain providers or other entities infinancials2.3.1 Maintain providers or other entities infinancials2.3.1 Maintain providers or other entities infinancials2.3.1 Maintain providers or other entities infinancials2.3.1 Maintain providers or other entities infinancialsFigure 8-38. Example of an RTM. Team Noridian traces requirements to use cases and test cases toensure traceability to design and test.A key element of our successful and proven system is the integration of COTS products and components.We will trace requirements to these components to the GSD in the RTM as we conduct the general systemdesign activities. COTS components are treated as a part of the architecture in a manner similar to customcomponents. However, the Information System Development Methodology (ISDM) processes may varyfor COTS components as needed. For example, COTS solutions typically will have their own relationaldatabase structure to support the COTS functionality. Hence, our team will not describe the details of thephysical relational database structure for COTS products while it may be necessary to do so for customcomponents. Regardless of the type of component (i.e., newly developed, COTS, or pre-existing), TeamNoridian will maintain ReqTrace to ensure each validated requirement is traced to the design and later totest cases.8.3.1.2.2 Documenting all RulesRFP Section 6.3.1.2, Requirement fTeam Noridian defines and documents all rules as we conduct JAD sessions during design. The DetailedSystem Design Document (DSD) for each business area specifically has sections to document these rulesas discussed in our response to RFP Section 6.3.1.2, requirement “r” below. The Operations ManagementDSD specifically will include the rules related to pricing, edits, and audits while the Care ManagementDSD will include benefit plan assignment rules.8 | 65
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: RFP MED-12-001 | Technical Proposal
Page 123: RFP MED-12-001 | Technical Proposal
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
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

Create successful ePaper yourself

Delete template?

Save as template?