Formalizing and Modeling Enterprise Architecture (EA) Principles with Goal-oriented Requirements Language (GRL)

Item does not contain fulltex

Towards consistent demarcation of enterprise design domains

This article supports the ideology that enterprise engineering (EE) could add more value if EE researchers focus on facilitating effective conversations within design teams to create a common understanding of the enterprise. One way of creating a common understanding is to define and demarcate enterprise design domains in a consistent way. Literature presents different conceptualisations for demarcating design domains, without using a systematic demarcation rationale. As an example, this article introduces Hoogervorst’s approach and associated enterprise design domains to highlight practical difficulties when emerging design principles are applied to four main design domains, as defined by Hoogervorst. Based on the suggestion to apply the basic system design process to demarcate the main enterprise design domains in a consistent way and addressing the need for additional design domains, we present four alternative enterprise design domains, developed via design science research. We also demonstrate the usefulness of the new design domains by presenting several examples of enterprise design cycles that occur during enterprise design.http://link.springer.combookseries/5582018-11-10hj2018Industrial and Systems Engineerin

Formalizing and Modeling Enterprise Architecture (EA) Principles with Goal-Oriented Requirements Language (GRL)

Item does not contain fulltex

An Action Design Research Approach within Enterprise Engineering

Enterprise engineering (EE) is emerging as a new discipline that is multi-disciplinary in nature. As highlighted by researchers within the EE discipline, the current status of EE endeavours as taken by several universities is unclear, which led to several initiatives and publications to develop a research agenda within the enterprise engineering research community. This article builds upon existing work aimed at establishing EE as a discipline, also accepting the epistemological stance of idealism, pragmatism and existential phenomenology as argued by Hoogervorst as an appropriate stance for EE research, prior to suggesting action design research (ADR) as an appropriate research method for EE research. More so, the article presents an Action Design Research within Enterprise Engineering (ADR-in-EE) approach as the main contribution to guide prospective EE researchers towards research within the EE discipline. The ADR-in-EE approach is based on ADR, but provides additional guidance by incorporating the use of an Enterprise Evolution Contextualisation Model (EECM), as well as creativity facilitation in the form of Univation’s brainstorming method. As a second contribution, we experiment with the ADR-in-EE approach and use a survey to extract feedback on the usefulness of the approach. The research findings are mostly positive, with qualitative feedback on further improving ADR-in-EE approach.http://link.springer.com/journal/112132018-04-30hb2016Industrial and Systems Engineerin

Overcoming implementation challenges in enterprise architecture management: a design theory for architecture-driven IT Management (ADRIMA)

Enterprise architecture management (EAM) is acknowledged as a discipline to drive organizational change, to improve IT landscapes' transparency, and to align business and IT. Despite its increasing popularity in practice, many EAM initiatives are confronted with substantial challenges, as demonstrated by the low usage level of enterprise architecture (EA) documentation and enterprise architects' lack of authority, and often fail. This motivates our research, which aims at developing a design theory that may guide organizations to successfully implement EAM. Based on three field studies, we first analyze the issues that arise when implementing EAM in practice. We find that EAM often suffers from being regarded as a separate and parallel initiative, although it needs to be embedded in established management processes and organization. We then suggest a design theory for architecture-driven IT management (ADRIMA) that synthesizes prescriptive knowledge related to embedding EAM practices, artifacts, and roles in the existing IT management processes and organization. By consolidating both IT management and EAM perspectives, our research goes beyond existing EA literature and EA frameworks which describe EAM as a stand-alone management concept focusing on EA models and the EA life cycle