Selection and prioritization of software requirements using the Verbal Decision Analysis paradigm

Barbosa, Paulo Alberto Melo; Pinheiro, Plácido Rogério; Silveira, Francisca Raquel de Vasconcelos; Filho, Marum Simão

doi:10.18293/seke2017-150

Cited by 4 publications

(27 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…As shown in Figure 4, Verbal Decision Analysis has solving methods for different ranking problems using natural language as input to the solution search. In previous research [8][9][10], we noticed that the alternative ranking generated by the ZAPROS III-i methodology was satisfactory for decision makers. The ease of application of this method and its adaptation to the problems proposed in this work lead us to adopt it in our research.…”

Section: Analysis Of the Information Obtainedmentioning

confidence: 82%

“…As seen, this is an excellent classifier widely known in the VDA field and has an interface developed to facilitate use by the decision maker. In previous works [8][9][10] all 20 requirements of a software problem were immediately prioritized for implementation; that is, there was no selection to predefine requirements that somehow or should not go to the prioritization queue. Thus, if less relevant requirements do not go to the prioritization list, fewer questions will be presented at the stage of choice (seen later) to the decision maker.…”

Section: Analysis Of the Information Obtainedmentioning

confidence: 99%

“…After the entered numerical parameters, it randomly generates data representing four software projects. For purposes of comparisons with previous papers [8,9], we maintain the same mathematical formulation as shown below:…”

Section: Problem Generationmentioning

confidence: 99%

“…In research using only the methods that make up the SBSE, we can find reasonable solutions, even considering projects with 2,000 requirements [30]. In the VDA field, we know that the number of criteria is still somewhat restricted because we consider, for example, the human effort to respond to questionnaires that contain many criteria and their respective criteria values [8,9]. In order to maintain the isonomy between SBSE and VDA methods, in this work, we consider that the characteristics of the requirements (SBSE) are criteria in VDA.…”

Section: Problem Generationmentioning

confidence: 99%

“…We have seen in previous research [8][9][10] some challenges, such as trying to reduce the number of questions asked to the decision maker, since this factor made the prioritization process time-consuming. Another factor that we seek to improve is the solutions found.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Selection and Prioritization of Software Requirements Applying Verbal Decision Analysis

et al. 2019

Self Cite

View full text Add to dashboard Cite

During the software development process, the decision maker (DM) must master many variables inherent in this process. Software releases represent the order in which a set of requirements is implemented and delivered to the customer. Structuring and enumerating a set of releases with prioritized requirements represents a challenging task because the requirements contain their characteristics, such as technical precedence, the cost required for implementation, the importance that one or more customers add to the requirement, among other factors. To facilitate this work of selection and prioritization of releases, the decision maker may adopt some support tools. One field of study already known to solve this type of problem is the Search-Based Software Engineering (SBSE) that uses metaheuristics as a means to find reasonable solutions taking into account a set of well-defined objectives and constraints. In this paper, we seek to increase the possibilities of solving the Next Release Problem using the methods available in Verbal Decision Analysis (VDA). We generate a problem and submit it so that the VDA and SBSE methods try to resolve it. To validate this research, we compared the results obtained through VDA and compared with the SBSE results. We present and discuss the results in the respective sections.

show abstract

Section: Analysis Of the Information Obtainedmentioning

confidence: 82%

Section: Analysis Of the Information Obtainedmentioning

confidence: 99%

Section: Problem Generationmentioning

confidence: 99%

Section: Problem Generationmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Selection and Prioritization of Software Requirements Applying Verbal Decision Analysis

et al. 2019

Self Cite

View full text Add to dashboard Cite

show abstract

Towards the Verbal Decision Analysis Paradigm for Prioritization of Software Requirements Implementable

Pam¹,

Pinheiro²,

FRdV³

2018

Preprint

Self Cite

View full text Add to dashboard Cite

The activity of prioritizing software requirements should be done as efficiently as possible. Selecting the most stable requirements for the most important customers for the development company can be a positive factor when we consider that the available resource does not always encompass the implementation of all requirements. Quantitative methods for reaching software prioritization in releases are many in the field of Search-Based Software Engineering (SBSE). However, we show that it is possible to use qualitative Verbal Decision Analysis (VDA) methods to solve this same type of problem. Moreover, we will use the ZAPROS III-i methods to prioritize requirements considering the opinion of the decision-maker, who will participate in this process. Finally, the results obtained in the VDA structured methods were quite satisfactory when compared to the methods using SBSE. A comparison of results between quantitative and qualitative methods will be made and discussed later.

show abstract

Dealing Hybrid Model Appling in the Selection and Prioritization of Software Requirements Using Verbal Decision Analysis

Barbosa¹,

Pinheiro²,

Silveira³

et al. 2020

Preprint

View full text Add to dashboard Cite

In the software development process, the decision-maker (DM) has a range of problems inherent to its function. Wrong choices during software planning can bring great risk to the project. Therefore, the planning of software releases to be delivered to the customer should be well done. This is not an easy task because releases are made up of many requirements that contain complex variables that must be considered, such as precedence, cost, requirement stability, among other features that make the requirements-selection process challenging. To make this process less exhaustive, DM can use tools that facilitate this work. In software engineering, we can find fields of research specialists in this context, such as Search-Based Software Engineering (SBSE). The SBSE makes use of advanced metaheuristics to search for optimal solutions or the closest to it. In this work, we try to use another field of research to solve this same problem type, the Verbal Decision Analysis (VDA). To do this, we elaborate a workflow that will use the same source data, execute two solutions using the two search fields (SBSE and VDA) and compare the results. In the end, we evaluated and commented on the results.

show abstract

Selection and prioritization of software requirements using the Verbal Decision Analysis paradigm

Cited by 4 publications

References 17 publications

Selection and Prioritization of Software Requirements Applying Verbal Decision Analysis

Selection and Prioritization of Software Requirements Applying Verbal Decision Analysis

Towards the Verbal Decision Analysis Paradigm for Prioritization of Software Requirements Implementable

Dealing Hybrid Model Appling in the Selection and Prioritization of Software Requirements Using Verbal Decision Analysis

Contact Info

Product

Resources

About