Formalising Behaviour Trees with CSP

Abstract

Abstract. Behaviour Trees is a novel approach for requirements engineering. It advocates a graphical tree notation that is easy to use and to understand. Individual requirements are modelled as single trees which later on are integrated into a model of the system as a whole. We develop a formal semantics for a subset of Behaviour Trees using CSP. This work, on one hand, provides tool support for Behaviour Trees. On the other hand, it builds a front-end to a subset of the CSP notation and gives CSP users a new modelling strategy which is well suited to the challenges of requirements engineering.

Requirements simulation for early validation using Behavior Trees and Datalog

“…It improves the verification time by reducing the parallelism in the model. Translation of BTs into Communicating Sequential Processes (CSP) allows for automated analysis using the Failure-Divergence Refinement (FDR) model checker [42]. Automated support to perform Failure Mode and Effect Analysis FMEA is also present [30].…”

Introducing requirements traceability support in model-driven development of web applications

“…In [5], an approach based on Behaviour Trees [56] is proposed to systematically derive a software design from functional requirements. This approach proposes representing behaviour in individual functional requirements by means of behaviour trees.…”

Integrating safety and security requirements into design of an embedded system

“…These properties can then be model checked using salsmc and sal-bmc tools. A BT specification can also be translated into a CSP representation [11]. The FDR model-checker can be used to model check the CSP specification to verify the BT model.…”

“…An integrated view of the system is first generated by integrating all the individually specified requirements into a single tree, referred to as integrated behavior tree (IBT) before deriving the system design in the form design behavior tree (DBT) by systematically refining the IBT. The automated translation of a DBT into other formal specification languages like Communication Sequential Process (CSP) [11] and Symbolic Analysis Laboratory (SAL) [12] makes it possible to formally verify the critical system properties like safety and security conditions, liveness, deadlocks, etc. A componentbased architecture and component behavior may be derived from the DBT in the form component interaction network (CIN) and component behavior tree (CBT) diagrams.…”