Behavior tree: Difference between revisions

Revision as of 21:17, 4 June 2025

Revision as of 21:45, 4 June 2025

Line 10:

The extensive amount of detail involved in describing the numerous requirements for a large-scale system using natural language can lead to [[short-term memory]] overload,<ref name="dromey07EngLgeScale">Dromey, R.G. 2007. [http://www.beworld.org/BE/resource/presentation/Eng-LargeScale-Systems.pdf Principles for Engineering Large-Scale Software-Intensive Systems]</ref><ref name="raytheonSysResearch">Boston, J. 2008. [http://www.raytheon.com.au/Default.aspx?x=501 Raytheon Australia supports pioneering systems research] {{webarchive|url=https://web.archive.org/web/20090915050723/http://www.raytheon.com.au/Default.aspx?x=501|date=15 September 2009}}</ref> hindering a comprehensive understanding of the system's needs.<ref name="raytheonAustJoint" /> In the use of [[natural language]], there are often ambiguities, aliases, inconsistencies, redundancies, and incomplete information.<ref name = "dromey03K1-Dromey"/> This creates uncertainty and makes the system appear more complex.

The behavior tree representation (withattempts to eliminate uncertainty by strictly using the vocabulary of the original requirements. For large requirement sets this may require the help of the composition tree<ref name = "compositionTree">Behavior Engineering. [http://www.behaviorengineering.org/index.php?option=com_content&task=view&id=24&Itemid=34 Composition Trees] {{Webarchive|url=https://web.archive.org/web/20090302063932/http://www.behaviorengineering.org/index.php?option=com_content&task=view&id=24&Itemid=34 |date=2 March 2009 }}</ref> representation that already resolves alias and other vocabulary problems within largea setsprior ofstep. requirements)The attemptsaim to eliminate these problemsis to produce a deep, accurate, and holistic representation of system needs<ref name = "dromey07EngLgeScale"/> that can be understood by all readers (often [[Project stakeholder|stakeholders]]), because it strictly uses the vocabulary of the original requirements. Since the behavior tree notation uses [[Semantics of programming languages|formal semantics]], it can bean madeinput intofor further processing, such as making an [[executable]] for anya given exampleset of requirements.

=== Behavior tree forms ===