Analysis:
 * Define Ticket Attribute instances such as:
    * Types - The nature of the ticket (for example, defect or enhancement request) 
    * Components - The project module or subsystem this ticket concerns.
    * Versions - Version of the project that this ticket pertains to.
    * Priorities - The importance of this issue, ranging from trivial to blocker.
    * Milestones - When this issue should be resolved at the latest.
    * Resolutions - Reason for why a ticket was closed. One of fixed, invalid, wontfix, duplicate, worksforme.
    * Status - What is the current status? One of new, assigned, closed, reopened.
 * Integrate the instances in Trac;

Design:

 * Types:
  * Planned_Task - this is a task from the schedule. It has four phases: Analysing, Designing, Implementing and Testing. These four are repeated three times during the project and these are: base (which represents the base version of the task), intermidiate (at this point the task should be more or less completed) and final (here all the parts of the task should be fully consistent and polished).
  * Unplanned_Task - this is a task that is not a part of the schedule so far. Things that appear throughout the project will be put here.
  * Bug - this represents an inconsistency of a task until its final version.
 * Components (These are the components of Sophie. Every conponent consists of multiple tasks and subtasks.): for details see the sophie2-wbs.py file in the repo (depends() function).
 * Priorities - The Priorities correspond to column A of resources.ods in the repo. That is:
  * blocker - 5
  * critical - 4 	 
  * major - 3 	 
  * minor - 2 	 
  * trivial - 1
 * Milestones are already defined. These include:
  * m1 - milestone 1
  * m2 - milestone 2
  * m3 - milestone 3
  * m4 - milestone 4
  * m5 - milestone 5
  * a1 - alpha 1
  * a2 - alpha 2
  * a3 - alpha 3 
  * b1 - beta 1
  * b2 - beta 2	
  * b3 - beta 3
  * rel - release
 * Resolutions
 * Status - The Status is self-defined by Trac.