The Evolutionary Process Development Model
–Feedback from the user is used throughout the entire process.
–The software product is refined through many versions
–Deals constantly with changes.
–Provides quickly an initial version of the system.
–Involves all development teams
–Quick fixes may be involved
–“Invisible” process, not well-supported by documentation.
–The system’s structure can be corrupted by continuous change.
–Special tools and techniques may be necessary
–The client may have the impression the first version is very close to the final product and thus be less patient.
–When requirements are not well understood.
–Good for small and medium-sized software systems.
You can also view:
1. Boehms Spiral Process Model
2. Rational Unified Process Model
3. Rapid Application Development-RAD
4. Prototyping Process Model
5. Incremental Process Model
6. Component Based Software Engineering
7. Evolutionary Process Development Model
8. Waterfall Process Model
9. Software Process Framework Activity
Create a Google+ Profile and Link give that link on k2 user url Open file "components/com_k2/templates/default/item.php" Add &qu...
Inception: define scope and nature How does a software project will started Define business plan Identify breath and depth of market Roug...
Use Case Diagrams: A use case in software engineering and systems engineering is a description of a system’s behavior. In other words, a ...
These define system properties and constraints e.g. reliability, response time and storage requirements. Constraints are I/O device capabili...