% author: Eemil Lagerspetz

\section{Risk analysis}

This section deals with the risks involved in the project.
Each risk is described and given probability- and seriousness ratings.
Steps to counteract a risk are described after it.  
This list of risks will update as the project progresses and risks are dealt with.
Newly found risks will be added to reflect the state of the project.

Each risk has a \textit{name}, \textit{status}, a longer \textit{description}, \textit{probability} and \textit{seriousness} and some measures to prevent it and/or to minimize its effects if it comes true.

The \textit{name} is a very short description of the risk. It should not be longer than a few words. 
Longer descriptions are placed in the risk's \textit{description}-section.
a risk's \textit{Status} indicates how the preventive measures have been taken into effect.
The status is one of:  \textit{Active} (The risk is waiting to happen),  \textit{Prevented} (The risk has been negated and cannot come true), \textit{Mitigated} (Measures have been taken to reduce the probability of the risk), or \textit{Realized} (The risk has come true)

The \textit{Probability} of a risk can be \textit{Low}, \textit{Moderate} or \textit{High}, where \textit{Low} could be something like 0\% to 10\%, \textit{Moderate} from 10\% to 40\% and \textit{High} from 40\% up.
These are guidelines, of course the `true probability' of a risk cannot be known.

A risk's \textit{Seriousness} has similar values with the \textit{Probability}. Here \textit{Low} indicates that the risk, if it comes true, would mean a minor setback, say 1-2 days of more work. \textit{Moderate} could be 2-4 days of extra trouble and \textit{High} might mean even a week's additional work.
Every risk includes preventive measures to take against it and a plan to minimize its effect if it comes true. Either of these may not be appropriate for all the risks; if so, the reason is indicated in its respective section. These are not comprehensive measures; more extensive prevention is advised. These are simple guidelines for actions to take.
\newline

\subsection{Risk ratings}

Overview of the rating system used:

\begin{tabular}[]{| l | p{10cm} |}
\hline
Risk name &  This is a very short description of the risk. \\
\hline
Status & This is the risk's status ---  one of `Active', `Mitigated', `Prevented' or `Realized'\\
\hline
Risk description & A longer description, maybe including
an example case in a few words. \\
\hline
Probability & The likelihood of the risk coming true,
on a scale of `Low, Moderate, High'. \\
\hline
Seriousness & An estimate of impact on the project,
`High' being the most serious, `Moderate' and `Low' the other choices. \\
\hline
Possible prevention & Actions to take to reduce the likelihood of the risk
or negate it altogether. \\
\hline
Minimizing the impact & Considerations as to how to proceed if indeed
the risk comes true.\\
\hline
\end{tabular}
\vspace{1cm}

\subsection{List of risks}

\subsubsection{Personnel related}

\begin{tabular}[]{| l | p{10cm} |}
\hline
Risk name & Temporary loss of work force \\
\hline
Status & Realized \\
\hline
Risk description & Someone can't take part in the project work for a short period of time. (For example someone gets ill.) \\
\hline
Probability & High \\
\hline
Seriousness & Low \\
\hline
Possible prevention & Schedule the work evenly for the work period. Minimizing stress. \\
\hline
Minimizing the impact & Keep the missing person up-to-date via e-mail or other communication
methods. Delegate the missing person's duties among other workers. \\
\hline
\end{tabular}
\vspace{1cm}



\begin{tabular}[]{|l | p{10cm} |}
\hline
Risk name & Permanent loss of work force \\
\hline
Status & Realized \\
\hline
Risk description &  Someone must quit the project. (For example someone gets seriously ill.) \\
\hline
Probability &  Low \\
\hline
Seriousness &  High \\
\hline
Possible prevention & 
Document source code so that everyone else can understand how it works. 
Keep people informed on progress done with sufficient communication.\\
\hline
Minimizing the impact & Reconsider the limits of the project. Possibly drop some of the 
lower priority requirements. \\
\hline
\end{tabular}
\vspace{1cm}



\subsubsection{Data issues}

\begin{tabular}[]{|l | p{10cm} |}
\hline
Risk name & CS network failure \\
\hline
Status & Realized \\
\hline
Risk description & The CVS or the Helsinki University servers are down, 
causing some data to be unreachable or inability to communicate. \\
\hline
Probability &  Moderate \\
\hline
Seriousness &  Moderate \\
\hline
Possible prevention & This is a project-independent matter. \\
\hline
Minimizing the impact & Everyone's CVS snapshots can be combined and a new repository can be
easily built. In case of email failure, IRC can be used instead.\\
\hline
\end{tabular}
\vspace{1cm}

\begin{tabular}[]{|l | p{10cm} |}
\hline
Risk name & Loss of project data \\
\hline
Status & Prevented \\
\hline
Risk description &  Some of the group's files are lost. (For example because of a computer virus or physical damage).\\
\hline
Probability &  Moderate \\
\hline
Seriousness &  Moderate \\
\hline
Possible prevention & Use virtual workspaces and version control systems so that copies of the files will be available and backed up at a safe location. Effectively negates the risk. \\
Minimizing the impact & No reasonable means to minimize\\
\hline
\end{tabular}
\vspace{1cm}


\subsubsection{Planning risks}

\begin{tabular}[]{|l | p{10cm} |}
\hline
Risk name & Delay \\
\hline
Status & Mitigated \\
\hline
Risk description &  A part of the project is delayed. \\
\hline
Probability &  Moderate \\
\hline
Seriousness &  High \\
\hline
Possible prevention & Control the working hours of everyone. 
Plan the schedule with extra space for adjustment. 
Schedule enough time for every part of the project. \\
\hline
Minimizing the impact & Adjust the timetable. Re-evaluate the project limits.
Work some more, if reasonable. \\
\hline
\end{tabular}
\vspace{1cm}


\begin{tabular}[]{|l | p{10cm} |}
\hline
Risk name & Schedule pressure \\
\hline
Status & Active \\
\hline
Risk description & Time grows short, the schedule presses on. The project
quality decreases. \\
\hline
Probability &  Moderate \\
\hline
Seriousness &  Moderate \\
\hline
Possible prevention & Plan the schedule with extra space for adjustment.
Prioritize requirements so that at least the essential ones will be implementable
in the given time frame. \\
\hline
Minimizing the impact & Re-evaluate the project limits, drop some of 
the lower priority requirements, if necessary. \\
\hline
\end{tabular}
\vspace{1cm}


\begin{tabular}[]{|l | p{10cm} |}
\hline
Risk name & Evolution of requirements \\
\hline
Status & Active \\
\hline
Risk description & Requirements change extensively on-the-fly,
altering plans and implementation. \\
\hline
Probability &  Low \\
\hline
Seriousness &  High \\
\hline
Possible prevention & Gather an exhaustive list of requirements for the
requirements specification document, then freeze the essential requirements, planning
for and implementing the requirements specified therein. \\
\hline
Minimizing the impact & Implement essential requirements,
 don't accept new essential requirements. \\
\hline
\end{tabular}
\vspace{1cm}

\begin{tabular}[]{|l | p{10cm} |}
\hline
Risk name & Over-planning\\
\hline
Status & Active \\
\hline
Risk description & Extensive planning results in problems when it is
discovered in the implementation phase that the plans must be altered
to produce a functioning software.\\
\hline
Probability & Moderate \\
\hline
Seriousness & Moderate \\
\hline
Possible prevention & Don't get alienated from the implementation altogether;
try planning solutions in practice sufficiently. \\
\hline
Minimizing the impact & Rationalize the plan, 
re-planning the parts in conflict with reality. \\
\hline
\end{tabular}
\vspace{1cm}


\begin{tabular}[]{|l | p{10cm} |}
\hline
Risk name & Over-prototyping \\
\hline
Status & Active \\
\hline
Risk description & Testing everything in practice results in haphazard
implementation and too little planning. \\
\hline
Probability & Moderate \\
\hline
Seriousness & Moderate \\
\hline
Possible prevention & Do enough planning to balance the prototyping. \\
\hline
Minimizing the impact & Concentrate on design for a while. \\
\hline
\end{tabular}
\vspace{1cm}

\begin{tabular}[]{|l | p{10cm} |}
\hline
Risk name & Harder than expected \\
\hline
Status & Active \\
\hline
Risk description & A component is found to be harder to
implement than expected. \\
\hline
Probability &  Moderate \\
\hline
Seriousness &  Moderate \\
\hline
Possible prevention & Prototype parts of the components to get a picture of
their required internal complexity. Implement all the crucial data structures and
algorithms in groups of people (opposed to people working alone). \\
\hline
Minimizing the impact & Implement the parts as described above. \\
\hline
\end{tabular}
\vspace{1cm}

\begin{tabular}[]{|l | p{10cm} |}
\hline
Risk name & The problem is more extensive than expected \\
\hline
Status & Active \\
\hline
Risk description &  The software is discovered to be too extensive
to implement in the given time frame. \\
\hline
Probability &  Moderate \\
\hline
Seriousness &  High \\
\hline
Possible prevention & Analyze the problem thoroughly in the analysis phase. \\
\hline
Minimizing the impact & Implement only essential requirements,
reducing the work to be done. \\
\hline
\end{tabular}
\vspace{1cm}

\begin{tabular}[]{|l | p{10cm} |}
\hline
Risk name & Incompatibility \\
\hline
Status & Active \\
\hline
Risk description &  Some parts of the software don't work with the other parts like they should. \\
\hline
Probability &  Moderate \\
\hline
Seriousness &  High \\
\hline
Possible prevention & Document component interfaces in a specific manner so that there is no chance of misunderstanding. Communicate with other group members so that everyone knows how the parts should fit together. \\
\hline
Minimizing the impact & Reimplement the parts by everyone's combined efforts.\\
\hline
\end{tabular}
\vspace{1cm}

\subsubsection{Technical risks}

\begin{tabular}[]{|l | p{10cm} |}
\hline
Risk name & Fortran issues \\
\hline
Status & Active \\
\hline
Risk description &  Problems with the Fortran compiler or the Fortran language. \\
\hline
Probability &  Moderate \\
\hline
Seriousness &  High \\
\hline
Possible prevention & Try other Fortran compilers in addition to the
GNU Fortran compiler. Have project members study
enough Fortran to understand how the language works. \\
\hline
Minimizing the impact & Change the Fortran compiler used.
Try different structures in the language. \\
\hline
\end{tabular}
\vspace{1cm}

\begin{tabular}[]{|l | p{10cm} |}
\hline
Risk name & Mis-implementation \\
\hline
Status & Active \\
\hline
Risk description & It is discovered that the product being built does not
conform to the customer's idea of the software. \\
\hline
Probability & Moderate \\
\hline
Seriousness & Moderate \\
\hline
Possible prevention & Verification and Validation. \\
\hline
Minimizing the impact & Contact the customer and negotiate on further
development. \\
\hline
\end{tabular}
\vspace{1cm}

\begin{tabular}[]{|l | p{10cm} |}
\hline
Risk name &  Wrong approach \\
\hline
Status & Active \\
\hline
Risk description & A problem in the technical level is being solved in the
wrong manner. (For example: too inefficiently) \\
\hline
Probability & Moderate \\
\hline
Seriousness & High \\
\hline
Possible prevention & Implement all the crucial data structures and
algorithms in groups of people (opposed to people working alone) \\
\hline
Minimizing the impact & Find the correct solution and reimplement the part. \\
\hline
\end{tabular}
\vspace{1cm}

\begin{tabular}[]{|l | p{10cm} |}
\hline
Risk name & Lack of technical specification \\
\hline
Status & Active \\
\hline
Risk description & Critical concepts of the implementation
have been left ambiguously defined.\\
\hline
Probability & Moderate \\
\hline
Seriousness & Moderate \\
\hline
Possible prevention & Use explicit definitions, avoid ambiguous words.\\
\hline
Minimizing the impact & Define the concept later on in specific terms,
integrate the use of the concept to match the definition. \\
\hline
\end{tabular}
\vspace{1cm}



%\begin{tabular}[]{|l | p{10cm} |}
%\hline
%Status & Active \\
%\hline
%Risk description & \\
%\hline
%Probability & \\
%\hline
%Seriousness & \\
%\hline
%Possible prevention & \\
%\hline
%Minimizing the impact & \\
%\hline
%\end{tabular}
%\vspace{1cm}
