##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.3.2. System Maintenance 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 documentation describing how to install the DOMS and how to maintain the installed system.

The goal is to write a document that enables any DOMS team member to install a full DOMS system and enables the system maintenance people to keep it running. That is, the document must contain a thorough installation guide and describe the DOMS software components and any components that it depends on, on a system level. Thus, enabling the maintenance people to supervise the system, checking its state and take proper action if the system shows any sign on irregularities.

Documents that need to be present before this task can be considered done:
 * System maintenance documentation
 * Application maintenance documentation

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

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

== Parent task ==
 * [[TaskD.3]]

== Progress history ==

=== 2008-06-03 ===
Updated task with lists of documents, including specification of System maintenance and Application maintenance as separate entities.

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