About: SCXML is a research topic. Over the lifetime, 54 publications have been published within this topic receiving 7290 citations. The topic is also known as: SCXML & State Machine Notation for Control Abstraction.
TL;DR: It is intended to demonstrate here that statecharts counter many of the objections raised against conventional state diagrams, and thus appear to render specification by diagrams an attractive and plausible approach.
TL;DR: An integrated approach towards using UML state machines transformed as DEVS models, available as an upcoming standard, State Chart XML (SCXML) that provides a generic execution environment based on CCXML and Harel State tables.
Abstract: Arizona Center for Integrative M&SECE Department, University of ArizonaTucson, AZ 85721AbstractModeling and Simulation (M&S) for system design and prototyping is practiced today both in the industryand academia. Modeling and Simulation are two di erent areas altogether and have speci c objectives.However, most of the times these two separate areas are taken together. The developed code is tightly wovenaround and model and the underlying simulator that executes it. This constraints both the developmentof model as well as the simulation engine and impacts scalability of the developed code. Modeling is moreart than science and the level of abstraction plays a crucial role in model’s performance. Furthermore, it isdicult to develop a model because it needs both domain knowledge and simulation techniques, which alsorequires communication among users and developers. UML is the preferred method used today in industry,but it lacks simulation power. Discrete Event Speci cation (DEVS) based modeling that separates themodel and the simulator, provides a cleaner methodology to develop models. However DEVS today is usedby engineers who understand discrete event modeling at a much detailed level and are able to translaterequirements to DEVS modeling code. It is oblivious to industry practitioners that use UML due to itsgraphical expressive power. There have been earlier e orts to integrate UML and DEVS but they haven’tsucceeded in providing a transformation mechanism due to inherent di erences in these two modelingparadigms. DEVS state machines are more expressive than UML state machines, require more information,speci cally nite timeouts for each state. This paper presents an integrated approach towards using UMLstate machines transformed as DEVS models. The transformation mechanism is available as an upcomingstandard, State Chart XML (SCXML) that provides a generic execution environment based on CCXML andHarel State tables. We will illustrate the transformation by taking a UML state machine and augmentingit with information during the process using SCXML to make it DEVS capable. Further, we will also showthat the obtained DEVS models belong to a speci c class of DEVS models called Finite Deterministic DEVS(FD-DEVS) that is available as a W3C XML schema.Keywords: DEVS, FD-DEVS, UML-based Modeling, XML, Model Transformation
TL;DR: This paper describes NVIDIA Corporation’s implementation of an editor and runtime for the SCXML statechart standard, used for both prototyping and production of user interfaces, and investigates the usefulness of statecharts in user interaction design.
Abstract: In this paper we describe NVIDIA Corporation’s implementation of an editor and runtime for the SCXML statechart standard. The editor and runtime are used for both prototyping and production of user interfaces, targeted primarily for automotive in-vehicle interfaces. We show how state machines improve the simplicity and stability of application development, particularly when using the hierarchical and parallel states available in SCXML. We investigate the usefulness of statecharts in user interaction design. We further describe subtle additions and deviations from the SCXML standard, the motivations for these changes, and their benefits compared to a strictly standardscompliant implementation. Author Keywords SCXML; state machine; statechart; gui
TL;DR: This paper proposes an approach for matching behavior of BOM components by matching their statemachines and describes the matching process and the implementation of the runtime environment in detail and presents a case study as proof of concept.
Abstract: Base Object Model (BOM) is a component-based standard designed to support reusability and Composability. Reusability helps in reducing time and cost of the development of a simulation process. Composing predefined components such as BOMs is a well known approach to achieve reusability. However, there is a need for a matching mechanism to identify whether a set of components are composable or not. Although BOM provides good model representation, it lacks capability to express semantic and behavioral matching.In this paper we propose an approach for matching behavior of BOM components by matching their statemachines. Our proposed process includes a static and a dynamic matching phase. In the static matching phase, we apply a set of rules to validate the structure of statemachines. In the dynamic matching phase, we execute the statemachines together at an abstract level on our proposed execution framework. We have developed this framework using the State Chart Extensible Markup Language (SCXML), which is a W3C compliant standard. If the execution terminates successfully (i.e. reaches specified final states) we conclude that there is a positive match and the behavior of these BOMs is composable. We describe the matching process and the implementation of our runtime environment in detail and present a case study as proof of concept.
TL;DR: In this article, a system for personalized voice dialogue can include tracking a user's use of voice dialogue states or transitions and progressively offering a user more efficient voice dialogue transitions or states such as voice dialogue transition or states having fewer and fewer words.
Abstract: A method (10) and system (200) for personalized voice dialogue can include tracking (12) a user's use of voice dialogue states or transitions and progressively offering (16) a user more efficient voice dialogue transitions or states such as voice dialogue transition or states having fewer and fewer words. The tracking of dialog states or transitions can include tracking (14) of repeated use of the dialogue states or transitions. A user can be prompted to create a new transition or state. The prompting (18) and confirmation and verification (20) by the user of a new transition or state can be done using SCXML language. The method can further include instantiating (21) the new transition or state with voice tags or words and performing (22) speech recognition using the new transition or state. The method can again determine (23) if the new transition or state is a repeat transition or state.