2015
DOI: 10.4204/eptcs.181.3
|View full text |Cite
|
Sign up to set email alerts
|

Towards Practical Graph-Based Verification for an Object-Oriented Concurrency Model

Abstract: To harness the power of multi-core and distributed platforms, and to make the development of concurrent software more accessible to software engineers, different object-oriented concurrency models such as SCOOP have been proposed. Despite the practical importance of analysing SCOOP programs, there are currently no general verification approaches that operate directly on program code without additional annotations. One reason for this is the multitude of partially conflicting semantic formalisations for SCOOP (… Show more

Help me understand this report
View preprint versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
9
0

Year Published

2016
2016
2019
2019

Publication Types

Select...
3
2

Relationship

2
3

Authors

Journals

citations
Cited by 6 publications
(9 citation statements)
references
References 25 publications
(51 reference statements)
0
9
0
Order By: Relevance
“…There are several established and contrasting semantics of Scoop [6,18,26,29,40] including a comprehensive reference semantics for RQ in Maude's conditional rewriting logic [26], and a semantics for the core of QoQ in the form of simple structural operational rules [40]. These formalisations, however, cannot easily be used for semantic comparisons, due to their varying levels of detail, coverage, extensibility, and tool support.…”
Section: A Graph-based Semantic Model For the Scoop Familymentioning
confidence: 99%
See 1 more Smart Citation
“…There are several established and contrasting semantics of Scoop [6,18,26,29,40] including a comprehensive reference semantics for RQ in Maude's conditional rewriting logic [26], and a semantics for the core of QoQ in the form of simple structural operational rules [40]. These formalisations, however, cannot easily be used for semantic comparisons, due to their varying levels of detail, coverage, extensibility, and tool support.…”
Section: A Graph-based Semantic Model For the Scoop Familymentioning
confidence: 99%
“…We demonstrate its use by formalising the two principal execution models of Scoop, analysing a representative set of programs with respect to both, and highlighting some behavioural and deadlock-related discrepancies that the workbench uncovers automatically. Our workbench is based on a modular and parameterisable graph transformation system (Gts) semantics, built upon our preliminary modelling ideas in [18], and implemented in the generalpurpose Gts analysis tool Groove [16]. We leverage this powerful formalism to atomically model complex programmer-level abstractions, and show how its…”
mentioning
confidence: 99%
“…In [40] SCOOP programs are verified for deadlocks and other behavioral properties using GROOVE [41]. The work in [40] proposes a redefinition of the most common features of the SCOOP semantics based on graph transformation systems (GPSs).…”
Section: Discussionmentioning
confidence: 99%
“…, q n }. Hence, assuming a predefined system configuration deadlock , the SCOOP transition rule in Maude corresponding to (40) can be written as:…”
Section: Formalizing Deadlocks In Scoopmentioning
confidence: 99%
“…We discuss how the visual yet algebraic nature of our Gts models can be used to ascertain soundness, and highlight how our approach could be applied to similar concurrent, asynchronous, distributed languages. This is a revised and extended version of our FASE 2016 paper, "A Graph-Based Semantics Workbench for Concurrent Asynchronous Programs" [CHP16] (itself based upon the preliminary modelling ideas in [HPCM15]), adding the following new content: (i) a new Gts semantics covering the distributed programming abstractions of D-Scoop, formalised orthogonally to the others by extending an existing semantics and not just replacing the components of one; (ii) a presentation of the underlying, compositional metamodel to which the family of Scoop and D-Scoop semantics all conform, including a discussion of the metamodel's genericity; (iii) an expanded evaluation that additionally explores the state spaces of our benchmarks in fully distributed contexts; and (iv) a significantly revised presentation, including new details, explanations, and examples throughout the paper.…”
Section: Introductionmentioning
confidence: 99%