What is in a step: On the semantics of statecharts

Pnueli, Amir; Shalev, Moran

doi:10.1007/3-540-54415-1_49

Cited by 153 publications

(145 citation statements)

References 5 publications

Supporting

Mentioning

141

Contrasting

Order By: Relevance

“…This section provides a brief introduction to Statecharts, and recalls the step semantics presented by Pnueli and Shalev in [51].…”

Section: Pnueli and Shalev's Interpretation Of Statechartsmentioning

confidence: 99%

“…As stated in the introduction, Pnueli and Shalev defined coinciding operational and declarative semantics of Statecharts configurations in their paper [51]. Given a configuration C, a step in the sense of Pnueli and Shalev comprises a maximal, globally consistent and causal, set of transitions in trans(C), which are mutually orthogonal, i.e., "consistent" in Statecharts terminology, and triggered by the events offered by the environment or produced by the firing of other transitions in the step.…”

Section: The Pnueli-shalev Step Semanticsmentioning

confidence: 99%

“…Using this enabledness function enabled, we may now present the step-construction procedure of [51] which operationally determines Statecharts steps relative to a configuration C and a set E of environment events:…”

Section: The Pnueli-shalev Step Semanticsmentioning

confidence: 99%

“…One of the many contributions of Amir Pnueli to the field of Computer Science is in the semantics of Statecharts [27,28,25,51,15]. Statecharts is a popular language for specifying and developing reactive systems, which was invented by Harel in the early 1980s [22].…”

Section: Introductionmentioning

confidence: 99%

“…In the words of Pnueli and Shalev, "a proven sign of healthy and robust understanding of the meaning of a programming or a specification language is the possession of both an operational and declarative semantics, which are consistent with one another" [51]. They showed in their seminal paper (cf.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

What Is in a Step: New Perspectives on a Classical Question

Roever

Lüttgen

Mendler

2010

Time for Verification

View full text Add to dashboard Cite

Abstract. In their seminal 1991 paper "What is in a Step: On the Semantics of Statecharts", Pnueli and Shalev showed how, in the presence of global consistency and while observing causality, the synchronous language Statecharts can be given coinciding operational and declarative step semantics. Over the past decade, this semantics has been supplemented with order-theoretic, denotational, axiomatic and game-theoretic characterisations, thus revealing itself as a rather canonical interpretation of the synchrony hypothesis. In this paper, we survey these characterisations and use them to emphasise the close but not widely known relations of Statecharts to the synchronous language Esterel and to the field of logic programming. Additionally, we highlight some early reminiscences on Amir Pnueli's contributions to characterise the semantics of Statecharts.

show abstract

“…This section provides a brief introduction to Statecharts, and recalls the step semantics presented by Pnueli and Shalev in [51].…”

Section: Pnueli and Shalev's Interpretation Of Statechartsmentioning

confidence: 99%

Section: The Pnueli-shalev Step Semanticsmentioning

confidence: 99%

Section: The Pnueli-shalev Step Semanticsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

What Is in a Step: New Perspectives on a Classical Question

Roever

Lüttgen

Mendler

2010

Time for Verification

View full text Add to dashboard Cite

show abstract

Model‐Based Software Testing

El-Far

Whittaker

2002

Encyclopedia of Software Engineering

111

View full text Add to dashboard Cite

Software testing requires the use of a model to guide such efforts as test selection and test verification. Often, such models are implicit, existing only in the head of a human tester, applying test inputs in an ad hoc fashion. The mental model testers build encapsulates application behavior, allowing testers to understand the application's capabilities and more effectively test its range of possible behaviors. When these mental models are written down, they become sharable, reusable testing artifacts. In this case, testers are performing what has become to be known as model-based testing. Model-based testing has recently gained attention with the popularization of models (including UML) in software design and development. There are a number of models of software in use today, a few of which make good models for testing. This paper introduces model-based testing and discusses its tasks in general terms with finite state models (arguably the most popular software models) as examples. In addition, advantages, difficulties, and shortcoming of various model-based approaches are concisely presented. Finally, we close with a discussion of where model-based testing fits in the present and future of software engineering.

show abstract

Specification Formalisms and Models

Wang

2009

Wiley Encyclopedia of Computer Science and Engineering

View full text Add to dashboard Cite

Many specification models are available in the industry, which range from natural languages, to pseudo code, to loose mathematical notations, and to formalisms with rigorous semantics. In this article, we first discuss the general challenges in writing proper specifications. We then discuss issues in choosing appropriate specification models for a system. Then, we briefly review several specification models, which include state machines, Petri nets, process algebras, temporal logics, guarded command languages, pseudo code, comments and assertions, VDM, Z, AMN, and message sequence charts. For each model, we also point to some available tools.

show abstract

What is in a step: On the semantics of statecharts

Cited by 153 publications

References 5 publications

What Is in a Step: New Perspectives on a Classical Question

What Is in a Step: New Perspectives on a Classical Question

Model‐Based Software Testing

Specification Formalisms and Models

Contact Info

Product

Resources

About