Scribd
Upload
19 views2 pages

Evolutionary Development Model

Uploaded by

manisingh970614
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
19 views2 pages

Evolutionary Development Model

Uploaded by

manisingh970614
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
You are on page 1/ 2

Evolutionary Development Model

The Evolutionary Development Model in software engineering is an approach where a system is


developed gradually, in small steps, while continuously improving and adapting it based on
feedback. Instead of trying to build the entire system at once (as in the Waterfall model), this model
focuses on creating working prototypes or small parts of the system first, and then refining them
over time.

Key Features:
1. Iterative Process: The development happens in cycles or iterations. Each iteration
produces a better or more complete version of the software.
2. Flexible and Adaptive: It allow developers to adapt to changes in requirements or user
needs as the project evolves.
3. User Involvement: Users provide regular feedback after each iteration, ensuring that the
final product meets their expectations.
4. Risk Reduction: This model reduces the risk of project failure, by identifying and fixing
problems early and in small steps.

Types of Evolutionary Development:


1. Exploratory Development:
• Used when the exact requirements are unclear.
• Focuses on building prototypes and refining them as more is learned about user
needs.
2. Throwaway Prototyping:
• Quick, rough prototypes are created to clarify requirements.
• These prototypes are discarded once the final requirements are clear, and the actual
system is developed.

Steps in the Evolutionary Development Model:


1. Initial Planning: Identify high-level goals and decide what part of the system to develop
first.
2. Develop Prototype/Version: Build a small, functional part of the system.
3. Evaluate and Gather Feedback: Share the prototype with users to collect feedback.
4. Refine and Improve: Use the feedback to make the system better in the next iteration.
5. Repeat: Keep repeating this cycle until the system is complete.

Advantages:
• Handles changing requirements: Perfect for projects where requirements are likely to
change.
• Early delivery of a working system: Users get some functionality to use quickly.
• Encourages user involvement: Helps ensure the system meets user needs.

Disadvantages:
• Lack of clear structure: Can lead to scope creep (project expanding beyond initial goals).
• Higher cost: Repeated iterations and changes can make it expensive.
• Needs skilled developers: Requires expertise to manage iterations and adapt quickly.

When to Use:
• When requirements are unclear or likely to evolve.
• For complex systems requiring regular feedback.
• When the project needs to adapt to user needs quickly.
Examples include web applications, mobile apps, and innovative products where user feedback is
crucial.

Note- If a project doesn't have a clear plan or structure, it can easily grow beyond what was
originally planned. This means people might start adding extra tasks or goals that weren't part of the
original idea, which can make the project harder to manage.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy