2017 IEEE/ACM 39th International Conference on Software Engineering Companion (ICSE-C) 2017
DOI: 10.1109/icse-c.2017.74
|View full text |Cite
|
Sign up to set email alerts
|

Dependency-aware software release planning

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
12
0

Year Published

2017
2017
2021
2021

Publication Types

Select...
3
2
2

Relationship

4
3

Authors

Journals

citations
Cited by 14 publications
(12 citation statements)
references
References 34 publications
0
12
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%
“…Fuzzy graphs have demonstrated to properly capture imprecision of real world problems [4,6]. Hence, we have used algebraic structure of fuzzy graphs for capturing the imprecision associated with strengths of value-related dependencies.…”
Section: Modeling Dependenciesmentioning
confidence: 99%
“…I i, j > 0 states that e j will ultimately in uence the value of e i in a positive way whereas I i, j < 0 indicates that the ultimate in uence of e j on e i is negative. e extent to which the value of an element e i is in uenced by ignoring positive value-related dependencies and/or selecting negative value-related dependencies of e i , is referred to as the penalty [6] of e i and denoted by p i . p i is calculated by taking supremum over the overall in uences of all ignored positive dependencies and selected negative dependencies of e i as given by (6).…”
mentioning
confidence: 99%
See 1 more Smart Citation
“…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%