As an experienced developer, I can tell you the Prototype model is the best choice here. It's like using a crystal ball to see the future, but without the risk of shattering.
Prototype is the way to go. Trying to force the customer into a rigid model like Waterfall or V-Model when they're uncertain is just asking for trouble.
I'd go with the Prototype model too. It's flexible and allows the customer to participate in the development process, which seems crucial when requirements are unclear.
The Prototype model seems like the obvious choice here. The customer is unsure, so an iterative approach that allows them to provide feedback early on is key.
Jacqueline
1 months agoJustine
3 days agoZoila
6 days agoPaulina
2 months agoDoug
20 days agoMelita
1 months agoLisha
1 months agoMary
2 months agoAlease
4 days agoAbel
6 days agoMonte
8 days agoArdella
12 days agoHermila
13 days agoMartina
1 months agoLouann
1 months agoNadine
1 months agoLatanya
2 months agoKanisha
2 months agoCorrina
1 months agoBrande
2 months agoLeanora
2 months agoAlecia
2 months agoTommy
3 months ago