a presentation on the topic Evolutionary Process Models

1. EVOLUTIONARY
PROCESS
MODELS
-Devang Gentyal

2. Need of Evolutionary Process Model ?
In industry large/ complex software applications needs
to evolve over a period of time. And all the requirements
can’t be collected during the initial development stage,
hence this makes a straight way development of a
software impossible. To limit this there should be a
development model which helps you to develop
programs in an evolutionary model. Instead of starting
from the beginning, we start implementing the changes
on the current work (evolving the software). Here is
where the Evolutionary Process Model comes in picture

3. What is Evolutionary Process Model ?
An evolutionary process model is a software development approach that emphasizes continuous
refinement and adaptation of the software through iterative cycles. It acknowledges that
software development is an evolving process, and requirements may change over time. The
primary goal of evolutionary process models is to deliver high-quality software while
accommodating changes in customer needs and project requirements.

4. Let’s Take an Example

5. PROTOTYPING
MODEL

6. What is a Prototyping Model?
The prototyping model in software development is like making a mini version of the software, just
as you would make a small model of a house before building it. With a prototype in hand, you can
see how the software will work and make improvements based on feedback. It's like taking a test
drive before buying the real car! This way, you can ensure that the final software is exactly what
you need and want. Prototyping is like having a sneak peek into the future, making sure
everything turns out just right!

7. Often, a customer defines a set of general objectives for software, but does not identify detailed
requirements for functions and features. In other cases, the developer may be unsure of the
efficiency of an algorithm, the adaptability of an operating system, or the form that human-
machine interaction should take. In these, and many other situations, a prototyping paradigm may
offer the best approach. Although prototyping can be used as a stand-alone process model, it is
more commonly used as a technique that can be implemented within the context of any one of the
process models noted in this chapter. Regardless of the manner in which it is applied, the
prototyping paradigm assists you and other stakeholders to better understand what is to be built
when requirements are fuzzy

8. Diagram

9. Let’s Take an Example

10. Problems of Prototyping Model
1. Stakeholders see what appears to be a working version of the software, unaware that the
prototype is held together haphazardly, unaware that in the rush to get it working you haven’t
considered overall software quality or long-term maintainability. When informed that the
product must be rebuilt so that high levels of quality can be maintained, stakeholders cry foul
and demand that “a few fixes” be applied to make the prototype a working product. Too often,
software development management relents.
2. As a software engineer, you often make implementation compromises in order to get a
prototype working quickly. An inappropriate operating system or programming language may
be used simply because it is available and known; an inefficient algorithm may be implemented
simply to demonstrate capability. After a time, you may become comfortable with these choices
and forget all the reasons why they were inappropriate. The less-than-ideal choice has now
become an integral part of the system

11. CONCLUSION
Although problems can occur, prototyping can be an effective paradigm for software
engineering. The key is to define the rules of the game at the beginning; that is, all
stakeholders should agree that the prototype is built to serve as a mechanism for
defining requirements. It is then discarded (at least in part), and the actual software is
engineered with an eye toward quality

12. THANK YOU