Part 4 - Iowa Medicaid Enterprise

RFP MED-12-001 | Technical ProposalIowa Medicaid Enterprise System Service Procurement | MMIS and Core MMIS OperationsWhere applicable, we have added a sub-area under a business area to include reports. The senior businessanalyst and their team for each business area will be responsible for the report requirements for thatbusiness area. We have learned from experience that if we centralize reports under separate teams that arenot integrated with the business areas, there is a higher risk of reports requirements being missed or notbeing addressed properly and may result in the discovery of potential issues with reports late in thelifecycle. The business area experts on each business area from both the Department and Team Noridianwill be the most knowledgeable in the business rules and reporting needs of the Department and should beresponsible for identifying reporting and interface requirements within their areas of expertise.We added an architecture team to oversee the requirements and design modifications associated withcommon services, including information technology (IT) infrastructure services, interoperability services,security and privacy services, and performance engineering. This team will also be responsible foraddressing cross-team touch points and integration.Business area teams will have a similar structure of resources to accomplish the requirements validationand design of the associated business area; however, due to the complexity of some business areas, thequantity of the resources for each category may differ. The start-up and implementation organizationalstructure delivered with this proposal provides the specific number of resources for each team. Thegeneral structure is as follows:• Senior Business Analyst• Business Analyst and/or subject matter expert (SME)• Programmer• Tester• Department designated staffTeam Noridian's iVision360 methodology adopts the Unified Modeling Language (UML) as a method ofconveying certain aspects of our system requirements and design. The term “system use case” is from theUML notation. The intent is not to inundate the Department with differing terminology, but rather toarticulate complicated concepts using well-defined notations. The following defines a few relevant pointsregarding terminology:• Business Use Case. A series of steps takenby the Department or Team Noridian staffto accomplish a business process, whichmay or may not be automated. The draftbusiness use case will be documented bybusiness analysts prior to JAD session andwill be updated based on informationgathered during the JAD sessions.• System Use Case. A thread offunctionality implemented by the system.Requirements are traced to system usecases during RV to ensure that system isbuilt and configured to implement all RFPrequirements fully.• Actor. Types of users and other systemsthat interact with the business or systemuse case. Please note that the intent is notto identify individually named users as actors but rather groups of users such as administrators andcase workers. Actors may also identify external systems such as the eligibility system.8 | 59