Domain Engineering with Event-B: Some Lessons We Learned

Mashkoor, Atif; Jacquot, Jean‐Pierre

doi:10.1109/re.2010.37

Cited by 8 publications

(6 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This is consistent with our findings on using Event-B for the modeling of transportation domain [15]. On the very positive side: we could model a reasonably complex algorithm and prove its correctness.…”

Section: Discussionsupporting

confidence: 91%

Scaling Up with Event-B: A Case Study

Yang

Jacquot

2011

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract. Ability to scale up from toy examples to real life problems is a crucial issue for formal methods. Formalizing a algorithm used in vehicle automation (platooning control) in a certification perspective, we had the opportunity to study the scaling up when going from a (toy) model in 1D to a (more realistic) model in 2D. The formalism, Event-B, belongs to the family of mathematical state based methods. Increase was quantitative: 3 times more events and 4 times more proofs; and qualitative: trigonometric functions and integrals are used. Edition and verification of the specification scale up well. The crucial part of the work was the adaptation of the mathematical and physical model through standard heuristics. The validation of temporal properties and behaviors do not scale up so well. Analysis of the difficulties suggests improvements in both tool support and formalism.

show abstract

Section: Discussionsupporting

confidence: 91%

Scaling Up with Event-B: A Case Study

Yang

Jacquot

2011

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

show abstract

“…The first case study is about a land transport domain model [32], [33]. The second case study is about the landing system of an aircraft [34].…”

Section: Proofmentioning

confidence: 99%

Validation of formal specifications through transformation and animation

Mashkoor¹,

Jacquot²

2016

Requirements Eng

Self Cite

View full text Add to dashboard Cite

A significant impediment to the uptake of formal refinement-based methods among practitioners is the challenge of validating that the formal specifications of these methods capture the desired intents. Animation of specifications is widely recognized as an effective way of addressing such validation. However, animation tools are unable to directly execute (and thus animate) the typical uses of several of the specification constructs often found in ideal formal specifications. To address this problem we have developed transformation heuristics that, starting with an ideal formal specification, guide its conversion into an animatable form. We show several of these heuristics, and address the need to prove that the application of these transformations preserves the relevant behavior of the original specification. Portions of several case studies illustrate this approach

show abstract

“…One is the specification of the domain of transportation [13], [14]. It consists of nine refinements.…”

Section: A Cases Studiesmentioning

confidence: 99%

Stepwise Validation of Formal Specifications

Mashkoor

Jacquot

2011

2011 18th Asia-Pacific Software Engineering Conference

Self Cite

View full text Add to dashboard Cite

Abstract-This paper explores the possibility to incorporate validation in the stepwise development process of formal specifications. Formal methods based on refinement break the intractable proof of the correctness of implementation into a sequence of many smaller proofs. Likewise, the validation of the specification could be broken into smaller steps associated to refinements with the technique of animation. Animating an abstract specification often requires to alter it in ways that proof obligations cannot be discharged anymore. So, we have developed a process and a set of transformation rules whose application produces an animatable specification which may be non-provable, but which is assured to have the same behavior. Guaranteeing behavioral preservation requires us to define an ad-hoc relationship between specifications based on a kind of trace semantics. 10 rules have been identified and proven to preserve behavior. Observations on the use of the technique on two case-studies are presented.

show abstract

Domain Engineering with Event-B: Some Lessons We Learned

Cited by 8 publications

References 21 publications

Scaling Up with Event-B: A Case Study

Scaling Up with Event-B: A Case Study

Validation of formal specifications through transformation and animation

Stepwise Validation of Formal Specifications

Contact Info

Product

Resources

About