A cycle is a logical flaw in a chain of dependencies. For example, a task cannot start after one task ends and ends after that same task begins, this set of dependencies creates a cycle that is not solvable. When you create a dependency, ForeSource checks to see if that dependency creates a cycle. If so, you must adjust one of the dependencies in the chain to resolve the cycle.
ForeSource allows you to break a task down into smaller tasks. These sub-tasks then become child tasks of the original task, which is now the parent task. Child tasks all support the completion of the parent task, and are all subject to the same constraints of the parent task. The parent task duration will expand or contract to reflex the earliest start date and latest end date of its children.
ForeSource provides flexibility in the types of dependencies that can be created between tasks. ForeSource supports Start to End, Start to Start, End to Start, and End to End dependencies between tasks as well as Start to Date and End to Date. Additionally, dependencies can be qualified with “At Least”, “Exactly”, or “At Most” to ensure tasks are moved only when necessary. More information about creating smart dependencies can be found under the Insights section of our website.
Do you have a question you would like to see answered that is not here? Simply fill out the form.