Evolutionary Process Models, stand-alone process model
Evolutionary models are iterative.
They are characterized develop increasingly more complete versions of the software.
Two common evolutionary process models.
The Spiral Model.
Customer defines a set of general objectives for software.
But does not identify detailed requirements for functions and features.
Developer may be unsure of the efficiency of an algorithm.
Prototyping paradigm may offer the best approach.
Can be used as a stand-alone process model.
Better understand what is to be built when requirements are fuzzy.
Start with communication, planned quickly, modeling, Construction, Deployment Delivery & Feedback.
Quick design focuses on GUI that visible to end users.
Quick design leads to the construction of a prototype.
Evaluated by stakeholders, who provide feedback that is used to further refine requirements.
Prototype serves as a mechanism for identifying software requirements.
Problems of prototyping
Stakeholders don’t know what appears to be a working version of the software, Unaware, Compromises in implementation working quickly.
Inappropriate operating system or programming language may be used.
Inefficient algorithm may be implemented.