Since end of March, I can proudly say, that I am finally part of the System Verification Team. Why finally? Well, from the moment I got to know System Verification, until signing my Internship Contract and having my first day working in our beautiful Office in Bonn, some time has passed.

Improving digital life is not just another buzzword for us. At System Verification,  it is in our DNA and fits perfect into our clients need: Deploying requirements in time, budget and quality into production. We believe that our vision ultimately adds value for our clients, for its consumers and businesses. But what does that actually mean and how are we improving digital life at System Verification? If you can take yourself 5 minutes of your time, you will soon know more. My name is Julian Göbert and dealing with those questions is part of my everyday work at System Verification. I joined the company in January 2020 and working as Testmanagement Consultant as well as Consultant Manager for the business unit Finance & Insurance.

We already know that there are a few titles related to people who work in the QA field: Quality Assurance Analyst, Software Test Engineer, Automation Test Engineer, Test Engineer. They all have the same goal when doing the task: to ensure that a product is developed and released with high quality and that it provides a smooth user experience. Having said that, the question of what is the role of a QA Consultant comes up? Let’s dive in deeper.

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:

January 2022 is not only the start of a new year, but also the official start of our new German System Verification office in Hamburg. Of course, our journey in Hamburg didn’t just start and our first Hamburg colleagues already joined us in October 2021. Michael Lucas, Prasanth Sivakumar and Andrei Suvorkov are very excited about the opening of the new office. Read what they think about the start in Hamburg and our future journey in the north of Germany: 

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.

I have always called myself a manual tester. But why really? What do I mean by that? It is very common in the test world to divide into two areas, automated tester or manual tester.

How often do you test a test case?

Two months ago, the well reputed Springer Nature journal SN Computer Science, published an article by our colleague Adha Hrusto and co-authors Prof. Per Runeson and Dr. Emelie Engström. The title was “Closing the Feedback Loop in DevOps Through Autonomous Monitors in Operations”. The work presented in the article has been carried out in collaboration with our customers in the region.

“Requirements, how complicated can it be?
Just listen to what the clients says, write it all down and you are good to go!”