2018
DOI: 10.5539/mas.v12n2p62
|View full text |Cite
|
Sign up to set email alerts
|

Requirements Prioritization Techniques Comparison

Abstract: Requirements prioritization is considered as one of the most important approaches in the requirement engineering process. Requirements prioritization is used to define the ordering or schedule for executing requirement based on their priority or importance with respect to stakeholders' viewpoints. Many prioritization techniques for requirement have been proposed by researchers, and there is no single technique can be used for all projects types. In this paper we give an overview of the requirement process and … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
21
0

Year Published

2018
2018
2024
2024

Publication Types

Select...
5
3
2

Relationship

1
9

Authors

Journals

citations
Cited by 53 publications
(29 citation statements)
references
References 18 publications
0
21
0
Order By: Relevance
“…All in all, one of the most common limitations of the methods mentioned above (AHP, PAHPT, Cost-Value, Pairwise Analysis, CBRank, DRank, Fuzzy AHP, Hierarchy AHP, IGA and Cognitive-Driven) is that they do not specifically address requirements collisions throughout the prioritization process. In fact, they turn out to be time-consuming for large sets of requirements, being hardly scalable (Karlsson, et al, 1998;Hudaib, et al, 2018) in the long run as well.…”
Section: Related Workmentioning
confidence: 99%
“…All in all, one of the most common limitations of the methods mentioned above (AHP, PAHPT, Cost-Value, Pairwise Analysis, CBRank, DRank, Fuzzy AHP, Hierarchy AHP, IGA and Cognitive-Driven) is that they do not specifically address requirements collisions throughout the prioritization process. In fact, they turn out to be time-consuming for large sets of requirements, being hardly scalable (Karlsson, et al, 1998;Hudaib, et al, 2018) in the long run as well.…”
Section: Related Workmentioning
confidence: 99%
“…Requirements prioritization is seen as one of the most significant tasks for decision-makers (leaders or managers) within a project [3]. On the other hand, Hudaib et al [4] treats it as the primary process in software engineering, providing the perfect order of implementation of the requirements to plan software versions and provide desirable functionality to customers.…”
Section: Requirement Prioritizationmentioning
confidence: 99%
“…• Coverage: All user scenarios and requirements have to be covered, considering the system-level importance as it is proposed in the MoSCoW technique 63 . Based on the MoSCoW mechanism, system requirements specifications (SRS) are categorized in nominal order according to their priority (must, should, could and won't have), which most of the time illustrates the user's needs.…”
Section: System Specifications: a Co-design Processmentioning
confidence: 99%