2010
DOI: 10.1007/978-3-642-11811-1_10
|View full text |Cite
|
Sign up to set email alerts
|

An Imperative Extension to Alloy

Abstract: We extend the Alloy language with the standard imperative constructs; we show the mix of declarative and imperative constructs to be useful in modeling dynamic systems. We present a translation from our extended language to the existing first-order logic of the Alloy Analyzer, allowing for efficient analysis of models.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
13
0

Year Published

2013
2013
2018
2018

Publication Types

Select...
4
3
1

Relationship

1
7

Authors

Journals

citations
Cited by 17 publications
(13 citation statements)
references
References 16 publications
0
13
0
Order By: Relevance
“…Nonetheless, such ad hoc specification is error-prone and verbose, and forces the developer to be concerned with particularities of the idiom rather than with the properties that he actually wishes to verify, and as a consequence regular Alloy is not well-suited to address R4. To overcome this limitation, considerable research has been dedicated to enhance Alloy with dynamic behavior [11,5,18,25,8]. The main drawback of these approaches is that they compromise the flexibility that the Alloy users are accustomed to, introducing syntactic extensions that force them to adhere to specific idioms, and consequently breaking the R3 requirement.…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…Nonetheless, such ad hoc specification is error-prone and verbose, and forces the developer to be concerned with particularities of the idiom rather than with the properties that he actually wishes to verify, and as a consequence regular Alloy is not well-suited to address R4. To overcome this limitation, considerable research has been dedicated to enhance Alloy with dynamic behavior [11,5,18,25,8]. The main drawback of these approaches is that they compromise the flexibility that the Alloy users are accustomed to, introducing syntactic extensions that force them to adhere to specific idioms, and consequently breaking the R3 requirement.…”
Section: Related Workmentioning
confidence: 99%
“…Although expressible in regular Alloy (via said idioms), verifying such properties with the Analyzer requires some insightfulness and care from the user, to avoid the spurious counter-examples that usually occur with a naive encoding of the bounded model-checking technique [25,8]. The technique from [18] enhances Alloy with imperative constructs, again undermining R3. In contrast, the technique proposed in [5] extends the relational logic of Alloy with CTL temporal logic.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…In this work we restrict ourselves to declarative constructs, disregarding imperative ones (known 1 http://www.eclipse.org/atl/ in ATL as called rules and do blocks). Giving semantics to imperative constructs in Alloy's relational logic is doable (see, for example, [38]), but the need to explicitly represent all intermediate updates to the models in execution traces would deem our solver based approach completely unfeasible, in particular in presence of loops.…”
Section: Atl Languagementioning
confidence: 99%
“…Imperative Alloy (Near and Jackson 2010) is a syntactic extension to the Alloy language for specifying dynamic systems. However, neither idiom provides good support for the composition of dynamic behaviours, and, since both idioms represent ad hoc solutions, specifications written by different authors may differ sufficiently to reduce readability.…”
Section: Adding Imperative Constructs To Alloymentioning
confidence: 99%