VisB: A Lightweight Tool to Visualize Formal Models with SVG Graphics

Werth, Michelle; Leuschel, Michaël

doi:10.1007/978-3-030-48077-6_21

Cited by 19 publications

(2 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This process may be improved by further integrating the formal modelling by automating systematic aspects of the modelling and generating interactive visualisations to enable broader stakeholder engagement with the models produced. In particular, we aim to create interactive visualisations of our Event-B models using BMotionWeb, an extension of ProB for rapid creation of formal prototypes [LL16], or its successor VisB [WL20]. Further extensions of this work would be to utilise alternative means of capturing requirements and specifying behaviour that aids communication amongst all stakeholders while embedding Event-B modelling within a Behaviour-Driven Development, including Linear Temporal Logic (LTL) [HSTW16], and the iUML-B diagrammatic front-end for Event-B [SHD + 18].…”

Section: Discussion and Future Workmentioning

confidence: 99%

Legislation-driven development of a Gift Aid system using Event-B

et al. 2020

View full text Add to dashboard Cite

This work presents our approach to formally model the Swiftaid system design, a digital platform that enables donors to automatically add Gift Aid to donations made via card payments. Following principles of Behaviour-Driven Development, we use Gherkin to capture requirements specified in legislation, specifically the UK Charity (Gift Aid Declarations) Regulations 2016. The Gherkin scenarios provide a basis for subsequent formal modelling and analysis using Event-B, Rodin and ProB. Interactive model simulations assist communication between domain experts, software architects and other stakeholders during requirements capture and system design, enabling the emergent system behaviour to be validated. Our approach was employed within the development of the real Swiftaid product, launched by Streeva in February 2019. Our analysis helped conclude that there was not a strong enough business case for one of the features, which was shown to provide nominal user convenience at the expense of increased complexity. This work provides a case study in allying formal and agile software development to enable rapid development of robust software.

show abstract

Section: Discussion and Future Workmentioning

confidence: 99%

Legislation-driven development of a Gift Aid system using Event-B

et al. 2020

View full text Add to dashboard Cite

show abstract

“…A heavy disadvantage however is the complex technology stack: BMotion-Web builds upon ProB Java API and uses Groovy, SVG, JavaScript and HTML5, where each component of the stack may go wrong, rendering development very cumbersome. Thus, a more simple successor was developed called VisB [92]. It also builds upon ProB Java API, but is easier to use and maintain.…”

Section: Visualisationmentioning

confidence: 99%

Integrating formal specifications into applications: the ProB Java API

Körner

Bendisposto

Dunkelau

et al. 2020

Form Methods Syst Des

Self Cite

View full text Add to dashboard Cite

The common formal methods workflow consists of formalising a model followed by applying model checking and proof techniques. Once an appropriate level of certainty is reached, code generators are used in order to gain executable code. In this paper, we propose a different approach: instead of generating code from formal models, it is also possible to embed a model checker or animator into applications in order to use the formal models themselves at runtime. We present a Java API to the ProB animator and model checker. We describe several case studies that use this API as enabling technology to interact with a formal specification at runtime.

show abstract