Commit 796a9951 authored by Markus Klinik's avatar Markus Klinik
Browse files

terminology: basic tasks

parent 1b584281
......@@ -37,9 +37,23 @@ In particular we see our work applicable in damage control situations, where wor
We do not focus on the happy flow of missions, which by design has no resource conflicts.
\paragraph{Terminology}
\subsection{Terminology}
\paragraph{Tasks}
A \textbf{basic task} is an atomic unit of work.
Atomic means that it is not useful to divide a task into subtasks that are managed by our system.
For example, repairing a machine is a basic task.
A mechanic should to be told that a machine needs repairing, and when the best time is to start.
The mechanic can then autonomously carry out the repair, even though conceptually the repair task consists of many tiny subtasks.
There would be no benefit in letting our system manage these subtasks.
The decision which tasks are basic tasks and which can be split up into subtasks must be made on a case-by-case basis, depending on whether one expects a benefit from from our system managing the subtasks.
\paragraph{Resources}
Lorem ipsum.
\begin{itemize}
\item Task
\item Resource
\item Capability
\item Capability requirement \todo{use consistently}
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment