Evolutionary Model in Software Engineering

This evolutionary model concept comes into the picture after the user faces the
partially developed system rather than waiting for the fully developed version. The idea
of this evolutionary model comes from developing the core module and then improving
the software product by using iterative and incremental techniques with appropriate
feedback.

In this evolutionary process model, the software product is in the sensitive version,
which is made through many iterations, and then the final product is prepared. This
evolutionary approach also suggests breaking down all the models into maintainable
smaller chunks. After that, we can prioritize all the smaller products. After completing
all the products, we can deliver those chunks one at a time to the users.

It plays a vital role in large projects where we can easily search the module for the
implementation of incremental things. It is also an influential model because it collects
customer feedback throughout the development process, and the customer can use
the base feature of the project before the release of the entire working version.

What is the Evolutionary Model?

The evolutionary model is also known as successive versions or incremental models.

The main aim of this evolutionary model is to deliver the products in total processes
over time. It also combines the iterative and collective model of the software
development life cycle (SDLC).

Based on the evolutionary model, we can divide the development model into many
modules to help the developer build and transfer incrementally. On the other hand, we
can also develop the skeleton of the initial product. Also, it refines the project to
increase levels of capability by adding new functionalities in successive versions.

Characteristics of the Evolutionary Model

There are so many characteristics of using the evolutionary model in our project. These
characteristics are as follows.

o We can develop the evolutionary model with the help of an iterative waterfall
model of development.

o There are three types of evolutionary models. These are the Iterative model,
Incremental model and Spiral model.

o Many primary needs and architectural planning must be done

o to implement the evolutionary model.

 o When the new product version is released, it includes the new functionality and
some changes in the existing product, which are also released with the latest
version.

o This model also permits the developer to change the requirement, and the
developer can divide the process into different manageable work modules.

o The development team also have to respond to customer feedback throughout

the development process by frequently altering the product, strategy, or process.

Prototyping Model

We can define this prototyping model as the first form using all other forms created or
copied. We can also call the prototyping model the set of general objects that helps to
create the software. We can not identify the input and output of requirement details. We
can develop the program quickly with the help of this model. We have some different
phases of using this prototyping model. These are as follows.

o Communication
In this phase, the client and the developer should have a meeting, and in that
meeting, they discuss the main objective of creating the project.

o Quick design
When we have the requirements known to the developer, then the developer can
implement the quick design. The quick design includes implementing important
aspects, such as the input and output format of the software. The main focus of
 this project is on the things visible to the user rather than the detailed plan. With
the help of this, we can also create the prototype of the project.

o Modelling quick design

In this phase, we can get a clear idea about the software development because
the software is now in the build state. Also, it allows the developer to understand
the project's basic requirements.

o Construction of prototype
The customer evaluates the prototype of the project.

o Deployment, delivery, feedback

If the client is unsatisfied with the project, then the developer can recreate the
project according to the client's satisfaction. This process repeats until the client
is fully satisfied. After the client is happy, the project will be developed based on
the final prototype.

Advantages of the Prototyping Model

There are so many benefits of using the prototype model. These are as follows:

o The prototype model does not need detailed input, output, processes,
adaptability of the operating system, or entire machine interaction.

o The user is fully active in the development process of this model.

o The development process is the best platform for users to understand the
project.

o We can easily detect the error with the help of this prototyping model.
 o It also identifies the missing functionality very quickly.

o It also identifies the confusing or difficult functions.

Disadvantages of the Prototyping Model

Using a prototyping model also has some disadvantages. These are as follows.

o In this model, the involvement of the client is greater. So, it is not always
considered by the developer.

o The development time is longer, so it is a prolonged process.

o The developer has to perform so many changes according to the client's

demand. It disturbs the rhythm of the development process.

o When the user is confused with the prototype, then this prototype will be thrown
away.

Spiral Model

This model is also known as the risk-driven process model. With the help of this spiral
model, we can generate the software project. During the risk analysis, if a risk is found,
an alternate solution should be suggested and implemented in the spiral model. We
can also say that it combines the sequential or waterfall models and the prototype
models. All the required activities are done in one iteration. The output of the large
project is small.

The framework activities of the spiral model are as shown below.

Advantages of the Spiral Model

There are so many benefits of using the spiral model. These are as follows:

o The amount of risk should be reduced in this model.

o This model is best for large and critical projects.

o It provides the developer with solid approval and documentation control.

o The software production time is less in this spiral model.

Disadvantages of Spiral Model

It also has some disadvantages to using the spiral model. These are as follows.

o We need a lot of financial support to develop a project.

o We should not use this model for a very small project.