In service oriented computing different techniques for monitoring Service Level Agreements (SLAs)

This paper investigates whether the ArchiMate modelling language can be used to model the most commonly used strategy models and concepts. This can be considered as an important step into closing the gap between Business and IT. By having a better understanding of what is needed to model strategy, we can analyse if the current version of the ArchiMate modelling language is sufficient or what additions need to be made. Also by knowing how the strategic concepts are used in the context of business we hope to improve the way they are modelled with ArchiMate. In order to do this, we start by taking a look at the strategic planning process and identify its main concepts. It starts by presenting the strategic planning process and its corresponding concepts and strategy models. This is followed by an analysis of the suitability of ArchiMate in which we argue that resource and capability concepts are concepts that should be included in the next versions of the language. Lastly, we demonstrate how strategy can be modelled with the help of a case study.

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.

No abstract

No abstract

No abstract

Abstract-Collaborations among businesses can be described from different viewpoints. Two of these viewpoints are the value viewpoint, representing estimated values exchanged in a collaboration, and the coordination viewpoint, representing messages exchanged between the actors to coordinate the execution of a collaboration. To observe and maintain the value viewpoint during the complete life cycle, the estimated values have to be validated during the execution of the collaboration. However, since the value model is not implemented, the necessary information for monitoring the value viewpoint needs to be derived from the coordination viewpoint. Relating coordination and value viewpoint is a difficult process because the coordination viewpoint lacks information present in the value viewpoint. In this paper we define the relation between both viewpoints for the complete collaboration life cycle. Furthermore, we provide a mechanism to monitor the collaboration from a value viewpoint.

No abstract