Translation of UML state machines to Modelica: Handling semantic issues

ModelicaML is a UML profile that enables modeling and simulation of systems and their dynamic behavior. ModelicaML combines the power of the OMG UML standardized graphical notation for systems and software modeling, and the simulation power of Modelica. This addresses the increasing need for precise...

Full description

Saved in:
Bibliographic Details
Published in:Simulation (San Diego, Calif.) Calif.), 2013-04, Vol.89 (4), p.498-512
Main Authors: Schamai, Wladimir, Fritzson, Peter, Paredis, Chris JJ
Format: Article
Language:English
Subjects:
Applied sciences
Computer programs
Computer science
control theory
systems
Computer simulation
Computer systems and distributed systems. User interface
Dynamical systems
Dynamics
Exact sciences and technology
execution semantics
Mathematical models
Modelica
ModelicaML
Software
Software engineering
state machine
State machines
statechart
TECHNOLOGY
TEKNIKVETENSKAP
UML
Unified Modeling Language
Citations: Items that this one cites
Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:ModelicaML is a UML profile that enables modeling and simulation of systems and their dynamic behavior. ModelicaML combines the power of the OMG UML standardized graphical notation for systems and software modeling, and the simulation power of Modelica. This addresses the increasing need for precise and integrated modeling of products containing both software and hardware. This article discusses the usage of executable UML state machines for system modeling, i.e. usage of the same formalism for describing the state-based dynamic behavior of physical system components and software. Moreover, it points out that the usage of Modelica as an action language enables an integrated simulation of continuous-time and reactive/event-based system dynamics. The main purpose of this article is however to highlight issues that are identified regarding the UML specification which are experienced with typical executable implementations of UML state machines. The issues identified are resolved and rationales for the taken design decisions are provided.
ISSN:0037-5497
1741-3133
1741-3133
DOI:10.1177/0037549712470296