The V model has played a huge part of the evolution of developing that we see today. Legend has it that it was developed in Germany during the early 1990’s and its mission was to describe the complex ritual of what we today know as developing. The model describes needs, that gets broken down to System architecture which leads to detailed design. The steps of the V model have many names so keep that in mind if you ever talk to someone about this model. However, the fundamental principle is to create requirement(s) structure based on a need. The second and third level of the model describes that development takes place and at the bottom we so how the developed system is tested. At the “test” step we need to keep in mind what I wrote earlier; a step of the model can be called different things depending on who you talk to. Some refer to testing activities as Test, validation or verification. All three concepts are important to consider when assuring oneself about the quality of the product/system. I keep this note always in my head:
THE QUALITY BLOG
My name is Magnus Hjelmgren and I am Regional Manager at System Verification in Jönköping. I have 20 years of experience in the QA business as a manager, test manager, project manager and more.
Here’s a list of stuff that my dog, and my role as a dog owner, taught me that I’ve been able to apply on my everyday work life in the field of QA.
“Requirements, how complicated can it be?
Just listen to what the clients says, write it all down and you are good to go!”