Saturday, March 14, 2009

Exercise 3. Rapid Evolutionary Prototyping Approach


Let me see. R E P A . That's REPA !

Just like prototyping, the need for instant gratification is always necessary. End users and web developers or application developers always need "feedback" - an active rather than passive pathway to gain better understanding of what has been done, and what can be done moving forward.

Only by making available an environment to help users and developers to visualise or to imagine how the complete system work can help make the entire project MOVE FORWARD.

This Rapid Evolutionary Prototyping Approach will involve two phases
i) evolutionary application prototyping - kind of staggering the application development process
ii) implementation

In this situation, it is often useful to apply project management techniques to ensure phased review checkpoints are available.

Agile software development is on the other hand a methodology in which many and frequent check points, review and adaptations are made when comes to development of software. Both of them has a significant amount of overlap.

No comments:

Post a Comment