Of course we all are aware of the V-model. We are also aware of reviewing and how it can contribute gain faster a vision about the quality.
Egbert Bouman: explained his view towards a SmarTEST W-model which represents more the iterative approach of development and the interaction with business
Jan Jaap Cannegieter: informed us about the historical mentioned W-model referring to Paul Herzlich who already spoke about a W-model in 1993 (source: http://gerrardconsulting.com/?q=node/531). He explained why and how reviewing methods adding to the well know V-model created a "W". He is also one of the co-author of a very good book about reviews (Dutch: "Reviews in de praktijk") In his W-model the moments of review results in the "W-model"
Jos van Rooyen: Who referred to his experience from already 15 years ago referring to a similar model where he added the products to be reviewed and/or the roles to perform to a similar W-model and created a "triple V-model"
Based on that event I cam up with some questions:
1. I always thought about the V-model as a development model. I might be a misperception from me. In the Dutch testing world we refer to the V-model too often to define and explain the testing process. We even spend time to proof that the V-model fits in other development models. Can this be done to make a development model fit into another? And why also spent this energy?
2. Another thing I wonder is why are we referring to a W-model if we speak about checking the test documentation and other information sources?
3. Do we need a model to refer to the importance of checking documentation?
Some other resources:
W-model from Andreas Spillner: http://squac.iti.upv.es/JTS/JTS2004/docs/Wmodel.pdf
Similar posting of W-models: http://www.testingthefuture.net/2009/09/the-w-model
The Dangerous and Seductive V Model: Nice twist here is the reference towards Morton's butterffy-model: Morton, S. (2001). "The Butterfly Model for Test Development". Sticky Minds website. Accessed 6th October 2008