Does the V-Model have a verification and validation stage for every stage?

Question

I recently sat a test, and got the wrong answer on a question, which made me question my knowledge on the V-model. The answer was a true/false and here is the statement relating to the V-model.

'Each stage of the SDLC has a corresponding verification and validation stage.'

Initially, I answered true, but it got me thinking 'Hmm, what about the development stage', I switched to false and got it wrong. Apparently the answer is true.

However, I don't understand why still. The following image provides the confusion.

Can someone explain to me why the Development (Coding) stage in the V-model structure would be considered to have a corresponding verfication/ validation stage? As I can't see/define what either these stages would be.

Thanks.

Answer 1

I can understand your confusion. To be honest, I think I would have gone for false as well.

I mean you could argue, that the code should be verified by the developer(s), throughout the implementation (code reviews would be an example). However, this is not mentioned specifically in the V-model.

You could also argue that the code is verified in the unit testing, which is deffinitely a smart thing to do. However, this still wouldn't be a corresponding verification, as the unit test (in the model) belongs to the module design.

My understanding of the V-model, is that it is primarily about design from the top and down. When you implement, you implement from the bottom and up. And that if a test fails, you go back to the corresponding design phase. Even if I could answer the question from your test, I doubt it would contribute a whole lot, to the way I use the model.