There were many reasons that lead us to conclude that the spiral methodology would be appropriate.
First of all we recognized that there are a lot of risks involved in this project.
The team has a lot of research to do in order to learn new technologies and comprehend image splitting technology.
The spiral model is a good choice for high risk projects since the model is built to handle it better than most other methodologies.
The spiral model is also good for providing the customer with multiple iterations.
We felt that providing the sponsor with progress updates through multiple releases would not only help them see where we’re going,
but also provide direction for us. We are hoping that it allows them to provide feedback for what we’re doing and
we can adjust our development efforts accordingly. The spiral model also contains four main phases in each iteration
that include determining objectives, identifying and resolving risks, development and test, and planning for the next iteration.
We plan to start our first iteration by putting all of the requirements together and determining the risks involved in the project.
Once we have accomplished this, we will then put together some prototypes using storyboards to give the sponsor an idea
of what we’re visioning.
The spiral methodology will also ensure that documents are up to date and detailed.
We will have our requirements document, our system architecture, our interface specifications, software test plan,
well commented source code, a component detailed design document, and our risk analysis document.
We will try and utilize some tools to help us automatically generate some of these documents,
but for the most part we will need to create and maintain most of the projects’ artifacts.