Information Technology Reference
In-Depth Information
cant advantages over previously described models.
The emphasis on risk analysis provides a major improvement and makes it an ideal
model for large, mission-critical projects (Munassar and Govardhan
2010
). On the
downside, it is not very ef
The spiral model has signi
cient in smaller projects; the risk assessment process can
increase the expenses of the system to a degree where even making the system,
regardless of risks, can be more
financially sustainable. The risk assessment is also
a procedure that demands a very peculiar expertise and needs to be custom-made
for every system, which will contribute even further to a steep rise in costs (Rah-
many
2012
).
2.5 The V Life Cycle Model
The V-Model was presented in the
final years of the 1980s by Paul Rook, as a
variation over the waterfall model that attempted to emphasize the existing con-
nection between each of the stages of the development process and its respective
stage of tests. By focusing on this relationship, it ensures that adequate quality
measurements and testing are constantly resorted to throughout
the life cycle
(Skidmore
2006
).
The method thus presented is that each step is implemented by resorting to
detailed documentation from the previous step. With this documentation, the
product is checked and approved at each stage of the process, before it can move on
to the next stage (Balaji and Murugaiyan
2012
). With constant testing, and its
respective documentation, it is possible to increase the overall ef
ciency of the
process, particularly because eventual problems can be detected and resolved early
(Mathur and Malik
2010
) (Fig.
2.4
).
The V-Model starts off with a very similar premise to the classic waterfall
models. In successive steps, the project goes from analysis of requirements and
speci
cations, to architectural and detailed design, to coding. However, instead of
Fig. 2.4 V life cycle model (adapted from Balaji and Murugaiyan
2012
)
Search WWH ::
Custom Search