2017 International Conference on New Trends in Computing Sciences (ICTCS) 2017
DOI: 10.1109/ictcs.2017.55
|View full text |Cite
|
Sign up to set email alerts
|

Requirements Prioritization Techniques Review and Analysis

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
5
0

Year Published

2018
2018
2023
2023

Publication Types

Select...
3
2

Relationship

0
5

Authors

Journals

citations
Cited by 7 publications
(5 citation statements)
references
References 23 publications
0
5
0
Order By: Relevance
“… Criticality‐driven issue prioritization in RE sessions . Requirements prioritization is an important activity of the requirement engineering (RE) process 59 . In RE sessions, developers are tasked to determine and prioritize the requirements of the software system, trying to integrate end‐users needs 58 .…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“… Criticality‐driven issue prioritization in RE sessions . Requirements prioritization is an important activity of the requirement engineering (RE) process 59 . In RE sessions, developers are tasked to determine and prioritize the requirements of the software system, trying to integrate end‐users needs 58 .…”
Section: Discussionmentioning
confidence: 99%
“…Requirements prioritization is an important activity of the requirement engineering (RE) process. 59 In RE sessions, developers are tasked to determine and prioritize the requirements of the software system, trying to integrate end-users needs. 58 Our results can be used to support collaborative decision-making processes in requirements prioritization.…”
Section: Discussionmentioning
confidence: 99%
“…In these techniques, human input is very important. Qaddoura et al [40] reviewed prioritization techniques and also shed light on the contribution of ML to the topic. ML can be used for automated analysis of these large set of software requirements prioritization, as well as in helping to improve existing techniques.…”
Section: B Requirements Specification and Analysismentioning
confidence: 99%
“…Many conventional software requirement prioritization techniques have been proposed by authors [12], [14], [29], [32], [37], [43], [47], [51], [55], [57]. These methods are quantitative as well as subjective in nature.…”
Section: Introductionmentioning
confidence: 99%
“…Existing requirements prioritization techniques suffer from several problems such as complexity of application, expensive in computations, lack of automation, scalability, ambiguity, and uncertainty [12], [37], [47], [53], [59]. Software initiatives might come with several risks, assumptions, and requirements that are incompatible.…”
Section: Introductionmentioning
confidence: 99%