Question#1: Evolutionary Model
Question#1: Evolutionary Model
You have studied different software lifecycle models and project management
techniques in the Software Enginnering-1 Course. We have observed that various
software application types require different software engineering models and
techniques for their design and development. As you are appearing in your final
year project so discuss at least three SDLC model. Discuss its pros and cons as
well.
Answer:
Evolutionary Model:
Evolutionary model is also referred to as the successive versions model and sometimes
as the incremental model. In Evolutionary model, the software requirement is first
broken down into several modules that can be incrementally constructed and delivered.
The development first develops the core modules of the system. The core modules are
those that do not need services from the other modules. The initial product skeleton is
refined into increasing levels of capability by adding new functionalities in successive
versions. Each evolutionary model may be developed using an iterative waterfall model
of development.
Maintenance
Difficult to divide the problem into several versions that would be acceptable to the
customer and which can be incrementally implemented and delivered.
Prototyping Model:
Incremental Prototyping:
Extreme Prototyping:
1. Basic prototype with all the existing page is present in the HTML format.
2. You can simulate data process using a prototype services layer.
3. The services are implemented and integrated into the final prototype.
Spiral model – is SDLC model, which combines architecture and prototyping by stages.
It is a combination of the Iterative and Waterfall SDLC models with the significant
accent on the risk analysis. The main issue of the spiral model – is defining the right
moment to make a step into the next stage. The preliminary set time frames are
recommended as the solution to this issue. The shift to the next stage is done according to
the plan, even if the work on the previous stage isn’t done yet. The plan is introduced
basing on the statistic data, received during the previous projects even from the personal
developer’s experience.
The earlier working prototype is done - sooner users can point out the flaws
The scalability allows to make changes and add new functionality even at the
relatively late stages
Lifecycle is divided into small parts, and if the risk concentration is higher, the
phase can be finished earlier to address the treats