98 | | |
99 | | There are four general types of dependencies for tasks: |
100 | | |
101 | | 1. Task B may have to ''start after'' task A. That is, B can't begin until A is done, perhaps because it uses a product of task A as a raw material. |
102 | | 1. Task A may be ''composed of'' tasks B, C, and D. That is, tasks B, C, and D are subtasks of task A. |
103 | | 1. Task A may have to ''start with'' task B (but they may end independently). For example, auditing someone's work may start when their work starts but may involve analysis and reporting after that work is done. |
104 | | 1. Task A may have to ''end with'' task B (though they may start independently). |
105 | | |
106 | | Each of these relationships has an inverse relationship in the other task. |
107 | | |
108 | | 1. If B ''starts after'' A, then A ''ends before'' B. |
109 | | 1. If A is ''composed of'' B, C, and D, then B, C, and D are ''part of'' A. |
110 | | 1. If A ''starts with'' B, then B also ''starts with'' A. |
111 | | 1. If A ''ends with'' B, then B also ''ends with'' A. |
112 | | |
113 | | While generally useful, the ''starts with'' and ''ends with'' dependencies are somewhat more esoteric than the others and implementation may be deferred. |
| 98 | While useful, the FF and SF dependencies are somewhat more esoteric than the others and implementation may be deferred. |