##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.

= D.4. Create Overall System Documentation =

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

## 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.

Write high level documentation describing how the DOMS system works. The goal of the documentation is to illustrate the high-level architecture and give non-technical people an overview over the capabilities of the DOMS system as well as an overview over the TDR requirements which are supported and which are not. That is, the documentation is supposed to be more like a "product specification" rather than a developers or end user documentation.

== Sub tasks ==
 . [[TaskD.4.1|D.4.1 Write White Paper]]
 . [[TaskD.4.2|D.4.2 Document TDR requirements]]
 . [[TaskD.4.3|D.4.3 Document Data Model Language]]

== 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.

 * [[TaskD.4AnalysisDocument|Analysis Document]]
 * [[TaskD.4DesignDocument|Design Document]]
 * [[TaskD.4SystemMaintenanceDocument|System Set-up and Maintenance Document]]

== Parent task ==
 * [[TaskD]]

== Progress history ==

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

## 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.



=== 2008-06-03 ===
Updated subtasks with lists of documents. Added task for Data Model Documentation

=== 2007-10-05 ===
Created this task from TDR requirements. See subtasks for details.