Analysis:

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

Design:

• Dependencies are stored in resources ODS in a column called depends.
• "Depends" means that a task cannot be completed prior the task it depends on!!!
• 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.
• After dependencies are put in the ODS document, all the document should be exported in the WBS document and task juggler calendars should be generated to check the consistency of the dependencies.

Implemeting:

• Filling the table called resources.ors - depends column.
• Extracting the dependencies in the sophie2-wbs.py file (function depends()).

Testing:

• After we struggled with the Python Syntax, Milo decided to help and the result was the checkOrder() function.
• checkOrder() function checks whether dependencies are correctly added. Result:
  • No dependencies for R0 of tasks.
  • About 90 dependencies from R0 on.
  • Dependencies between non bottom level tasks also exist (not counted).