Dynamic Consistency Between Value and Coordination Models – Research Issues

Abstract

Inter-organizational business cooperations can be described from different viewpoints each fulfilling a specific purpose. Since all viewpoints describe the same system they must not contradict each other, thus, must be consistent. Consistency can be checked based on common semantic concepts of the different viewpoints. This is sufficient for equal concepts, while weakly related concepts, e.g. related to runtime behavior of viewpoints, have to be considered explicitly. In this paper we identify dynamic consistency issues correlated to the runtime behavior between value and coordination viewpoints on behalf of an example. In particular, an issue class on occurrence estimations of execution options and an issue class on granularity differences in modelling are identified and illustrated.

From Business Value Model to Coordination Process Model

“…Most of these approaches have solely considered consistency checking of static aspects, i.e., during design time and do not consider the runtime behavior of a model [4,5,6]. Bodenstaff [7,8] has introduced another approach toward consistency checking by considering the runtime behavior of the coordination process models. These approaches don't use the same definition for consistency and none of them is comprehensive enough to justify the consistency of these two models solely.…”

Managing dependency relations in inter-organizational models

“…Since the goal of this chapter is to illustrate usability of our method to business and process models we exclude repetitions for the sake of readability. However, a formalization of consistency constraints including such repetitions can be found in a technical report extending this chapter [20].…”

Assessing business-IT alignment in networked organizations

“…Nine theories and eight models, developed elsewhere, were identified as potentially useful to give insights for understanding the processes related to B-ITa in CNOs presented in the previous section (e.g., [21,22,48,57,73,81,90,95,122,136,138,189,204,206,260,302,310,312]). By 'model' we mean a conceptual model, i.e., a set of constructs used to describe B-ITa or a domain of B-ITa.…”

“…Based on this statement, Bodenstaff et al [22] claim that it is important to combine profitability models and process models with event logs. Event logs represent an additional view of the ISs.…”

“…The combination of the two models with event logs represents thus the currect ISs and they should therefore be consistent, i.e., not contradict each other. The theory and methods presented by Bodenstaff et al [22] help to establish and maintain a quantitative understanding of the consistency between event logs and process and profitability models. This allows CNOs (i) to gain a clear view of the performance of their processes in support of quality and process-performance objectives, and (ii) to provide the data and models to quantitatively manage the CNOs projectsbecause event logs enable traceability of execution processes during collaboration.…”