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.

Sven Ullstad, one of our great consultants at System Verification, wanted to make blood donations  become a natural part of our everyday work life. He suggested an initiative that now allows System Verification employees to donate blood during work hours.

Last week our Talent Acqusition Team hosted a student event, at our HQ in Malmö. They invited students that are currently studying to become software test engineers at EC Utbildning in Malmö. This program and System Verification’s niche are very aligned, and we are happy for our continued collaboration with EC. System Verification has employees that has studied this program before, both newly graduated and some more experienced. A perfect match for future opportunities for students to land a matching job and for us to connect with these talents.

The evening consisted of interesting and insightful panel discussions together with some of our expert consultants and our very own doctor in Software Quality Assurance, Magnus C Ohlsson. Before the event the students had submitted what they were most curious to know about test, QA and the role as consultant. Resulted in different topics and discussions - both on a more technical level but also everything from agile methodologies, qualities as a tester and different roles within QA.

With amazing food and drinks that was served later we had a great time. The evening continued with some contact-making mingle with our experts and the students.

Earlier this week our colleagues Goran Jouma and Patrick Engström Roxendal won the Space Community Cup and took home the coveted trophy to our office. Meet the FIFA pros;

Congratulations on the victory! How does it feel to be the best at FIFA 2021 in the whole office complex?

''It feels really good! There were some tough opponents, but we managed to win in the end! Very fun to have these kind of events within the community. I haven’t played in a while actually, but it’s always big fun to play with friends when I get the chance!'' Patrick says. ''Thank you! It's not something that I expected to be at my workplace (but I'll take it), it feels great! I feel that it was a hard fought victory against some great opponents. It’s also a fun form to socialize in I must say! '' Goran says. 

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: