Specifying Value in GRL for Guiding BPMN Activities Prioritization

In a value-based requirements engineering approach, the stakeholders’ value propositions must be considered ahead in order to prioritize which requirements will be developed first to drive the software development activities. Early requirements approaches like the Goal- Oriented Requirements Language (GRL) focuses on modeling goals, tasks, contributions, and dependencies in order to satisfy the stakeholders’ needs, but do not provide a mechanism to specify value according to stakeholders’ value propositions. Moreover, in software development, after specifying value propositions, there is a need to align goal elements into business process elements in order to prioritize which business process activity is going to be developed next. Thus, we propose a new approach (value@GRL) to improve GRL and prioritize Business Process Model and Notation (BPMN) activities. Value@GRL provides guidelines for specifying value in GRL models according to the stakeholders’ needs and prioritization mechanisms to define BPMN activities\u27 order in an incremental software development