An Enterprise Architecture Methodology for Business-IT Alignment: Adopter and Developer Perspectives

Abstract

This paper proposes the use of an enterprise architecture methodology known as the Systemic Enterprise Architecture Methodology to determine the relevance of EA in addressing the business-IT alignment. A construct that characterized EA was developed based on review of the literature. A theoretical framework build upon the Systemic Enterprise Architecture Methodology (SEAM) was used based on a business-IT alignment market, in which supplier business systems compete to provide a value to an adopter business system. Data was empirically gathered based on survey respondents who are concerned with the adoption, planning and implementation of EA in their organizations. Respondents were managers and executives representing the IT and senior level management of public and private organizations in Malaysia. The data collected was then analyzed based on the following factors: (1) EA business issues; (2) EA environment; (3) EA governance; and (4) EA methods, tools and frameworks. Comparative analysis was carried out based on the four factors to examine the trend and status of EA adoption and implementation in Malaysia vis-à-vis the international scenario. Statistical analysis was used to validate the SEAM, which was found to be relevant in addressing the business-IT alignment.

Enterprise architecture and enterprise architecture artifacts: Questioning the old concept in light of new findings

“…Consequently, the declared usage, as well as non-usage, of EA frameworks cannot be considered as a significant factor in EA research. For instance, all the industry surveys showing which EA frameworks are used in organizations (Ambler, 2010; Aziz & Obitz, 2007; Buckl, Ernst, Lankes, Matthes, & Schweda, 2009; Cameron & McMillan, 2013; Dahalin, Razak, Ibrahim, Yusop, & Kasiran, 2010; Gall, 2012; Obitz & Babu, 2009; Schekkerman, 2005; Scholtz, Calitz, & Connolley, 2013) cannot be considered as informative since no specific correlation between the declared use of EA frameworks and actual EA practices can be observed. Generally, EA frameworks demonstrate evident signs of management fads (Miller & Hartwick, 2002; Miller, Hartwick, & Le Breton-Miller, 2004), while their prescriptions are very distant from the established EA best practices widely adopted in industry.…”

Studi Komparatif Model Proses Perangkat Lunak Terhadap Karakteristik Sistem ERP

“…Untuk itu, ada persyaratan untuk set standar langkah, teknik, dan alat untuk memecahkan masalah ini untuk membangun perangkat lunak, yang disebut model proses perangkat lunak. Hal ini digunakan untuk mengembangkan dan mendukung sistem informasi mereka dan pengembangan sistem ini sering mengikuti siklus pengembangan perangkat lunak [2] [3] [4].…”

A new approach for collaborative Enterprise Architecture development

“…It examines the key business, information, application, and technology strategies and their impact on business functions. It provides the framework for planning and implementing a rich, standards-based, digital information infrastructure with well-integrated services and activities [4]. It's a strategic information asset base, which defines the mission, the information necessary to perform the mission, the technology, and the transformational processes for implementing new technologies in response to the changing mission needs.…”