Defining requirements is the foundation of your product. If mistakes are made or the work is not thorough enough, the whole project is put at risk. We believe that requirements engineering can only achieve its goals in a transparent, iterative partnership. A requirement specification can serve as a basis for this, but it can never replace joint requirements engineering.
more complete and consistent definition of requirements through interdisciplinary perspectives
reduced development costs by identifying and preventing incorrect developments at an early stage
easier to plan project duration, sizing and budgeting
Absolutely user-centric user experience through early user involvement
continuous consideration of the technical framework and feasibility
Use cases document the intended functionality of the software solution using simplified models. In a use case or application, the externally visible response of a system is described from the user's perspective.
Personas are used to better understand the hypothetical user. They provide a realistic picture of the user and can be used at all stages of the development process.
We visualise and analyse the processes in the company that are affected by the desired solution. We look at the processes in general, how they are actually lived and whether there is potential for optimisation or, if necessary, process breakdowns.
A user story is a software requirement written in everyday language. It is deliberately kept short, usually no more than two sentences. The author of the story is the Product Owner.
Screen scribbles provide initial approaches and ideas for the future software interface. They serve as a basis for collaborative work on the user experience, the user interface and interaction concepts.
An entity-relationship diagram shows the relationships between entities in the system. This supports the detailed system design later in the process.
In this part of the workshop, we will look at what dependencies exist with existing systems and what conditions need to be created.
During the entire workshop, we jointly check whether what has been developed is consistent, i.e. free of contradictions.
Immediately after the workshop, you will receive a photo documentation in which we will record the results and the development process. This is followed by a detailed preparation of the workshop with the following components:
Requirements engineering is not a one-off activity. Rather, it is a series of smaller workshops throughout the development process in which requirements are defined and goals are set. Requirements engineering is therefore an integral part of the iterative development process.