Exercise 3: Finding some common ground

Steps involved with the Rapid Evolutionary Prototypng model


Figure 1: Steps involved in Evolutionary Prototyping model. Retrieved 21 March 2009 from http://www.wittmannclan.de/ptr/cs/slcycles.html

In developing web application, the requirements of each module within the web application may be different and may be unclear. The evolutionary prototyping model, divide the application into modules for development. Within the model, the prototype is coded. When there are changes with the requirements, codes are modified or added.

Each module produces its prototype with its development cycle to meet the requirements for next phrase. Those including analysis of the requirements, design, implementation and test phrases.

As a result, each module contains a prototype for their requirements. Each prototype is refined during the cycle. The project is completed with joining the prototype into a single web application. (Clan, 2009)

Clan (2009) suggested the approach should be used on small projects rather than large projects. It is because the maintenance work is difficult for large projects.

How is it related to agile development?



Figure 2: Agile Model Driven Development Life cycle Retrieved 24 March 2009 from http://www.agilemodeling.com/essays/amdd.htm

Both Rapid Evolutionary Prototyping and Agile Development sharing the same characteristics.

• Identify the basic requirements at initial phrase
  
• Frequently change of the requirements or requirements is unclear.
  
• Requiring customer involvement including face-to-face communication as technical team for the successful of the product.
  
• Activities are broken down into individual module for development.
  
• Features can be add or change during the development.
  
• Each module development has its own development cycle.
  
• Modules combined into a single application
  

The different between them:

• The Agile development focus on the modeling the system but not coding on system.
  
• Evolutionary Prototyping model focus on coding for user requirements not modeling the system.
  

Reference:
Clan, W. (2009), Software Life-cycles, Retrieved 22 March 2009 from http://www.wittmannclan.de/ptr/cs/slcycles.html

Wikipedia (2009), Agile web development, Retrieve 22 March 2009 from http://en.wikipedia.org/wiki/Agile_web_development

Scott W. A.,(2007), Agile Modeling: Effective Practices for Extreme Programming and the Unified Process, John Wiley & Sons