2015
DOI: 10.1016/j.knosys.2015.04.010
|View full text |Cite
|
Sign up to set email alerts
|

PHandler: An expert system for a scalable software requirements prioritization process

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
41
0

Year Published

2016
2016
2023
2023

Publication Types

Select...
4
4

Relationship

0
8

Authors

Journals

citations
Cited by 47 publications
(41 citation statements)
references
References 25 publications
0
41
0
Order By: Relevance
“…An expert decision support system (i.e., PHandler) [7] was introduced to prioritize the large scale requirements. This approach was a combination of three methods such as the AHP, Value-based Intelligent Requirement Prioritization (VIRP) method and Neural Network.…”
Section: Related Workmentioning
confidence: 99%
“…An expert decision support system (i.e., PHandler) [7] was introduced to prioritize the large scale requirements. This approach was a combination of three methods such as the AHP, Value-based Intelligent Requirement Prioritization (VIRP) method and Neural Network.…”
Section: Related Workmentioning
confidence: 99%
“…It improved the decision-making process, but it lacked an automatic system for selecting the requirements. Babar et al (2015) proposed an expert system named as the Priority Handler (PHandler) for requirement prioritisation. This method used a technique known as the value-based intelligent requirement prioritisation technique, neural network and analytical hierarchical process for improving the scalability of the method.…”
Section: Literature Reviewmentioning
confidence: 99%
“…The main challenge is the domain knowledge for prioritising the requirements, which raises the need for the human interference in the decision-making process (Babar et al, 2015), this, in turn, poses the need for the automatic selection (Khan et al, 2016) of performing the prioritising technique.…”
Section: Challengesmentioning
confidence: 99%
“…System development life cycle is constructed with the various phases to be used in order to develop a good quality system [1][2][3]. Requirement elicitation is an important phase of system development life cycle, since it is the phase where the requirements are elicited and extracted from the stakeholders [4][5][6] Implementing and developing all the elicited requirements is extremely difficult with limited resources such as budget constraints, short schedule, and limited staff power [7,8]. On the other hand, the implementation of the stakeholders' requirements is considered as a main factor that can lead to develop and deliver a successful system [4,[9][10][11].…”
Section: Introductionmentioning
confidence: 99%
“…Requirement elicitation is an important phase of system development life cycle, since it is the phase where the requirements are elicited and extracted from the stakeholders [4][5][6] Implementing and developing all the elicited requirements is extremely difficult with limited resources such as budget constraints, short schedule, and limited staff power [7,8]. On the other hand, the implementation of the stakeholders' requirements is considered as a main factor that can lead to develop and deliver a successful system [4,[9][10][11]. Prioritizing the requirements is considered as one of the solutions in such a case, since requirements prioritization (RP) is defined as a process of prioritizing the requirements based on the stakeholders' preferences in order to identify the most important requirements among others and to produce a ranked list of requirements [12][13][14] This requirement list is used in release planning and implementation of the system.…”
Section: Introductionmentioning
confidence: 99%