Verification and Code Generation for Timed Transitions in pCharts

Nokovic, Bojan; Sekerinski, Emil

doi:10.1145/2641483.2641522

Cited by 4 publications

(4 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Probabilistic junctions, also used in other techniques [58,59], are a special form of junction introduced to capture probabilistic choices. Only transitions from a probabilistic junction can be labelled with probability values, which must add up to 1.…”

Section: Notationmentioning

confidence: 99%

Probabilistic modelling and verification using RoboChart and PRISM

Cavalcanti

Foster

et al. 2021

Softw Syst Model

View full text Add to dashboard Cite

RoboChart is a timed domain-specific language for robotics, distinctive in its support for automated verification by model checking and theorem proving. Since uncertainty is an essential part of robotic systems, we present here an extension to RoboChart to model uncertainty using probabilism. The extension enriches RoboChart state machines with probability through a new construct: probabilistic junctions as the source of transitions with a probability value. RoboChart has an accompanying tool, called RoboTool, for modelling and verification of functional and real-time behaviour. We present here also an automatic technique, implemented in RoboTool, to transform a RoboChart model into a PRISM model for verification. We have extended the property language of RoboTool so that probabilistic properties expressed in temporal logic can be written using controlled natural language.

show abstract

Section: Notationmentioning

confidence: 99%

Probabilistic modelling and verification using RoboChart and PRISM

Cavalcanti

Foster

et al. 2021

Softw Syst Model

View full text Add to dashboard Cite

show abstract

“…Model checking allows to explore all possible system states in a systematic manner. In our approach, the system model is described by pCharts [21], a version of hierarchical state machines extended with probabilistic transitions, timed transitions, stochastic timing, and costs/rewards. Using pCharts we can specify both a system and its environment.…”

Section: Figure 1: Conventional Software Design Processmentioning

confidence: 99%

“…The same formalism, pCharts is used to describe the system model and the environment (unlike in classical discrete event systems). Code is generated according to the algorithm presented in [21], and tested on a number of case studies. Although it is not formally proved to be correct, we believe that generated code is trustworthy.…”

Section: Figure 1: Conventional Software Design Processmentioning

confidence: 99%

A Holistic Approach in Embedded System Development

Nokovic

Sekerinski

2015

Electron. Proc. Theor. Comput. Sci.

Self Cite

View full text Add to dashboard Cite

We present pState, a tool for developing "complex" embedded systems by integrating validation into the design process. The goal is to reduce validation time. To this end, qualitative and quantitative properties are specified in system models expressed as pCharts, an extended version of hierarchical state machines. These properties are specified in an intuitive way such that they can be written by engineers who are domain experts, without needing to be familiar with temporal logic. From the system model, executable code that preserves the verified properties is generated. The design is documented on the model and the documentation is passed as comments into the generated code. On the series of examples we illustrate how models and properties are specified using pState.Comment: In Proceedings F-IDE 2015, arXiv:1508.0338

show abstract

“…For (sub-) charts without probabilistic transitions, executable code can be generated. Thus pCharts can model both the system under development as well as its environment [28].…”

Section: Introductionmentioning

confidence: 99%

A Notebook Format for the Holistic Design of Embedded Systems (Tool Paper)

Park

Sekerinski

2018

Electron. Proc. Theor. Comput. Sci.

Self Cite

View full text Add to dashboard Cite

This paper proposes the use of notebooks for the design documentation and tool interaction in the rigorous design of embedded systems. Conventionally, a notebook is a sequence of cells alternating between (textual) code and prose to form a document that is meant to be read from top to bottom, in the spirit of literate programming. We extend the use of notebooks to embedded systems specified by pCharts. The charts are visually edited in cells inline. Other cells can contain statements that generate code and analyze the charts qualitatively and quantitatively; in addition, notebook cells can contain other instructions to build the product from the generated code. This allows a notebook to be replayed to re-analyze the design and re-build the product, like a script, but also allows the notebook to be used for presentations, as for this paper, and for the inspection of the design. The interaction with the notebook is done through a web browser that connects to a local or remote server, thus allowing a computationally intensive analysis to run remotely if needed. The pState notebooks are implemented as an extension to Jupyter. The underlying software architecture is described and the issue of proper placement of transition labels in charts embedded in notebooks is discussed.

show abstract

Verification and Code Generation for Timed Transitions in pCharts

Cited by 4 publications

References 20 publications

Probabilistic modelling and verification using RoboChart and PRISM

Probabilistic modelling and verification using RoboChart and PRISM

A Holistic Approach in Embedded System Development

A Notebook Format for the Holistic Design of Embedded Systems (Tool Paper)

Contact Info

Product

Resources

About