The process used will be modeled after the Spiral process definition.  The Spiral has been described as more of a process generator than a process itself, but there are a few key ideas.  First, the process is risk-based.  Each cycle begins with identifying risks, and the rest of the cycle is concerned with resolving those risks.  Second, there are no discrete phases in which a particular artifact is begun and completed.  A portion of every artifact in the project is completed in every cycle, and the focus shifts to and from particular tasks depending on which cycle it is.  For example, a greater amount of time is spent on requirements during early cycles.  The process does a good job of allowing team members to work on tasks concurrently.

The goal of the process is to be useful, clear, and repeatable.  If the process is too heavy to be followed correctly, it is not useful.  It should be documented clearly to be repeated by the development team and others in future projects.  A plan will be integrated into the process to ensure the timeliness of deliverables.