INF4883 – Assignment 3 (871998) due date 3 October 2016 1 Research Strategy and Design 1 Background: You are tasked with the responsibility of communicating an As-Is architecture to the leaders of an organization. In this particular case the architecture was captured and presented as a PDF document that includes high level information as well as some ArchiMate diagrams. The problem for the stakeholders is that the PDF document is very technical and hard to understand. Fortunately for the ArchiMate standard includes a viewpoint framework targeted at communicating the architecture to different stakeholders. 2 Requirement The third assignment in this module require you to produce a comprehensive report on the meaning of the As-Is architecture as captured for the case study presented (see appendix A). The report will serve to communicate the As-Is architecture to a specific group of stakeholders. The stakeholders are as follows:  Strategic leadership (i.e the board of directors)  CIO  Application architects  Systems architects In order to produce the report, you must do the following: a) Capture the AS-IS architecture (based on the existing models) as completely as possible in the ArchiTool (used in your previous assignment) b) Understand the communication needs of every stakeholder in terms of the level of detail c) Decide on appropriate ArhiMate viewpoint for each stakeholder d) Write the report Prepare the report that will be used to communicate the As-Is architecture (use the viewpoints that you created in the previous task) to the relevant stakeholders in terms of: a) Background information b) Overview of the stakeholders and their concerns c) The purpose of each viewpoint (i.e. Designing, Deciding and/or Informing) d) The contents of each viewpoint (in terms of abstraction levels namely, Details, Coherence and Overview) – embed a diagram of the viewpoint in your report e) Short narrative that explains the viewpoint Finally, compile the report in Microsoft word and submit to the myunisa assignment system. 3 Layout Structure your report as follows:  Title page (use the module title page)  Table of contents INF4883 – Assignment 3 (871998) due date 3 October 2016 2  Executive overview (short abstract detailing the purpose of the report)  Project background  Overview of stakeholders and their concerns  Viewpoint and discussion per stakeholder  Conclusion Remember that this is not a research report so you do not need to make use of citations etc. use clear language and communicate to the point. Remember that the main purpose fo the report is that your reader must understand the architecture. 4 Overview of steps to follow Step 1: Capture the as-is architecture in the ArchiTool as completely as possible based in the work already completed (Appendix A) Step 2: Plan and produce relevant viewpoints Step 3: Write the report and submit to myunisa INF4883 – Assignment 3 (871998) due date 3 October 2016 3 Appendix A - MEDICO CASE STUDY 1 GENERAL BACKGROUND – MEDICO BASELINE MediCo is a medical scheme that provides scheme members with a wide variety of services and medical aid scheme packages, plans and benefits. MediCo operates as a non–profit medical scheme in terms of the Medical Schemes Act. Historically MediCo started out as a small medical scheme that provided services only to specific professions and professionals. MediCo focussed mostly on satisfying a select group of members’ needs. The core functions of MediCo were as follows:  The Acquisition of Members  The Acquisition of Service Providers  General Member and Service Provider Relationship Management  Managing Funds and Medical Benefit Plans  Member Risk and Risk Assessment  Member Lifecycle Management  Member Policy Management The current IT infrastructure utilises a legacy system for membership and membership fund and benefit administration. Even though the legacy system is maintained by one of MediCo’s third-party service providers by way of a service level agreement, the system is physically located in one datacentre and all users log into the system over a network by means of terminal emulation. Over the years MediCo acquired additional medical schemes and integrated these schemes into the core functions of MediCo. As such, MediCo matured quite significantly and manages a very large membership base. Currently, MediCo’s functions are no longer as simple and direct as previously stated. The current core functions have been subdivided into three main business functions and areas of continuous activity. The core business functions as well as the individual functions are as follows: Core Business Function Individual Business Functions Member Lifecycle Management Accounts and Policies Acquisition Audits and Controls Medical Claims and Medical Payments Exception Management Relationship Management Risk and Risk Assessment TopUP-Benefit (Backup) Insurance Travel Insurance Third-Party Lifecycle Management Accounts and Payments Acquisition Audits and Controls Contracting Exception Management Relationship Management Service Level Management Service Provider Lifecycle Management Account and Payments Acquisition Audits and Controls INF4883 – Assignment 3 (871998) due date 3 October 2016 4 Claims and Payments Contracting and Outsourcing Exception Management Relationship Management Service Level Management Insurance Management After several years of growth MediCo can no longer manage to administer all the various functions on its own. As such the executive of MediCo decided to outsource certain functions related to the management and administration of members to one of its Service Providers. The first step in the process of deciding to migrate to an outsourced Service Provider is to get a clear overall picture of the As-Is enterprise architecture (Note: the emphasis is on the Medical Claims and Payment function). INF4883 – Assignment 3 (871998) due date 3 October 2016 5 2 As-Is (baseline) architecture diagrams 2.1 LEVEL 0 - MEDICO’S VALUE CHAIN MLM: Member Lifecycle Management TLM: Third-Party Lifecycle Management SLM: Service Provider Lifecycle Management Medical Claims and Payments Acquisition Audits and Controls Accounts and Policies Exception Management Relationship Management Risk and Risk Assessment TopUP-Benefit Insurance Travel Insurance Accounts and Payments Acquisition Audits and Controls Contracting Exception Management Relationship Management Service Level Management Accounts and Payments Acquisition Audits and Controls Insurance Management Exception Management Relationship Management Service Level Management Claims and Payments Contracting and Outsourcing MEDICO VALUE CHAIN – LEVEL 0 SUPPORT ACTIVITIES Infrastructure Management Human Resource Management Technology Development PRIMARY ACTIVITIES Procurement INF4883 – Assignment 3 (871998) due date 3 October 2016 6 2.2 LEVEL 1 - MEDICO’S MEMBER LIFECYCLE MANAGEMENT Acquisition Audits and Controls Travel Insurance MLM: MEMBER LIFECYCLE MANAGEMENT – LEVEL 1 TopUP-Benefit Insurance Risk and Risk Assessment Relationship Management Exception Management Accounts and Policies Inbound Claim Claim Assessment Claim Reconciliation Claim Settlement Outbound Claim Medical Claims and Payments Incoming Request Follow-up Service Request Assessment Categorise Request Resolve Request Monitor Service INF4883 – Assignment 3 (871998) due date 3 October 2016 7 2.3 LEVEL 2 - MEDICO’S CLAIMS AND PAYMENT MLM: Medical Claims And Payments – Level 2 Inbound Claim Accept Claim Inbound Evaluate Claim Content Receive Medical Claim Claim Assessment Assess Claim Assess Claim Account Assess Benefit Assess Member Flags Assess Member History Accept Claim Claim Reconciliation Reconcile Claim Reconcile Account Claim Cooldown Claim Settlement Claim Fund Transfer Claim Audit Log Reconcile Member Fund Member Fund Update Member Audit Log Outbound Claim Claimant Notification Member Notification Notification Audit Log INF4883 – Assignment 3 (871998) due date 3 October 2016 8 2.4 LEVEL 3 - INTEGRATED BASELINE ARCHITECTURE Medical Claims and Payments DATACENTRE Inbound Claim Evaluate Claim Content Receive Medical Claim Claim Assessment Assess Claim Assess Claim Account Assess Benefit Assess Member Flags Assess Member History Accept Claim Claim Reconciliation Reconcile Claim Reconcile Account Claim Cooldown Claim Settlement Claim Fund Transfer Claim Audit Log Reconcile Member Fund Member Fund Update Member Audit Log Outbound Claim Claimant Notification Member Notification Notification Audit Log Claim Acquisition Claim Reconciliation Claim Payment Membership Management Benefit Management Accounts Management Record and Audit Management Application Manager & Services Host Web Applications Interface Permission Manager Application Server Database RDBMS Database Server CRUD Services Networking Services System Interface Service Workstation Database Services LAN Gateway Network Browser Mail Client User Interface (Web) USER ENVIRONMENT CLAIM BENEFIT ACCOUNT THIRD PARTY PAYMENT CLAIM APPROVED CLAIM PAYMENT ADVICE PAYMENT NOTIFICATION LOG Claim Acceptance Service Claim Reconciliation Service Claim Payment Service Claim Inbound Service Claim Assessment Service Claim Reconciliation Service Claim Payment Service Notification Service CLAIMS AND PAYMENTS MEMBER THIRD PARTY PAYMENT AGREEMENT Accept Claim Inbound MEDICAL CLAIMS AND PAYMENTS MEMBERSHIP CONTRACT Claimant Scheme Member Third Party CLAIM LOG INF4883 – Assignment 3 (871998) due date 3 October 2016 9 2.5 LEVEL 3 - BASELINE BUSINESS ARCHITECTURE Inbound Claim Evaluate Claim Content Receive Medical Claim Claim Assessment Assess Claim Assess Claim Account Assess Benefit Assess Member Flags Assess Member History Accept Claim Claim Reconciliation Reconcile Claim Reconcile Account Claim Cooldown Claim Settlement Claim Fund Transfer Claim Audit Log Reconcile Member Fund Member Fund Update Member Audit Log Outbound Claim Claimant Notification Member Notification Notification Audit Log CLAIM BENEFIT ACCOUNT THIRD PARTY PAYMENT CLAIM APPROVED CLAIM PAYMENT ADVICE PAYMENT NOTIFICATION LOG Claim Inbound Service Claim Assessment Service Claim Reconciliation Service Claim Payment Service Notification Service AGREEMENT Accept Claim Inbound MEDICAL CLAIMS AND PAYMENTS MEMBERSHIP CONTRACT Claimant Scheme Member Third Party INF4883 – Assignment 3 (871998) due date 3 October 2016 10 2.6 LEVEL 3 - BASELINE APPLICATION ARCHITECTURE Claim Acquisition Claim Reconciliation Claim Payment Membership Management Benefit Management Accounts Management Record and Audit Management CLAIMAS AND PAYMENTS MEMBER THIRD PARTY CLAIM LOG PAYMENT 2.7 LEVEL 3 - BASELINE TECHNOLOGY ARCHITECTURE DATACENTRE Application Manager & Services Host Web Applications Interface Permission Manager Application Server Database RDBMS Database Server Workstation LAN Gateway Network Browser Mail Client User Interface (Web) USER ENVIRONMENT

Attachments:

• 1509373768-Assignment32016.pdf