Requirement Engineering

Good business software must be tailored to the user's expertise and tasks. That is why software development does not work in a "quiet room", but only in close cooperation with the experts. Permanent feedback is the basis of good requirements.

Good software cannot be developed from poorly understood requirements.

In our view, requirements elicitation is a constant learning and communication process. In order to develop a common understanding, timely feedback is needed - through direct dialogue (no "silent mail"), through joint modelling and with the help of meaningful documents. To this end, we use various methods and techniques that we have summarised in our toolbox.