Information Technology Reference
In-Depth Information
sequential description of the product
'
s life cycle that spans 7 different stages,
originally denominated
system requirements, software requirements, analysis,
program design, coding, testing and operations
(Royce 1970 ).
first premise in which this model is based is that any development process of
any software or system starts off by two essential steps: analysis and coding. This is
the simplest conceptualization of the model, but is ineffective to understand the
product
The
s further development beyond the stage of creation. Therefore, the analysis
stage is broken down into two steps
'
analysis of both system and software
requirements, while the coding stage is preceded by program design (Royce 1970 ).
The essence of the waterfall model is that it attempts to provide a useful set of
guidelines for the development of new programs or systems. In his original work,
Royce ( 1970 ) provides
five key principles that he believes are essential for the
successful development of large software systems.
The
It is essential to allow designers to be a
part of the initial process, because of their invaluable feedback regarding resources
and limitations. The second is
first is
program design comes
rst.
Extensive documentation of
the development process is paramount, not just to facilitate management of the
process, but to facilitate performance assessments, making the eventual correction
of mistakes more ef
document the design.
final version
of the product should actually be the second version, where all the stages have been
performed and it is easier to pinpoint strengths and weaknesses, to emphasize the
cient. The third is
do it twice,
referring that the
Testing
is a fundamental stage. It is important to bring in specialists that did not participate
in the earlier stages of the process. It is also important to test every single aspect of
the project, regardless of how relevant it is. Finally, the
first and correct the latter. The fourth is
plan, control and monitor testing.
fifth guideline is
involve
the customer.
Having the insight, judgment, and commitment of the customer
taken into account during the development process is a viable option that will
greatly improve its potential for general acceptance (Royce 1970 ).
The waterfall model was a popular approach, and for that reason, it evolved and
adapted into numerous forms, according to different research studies and the con-
text of application. Denomination of each step varies greatly and can re
ect the
speci
field in which it is applied.
However, one common trait covers all the variations of this model: it is a
sequential model. Each of its stages must be entirely concluded before the next can
begin. Similarly to the
c objective of the study or the
flow of a waterfall, the development of the software is
regarded as continuously streaming downward throughout its different stages
(Massey and Satao 2012 ). Thus, for example, analysis of requirements must be
thorough and
ciently carried
out once coding is entirely complete. Each stage is regarded as a static component, a
rigid step in the process. Subsequent changes in previous steps (e.g., awareness of
new requirements) cannot be taken into account (Balaji and Murugaiyan 2012 )
(Fig. 2.1 ).
The waterfall model took precedence over other models in the 1980s and the
beginning of the 1990s. But this preponderance suffered an important setback with
the increasing speed of technological evolution and the subsequent need to swiftly
final before design begins, and testing can only be ef
 
Search WWH ::




Custom Search