Operational ASM Semantics behind Graphical SEAM Notation Irina Rychkova, Alain Wegmann 1 , and Pavel Balabko 1 School of Computer and Communication Sciences (I&C), ´ Ecole Polytechnique F´ed´erale de Lausanne (EPFL) CH-1015 Lausanne, Switzerland {Irina.Rychkova, Alain.Wegmann, Pavel.Balabko}@epfl.ch http://lamswww.epfl.ch Abstract. The context of this paper is Enterprise Architecture (EA). EA is a multi-disciplinary approach that allows different specialists to design new business and IT systems and focuses on the integration of these systems. Our group develops a specific EA method that is called SEAM. The current version of SEAM has a formal denotational seman- tics for its modeling language. In order to provide model simulation and checking at each level of abstraction, SEAM needs an operational se- mantics. Currently this work is at the stage of problem setting. In this paper 1 we present SEAM and describe the main research problem. We propose to use ASM as operational semantics for SEAM to verify that models, produced by different specialists are consistent. We illustrate our approach by giving an example of SEAM notation that has already been mapped to ASM. 1 Introduction Enterprise architecture (EA) is a multi-disciplinary approach that enables en- terprises to anticipate or react to necessary business or technical changes. The EA team designs and deploys new organizations and IT systems in the light of necessary changes. In an EA project, the EA team develops a model that represents the enterprise: the enterprise model. The enterprise models are usu- ally structured in hierarchical levels. The highest level describes the marketing aspects, the middle level describes the business processes, and the lower level describes the IT systems.[1] Our group develops a theory for enterprise architecture (EA) and then applies this theory to the development of a specific EA method called SEAM [1]. SEAM stands for the ”Systemic Enterprise Architecture Methodology” or for seamless integration between business and IT. The important parts of SEAM are the method and the notation. The SEAM method explains how to proceed in the analysis and design of the enterprise[1]. 1 This paper is written by Irina Rychkova. Alain Wegmann, the scientific advisor of the project, proposed to study the EA context. This work is a continuation of the work done by Pavel Balabko, who proposed to consider ASM in context of our research problem.