Article

{{post_terms.hashtags}}

Collaborative Business Process Management – A Literature-based Analysis of Methods for Supporting Model Understandability

Due to the growing amount of cooperative business scenarios, collaborative Business Process Management (cBPM) has emerged. The increased number of stakeholders with minor expertise in process modeling leads to a high relevance of model understandability in cBPM contexts. Despite extensive works in the research fields of cBPM and model understandability in BPM, there is no analysis and comprehensive overview of methods supporting process model understandability in cBPM scenarios. To address this research gap, this paper presents the results of a literature review. The paper identifies concepts for supporting model understandability in BPM, provides an overview of methods implementing these concepts, and discusses the methods’ applicability in cBPM. The four concepts process model transformation, process model visualization, process model description, and modeling support are introduced. Subsequently, 69 methods are classified and discussed in the context of cBPM. Results contribute to revealing existing academic voids and can guide practitioners in cBPM scenarios.

Three Schools of Thought on Enterprise Architecture

Three schools of thought on enterprise architecture exist, each with its own belief system (definitions, concerns, assumptions, and limitations). A novel taxonomy of these schools creates a starting point for resolving terminological challenges to help establish enterprise architecture as a discipline.

Seeking to Control Enterprise with Architecture: the Limits and Value of an Engineering Approach From the Perspective of an Enterprise Architect

In this (DMan) thesis, I challenge assumptions underlying my discipline of enterprise architecture that led to two choices facing practitioners: either to work with tools and techniques which predict and control changes towards predetermined ends or to accept informal processes that are unpredictable and wasteful. Orthodox enterprise architecture defines an enterprise as an organisation, which is a system, and prescribes methods that seek to provide control over the transformation of an organisation into a desired state of affairs by achieving complete knowledge of the system before initiating the desired transformation. Drawing on complexity sciences, I offer a different perspective on organisation and claim that organising what we do is an aspect of doing what we do. Organising is process. I furthermore claim that the people who are organising what we do can act spontaneously and surprise both themselves and others, but often they act habitually. Habitual ways of acting allow us to anticipate to some extent how others are likely to respond to us and, as we grow up, we learn how to behave ourselves, that is, how to adjust our behaviour to what we judge socially acceptable to increase the likelihood of being able to garner support and collaboration. I posit that social control is exercised in this way as mutual self-adjustment that forms what is normal and valued conduct. In other words, our shared social norms and values thus paradoxically and simultaneously form individuals and their conduct and are formed by individuals and their conduct. I claim that in this way we have partial, but never full, knowledge of how others generally respond to certain behaviour of ours. We can ever have only partial knowledge of that which is—in the words of Mannheim—in the process of becoming. I therefore reject the central assumptions upon which orthodox enterprise architecture is based. In organisations, we engineer and exploit mechanical mechanisms that can conduct certain action more effectively and efficiently than people can. Materiality, objects in the world, can resist attempts to shape them to suit our needs but do so without intentionality or spontaneity. Accommodating material resistance is thus repeatable. Enterprise architecture as a discipline grew out of engineering of physical mechanisms and assumes a similar repeatability and predictability when working with the social, which I find to be an unwarranted assumption. I argue against the claim of orthodox enterprise architecture that we can bring about a pre-determined state in a controlled fashion and against the claim that without such control we have informal processes that are inevitably unpredictable and wasteful. I posit that what emerges is paradoxically stable instabilities of socially enabled and constrained recognisable patterns of behaviour. When devising a mechanism in a physical object, such as a software programme, a repertoire of scripted action is transcribed into it which remains constant until transcription is renewed. Transcription has a tendency to render action less fluid. Some members of an organisation may judge particular scripted action to be awkward or detrimental while others may judge the same scripted action to be efficient and beneficial. Thus, determining which scripted action to transcribe into mechanisms is a highly political decision which attracts the attention of skilful political players. Enterprise architects can have a valuable role to play, since we have a better than average partial knowledge about technology, and since technology is increasingly important for many enterprises. I posit that becoming more aware of power and power plays, developing a feel for the game, and becoming more detached about our involvement will allow us to play into what is emerging socially with more political awareness and expertise.

Investigation of the Lack of Common Understanding in the Discipline of Enterprise Architecture : A Systematic Mapping Study

The number of publications, along with the organization of new conferences are a couple of the relevant elements that usually indicate the progress of an area of study over the years. This is definitely true in the case of the Enterprise Architecture (EA) discipline, which went from having its first journal article published in 1989 to over two hundred published articles by 2015. But in spite of this evolution, EA is still suffering from a considerable lack of common understanding. It has become very important to investigate the current state of affairs concerning the EA discipline through its relevant publications in order to shed some light on this challenge. 171 journal papers published between 1990 and 2015 were systematically selected and examined in order to accomplish this investigation. The quantitative and qualitative findings of this examination show that EA is a young discipline which raises a growing interest in recent years. This examination also confirms the lack of common understanding in EA, which can be observed in the different descriptions of the term “enterprise architecture,” and in the diversity of perspective with regards to the whole discipline. Several issues related to this lack has been reported, such as multidisciplinary issue, language issue, structure of research and mode of observation issues. The major issue concerns the absence of enough research to shed some light on this challenge. In addition to this investigation, helpful directions for future research in this area was proposed.

Exploring the future of enterprise architecture: A Zachman perspective

Today, and for the foreseeable future, organizations will face ever-increasing levels of complexity and uncertainty. Many believe that enterprise architecture (EA) will help organizations address such difficult terrain by guiding the design of adaptive and resilient enterprises and their information systems. This paper presents the Grand Challenges that we believe will challenge organizations in the future and need to be addressed by enterprise architecture. As a first step in using enterprise architecture as a solution for overcoming identified challenges, the Zachman Enterprise Architecture Framework is used to guide and structure the discussion. The paper presents the Grand Challenges and discusses promising theories and models for addressing them. In addition, current advances in the field of enterprise architecture that have begun to address the challenges will be presented. In conclusion, final thoughts on the future of enterprise architecture as a research field and a profession are offered.

Business Cloudification – An Enterprise Architecture Perspective

Cloud computing is emerging as a promising enabler of some aspects of the ‘agile’ and ‘lean’ features that businesses need to display in today’s hyper-competitive and disruptive global economic ecosystem. However, it is increasingly obvious that there are essential prerequisites and caveats to cloudification that businesses need to be aware of in order to avoid pitfalls. This paper aims to present a novel, Enterprise Architecture-based approach towards analysing the cloudification endeavour, adopting a holistic paradigm that takes into account the mutual influences of the entities and artefacts involved, in the context of their life cycles. As shown in the paper, this approach enables a richer insight into the ‘readiness’ of a business considering embarking on a cloudification endeavour and therefore empowers management to evaluate consequences of- and take cognisant decisions on the cloudification extent, type, provider etc. based on prompt information of appropriate quality and deta