UX Design, Requirements Engineering

Taking into consideration more than just requirements

More than just writing down and implementing requirements, there is much more to professional and immediately efficient requirement engineering.

It is important to transform the already existing approaches and wishes into a vision and this vision will outline the overall goals of the project, at the highest level possible. On the basis of this vision, first of all, solution-neutral, rough requirements are determined and possible solutions are developed.

Our motivated employees will support you in this process from start to finish.


Developing requirements

What do I want to achieve with my product?

We offer you extremely competent support in all aspects of requirements engineering. Our well-trained employees, with their many years of versatile experience, can offer you concrete advice. Together, we work out what is to be achieved with the product and from this, the solution-neutral and rough requirements are determined. With these findings, possible solutions are then discussed and at the end you decide how the project will be realised.

Do you have a project and want to realise it?

Get in touch with our requirement engineer Roland Spycher.

Roland Spycher
Roland Spycher
Dipl. Ing. ETH
Product Manager Ā«SolutionsĀ» Project Manager
T +41 71 914 40 66

Requirements engineering in the agile working world

Everything must be agile

To be presented with a product at the end of a project, which is already outdated, is something no customer wants.

In today's working world, agile working methods are used to avoid exactly this scenario. After all, who knows exactly what requirements his product will have to meet in one or even two years?

Projects are more successful and customer-oriented with an agile approach, such as Scrum. To achieve this, the requirement engineering must also adapt and change. In an agile approach, a minimum functional product, also called MVP, is defined at the start. The requirements for this product are then recorded in a first sprint and then implemented.

New functions and features are added to the product in further sprints and requirements for additional implementations are recorded and compiled in a continuous process. Depending on the customer's wishes and the situation, a slightly different and perhaps better path can be taken after the first product than planned from the get go.

This would not be possible without agile working methods.

Requirements Engineering mit agiler Vorgehensweise
Requirements Engineering, Minimum Viable Product (MVP)