Technical Report

Hybrid Sequence Charts

Author(s): Radu Grosu, Ingolf Krüger, Thomas Stauner
Year: 1999
Number: TUM-I9914
Editor:
CR Classification: D.2.1, C.3
CR General Terms: Design, Languages
Keywords: Real-time and hybrid systems, systems engineering, requirements engineering, specification, formal methods
Abstract:We introduce Hybrid Sequence Charts (HySCs) as a visual description technique for communication in hybrid system models. To that end, we adapt a subset of the well-known MSC syntax to the application domain of hybrid systems. The semantics of HySCs is different from standard MSC semantics. Most notably, we use a shared variables communication model and assume the existence of a continuous, global clock. Similar to their classic counterpart HySCs can be advantageously used in the early phases of the software development process. In particular, in the requirements capture phase, they improve the dialog between customers and application experts. They complement existing formalisms like hybrid automata by focusing on the interaction between the system's components. We outline the key concepts and the usage of HySCs along an example, the specification of an electronic height control system. Then we define their formal semantics.

Available as compressed Postscript

BibTeX-Entry:

@techreport{GKS99, author = {Radu Grosu and Ingolf Krüger and Thomas Stauner}, title = {Hybrid Sequence Charts}, number = {TUM-I9914}, institution = {Technische Univerit\"at M\"unchen}, year = {1999}, url = {http://www4.informatik.tu-muenchen.de/reports/GKS99.html}, abstract = {We introduce Hybrid Sequence Charts (HySCs) as a visual description technique for communication in hybrid system models. To that end, we adapt a subset of the well-known MSC syntax to the application domain of hybrid systems. The semantics of HySCs is different from standard MSC semantics. Most notably, we use a shared variables communication model and assume the existence of a continuous, global clock. Similar to their classic counterpart HySCs can be advantageously used in the early phases of the software development process. In particular, in the requirements capture phase, they improve the dialog between customers and application experts. They complement existing formalisms like hybrid automata by focusing on the interaction between the system's components. We outline the key concepts and the usage of HySCs along an example, the specification of an electronic height control system. Then we define their formal semantics.}, CRClassification = {D.2.1, C.3}, CRGenTerms = {Design, Languages}}