# Towards Utility-based Prioritization of Requirements in Open Source Environments

arXiv: https://arxiv.org/abs/2102.08638 · HTML: https://mlsanity.com/paper/2102.08638/

## Key facts

- Cited by 1 papers in the map (data through 14 Oct 2026).
- Builds on 2 of its 29 references that are in the map.
- First posted on arXiv 17 Feb 2021.

## Builds on (most cited first, 2 of 2)

- [Developer Prioritization in Bug Repositories](https://mlsanity.com/paper/1704.04764/) (2017)
- [Solving the Large Scale Next Release Problem with a Backbone Based Multilevel Algorithm](https://mlsanity.com/paper/1704.04768/) (2017)

## Built on by (most cited first, 1 of 1)

- [AI Techniques for Software Requirements Prioritization](https://mlsanity.com/paper/2108.00832/) (2021)

## Abstract (arXiv)

Requirements Engineering in open source projects such as Eclipse faces the challenge of having to prioritize requirements for individual contributors in a more or less unobtrusive fashion. In contrast to conventional industrial software development projects, contributors in open source platforms can decide on their own which requirements to implement next. In this context, the main role of prioritization is to support contributors in figuring out the most relevant and interesting requirements to be implemented next and thus avoid time-consuming and inefficient search processes. In this paper, we show how utility-based prioritization approaches can be used to support contributors in conventional as well as in open source Requirements Engineering scenarios. As an example of an open source environment, we use Bugzilla. In this context, we also show how dependencies can be taken into account in utility-based prioritization processes.