Utilizing Event-B for domain engineering: a critical analysis

Mashkoor, Atif; Jacquot, Jean‐Pierre

doi:10.1007/s00766-011-0120-5

Cited by 21 publications

(5 citation statements)

References 31 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The introduction order of the features in M2 up to M5 was arbitrary. This is related to the problem of expressing topological orders in the strict Event-B refinement hierarchy even tho there are attempts, such as by Mashkoor et al [24]. We provide an overview of the exact metrics of all refinement steps in table 1.…”

Section: Automotive Adaptive Exterior Light Systemmentioning

confidence: 99%

Trace Refinement in B and Event-B

Stock¹,

Mashkoor²,

Leuschel³

et al. 2022

Preprint

Self Cite

View full text Add to dashboard Cite

Traces are used to show whether a model complies with the intended behavior. A modeler can use trace checking to ensure the preservation of the model behavior during the refinement process. In this paper, we present a trace refinement technique and tool called BERT that allows designers to ensure the behavioral integrity of high-level traces at the concrete level. The proposed technique is evaluated within the context of the B and Event-B methods on industrial-strength case studies from the automotive domain.

show abstract

Section: Automotive Adaptive Exterior Light Systemmentioning

confidence: 99%

Trace Refinement in B and Event-B

Stock¹,

Mashkoor²,

Leuschel³

et al. 2022

Preprint

Self Cite

View full text Add to dashboard Cite

show abstract

“…• adding new events; this amounts to decompose an abstract "large" event into several concrete "smaller" events. This is called a change in observation level in [21].…”

Section: Refinementmentioning

confidence: 99%

Rigorous Modeling and Analysis of Interoperable Medical Devices

Mashkoor

Sametinger

2016

Modeling and Simulation in Medicine Symposium (MSM 2016)

View full text Add to dashboard Cite

Medical Devices (MDs) are by definition safety-critical and increasingly also become security-critical when interoperating, i.e., when communicating in some form. Finding errors, inconsistencies, or vulnerabilities in MDs before deployment can significantly decrease costs, and increase quality and reliability. In this paper, we present a rigorous "correct-byconstruction" approach for modeling and analyzing interoperating MDs by considering various abstraction levels, i.e., the functional, the safety, and the security level. The approach is illustrated using sample requirements of a hemodialysis device.

show abstract

“…The choice of formal method can be another difference. A brief comparison of both languages, Event-B and RAISE [18], is available in [19].…”

Section: A Domain Modeling In Raisementioning

confidence: 99%

Guidelines for Formal Domain Modeling in Event-B

Mashkoor

Jacquot

2011

2011 IEEE 13th International Symposium on High-Assurance Systems Engineering

Self Cite

View full text Add to dashboard Cite

Abstract-In this paper, we explore the possibility to use Event-B as a formal domain modeling tool. We identify the areas where domain modelers can struggle and present some guidelines to avoid these pitfalls. We mainly address three questions about domain modeling: what to specify, how to refine, and how to verify. We discuss the strategy to express domain assumptions, protocols, time, and temporal properties. We also analyze the refinement and proof system of Event-B in this realm. We advocate small incremental steps and alternative refinement mechanisms, such as "observation levels." We find animation a very helpful activity to complement the verification process.

show abstract

Utilizing Event-B for domain engineering: a critical analysis

Cited by 21 publications

References 31 publications

Trace Refinement in B and Event-B

Trace Refinement in B and Event-B

Rigorous Modeling and Analysis of Interoperable Medical Devices

Guidelines for Formal Domain Modeling in Event-B

Contact Info

Product

Resources

About