Defining task hierarchy

Building a task hierarchy is the first step in constructing a mission.

• Every mission/procedure is defined by a number of high-level tasks.

• Each task summarizes a set of operations that are logically or temporally related.

• Each high-level task is made up of a set of low-level tasks (or subtasks) that are more specific. Usually a two level hierarchy is enough, but sometimes a deeper structure is needed.

• A good approach is to create task tree nodes that relate to atomic actions.

Code example

<task name="mission">

<task name="t1" >

<task name="t1_1">

</task>

</task>

<task name="t2">

<task name="t2_1" >

</task>

<task name="t2_2" >

<task name="t2_2_1" >

</task>

<task name="t2_2_2" >

</task>

</task>

</task>

</task>

Guidelines

• Always remember that the root task node must be called mission.

• Use a number-based naming convention for tasks.