Requirement documents that win the race. Not overweight or emaciated but powerful and in shape

Time-constrained projects ask for requirements approaches that are agile, i.e. adapted to the project needs and without comprehensive documentation. But how can this be achieved? Our approach provides the steps toward the solution of this question. It supports the identification of the essential content of the requirements document as well as the selection of the appropriate modeling technique. The essential content is determined by conducting a systematic risk analysis, which allows identifying the most important elements of the requirements documentation. For the requirement document to be useful it must be precise and understandable for all project participants. The appropriate modeling technique is selected by taking the identified content and the context of the project into account. This paper reports work in progress. It describes the motivation, related work and first ideas