scholarly journals Ontological Map of Service Oriented Architecture Based on Zachman

2017 ◽  
Vol 2 (4) ◽  
pp. 33
Author(s):  
Nesa Shafighi ◽  
Babak Shirazi

<em>Service orientation is an approach in the field of enterprise architecture, business information systems and software application that its main element is the service. Shared services is an organization model of sharing, across an organization. It enables collaboration among the functions/departments. Main motivations for shared services are sharing, promote efficiency, reduce cost, and support scalability. Despite of the widespread use of these two approaches in information technology, there is no tool to optimize the management of them. The aim of this study is Ontological map of service oriented architecture based on zachman framework to adapt it in the reference enterprise architecture framework through implementation ontology views on system architect software and as well as equivalent ontology component with UML diagrams. After the implementation of the suggested model, the results showed that ontology is a formal description and explicit display of objects, concepts and other entities in the relationship between them. In other words, there is a model that describe all that is in fact in to understandable language for the system. Thus the proposed establishes have association between all aspects of zachman framework, also to create a clear description of business concepts in the management of shared services and is effective to provide a unified platform for enterprise modeling.</em>

Author(s):  
Ayed Alwadain ◽  
Erwin Fielt ◽  
Axel Korthaus ◽  
Michael Rosemann

In recent years, enterprise architecture (EA) has captured increasing interest as a means to systematically consolidate and manage various enterprise artefacts in order to provide holistic decision support for business/IT alignment and business/IT landscapes management. To provide a holistic perspective on the enterprise over time, EA frameworks need to co-evolve with the changes in the enterprise and its IT over time. In this paper the authors focus on the emergence of Service-Oriented Architecture (SOA). There is a need to integrate SOA with EA to keep EA relevant and to use EA products to help drive successful SOA. This paper investigates and compares the integration of SOA elements in five widely used EA frameworks: Archimate, The Open Group Architecture Framework (TOGAF), Federal Enterprise Architecture Framework (FEAF), Department of Defence Architecture Framework (DoDAF) and the Ministry of Defence Architecture Framework (MODAF). It identifies what SOA elements are considered and their relative position in the overall structure. The results show that services and related elements are far from being well-integrated constructs in current EA frameworks and that the different EA frameworks integrated SOA elements in substantially different ways. The results can support the academic EA and SOA communities with a closer and more consistent integration of EA and SOA and support practitioners in identifying an EA framework that provides the SOA support that matches their requirements.


Author(s):  
Awel S Dico

Governments around the world have acknowledged the complexity associated with public sector transformation and have initiated enterprise architecture programs to help manage those complexities and enable the desired strategic transformation. Along with the EA program, governments have adopted some sort of EA framework and/or Service Oriented Architecture (SOA) individually or in integrated form. However, the majority of those EA programs are of limited scope in both EA and SOA practices, and are not comprehensive enough to deal with and manage the associated complexities. As a result, those EA programs suffer from the inability to leverage EA and SOA benefits across agencies or jurisdictional boundaries. Currently, the majority of government agencies use EA and SOA within the agency boundaries to deliver solutions by focusing on technical factors that define detailed blueprints of systems, data, and technology. What is needed rather is effective Whole-of-Government Enterprise Architecture (EA) that facilitates the alignment of individual agencies’ visions with the Whole-of-Government vision to enable sustainable government transformation. Research has pointed out that the Whole-of-Government EA is currently at the conceptual level and still has a long way to go to reach the maturity level required for value realization. This chapter first gives a brief analysis of the current state of enterprise architecture in governments to highlight the current challenges. It then discusses the various scopes of Whole-of-Government EA and recommends the plausible EA approach to enable sustainable connected government based on The Open Group Architecture Framework (TOGAF) and SOA.


2021 ◽  
Vol 13 (2) ◽  
pp. 879
Author(s):  
Montree Thirasakthana ◽  
Supaporn Kiattisin

The suitable utility of driving the enterprise architecture exercise is to utilize the enterprise architecture framework as the fundamental guidance. But there are some challenges of applying those frameworks for government and their agencies because most of the frameworks have concentrated focus for the private sector which some fundamentally requirement of government would be specifically different. This paper aims to propose that the sustainable government enterprise architecture framework specifically applies for the national strategic planning in the optimum exercise process and clarity guidance for the information technology organization being able to transform and improve their services for an achievable adaptation efficiency, simplification, cost management, collaboration, shareability, and standardization which accommodate the rapidly changing service usability on digitalization known as “e-Government.” The fundamental design idea of this proposed framework has identified five keys principles, which are (1) legislation support, (2) top-down target architecture, (3) architecture governance, (4) shared services, and (5) cross-organization collaboration that would be considered as the key critical success factors for achieving the exercise. The overall response of the specific expert survey of this proposed framework has demonstrated the consensus responded at 90 percentage agreeable, which would strongly consider this framework applicable for groups of developing countries as the baseline framework for their digitalized transformation.


Author(s):  
S. Ghosh

This chapter describes the DoD (Department of Defense) policy goal toward Net centric transformation as an example of enterprise architecture in practice. An integrated architecture across the enterprise provided by the DoD Global Information Grid (GIG) is a key ingredient toward meeting Net centricity. The chapter provides background information on key concepts and details the steps necessary to meeting the Net-ready key performance parameter (NR-KPP). The DoD architecture framework provides the Supporting System View, Operational View, and Technical Standards View architecture products that each DoD program must create to meet the Net-centric model. The Net-centric transformation is detailed based on the Net-centric data strategy, Net-centric IA strategy, use of service-oriented architecture, and use of a communications transport strategy. The path toward Net centricity is a significant and long-term effort and the chapter focuses on specific areas that affect DoD programs on their path toward Net-centric compliance. The implementation of enterprise services and the use of key technical standards are also discussed as emerging efforts.


2019 ◽  
Vol 9 (1) ◽  
pp. 11-20
Author(s):  
Didik Suwito Pribadi

Dalam   Pengembangan System Informasi, rumusan System Requirement merupakan bagian yang sangat  penting, karena menentukan isi dari  system informasi yang dibangun. Requirement harus mencakup komponen data, Hardware, Software, Sumber Daya Manusia, Network, organisasi dan procedure, dan komponen  lainnya.  Bentuk Requirement system informasi bervariasi sesuai dengan paradigma dan teknik pengembangannya. Paradigma penyusunan antara lain pendekatan function driven, data driven, dan object driven.  Teknik penyusunannya dapat menggunakan  pendekatan Top down  atau bottom up atau pendekatan lainnya.Sebelum  pengembangan   system informasi dilakukan perlu dibuat arsitekturnya   yang  mencakup komponen apa saja yang harus ada dalam system. Komponen tersebut menjelaskan fungsi dan perannya dalam mendukung operasi system informasi yang dikembangkan. Untuk mendukung proses pengembangan arsitektur dan kebutuhan system informasi dapat menggunakan tools yang dbuat oleh john zachman yaitu zachman Enterprise Architecture Framework. Zachman framework mempunyai  tiga variable utama yaitu pertama dinamakan Interrogative Communication, kedua  dinamakan Reification Transformation dan  ketiga yang dinamakan cells. Dengan menggunakan Zachman Framework, diharapkan  membantu pelaksanaan  pengembangan system informasi khususnya perumusan Requirement SIM   yang baik


2021 ◽  
Vol 6 (Suppl 5) ◽  
pp. e005242
Author(s):  
Sunita Nadhamuni ◽  
Oommen John ◽  
Mallari Kulkarni ◽  
Eshan Nanda ◽  
Sethuraman Venkatraman ◽  
...  

In its commitment towards Sustainable Development Goals, India envisages comprehensive primary health services as a key pillar in achieving universal health coverage. Embedded in siloed vertical programmes, their lack of interoperability and standardisation limits sustainability and hence their benefits have not been realised yet. We propose an enterprise architecture framework that overcomes these challenges and outline a robust futuristic digital health infrastructure for delivery of efficient and effective comprehensive primary healthcare. Core principles of an enterprise platform architecture covering four platform levers to facilitate seamless service delivery, monitor programmatic performance and facilitate research in the context of primary healthcare are listed. A federated architecture supports the custom needs of states and health programmes through standardisation and decentralisation techniques. Interoperability design principles enable integration between disparate information technology systems to ensure continuum of care across referral pathways. A responsive data architecture meets high volume and quality requirements of data accessibility in compliance with regulatory requirements. Security and privacy by design underscore the importance of building trust through role-based access, strong user authentication mechanisms, robust data management practices and consent. The proposed framework will empower programme managers with a ready reference toolkit for designing, implementing and evaluating primary care platforms for large-scale deployment. In the context of health and wellness centres, building a responsive, resilient and reliable enterprise architecture would be a fundamental path towards strengthening health systems leveraging digital health interventions. An enterprise architecture for primary care is the foundational building block for an efficient national digital health ecosystem. As citizens take ownership of their health, futuristic digital infrastructure at the primary care level will determine the health-seeking behaviour and utilisation trajectory of the nation.


Sign in / Sign up

Export Citation Format

Share Document