##Analysis Documentation

## Headline such as "Analysis of Backup Requirements"
= Analysis of Summa Integration =
## Add detailed explanation/analysis of the task(problem)/action.

## This may include use-case diagrams etc. attached like this:
## attachment:MyUseCase.png

When addressing this task, we should consult the following TDR requirements:

 * Data must be searchable/discoverable: R71
 * Access log required: B5.2, C3.2, R36

See [[TaskC.1AnalysisDocumentDetails#Searchable]] 

See [[TaskC.1AnalysisDocumentDetails#AccessLog]] 


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

== Risks and Potential Problems ==
## Describe anything that may cause problems when solving this task.

## == Stakeholders ==
## List of links to any relevant stakeholders. That is, people who has knowledge about this task or in any other way are relevant to contact for input.

## ||<tablewidth="98%" tablestyle="text-align: left;"30% bgcolor="#cccccc" style="text-align: left;">Stakeholder ||<bgcolor="#cccccc" style="text-align: left;">Knowledge||
## ||["Link to stakeholder"] ||Usability expert. ||
## ||["Link to Bart Ender"] ||Expert on mixing margaritas ||
## ||["Link to out esteemed customer"] ||The guy with the money who actually may know what he wants. ||

## == Ressources ==
## 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]