Riegel, NormanNormanRiegel2022-03-042022-03-042013https://publica.fraunhofer.de/handle/publica/232085Requirements engineers in business-process driven software development are faced with the challenge of letting stakeholders determine which requirements are actually relevant for early business success and should be considered first or even at all during the elicitation and analysis activities. In the area of requirements engineering (RE) and release planning, prioritization is an established strategy for achieving this goal. Available prioritization approaches, however, do not consider all idiosyncrasies of business-process-driven software development. This lack of appropriate prioritization leads to effort often being spent on (RE) activities of minor importance. To support the requirements engineer in overcoming this problem, the idea of applying different models during prioritization is introduced, which shall bring it to a more reliable basis. Through this notion it is expected to reduce unnecessary (RE) activities by focusing on the most important requirements.derequirements engineeringrequirements prioritizationrequirements elicitationinformation system004005006681journal article