== Analysis ==
 * You must create general standards of the results.
 * Describe:
  * what are the kinds of results(diagrams, how-to, documentation...)
  * that the results of the tasks must have visible results
  * that, which is common with the platform standards and which is not included in the subtasks of this task
  * where and how to keep the proceed task phases
== Design ==
 * Task results can be:
  * a specification (produced in the analysis phase of each task)
  * a development document (produced in the design phase). Can also be the final result of a task.
  * a diagram (usually as a part of a specification or development document)
  * a how-to (usually as a part of a development document)
  * source code (produced in the implement phase of most tasks).
  * a review (done after each phase). This decides whether the task can proceed to the next phase.
  * '''There is no task without a visible result''' 
 * Each revision of every task should have its page in Sophie 2 wiki. It should have different parts for the task's phases. These parts can contain either text and images or links(or embedded pages).
  * You can use Templates/TaskPageTemplate as a template for task pages.
  * source code is kept in the Sophie 2 repository.
  * specification may be part of the System Requirements Specification(SRS). If this is the case it should be in the SRS tree of the wiki.
  * some special tasks may have their result stored in separate wiki pages. This task is an example.