2.2 THE Augmented Web-Helix Process


Web Helix (WH) process uses a modified spiral approach to systems development.
Web Helix is not at all suitable for straightforward applications as it
Suffers from a lack of metrics to determine when to release or to continue to the next slice of the helix.
Depends on ROI as the only means for moving from one slice of the helix to the next.

2.2 THE Augmented Web-Helix Process


Figure 2.1: The original Web-helix process

2.2 THE Augmented Web-Helix Process


The Augmented WebHelix process (AWH) as follows:
Provided a systematic framework to qualitatively evaluate whether to release the project in the current state
and/or to continue to the next slice; this evaluation framework is called the project evaluation framework
(PEF)
The evaluation is done at the end of each phase of a slice rather than once at the end of a slice; this helps to
keep the project on track.
In order to more accurately reflect the needs of the real world, the AWH gives the following choices for the
project at the end of each slice:
Release the project and do not continue to the next slice (go the deployment and maintenance phase of
the project).
Release the project and continue to the next slice (the released portion goes into the deployment and
maintenance phase).
Do not release the project but go to the next slice to add additional features.

2.2 THE Augmented Web-Helix Process


Figure 2.2: The Augmented Web-helix process

2.2 THE Augmented Web-Helix Process


As illustrated in Figure 2.2, the process starts with the Business Analysis and Planning phases, respectively, the
PreHelix1 and PreHelix2 phases.
After the Planning phase, the project enters the first slice of the helix at the Analysis phase and then proceeds
clockwise round the slice through the Design, Coding, and Test phases.
After each phase in a slice, there is an Evaluation phase (represented by e) wherein the PEF is applied to
decide whether to proceed to the next phase in the slice or not.
During the evaluation the Test phases, the major decision of whether to release the product (Release) or to
continue to the next slice of the helix (Continue) or both is determined.
After the final slice, the post helix phases of deployment (Deploy or PostHelix1) and maintenance (Maintain or
PostHelix2) are performed.
If a Continue decision is made at the end of a slice then the project can proceed along two paths
simultaneously- one, taking it to the Analysis phase of the subsequent slice, and the other taking the project to
the deployment phase.