At Beeliners we work according to the V-model, this model provides insight into processes for adjustments in hardware and software development. It therefore provides the desired structure to achieve the best results. In addition, we notice that there is a good relationship between the verification, test and validation phase. This forces us to ensure that we have SMART formulated the objectives, together with the customer during the verification phase. Finally, we will have to verify this in the validation phase.

On the left side of the V-model are phases in which a product is designed (specified) and developed into a prototype. A strategic session was often carried out in advance. It is important here that results from the phase are tested against the next phase, this is in relation to the intended change or changes.

On the right side of the V-model are the phases in which testing and verifications are central. The V-model has been a simple tool for years to gain insight into processes for changes in the information provision, in particular for the software. The horizontal line is the formal division between the supplying and accepting party.

Despite the linear presentation of the V-Model, it is also very applicable in our own agile development approach. A useful feature of the V-model is that it provides insight into the phases about which we make agreements with customers.