Quality is delighting customers
When to select Waterfall Model:
1)Requirements should be well known.
2)Product definition must be stable.
3)Technology must be understood.
4)New version of existing product.
When to select V model:
1)All requirements should be well known up-front.
2)Solution and technology must be known well.
3)When it can be modified to handle changing requirements beyond analysis phases.
Its not clear with the given statements ...can you describe it more.?
would like to add some more..
Water fall normally for small duration of projects..
requirement changes or modifications r not encouraged..
V model for longer duration of projects..
Requirement changes or modifications r welcomed..
But at the initial stage of the project you will not aware of the fact that Requirement are going to be changed or not. and we have to select model at early stage.
Means that in Waterfall Model we cant accept the change in requirements.
yes you are correct, thats why Water Fall model was left later by companies and new models came to picture with this flaw in water fall
Hi this is my interview question
If you r using V model. Requirements are changing oftentimes. then what we do ? if one are two times its ok. oftenly requirements are changing then what you do .....?
Waterfall model encourages testing at later stage of software development life cycle after coding has completed. But V-Model encourages testing associated with all phases of software development life cycle.
So, waterfall model can be choose in following conditions :-
1) When project is of short time span.
2) We are very clear with the user requirement.
3) We work with experienced people.
4) We should not encourage the change in requirements.
V-model can be choose in following conditions :-
1) When project is of long time span.
2) We are not clear with the user requirement.
3) We work with inexperienced people.
4) We should encourage the change in requirements everytime.
Thanks and regards
@ Sitam jana ,
Your answer is good... V Model 3rd point , the team may be of Exp persons too. it is not a prerequisite to have a team of in-exp persons to use V model.
I mean to say that : V Model is mostly followed when there are maximum inexperienced people in the team for software development.
But you said it right the team may be of experienced persons too.
Can we change our requirements in V-model. Then in that case how does it differ from Agile apart from the former being sequential and the latter being iterative. And customer participation and small releases in agile which is not a pre-requisite for V model.
If we can change our requirements in V model, then when can that be done?
When to select Waterfall Model: 1)Requirements should be well known and Clear. 2)Product definition must be stable means static project. 3)Technology must be understood. 4)New version of existing product. 5) After creating one phase than after go to next phase,no turning back possible here.6)It cannot handle dynamic changes
When to select V model: 1)All requirements should be well known up-front. 2)Solution and technology must be known well. 3)When it can be modified to handle changing requirements beyond analysis phases.4)Here all phase after complition should verified.
If i m wrong any where plz correct me.
Only Select V model, dont think about Waterfall model.