\section{Introduction}

This section describes the project plan for the PIANOS project.

The project plan defines the timetable and the program to be developed, assesses risks, estimates the size and complexity of the program and introduces the project team and communication methods.

This document is used to manage the project. Also the customer and the project supervisor are able to track the project with this document since it is updated regularly.

\subsection{Goals}

The project's goal is to produce a program for the University of Helsinki's spatial data analysis research group. The program analyzes spatial data by using a prior distribution and a mathematical model to calculate the posterior distribution for a set of variables. Certain statistical measures are then calculated from the posterior distribution. The project must deliver by the 2nd of September 2005.

\subsection{Current systems}

The software is related to another currently in use, named Bassist: `Bassist is a tool that automates the use of hierarchical Bayesian models in complex analysis tasks. Such models offer a powerful framework for modeling statistically complex real-world phenomena.' [Bass]

Currently the research group is using BASSIST to analyze spatial problems. BASSIST wasn't designed for problems with spatial dependencies. It's modeling language lacks features which would allow efficient definition of spatial problems. The goal is to concentrate on a small portion of spatial problems which can't be solved efficiently with BASSIST.

\subsection{Version history}
\input{version}

\subsection{Overview of the project plan}

\begin{tabular}[]{ p{3.9cm} p{10cm} }
1. Introduction & Describes this document and the program being produced. \\
& \\
2. Project organization  & Describes the organization and people involved in this project. \\
& \\
3. Communication and data storage  & Describes the communication methods that the project personnel use and the data storage methods used. \\
& \\
4. Risk analysis & Describes the risks involved in the project. Each risk has a probability and impact rating. The list is updated to show current risks. \\
& \\
5. Hardware and software requirements & Describes the working environment of the program. \\
& \\
6. Project schedule & Describes the phases, milestones and timetable of the project. The chapter gives an overall description of the software engineering process. The chapter also describes function points and a size estimate of the project. \\
& \\
7. Monitoring and reporting & Describes the ways the project is being tracked and documentation. \\
& \\
8. Quality assurance & Describes the measures taken to ensure the quality of the product. \\
\end{tabular}