Information Technology IT – 16 System life cycle | e-Consult

The project manager should consider several factors when choosing between evolutionary and throwaway prototyping:

• Requirement Clarity: If the requirements are well-defined and stable, evolutionary prototyping is more suitable. If the requirements are unclear or likely to change, throwaway prototyping allows for more flexibility.
• Risk Tolerance: If the project has a low tolerance for risk, evolutionary prototyping is preferred as it reduces the risk of building a completely incorrect product.
• Time Constraints: Throwaway prototyping is generally faster, as it focuses on rapid iteration. Evolutionary prototyping can be more time-consuming due to the iterative nature of development.
• Budget: Throwaway prototyping can be more cost-effective in the short term, as it avoids investing in a final product that may not be viable. However, evolutionary prototyping may be more cost-effective in the long run if it helps to avoid costly rework.
• User Involvement: Both approaches benefit from user involvement, but evolutionary prototyping requires more continuous user feedback.

Recommendation: For a new online banking application, I would recommend an evolutionary prototyping approach. Online banking applications are complex and require a high degree of security and usability. Early user feedback is crucial to ensure that the application is secure, easy to use, and meets the needs of the target audience. While it may take longer initially, the benefits of incorporating user feedback throughout the development process outweigh the potential drawbacks. The iterative nature of evolutionary prototyping allows for the identification and resolution of usability issues early on, reducing the risk of costly rework later in the project. Furthermore, the need for stringent security in online banking necessitates thorough testing and refinement, which evolutionary prototyping facilitates.