本帖最后由 beiwei5du 于 2019-10-8 20:56 编辑
这个可以参考,其实我们现在很多都会先做一个模型prototype,然后基于这个原型,相应的人员感知也会更好一些,而非是等所有的design都做好后,才进行system building,这个对于相对比较复杂的系统来说是很困难的。 Disadvantages of V-model: - Very rigid and least flexible.
- Software is developed during the implementation phase, so no early prototypes of the software are produced.
- If any changes happen in midway, then the test documents along with requirement documents has to be updated.
When to use the V-model: - The V-shaped model should be used for small to medium sized projects where requirements are clearly defined and fixed.
- The V-Shaped model should be chosen when ample technical resources are available with needed technical expertise.
High confidence of customer is required for choosing the V-Shaped model approach. Since, no prototypes are produced, there is a very high risk involved in meeting customer expectations. |