Autonomy and mission behaviour
Define what the aircraft does on its own, and prove it before it flies.
Autonomy and mission behaviour
Autonomous behaviour is often buried in code and mission files that only their author understands. What the aircraft will do at a lost link, a low battery or a rejected waypoint is discovered in the air rather than agreed on the ground.
Mission behaviour is a state machine with edge cases, and the dangerous ones are exactly the states that are hard to reach in a real flight test. You cannot fly every combination, so most of them are never checked.
Waypoint makes autonomy and mission behaviour explicit, reviewable artefacts, and hands them to Crosswind so the edge cases are exercised in simulation. What the aircraft will do is decided and tested on the ground, then flown with the same definition.
Waypoint's behaviour runs against the airframe definition in Crosswind and commands through Sortie, so the autonomy tested is the autonomy that flies.
Tell us what you are flying and where the programme is losing time. We will tell you honestly which of these helps and which does not.