Claim Missing Document
Check
Articles

Found 3 Documents
Search
Journal : JURNAL SISTEM INFORMASI BISNIS

Analisis Tingkat Kematangan Adopsi Service Oriented Architecture Menggunakan ISO/IEC 16680 (OSIMM) Mutiah, Nurul; Febriyanto, Ferdy
JSINBIS (Jurnal Sistem Informasi Bisnis) Vol 11, No 1 (2021): Volume 11 Nomor 1 Tahun 2021
Publisher : Universitas Diponegoro

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.21456/vol11iss1pp18-25

Abstract

Enterprise application integration makes data sharing easier, efficient and provides flexibility for organizations to seize opportunities and respond to stakeholder needs. Faculty of Mathematics and Natural Sciences (FMIPA) Tanjungpura University is an organization that wants to apply information technology effectively to support its business processes. Currently the application at FMIPA is built with different platforms and databases so that it cannot be integrated to share data between parts of the organization. FMIPA intends to build a service-oriented technology architecture to support the realization of organizational goals. SOA (Service Oriented Architecture) can be used as a framework for enterprise application integration. SOA adoption is often not as expected because organizations do not plan their processes comprehensively. It is necessary to measure the maturity level of the organization's SOA adoption so that the current state of the organization's SOA and future expectations can be found. ISO/IEC 16680 (OSIMM) is a method for measuring the SOA maturity level with 7 levels of maturity and 7 dimensions. To expedite the SOA adoption process in FMIPA, SOA maturity level was measured using ISO/IEC 16680. Based on measurements of the seven dimensions of SOA at ISO/IEC 16680, it was found that the current level of SOA adoption maturity (As-Is) at FMIPA Untan was at the level one (Silo), while the expected maturity level (To-Be) is level four (Service). Gap analysis then carried out related to the gap in maturity levels, and is followed by making recommendations dan roadmap for SOA adoption.
Analisis Tingkat Kematangan Adopsi Service Oriented Architecture Menggunakan ISO/IEC 16680 (OSIMM) Mutiah, Nurul; Febriyanto, Ferdy
JSINBIS (Jurnal Sistem Informasi Bisnis) Vol 11, No 1 (2021): Volume 11 Nomor 1 Tahun 2021
Publisher : Universitas Diponegoro

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.21456/vol11iss1pp18-25

Abstract

Enterprise application integration makes data sharing easier, efficient and provides flexibility for organizations to seize opportunities and respond to stakeholder needs. Faculty of Mathematics and Natural Sciences (FMIPA) Tanjungpura University is an organization that wants to apply information technology effectively to support its business processes. Currently the application at FMIPA is built with different platforms and databases so that it cannot be integrated to share data between parts of the organization. FMIPA intends to build a service-oriented technology architecture to support the realization of organizational goals. SOA (Service Oriented Architecture) can be used as a framework for enterprise application integration. SOA adoption is often not as expected because organizations do not plan their processes comprehensively. It is necessary to measure the maturity level of the organization's SOA adoption so that the current state of the organization's SOA and future expectations can be found. ISO/IEC 16680 (OSIMM) is a method for measuring the SOA maturity level with 7 levels of maturity and 7 dimensions. To expedite the SOA adoption process in FMIPA, SOA maturity level was measured using ISO/IEC 16680. Based on measurements of the seven dimensions of SOA at ISO/IEC 16680, it was found that the current level of SOA adoption maturity (As-Is) at FMIPA Untan was at the level one (Silo), while the expected maturity level (To-Be) is level four (Service). Gap analysis then carried out related to the gap in maturity levels, and is followed by making recommendations dan roadmap for SOA adoption.
Perancangan Arsitektur Enterprise FMIPA UNTAN Menggunakan Kerangka Kerja TOGAF Berbasis SOA Nurul Mutiah; Ferdy Febriyanto
JSINBIS (Jurnal Sistem Informasi Bisnis) Vol 12, No 2 (2022): Volume 12 Nomor 2 Tahun 2022
Publisher : Universitas Diponegoro

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.21456/vol12iss2pp116-123

Abstract

The research aims to develop an Enterprise Architecture from FMIPA UNTAN, this is based on the many individual information systems that have been developed by FMIPA UNTAN which are not integrated in data and technology. This situation results in overlapping data that can affect the effectiveness of decision making within the organization. The designed Enterprise Architecture implements the concept of service-oriented architecture in order to support the integration between the business layer and the organization's technology layer. To support the research, several concepts are used, such as TOGAF as a framework for developing Enterprise Architecture, Service Oriented Architecture as a supporter for integration of architectural layers, and Archimate and Business Process Modeling Notation as a modeling language used to create architectural artifacts. The stages of the research included problem identification, the Enterprise Architecture development process followed the stages of TOGAF ADM namely the preliminary phase, architectural vision, business architecture, information system architecture, technology architecture, and making an architecture implementation roadmap. The results of the development of Enterprise Architecture are architectural artifacts consisting of catalogs, matrices, and diagrams of business, information system, and technology architecture. Based on the design results, it is found that the Enterprise Service Bus concept in Service Oriented Architecture can be used to support application and data integration in organization, as well as the concept of service access can bridge the gap between the business layer and the technology layer.