Revision as of 02:44, 23 May 2025 edit Jiffles1 (talk \| contribs) Extended confirmed users, Rollbackers 13,808 edits m Reverted edits by ScottTheWoz69 (talk): nonconstructive edits (HG) (3.4.12) Tags: Huggle Rollback ← Previous edit		Revision as of 13:29, 24 May 2025 edit undo Zayar8825 (talk \| contribs) 19 edits m "Improved grammar and readability: clarified phrasing, replaced passive construction with active voice, and split the sentence for better flow and comprehension. Tags: Visual edit Newcomer task Newcomer task: copyedit Next edit →
Line 76: === Requirements integration === Once the set of requirements is formalized as individual requirement behavior trees, two joint properties of systems and requirements need to be exploited in order to proceed with composing the integrated behavior tree: * In general, a fragment of behavior ~~expressed~~described by a requirement always has an associated ~~with it a~~ precondition ~~which~~that ~~needs to~~must be satisfied before the behavior can ~~take~~occur. ~~place (this~~This precondition may or may not be ~~expressed~~explicitly stated in the requirement). * If the requirement is really part of the system, then some other requirement in the set must establish the precondition needed in (1).

Behavior tree: Difference between revisions