Enterprise Architecture Application - Assignment
29 Pages3018 Words281 Views
Added on 2020-03-28
Enterprise Architecture Application - Assignment
Added on 2020-03-28
ShareRelated Documents
ENTERPRISEARCHITECTUREAPPLICATIONAssignment 40
AbstractThe MediCo enterprise’s case study is studied and analysed. This report is intended to sketch outthe importance of enterprise's architecture and the importance of communication in processing the processes. It provides detail information about the current and the future expected state of theenterprise, with the help of a "To-Be" architecture. The intension is to process and deliver the required outsourcing service. The problem of the enterprise, its approach towards the solution and the best practices are determined. The importance of Enterprise Lifecycle Management is also determined. The aim is to provide a clear understanding of the architecture, to the stakeholders, Chief information officer (CIO), directors, application architects and systems architects. On the other hand, this report focuses to provide a clear picture of the business architecture, application architecture and technology architecture. The enterprise involves medical claims and payments as its functions and processes. The ArchiMate modelling tool is used for generating the “To-Be” architecture.
Table of ContentsAbstract......................................................................................................................................................11.Introduction.......................................................................................................................................12.As-Is architecture of MediCo........................................................................................................12.1Viewpoints and Discussion per Stakeholder................................................................................23.1Vision..........................................................................................................................................73.2Mission........................................................................................................................................73.3Products and Services................................................................................................................83.4Reason for Transformation.......................................................................................................83.5Principles of the Architecture...................................................................................................83.6Actors..........................................................................................................................................83.7Challenges..................................................................................................................................93.8Approach....................................................................................................................................93.9Deliverable..................................................................................................................................93.10Best Practices or Solutions........................................................................................................94.Overview of Stakeholders and their Concerns..............................................................................104.1Needs of the Stakeholders.......................................................................................................104.2Concerns...................................................................................................................................105.Viewpoints and Discussion per Stakeholder..................................................................................115.1To-Be Architecture..................................................................................................................126.Conclusion........................................................................................................................................21References................................................................................................................................................22
1.IntroductionAt present, the business practices are mostly integrated with the IT infrastructure, whichis essential and its demand is increasing day-by-day. The business architecture, applicationarchitecture and technology architecture provides a clear understanding of the processesfollowed in the enterprise or an organization. The stakeholders possess a key role in theenterprise and it is necessary to effectively communicate the enterprise to them. The enterprisearchitecture helps in representing the working of the enterprise. The case study of MediCo isrepresented in this report. It has decided to outsource the claims and payment function to one ofits Administrative partners. Because, it no more intends to directly manage and handle theclaims, of the medical payments from its members. The enterprise involves medical claims andpayments are the functions and process. At present, it is planning to add additional members tomanage the general relationships with the customers and partners. The addition of outsourcingincludes various decision processes, in the overall process. It also contains certain exceptionsthat are handled only by MediCo. The objectives are listed below:1)To provide a To-Be architecture from the ArchiMate modelling tool. 2)To provide viewpoints to communicate the To-Be architecture, to thestakeholders.3)Demonstrate the understanding of stakeholders and their needs.4)To provide business architecture, application architecture and technologyarchitecture.5)The importance of Enterprise Lifecycle Management will be determined.2.As-Is architecture of MediCoThe AS-IS structure of the Medico is presented as the PDF document to the stakeholders, the problem is that it is very technical and hard to understand the document.The legacy system is maintained by one of the third-party service providers. With the 1
help of the terminal emulation the all the user log into the system that is physically located in one data center. The current core function of the Medicos are subdivided into three main business functions and areas of continuous activity.Actors: In the AS-IS structure there are 2 actors 1. MemberThe member handle all the functions that is related to the member lifecycle management2.Third-partyThe third-party handles the functions of the third-party management.2.1Viewpoints and Discussion per StakeholderThe viewpoint-oriented method supports to know the issues. The key intension of the viewpoints is to provide a quick guide to various stakeholders to different parts of the AS-IS Architecture Diagram. Every views can be presented by using the language and notation suitable to the knowledge, proficiency, and concerns of the projected leadership. The necessities are considered as the viewpoints.As-Is (baseline) architecture diagramsLevel 0: MediCo’s Value ChainThe core business functions are subdivided into three member lifecycle management (MLM),third-party lifecycle management (TLM) and service provider lifecycle management (SLM) and particular activities that is to be done are being allotted to each actors. Medical claims and payments, relationship management and other top-up benefits are under the MLM. Audit control and contract are under the TLM, insurance management and service level management are provided by the SLM.2
3
End of preview
Want to access all the pages? Upload your documents or become a member.
Related Documents
INF4883 Research Strategy and Design Assignmentlg...
|11
|2589
|324
Business Architecture - Introdctionlg...
|15
|2343
|71
Enterprise Architecture (EA) Assignmentlg...
|16
|3171
|213
Assignment Enterprise Architecture (EA)lg...
|16
|3119
|340
Enterprise Architecture Applications Task 2022lg...
|16
|2606
|20
AVBS1002 - Livestock Management ArchiFarm - Case Studylg...
|18
|3626
|72