##Analysis Documentation

## Headline such as "Analysis of Backup Requirements"

= Analysis of System Maintenance Documentation =

## Add detailed explanation/analysis of the task.

## This may include use-case diagrams etc. attached like this:
## Link to original: [http://merkur/svn/doms/trunk/MODULE/docs/MyUseCase.dia]
## png on the wiki page: [http://merkur/svn/doms/trunk/MODULE/docs/MyUseCase.png]

== Prerequisites and Assumptions ==

## Describe any prerequisites and assumptions that are important for this analysis, e.g.:
## What can we rely on?
## Which assumptions must hold in order to solve the problem described in this document?

The estimation of this task is based on these notes, which also should be taken into consideration when implementing the task:

'''BAM:'''   både til drift og os selv

'''TE:'''    Install, deploy, systems, detaljer, også til os selv

'''TSH:'''   Quick Rescue Guide. Detalj oversigt over alle hjul og trisser som udgør systemet.

'''MKE:'''   Extensive step-by-step for maint. AU components. Developer oriented.

'''KFC:'''   Detaljeret deploy-dokumentation, system-dokumentation, "quick-help"


## Risks and Stakeholders are of course important to the analysis, but we have dedicated pages for these, and they should only be included here if this task poses additional risks or new problems...

##== Resources ==

## List links to documents, wiki pages etc. that are relevant to this analysis.
## * [:LinkToMyRessource:Use case diagram xx]
## * [:LinkToMyVersionControlledDocument:Link to document on user studies e.g. stored in SVN]