Commit b7f940af authored by Markus Klinik's avatar Markus Klinik
Browse files

wording

parent 988759e2
......@@ -45,7 +45,7 @@ A \emph{basic task} is an atomic unit of work.
Atomic means that it is not useful to divide a task into subtasks.
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.
A mechanic only needs 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 it consists of many tiny subtasks.
There would be no benefit in letting our system manage these subtasks.
......@@ -78,5 +78,5 @@ Resources have one or more capabilities, and tasks have one or more \emph{capabi
In the scheduling literature capabilities are often called \emph{skills}.
We chose not to use this word, because it suggests that resources can only be people.
We want to emphasize that resources can be anything from machines to people to tools, so we chose the more general term capabilities.
We want to emphasize that resources can be anything from machines to people to tools, so we chose a more general term.
\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