Business Architecture Development for Integrated Agriculture Information System (Iais) Using Togaf Framework

Abstract

INTRODUCTION:Indonesia is one of the largest agricultural countries in the world. During 2010 - 2013, this sector has contributed 14.9% in Indonesia's Gross Domestic Product (GDP) (Direktorat Pangan dan Pertanian, 2013) with 26.14 million of household works in agriculture sector (Badan Pusat Statistik, 2013). Based on those data, agricultural sector has big influence to Indonesia economic and society welfare. One of its ways to improve productivity and quality of agricultural product in Indonesia is by utilization of Information and Communication Technology in Agriculture Sector.Implementation of Information and Communication Technology in agricultural sector gives some benefits: (1) Increasing agriculture production; (2) Mitigating risk in agriculture sector; (3) Supporting profit optimization to farmers; (4) Increasing effectiveness in information sharing and communication between stakeholder in agriculture sector; (5) Increasing farmer's bargaining power; and (6) Supporting agriculture environmentally friendly (Delima, Santoso, & Purwadi, 2016). ICT brings big benefits to increase productivity, but implementation of ICT is still minimized. Some of the applications of agriculture with Indonesia language as the main language is still limited and can't be accessed, such as publication, public service, and product sales and agriculture tools from some vendors. Meanwhile, some of agricultural website which use Indonesian language as the main language as information and knowledge source is still limited (Delima & Purwadi, 2015). This problem is the main reason to develop Integrated Agriculture Information System (IAIS).Nowadays, IAIS is still in development phase. This system is specifically in place to process data, information, and knowledge in agriculture sector. IAIS is planned to be an integrated agriculture system that has some connected subsystems and able to link stakeholders in agriculture sector.The development process of a complex and integrated system needs well planned activities in some phases in order for all components in the system to have good interoperability capacity. System development plan is covered in system blueprint. System blueprint includes strategic development: (1) Organization vision and mission; (2) Data, Information, and Knowledge requirements; (3) Infrastructure requirements; (4) Application requirements; (5) Human resources requirements. Blueprint can be a guidance to develop and implement system.Enterprise Architecture (EA) approach is used to develop IAIS blueprint. Enterprise Architecture is used because of its ability to integrate all functions in Information Technology with organization business process (Marques, Borges, Sousa, & Pinho, 2011). Enterprise Architecture has 4 different architecture layers: (1) Business Architecture; (2) Application Architecture; (3) Information Architecture and (4) Technical Architecture. This article discusses about the development of Business Architecture for IAIS. Business Architecture Component is developed based on TOGAF Framework. Business Architecture is the second component in TOGAF and has 6 catalogues, 3 matrixes, and 9 diagrams. Business Architecture can help in determining the business activities and stakeholders involved in every business processes. Thus, will ease to develop application and information architecture.LITERATURE REVIEW:ENTERPRISE ARCHITECTURE:Enterprise Architecture is an architecture to design an enterprise system. This architecture involves business process modelling and information characteristics (Schekkerman, 2004). By using EA, an organization can identify system needs to support business process and align the organization needs and information technology functions (Pereira & Sousa, 2005). This architecture is also able to give information and knowledge to decision makers. Enterprise Architecture is able to give integration perspective for all information technology function which is related with organization business process (Marques, Borges, Sousa, & Pinho, 2011). …