##Risk Description

= Risk Description =

## Detailed description of this risk and its possible implications.
## E.g. If one of the car's tires suffers a puncture, we may run off the road.

At the moment we are confident that we can handle the integration with Summa and carry out the task within a reasonable time frame. However, this integration is crucial for the success of the DOMS project and therefore we must monitor this risk regularly.

The reason why we are confident and currently do not see this risk as a major risk is due to these facts:

 * We have Summa developers in the project group.
 * The pre-analysis project not only demonstrated that integration with Summa was feasible but also rather easy.
 * It is possible for us to influence the Summa development and request features due to our strong relations with the Summa team.
 * Summa is very flexible in the range of data it accepts for indexing as well as presentation. Any XML document is accepted, and XSLTs provide control over indexing mechanism as well as presentation.

The reason why we think that this risk must be regularly monitored is due to these uncertainties:

 * It may not be a trivial task to represent our data in a suitable way to allow Summa to index and search through it.
 * Future material to be stored in the DOMS may apply datamodels that are unexpectedly difficult present through Summa or maybe even difficult to index and search through.

== When to react? ==

## When must we respond to the risk? E.g. When the event occurs or already when we see the warning signs?
## E.g. We must react if we hear a hissing sound.

We must analyse the situation if the tasks related to the Summa integration tends to take more time to implement than originally estimated or if there are any changes in the requirements regarding the material to be stored in the DOMS.

== Reaction ==

## Detailed description of how to react on the risk and which actions to take, if it is imminent.

## There exists 4 basic reactions:
## 1: Accept the risk.
## 2: Eliminate the cause to the risk.
## 3: Mitigate the probability or the consequence of the risk.
## 4: Delegate the risk to another party, e.g. by outsourcing it or take out insurance for it.

## E.g. We accept the risk and change the tire if we suffer a puncture.

We will have to accept this risk, however, we have good chances to handle any problems gracefully as we are confident that we will be able put anything into the DOMS and due to the fact that we can rely on the Summa team to fix any shortcomings in Summa.


== Responsible Persons ==

The below persons are responsible for continuously monitoring and acting on this risk:

## Add a bullet list with links to the wiki pages of the responsible persons here:
## E.g.
## * [:JohnDoe: John Doe]