(Compare Development Models). We emphasize model
characteristics and consider similar activities between models,
such as, requirements, analysis, design, coding, implementation
and testing. CDM is a systematic and defined process, using a
classification technique as a comparison tool. It is similarly
applied to software development models, facilitating reasoning,
communication, customization and education.
Differently from most of the previously published comparisons
of software development models, CDMod allow us to identify
characteristics of the models, highlighting qualities and drawbacks
of each one and following a logical sequence for the comparison.
Two models are compared in our case study. We present the
results of such comparison and discuss how CDMod could be
used in fine-tuning the software development process currently
used in an organization.
2. RELATED WORK
Several software development models [7, 5, 11] are available in
the literature; some are more thoroughly discussed, such as, the
Waterfall Model [9] and the Spiral Model [2]. For that reason we
have selected these two models to use in our case study.
• The Waterfall Model – “Classic Life Cycle”, presents
the following sequence of development phases:
requirements, analysis, program design, coding, testing
and operations. It is the oldest model [5] and is still
thoroughly used [7].
• The Spiral Model appeared as a model that had a greater
flexibility to the developer. It encompasses
requirements gathering, design planning,
implementation and deployment in an interactive and
incremental fashion. It also incorporates a risk analysis
phase.
2.1 Waterfall Life Cycle
The Classic Life Cycle or Waterfall, also known as the “topdown”
approach, was proposed by Royce [9]. Up until the mid
80's it was the only model with a level of general acceptance. It
was derived from models used in traditional engineering activities
with the objective of establishing an order in the development of
large software products. Compared with other software
development models, it is more rigid and less manageable.
The Waterfall Model is one of the most important models ever
published. It is a reference to others, and serves as the basis for
many modern projects. Its original version was improved over
time and is still frequently used today [5].
A great part of the success of the Waterfall Model is due to the
baseline management, which identifies a fixed group of
documents produced as a result of each phase of the life cycle [5].
The produced documentation includes more than text files, it has
graphical representations of the software and even simulations. In
this model the phases are executed systematically in a sequential
order as shown in Figure 1 and it usually has the following phases:
Analysis, Design, Construction, Evaluation and Maintenance.
(Compare Development Models). We emphasize model
characteristics and consider similar activities between models,
such as, requirements, analysis, design, coding, implementation
and testing. CDM is a systematic and defined process, using a
classification technique as a comparison tool. It is similarly
applied to software development models, facilitating reasoning,
communication, customization and education.
Differently from most of the previously published comparisons
of software development models, CDMod allow us to identify
characteristics of the models, highlighting qualities and drawbacks
of each one and following a logical sequence for the comparison.
Two models are compared in our case study. We present the
results of such comparison and discuss how CDMod could be
used in fine-tuning the software development process currently
used in an organization.
2. RELATED WORK
Several software development models [7, 5, 11] are available in
the literature; some are more thoroughly discussed, such as, the
Waterfall Model [9] and the Spiral Model [2]. For that reason we
have selected these two models to use in our case study.
• The Waterfall Model – “Classic Life Cycle”, presents
the following sequence of development phases:
requirements, analysis, program design, coding, testing
and operations. It is the oldest model [5] and is still
thoroughly used [7].
• The Spiral Model appeared as a model that had a greater
flexibility to the developer. It encompasses
requirements gathering, design planning,
implementation and deployment in an interactive and
incremental fashion. It also incorporates a risk analysis
phase.
2.1 Waterfall Life Cycle
The Classic Life Cycle or Waterfall, also known as the “topdown”
approach, was proposed by Royce [9]. Up until the mid
80's it was the only model with a level of general acceptance. It
was derived from models used in traditional engineering activities
with the objective of establishing an order in the development of
large software products. Compared with other software
development models, it is more rigid and less manageable.
The Waterfall Model is one of the most important models ever
published. It is a reference to others, and serves as the basis for
many modern projects. Its original version was improved over
time and is still frequently used today [5].
A great part of the success of the Waterfall Model is due to the
baseline management, which identifies a fixed group of
documents produced as a result of each phase of the life cycle [5].
The produced documentation includes more than text files, it has
graphical representations of the software and even simulations. In
this model the phases are executed systematically in a sequential
order as shown in Figure 1 and it usually has the following phases:
Analysis, Design, Construction, Evaluation and Maintenance.
การแปล กรุณารอสักครู่..