Analysis: 

 * Verify the existing dependencies in work breakdown structure document(make automatic script to check if the revisions are correct in the related tasks).[[BR]]
 * Add more dependencies for base tasks.[[BR]]
 * Check manually if the created schedule is possible(this can be done by the generated exports or task juggler calendars).[[BR]]

Design:
 * Dependencies are stored in resources ODS in a column called depends.
 * It is not necessary to explicitly say that A depends on C when A depends on B and B depends on C.
 * In most of the cases every subtask of a task depends on ....COMMONS subtask of the same task.
 * Task may depend on task with subtasks or only on a set of subtasks of a task.
 * Since all Tasks have unique names, the name of a task is enough to determine the dependencies.