Requirement artifacts such as use cases, business process models, or GUI mockups are used for many activities in software development. They serve as an important reference point in the communication and clarification of requirements. The way requirements are represented influences which activities can be carried out particularly well. For example, developers can effectively use user stories for estimating and prioritizing requirements. In this regard, business process models provide a better overall overview. A special case is represented by hybrid development approaches that combine agile and traditional methods. Agile and traditional methods fundamentally use different types of requirement artifacts, raising the question of what a requirement solution looks like that supports elements of both methods. The first goal of this work is to gain a closer understanding of how requirement artifacts are used in practice and what advantages and disadvantages different roles see in various artifacts. To this end, an interview study will be conducted as part of the work. Based on the findings regarding the handling of artifacts, this work presents a concept that addresses the identified problem on two levels. On the methodological level, approaches for modeling and improving the structure of requirement landscapes are developed. This involves deciding whether, for example, additional artifacts such as specifications should be used and linked alongside user stories. On the second level, the project level, tool-based approaches that utilize automated connections assist project participants in dealing with specific requirements and dependencies. This includes, for example, reminding project participants to adjust dependent requirements when a requirement is changed.