Behavior tree: Difference between revisions

Revision as of 04:43, 30 May 2025

Revision as of 14:35, 31 May 2025

Line 17:

Both single and integrated (composite) behavior tree forms are important in applying behavior trees in [[systems engineering|systems]] and [[software engineering]].

* '''Requirement behavior trees (RBT):''' Initially, individual requirement behavior trees are usedconstructed to capture all thebehavioral fragments of behavior infrom each natural language requirement bythrough a rigorous translation process ofthat rigorous,preserves both intent-preserving and vocabulary-preserving translation. The translation process can uncover a range of defects in original [[natural language]] requirements.

* '''Integrated behavior trees (IBT):''' Because a set of requirements imply the integrated behavior of a system, all the individual requirement behavior trees can be composed to construct an integrated behavior tree that provides a single holistic view of the emergent integrated behavior of the system. This enables the construction of the system's integrated behavior from its requirements.<ref name = "winters">Winter, K. 2007. [http://espace.library.uq.edu.au/eserv/UQ:100586/Formalising_behaviour_trees_with_csp.pdf Formalising Behaviour Trees with CSP]</ref> An analogy to help describe this process is the transition from a randomly arranged set of [[jigsaw puzzle]] pieces to putting each of the pieces in its appropriate place. When this happens, each piece of information is placed in its intended context and their collective emergent properties become clear.