2019
DOI: 10.3233/jifs-182810
|View full text |Cite
|
Sign up to set email alerts
|

Dependency-aware release planning for software projects using fuzzy graphs and integer programming

Abstract: Software requirements selection aims to find an optimal subset of the requirements with the highest value while respecting the project constraints. But the value of a requirement may depend on the presence or absence of other requirements in the optimal subset. Such Value Dependencies, however, are imprecise and hard to capture. In this paper, we propose a method based on integer programming and fuzzy graphs to account for value dependencies and their imprecision in software requirements selection. The propose… Show more

Help me understand this report
View preprint versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2020
2020
2021
2021

Publication Types

Select...
2
1

Relationship

3
0

Authors

Journals

citations
Cited by 3 publications
(4 citation statements)
references
References 84 publications
(224 reference statements)
0
4
0
Order By: Relevance
“…Also, value-annotated APIs can help detect value dependencies [13,[15][16][17][18] and conflicts in software code [19]. This is particularly important for reconciling value conflicts (tensions) in software projects.…”
Section: Value Annotation Of Apismentioning
confidence: 99%
“…Also, value-annotated APIs can help detect value dependencies [13,[15][16][17][18] and conflicts in software code [19]. This is particularly important for reconciling value conflicts (tensions) in software projects.…”
Section: Value Annotation Of Apismentioning
confidence: 99%
“…We employed 5 stakeholders to estimate [35] the costs and values of requirements of the PMS. Each requirement r i was assigned an estimated cost of c i ∈ [1,20] and an estimated value of v i ∈ [1,20] by different stakeholders.…”
Section: Case Studymentioning
confidence: 99%
“…However, several studies have argued that this assumption does not hold when interdependencies exist among requirements [14,18,11,19]. The reason is that software requirements affect each other's values due to the valuerelated dependencies among them [20,21,22,23,24,25,14,26]. As a result, excluded requirements may impact the values of selected requirements that depend on them.…”
Section: Introductionmentioning
confidence: 99%
“…Moreover, the extant release planning models do not take into account the fact that the value of a software requirement may depend on the presence or absence of other requirements in the optimal set. Ignoring such Value Dependencies increases the risk of value loss through ignoring (selecting) requirements that positively (negatively) influence the values of other requirements [13], [9], [14], [15], [16], [17]. It is imperative that value dependencies are not limited to the economic value; they extend to a broader range of human values [18], [3].…”
Section: Introductionmentioning
confidence: 99%