ICT301Assign1TunK34667827

pdf

School

James Cook University *

*We aren’t endorsed by this school

Course

110

Subject

Information Systems

Date

Nov 24, 2024

Type

pdf

Pages

Uploaded by HighnessSquirrelPerson357

Khin Maung Tun 34667827 ICT 301 B ICT301 ENTERPRISE ARCHITECTURES Assignment 1

Table of Content Introduction ................................................................................................................ 2 Case Description ........................................................................................................ 2 Architecture in the case .............................................................................................. 3 A. Architecture Vision ........................................................................................ 4 B. Business Architecture (BA) ........................................................................... 5 C. Application Architecture (AA) ........................................................................ 7 D. Technology Architecture (TA) ........................................................................ 7 E. Transition Architecture (TRA) ........................................................................ 7 Comparison ................................................................................................................ 8 Conclusion ................................................................................................................. 9 References ................................................................................................................. 9 Abstract .................................................................................................................... 10

Introduction Enterprise Architecture (EA) is a holistic management practice that provides organizations with valuable insights and a comprehensive overview of their operations. It encompasses both business and information technology, aiding in complexity management and facilitating strategic decision-making (Op't Land et al., 2009). While EA initially originated as a tool for information systems management, it has evolved over time to become a crucial instrument for achieving business-IT alignment (Simon et al., 2013) and even a leadership practice. Early EA implementations primarily focused on describing enterprises from an information systems architecture perspective, often neglecting the integration of business goals and strategy (Zachman, 1987). However, as EA progressed, it increasingly intertwined with strategic planning and business transformation. Despite this evolution, studies indicate that business-oriented EA implementation often falls short of its potential scope. Moreover, existing research highlights a predominant emphasis on IT consolidation, business-IT alignment, and IT landscape management, with a relative neglect of the business architecture layer within EA. The main objective of this report is to examine the Enterprise Architecture (EA) of African Healthcare Information Systems. By conducting a case study on the African Healthcare Information System, we seek to understand the significance and implementation of EA within the organization, as well as its contribution to the company's success over time. Additionally, we will compare the EA in the case study with the EA3 framework from the textbook to highlight any differences between the two. In conclusion, the report will provide a final assessment of the benefits derived from implementing an EA framework in this specific case. Case Description This case study examines a health information system implemented in a hospital warehouse in Mali, which is facing the challenge of adapting to changes. A healthcare information system is designed to organize the necessary information for managing a health system. The system discussed in this case study is a Web Application, consisting of a three-layered architecture (presentation, business, and data layers), which will be further elaborated in Figure 1. The purpose of this system is to manage various departments within the hospital, including pharmacy, laboratory, consultation, cash register, and the warehouse. The hospital's head manager aims to enhance the system by introducing new features and improving its efficiency to address vulnerabilities. Specifically, this case study focuses on the warehouse component of the system and explores potential avenues for its more effective evolution. As the system faces future changes, it becomes increasingly risky and vulnerable, encountering numerous issues that compromise its reliability. These forthcoming changes give rise to new requirements, objectives, problems, goals, principles, and drivers that need to be addressed. Additionally, new business processes must be identified to accommodate the evolving system. Determining the necessary

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

applications, data, and technological infrastructure to support these process changes in the system is also essential. Figure 1 Architecture in the case In this case study, the ArchiMate modeling technique is utilized within the O-DA framework to identify the stakeholders, new requirements, objectives, and risks associated with the system. The O-DA standard, which focuses on reliability and risk

mitigation in complex interoperable systems, also emphasizes individual responsibility and enhances the quality assurance of IT architecture. This approach addresses O-DA challenges related to changes in business, application, and technology architecture within TOGAF. The O-DA framework is centered around modeling dependencies, building assurance cases, and establishing accountability in the event of failures. Dependability cases play a crucial role in ensuring the reliability of architectures in dependable systems. To manage dependability in complex systems, the DEOS process, which utilizes dependability cases, was proposed. Organizations relying on complex systems can benefit from the O-DA standard as it helps prevent or mitigate the impact of system failures. The O-DA framework incorporates the DEOS process and provides a framework for critical processes through the Change Accommodation Cycle and the Failure Response Cycle. It aligns with The Open Group's vision of Boundaryless Information Flow. ArchiMate, as a modeling language, is used to describe enterprise architectures. It defines three layers: the Business Layer, which delivers products and services to external customers through business processes performed by business actors; the Application Layer, which describes application services realized by software applications supporting the entities in the Business Layer; and the Technology Layer, which provides infrastructure services such as processing, storage, and communication. The case study has two main focuses: the requirements part of the O-DA framework and a phased architecture roadmap for constructing an architecture quality assurance service. A. Architecture Vision The Architecture Vision is a powerful tool for sponsors to showcase the benefits of the proposed capability to stakeholders and decision-makers. It explains how the new capability will align with business goals, strategic objectives, and address stakeholder concerns. The Architecture Vision section outlines the key elements of the target architecture. It aims to identify stakeholders, understand their concerns and requirements, and validate business goals, drivers, and principles. To analyze the system, the Business Scenario illustrated in Figure 2 is used. The Business Scenario helps identify problems and individual entities within their operational scope, such as people, places, security principals, hardware assets, software assets, and information assets. This approach offers several advantages, including objective assessment of system architecture quality and identification of new needs. ArchiMate is employed to model stakeholder requirements, as depicted in Figure 3 , which illustrates the stakeholders analyzed in the Business Scenario and some requirements derived from the analysis. This modeling captures the drivers and goals that have led to these requirements.

Figure 2 Figure 3 B. Business Architecture (BA) The Business Architecture section covers the baseline and target business architecture, analyzing the differences between them. It defines the architecture

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

quality assurance process based on assurance cases, which include architecture, quality properties, risks, risk countermeasures, and the assurance case. Figures 4 and 5 provide examples of using ArchiMate to address identified problems and requirements. For example, Figure 4 demonstrates how ArchiMate can be used to enhance the system by adding a search component, while Figure 5 showcases the modeling of a Web Application Firewall (WAF) to secure the system's data, taking into account stakeholder requirements. Figure 4

Figure 5 C. Application Architecture (AA) The Application Architecture section aims to define the necessary application systems to process data and support the business. It covers both the baseline and target application architecture, analyzing the differences between them. It clarifies the functions and information associated with the application architecture and considers risk measures based on assurance cases. This section explores and defines the components of application architectures, including input and output information and their relationships, functions of application elements, and the relationships between application elements and actors. D. Technology Architecture (TA) The Technology Architecture section defines both the baseline and target technology architecture. It also analyzes the differences between them. The information infrastructure environment is clarified to assess risk measures for the technology architecture based on assurance cases. This section covers the devices, software, and their relationships required to realize the technology architecture. It also outlines the roles for each component. E. Transition Architecture (TRA)

The Transition Architecture focuses on creating a phased approach to transition from the baseline architecture to the target architecture. It involves an architecture roadmap that includes three main phases: the introduction phase for assurance cases, the quality risk management phase, and the comprehensive quality assurance phase. The architecture roadmap outlines the steps needed to achieve the target architecture from the baseline architecture. Each phase is clearly defined, and it includes artifacts from the Business Architecture (BA), Application Architecture (AA), and Technology Architecture (TA) for each respective phase. Furthermore, the return on investment and associated risks are evaluated for each phase. Comparison The content highlights the importance of designing cooperative information systems that prioritize the analysis and organization of human work, rather than solely focusing on data and automation. It emphasizes the need to integrate various formalisms for representing cooperation activities within a unified modeling environment, enabling the seamless implementation of cooperative processes. The case study illustrates the successful application of the ArchiMate modeling language and the O-DA framework in the healthcare sector of developing countries, such as Mali. By adopting frameworks like TOGAF and O-DA, these countries can establish functional healthcare information systems and streamline complex procedures. These frameworks assist in identifying stakeholders, requirements, and goals, facilitating the development of well-structured system architectures. Below is the comparison between the case study framework and EA3 cube framework in the textbook in table format. Case Study Framework EA3 framework from textbook ArchiMate O-DA Framework E3 Cube Architecture Framework Purpose Modeling technique for describing enterprise architectures Provides guidance for developing assured and dependable architectures Framework for designing cooperative information systems Focus Describes enterprise architectures Ensures system dependability and reliability Analyzes, understands, and organizes human work Integration Integrates business, application, and technology layers Integrates formalisms for representing cooperation activities Integrates workflow and groupware technologies Modeling Language Yes No Yes

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

Stakeholder Consideration Considers stakeholders, their concerns, and requirements Considers stakeholders and their accountability in case of failures Considers stakeholders and facilitates development of architecture Application Scope Broadly applicable across various industries and domains Primarily focused on system dependability and reliability Primarily focused on cooperative information systems Conclusion The case study incorporates both the ArchiMate and O-DA frameworks to enhance the overall architecture, particularly focusing on system dependability and reliability. ArchiMate provides a detailed modeling language with multiple layers, while the EA3 framework offers a high-level, holistic approach to enterprise architecture. ArchiMate is widely adopted and supported by various tools, whereas the EA3 framework has a smaller but dedicated user base. Considering these factors, the report concludes that the use of ArchiMate and the O-DA framework is more suitable for the hospital scenario compared to the EA3 framework. References Oliveira , Vasconcelos de. “A TOGAF -Based Framework for the Development of Sustainable Product- Service Systems.” Procedia Manufact uring, November 3, 2021. https://www.sciencedirect.com/science/article/pii/S2351978921002365 . Traoré, Mariam, and Shuichiro Yamamoto. “A Case Study of ArchiMate® for the African Healthcare Information System.” IEEE Xplore, November 16, 2017. https://ieeexplore.ieee.org/document/8113257 Daeli, Cosmas Samuel, Erwin Setiawan Panjaitan, and Roni Yunis. “Hospital Enterprise Architecture Design Using EA3 Cube Framework.” INFOKUM, December 27, 2022. https://infor.seaninstitute.org/index.php/infokum/article/view/973 Mate, Archi. “What Is Archimate Core Framework?” ArchiMate Resources for FREE, February 13, 2018. https://archimate.visual-paradigm.com/2018/02/09/what-is- archimate-core-framework/ Pérez-Castillo, Ricardo, Andrea Delgado, Francisco Ruiz, Virginia Bacigalupe, and Mario Piattini. “A Method for Transforming Knowledge Discovery Metamodel to Archimate Models - Software and Systems Modeling.” SpringerLink, August 2, 2021. https://link.springer.com/article/10.1007/s10270-021-00912-y

Abstract

ICT301Assign1TunK34667827

Related Documents