Abstract
Software development is a complex process and the information technology market is faced by many challenges. Among the challenges is the effect of technology "platforms" change (languages, operating-systems, interoperability solutions, architecture frameworks etc.). Model Driven Architecture (MDA) is a new development method as a positive effort from the Object Management Group (OMG) to overcome software development problems including but not limited to technology change. The philosophy of MDA regarding technology change is the separation of concerns. In MDA, structures and behaviors based on the business functions are abstracted and modeled in a Platform Independent Model (PIM). The implementation specific structures and behaviors are modeled in a Platform Specific Model (PSM). The PIM is then realized into the PSM through a mapping process to automatically generate the software. Current practice shows that MDA approach works quite well but, in most cases, behavioral models are used for other purposes like documentation rather than complementing the structural models to facilitate automatic software generation. This paper examines the issues and challenges when mapping behavior models between different abstraction layers, respectively PIM and PSM using state machine models. A general solution to one of those challenges is discussed and outlined using a case study.