##Task
## If any of the below links or sections are not applicable to your page, then please comment them out rather than deleting
## as they may become relevant later on.

= G.3. Risk analysis =

## Valid states: "Not started", "In progress" and "Finished"
'''State:''' In progress

## The time used is measured in man days and does not include the time spent on any sub-tasks.
'''Time used:''' 0 md.

== Description ==

## Add a high level task (goals / sub-goals) description here, sufficiently detailed to provide a background for creation of action descriptions.
## Any available (technical) details goes into the below documentation pages.

The RiskAnalysis page must be reviewed and revised regularly, say at the beginning of each iteration, to ensure that it is up to date with all relevant risks and that the information about them is current.

Whenever a new risk is identified a new risk description page must be created, using the RiskDescriptionTemplate, and the table on the RiskAnalysis page must be updated with the risk and a link to the risk description page.

This task will be active during the whole project.

## == Sub tasks ==

##  . [:TaskX.Y.Z: Add sub task link 1 here]
##  . [:TaskX.Y.Z: Add sub task link 2 here]
##  .         ..[[BR]]
##  .         ..[[BR]]
##  .         ..
##  . [:TaskX.Y.Z: Add sub task link N here]

## == Documentation ==

## The documentation section links to the documentation relevant to this task and its sub-tasks (if any).
##
## The below links will automatically be expanded to page names like "MyTaskPageNameAnalysisDocument" in your created page.
## This should be a proper default, however, it may be changed.
 
##  * [:TaskG.3AnalysisDocument: Analysis Document]
##  * [:TaskG.3DesignDocument: Design Document]
##  * [:TaskG.3SystemMaintenanceDocument: System Set-up and Maintenance Document]

== Parent task ==
 * [[TaskG]]

== Progress history ==

<<PageDicts(Action,Iteration, Time used,Status,Notes,Tasks adressed ~= TaskG.3)>>

## Add information about about the current state of the task here. That is, information about what has been completed so far and
## what outstanding issues that are left. Example:
##
##=== 2007-09-13 ===
##Finished the design documentation. A review is needed before this task can is completed.
##
##=== 2007-08-25 ===
##Completed requirement specification. We are now ready for writing the design document.