TY - GEN
T1 - Estudio sistemático de literatura sobre estimación y priorización de requisitos de calidad en desarrollo de software
AU - Salamea, Maria Jose
AU - Gonzalez-Palacio, Liliana
AU - Oriol, Marc
AU - Farre, Carles
PY - 2020/6
Y1 - 2020/6
N2 - Quality requirements (also known as non-functional requirements) are those that address the quality of the software. They involve diverse aspects such as availability, security, performance, scalability, portability and usability, among others. Continuous technological advances such as cloud computing or the Internet of Things present new challenges in guaranteeing a satisfactory level of quality in these aspects. Moreover, agile development methodologies, whose use is increasing, such as SCRUM, XP, Kanban, do not provide the necessary support for the management of these quality requirements. To support software engineers when making decisions about the level of quality needed in a project, it is essential to know in advance (1) what criteria will be considered to verify, prioritize, plan, and/or negotiate quality requirements. Likewise, it is necessary to specify (2) how these criteria will be evaluated and (3) what factors in the project context may affect that evaluation. To try to answer these 3 research questions, the authors of this article have designed and are carrying out a systematic literature review. This article presents for discussion the description of the methodology followed in that literature review, as well as some of the preliminary results obtained during its execution.
AB - Quality requirements (also known as non-functional requirements) are those that address the quality of the software. They involve diverse aspects such as availability, security, performance, scalability, portability and usability, among others. Continuous technological advances such as cloud computing or the Internet of Things present new challenges in guaranteeing a satisfactory level of quality in these aspects. Moreover, agile development methodologies, whose use is increasing, such as SCRUM, XP, Kanban, do not provide the necessary support for the management of these quality requirements. To support software engineers when making decisions about the level of quality needed in a project, it is essential to know in advance (1) what criteria will be considered to verify, prioritize, plan, and/or negotiate quality requirements. Likewise, it is necessary to specify (2) how these criteria will be evaluated and (3) what factors in the project context may affect that evaluation. To try to answer these 3 research questions, the authors of this article have designed and are carrying out a systematic literature review. This article presents for discussion the description of the methodology followed in that literature review, as well as some of the preliminary results obtained during its execution.
KW - agilism
KW - estimation
KW - non-functional requirement
KW - prioritization
KW - quality requirements
UR - http://www.scopus.com/inward/record.url?scp=85089016219&partnerID=8YFLogxK
U2 - 10.23919/CISTI49556.2020.9140957
DO - 10.23919/CISTI49556.2020.9140957
M3 - Contribución a la conferencia
AN - SCOPUS:85089016219
T3 - Iberian Conference on Information Systems and Technologies, CISTI
BT - Proceedings of CISTI 2020 - 15th Iberian Conference on Information Systems and Technologies
A2 - Rocha, Alvaro
A2 - Perez, Bernabe Escobar
A2 - Penalvo, Francisco Garcia
A2 - del Mar Miras, Maria
A2 - Goncalves, Ramiro
PB - IEEE Computer Society
Y2 - 24 June 2020 through 27 June 2020
ER -