|
|
|
@@ -34,7 +34,7 @@ These features are implemented one by one with in the rapid development cycle us |
|
|
|
This section discusses each of these three parts and how they fit in the waterfall model. |
|
|
|
|
|
|
|
\subsection{Rapid Development Cycle} |
|
|
|
The rapid development cycle consists of multiple iterations, where each iteration implements and tests one feature, that was defined during the preparation. |
|
|
|
The goal of the rapid development cycle is sequential implementation of the features in a system. |
|
|
|
Each iteration of the rapid development incorporates the following steps: |
|
|
|
\begin{enumerate} |
|
|
|
\item Create an initial design and corresponding tests for the next feature. |
|
|
|
@@ -58,7 +58,7 @@ The variable detail approach is finished when all the tests are passed and all t |
|
|
|
\subsection{Preparation} |
|
|
|
Although the \ridm does not specify the complete steps for the preparation, it does state some requirements. |
|
|
|
The rapid development cycle requires a list of features that can be implemented one by one. |
|
|
|
These features are gained by splitting the system into individual subsystems, where each subsystem can be implemented and tested individually. |
|
|
|
These features are gained by partitioning the functionality of the system, such that features can be implemented and tested individually. |
|
|
|
For each feature it is required to specify the feature requirements and the corresponding test protocol. |
|
|
|
The feature requirements are based on the system requirements and the tests are used to validate that the feature meets its requirements. |
|
|
|
About the order of implementation, the \ridm states that critical features should be implemented first, as these features have an increased chance of invalidating the complete design. |
|
|
|
|
