Business Capability Maps: Current Practices and Use Cases for Enterprise Architecture Management

This paper provides a state-of-the-art report on the usage of business capability maps in enterprise architecture management. We conducted expert interviews with 25 organizations to reveal the benefits and challenges of capability-based enterprise architecture management and evaluated 14 use cases on the feasibility and benefit of using business capability maps in practice. The results reveal increasing interest and acceptance of the approach in practice and among support organizations

Enterprise Engineering and Management at the Crossroads

The article provides an overview of the challenges and the state of the art of the discipline of Enterprise Architecture (EA), with emphasis on the challenges and future development opportunities of the underlying Information System (IS), and its IT implementation, the Enterprise Information System (EIS). The first challenge is to overcome the narrowness of scope of present practice in IS and EA, and re-gain the coverage of the entire business on all levels of management, and a holistic and systemic coverage of the enterprise as an economic entity in its social and ecological environment. The second challenge is how to face the problems caused by complexity that limit the controllability and manageability of the enterprise as a system. The third challenge is connected with the complexity problem, and describes fundamental issues of sustainability and viability. Following from the third, the fourth challenge is to identify modes of survival for systems, and dynamic system architectures that evolve and are resilient to changes of the environment in which they live. The state of the art section provides pointers to possible radical changes to models, methodologies, theories and tools in EIS design and implementation, with the potential to solve these grand challenges.Griffith Sciences, School of Information and Communication TechnologyNo Full Tex

Automated Modeling with Abstraction for Enterprise Architecture (AMA4EA):Business Process Model Automation in an Industry 4.0 Laboratory

The transformation towards the Industry 4.0 paradigm requires companies to manage large amounts of data. This poses serious challenges with regard to how effectively to handle data and extract value from it. The state-of-the-art research of Enterprise Architecture (EA) provides limited knowledge on addressing this challenge. In this article, the Automated Modeling with Abstraction for Enterprise Architecture (AMA4EA) method is proposed and demonstrated. An abstraction hierarchy is introduced by AMA4EA to support companies to automatically abstract data from enterprise systems to concepts, then to automatically create an EA model. AMA4EA was demonstrated at an Industry 4.0 laboratory. The demonstration showed that AMA4EA could abstract detailed data from the Enterprise Resource Planning (ERP) system and Manufacturing Execution System (MES) to be relevant for a business process model that provided a useful and simplified visualization of production process data. The model communicated the detailed business data in an easily understandable way to stakeholders. AMA4EA is an innovative and novel method that contributes new knowledge to EA research. The demonstration provides sufficient evidence that AMA4EA is useful and applicable in the Industry 4.0 environment

SOA-Based Distributed System in Online Transaction Processing

Service Oriented Architecture (SOA) with transactional workflow support is a state- of- the- art architectural style for constructing enterprise application. In this research, rate of progress activities raise distributed service in a coordinated manner, using transaction context propagating message, coordination protocol and compensation logic. We reviewed the past, present and future of transaction processing and transaction integrity. Most of the challenges and requirement that led to the development and evolution of transaction processing system are still applicable today and recently, we have some intriguing developments. We take an explorative approach to probe the theoretical and implementational feasibility of managing transaction in the web service world

Ontology Matching Techniques for Enterprise Architecture Models

Abstract. Current Enterprise Architecture (EA) approaches tend to be generic, based on broad meta-models that cross-cut distinct architectural domains. Integrating these models is necessary to an effective EA process, in order to support, for example, benchmarking of business processes or assessing compliance to structured requirements. However, the integration of EA models faces challenges stemming from structural and semantic heterogeneities that could be addressed by ontology matching techniques. For that, we used AgreementMakerLight, an ontology matching system, to evaluate a set of state of the art matching approaches that could adequately address some of the heterogeneity issues. We assessed the matching of EA models based on the ArchiMate and BPMN languages, which made possible to conclude about not only the potential but also of the limitations of these techniques to properly explore the more complex semantics present in these models. Enterprise Architecture (EA) is a practice to support the analysis, design and implementation of a business strategy in an organization, considering its relevant multiple domains. In recent years, a variety of Enterprise Architecture To support the matching tasks we have used AgreementMakerLight (AML

Microservice Transition and its Granularity Problem: A Systematic Mapping Study

Microservices have gained wide recognition and acceptance in software industries as an emerging architectural style for autonomic, scalable, and more reliable computing. The transition to microservices has been highly motivated by the need for better alignment of technical design decisions with improving value potentials of architectures. Despite microservices' popularity, research still lacks disciplined understanding of transition and consensus on the principles and activities underlying "micro-ing" architectures. In this paper, we report on a systematic mapping study that consolidates various views, approaches and activities that commonly assist in the transition to microservices. The study aims to provide a better understanding of the transition; it also contributes a working definition of the transition and technical activities underlying it. We term the transition and technical activities leading to microservice architectures as microservitization. We then shed light on a fundamental problem of microservitization: microservice granularity and reasoning about its adaptation as first-class entities. This study reviews state-of-the-art and -practice related to reasoning about microservice granularity; it reviews modelling approaches, aspects considered, guidelines and processes used to reason about microservice granularity. This study identifies opportunities for future research and development related to reasoning about microservice granularity.Comment: 36 pages including references, 6 figures, and 3 table