Systematic Mapping of the Literature on Smells in Software Development Requirements

One of the activities responsible for the success of a software development project is the specification of requirements, whose purpose is to ensure that the wishes or needs of the client clearly and accurately represent what they expect. A clear and structured requirement specification process avoi...

Full description

Autores:
Tipo de recurso:
Fecha de publicación:
2023
Institución:
Universidad Pedagógica y Tecnológica de Colombia
Repositorio:
RiUPTC: Repositorio Institucional UPTC
Idioma:
eng
OAI Identifier:
oai:repositorio.uptc.edu.co:001/14363
Acceso en línea:
https://revistas.uptc.edu.co/index.php/ingenieria/article/view/15233
https://repositorio.uptc.edu.co/handle/001/14363
Palabra clave:
Requirements smells
requirements debt
software development
software engineering
requirements engineering
Requisito oloroso
deuda de requisitos
desarrollo de software
ingeniería de software
ingeniería de requisitos
Rights
License
http://creativecommons.org/licenses/by/4.0
id REPOUPTC2_735ed523d7e5f880032149d98baa6779
oai_identifier_str oai:repositorio.uptc.edu.co:001/14363
network_acronym_str REPOUPTC2
network_name_str RiUPTC: Repositorio Institucional UPTC
repository_id_str
dc.title.en-US.fl_str_mv Systematic Mapping of the Literature on Smells in Software Development Requirements
dc.title.es-ES.fl_str_mv Mapeo sistemático de la literatura sobre los malos olores en los requisitos de desarrollo de software
title Systematic Mapping of the Literature on Smells in Software Development Requirements
spellingShingle Systematic Mapping of the Literature on Smells in Software Development Requirements
Requirements smells
requirements debt
software development
software engineering
requirements engineering
Requisito oloroso
deuda de requisitos
desarrollo de software
ingeniería de software
ingeniería de requisitos
title_short Systematic Mapping of the Literature on Smells in Software Development Requirements
title_full Systematic Mapping of the Literature on Smells in Software Development Requirements
title_fullStr Systematic Mapping of the Literature on Smells in Software Development Requirements
title_full_unstemmed Systematic Mapping of the Literature on Smells in Software Development Requirements
title_sort Systematic Mapping of the Literature on Smells in Software Development Requirements
dc.subject.en-US.fl_str_mv Requirements smells
requirements debt
software development
software engineering
requirements engineering
topic Requirements smells
requirements debt
software development
software engineering
requirements engineering
Requisito oloroso
deuda de requisitos
desarrollo de software
ingeniería de software
ingeniería de requisitos
dc.subject.es-ES.fl_str_mv Requisito oloroso
deuda de requisitos
desarrollo de software
ingeniería de software
ingeniería de requisitos
description One of the activities responsible for the success of a software development project is the specification of requirements, whose purpose is to ensure that the wishes or needs of the client clearly and accurately represent what they expect. A clear and structured requirement specification process avoids reprocessing at later stages of the project life cycle, generating a benefit in terms of time estimation for new tasks, cost, and effort. In this sense, it is important to have mechanisms or techniques to identify and mitigate possible errors during the requirements specification. Software engineering proposes the term “smell”, which can be defined as a specific symptom that can generate defects in a requirement. The objective of this paper is to establish a broader state of knowledge on the smell identification and classification present during the requirements specification and their impact on the generation of a phenomenon known as requirements debt. This article presents the results obtained after carrying out a systematic mapping of the literature, describing the proposals, initiatives, results, technological tools, benefits and challenges of smell identification and management in the requirements-gathering stage during the software development solutions.
publishDate 2023
dc.date.accessioned.none.fl_str_mv 2024-07-05T19:12:10Z
dc.date.available.none.fl_str_mv 2024-07-05T19:12:10Z
dc.date.none.fl_str_mv 2023-02-09
dc.type.none.fl_str_mv info:eu-repo/semantics/article
dc.type.coar.fl_str_mv http://purl.org/coar/resource_type/c_2df8fbb1
dc.type.coarversion.fl_str_mv http://purl.org/coar/version/c_970fb48d4fbd8a85
dc.type.version.spa.fl_str_mv info:eu-repo/semantics/publishedVersion
dc.type.coarversion.spa.fl_str_mv http://purl.org/coar/version/c_970fb48d4fbd8a154
status_str publishedVersion
dc.identifier.none.fl_str_mv https://revistas.uptc.edu.co/index.php/ingenieria/article/view/15233
10.19053/01211129.v32.n63.2023.15233
dc.identifier.uri.none.fl_str_mv https://repositorio.uptc.edu.co/handle/001/14363
url https://revistas.uptc.edu.co/index.php/ingenieria/article/view/15233
https://repositorio.uptc.edu.co/handle/001/14363
identifier_str_mv 10.19053/01211129.v32.n63.2023.15233
dc.language.none.fl_str_mv eng
dc.language.iso.spa.fl_str_mv eng
language eng
dc.relation.none.fl_str_mv https://revistas.uptc.edu.co/index.php/ingenieria/article/view/15233/12621
https://revistas.uptc.edu.co/index.php/ingenieria/article/view/15233/13180
dc.rights.en-US.fl_str_mv http://creativecommons.org/licenses/by/4.0
dc.rights.coar.fl_str_mv http://purl.org/coar/access_right/c_abf2
dc.rights.coar.spa.fl_str_mv http://purl.org/coar/access_right/c_abf71
rights_invalid_str_mv http://creativecommons.org/licenses/by/4.0
http://purl.org/coar/access_right/c_abf71
http://purl.org/coar/access_right/c_abf2
dc.format.none.fl_str_mv application/pdf
text/xml
dc.publisher.en-US.fl_str_mv Universidad Pedagógica y Tecnológica de Colombia
dc.source.en-US.fl_str_mv Revista Facultad de Ingeniería; Vol. 32 No. 63 (2023): January-March 2023 (Continuous Publication); e15233
dc.source.es-ES.fl_str_mv Revista Facultad de Ingeniería; Vol. 32 Núm. 63 (2023): Enero-Marzo 2023 (Publicación Continua); e15233
dc.source.none.fl_str_mv 2357-5328
0121-1129
institution Universidad Pedagógica y Tecnológica de Colombia
repository.name.fl_str_mv Repositorio Institucional UPTC
repository.mail.fl_str_mv repositorio.uptc@uptc.edu.co
_version_ 1839633797385027584
spelling 2023-02-092024-07-05T19:12:10Z2024-07-05T19:12:10Zhttps://revistas.uptc.edu.co/index.php/ingenieria/article/view/1523310.19053/01211129.v32.n63.2023.15233https://repositorio.uptc.edu.co/handle/001/14363One of the activities responsible for the success of a software development project is the specification of requirements, whose purpose is to ensure that the wishes or needs of the client clearly and accurately represent what they expect. A clear and structured requirement specification process avoids reprocessing at later stages of the project life cycle, generating a benefit in terms of time estimation for new tasks, cost, and effort. In this sense, it is important to have mechanisms or techniques to identify and mitigate possible errors during the requirements specification. Software engineering proposes the term “smell”, which can be defined as a specific symptom that can generate defects in a requirement. The objective of this paper is to establish a broader state of knowledge on the smell identification and classification present during the requirements specification and their impact on the generation of a phenomenon known as requirements debt. This article presents the results obtained after carrying out a systematic mapping of the literature, describing the proposals, initiatives, results, technological tools, benefits and challenges of smell identification and management in the requirements-gathering stage during the software development solutions.Una de las actividades responsables del éxito en los proyectos de desarrollo de software es la especificación de requisitos, cuyo propósito es asegurar que los deseos o necesidades del cliente representan de forma precisa lo que ellos esperan. Un proceso claro y estructurado durante la especificación de requisitos permite evitar reprocesos en etapas posteriores del ciclo de vida del proyecto, generando un beneficio en términos de estimación de tiempos para nuevas tareas, costo y esfuerzo. En este sentido, es importante contar con mecanismos o técnicas que permitan identificar y mitigar posibles errores durante la especificación de requisitos. En particular, la ingeniería de software propone el término “olor”, que se puede definir como un síntoma concreto que puede generar defectos en un requisito. Con el objetivo de establecer un estado del conocimiento más amplio en torno a la identificación, clasificación de olores presentes durante la especificación de requisitos y su impacto en la generación de un fenómeno conocido como deuda de requisitos, este artículo presenta los resultados obtenidos después de realizar un mapeo sistemático de la literatura, en el cual se describen las propuestas, iniciativas, resultados, herramientas tecnológicas, beneficios y desafíos en torno a la identificación y gestión de olores en la etapa de levantamiento de requisitos durante el desarrollo de soluciones software.application/pdftext/xmlengengUniversidad Pedagógica y Tecnológica de Colombiahttps://revistas.uptc.edu.co/index.php/ingenieria/article/view/15233/12621https://revistas.uptc.edu.co/index.php/ingenieria/article/view/15233/13180Copyright (c) 2023 Mayra-Alejandra Castillo-Motta, Rubén-Darío Dorado-Córdoba, César-Jesús Pardo-Calvache, Carlos-Eduardo Orozco-Garcéshttp://creativecommons.org/licenses/by/4.0http://purl.org/coar/access_right/c_abf71http://purl.org/coar/access_right/c_abf2Revista Facultad de Ingeniería; Vol. 32 No. 63 (2023): January-March 2023 (Continuous Publication); e15233Revista Facultad de Ingeniería; Vol. 32 Núm. 63 (2023): Enero-Marzo 2023 (Publicación Continua); e152332357-53280121-1129Requirements smellsrequirements debtsoftware developmentsoftware engineeringrequirements engineeringRequisito olorosodeuda de requisitosdesarrollo de softwareingeniería de softwareingeniería de requisitosSystematic Mapping of the Literature on Smells in Software Development RequirementsMapeo sistemático de la literatura sobre los malos olores en los requisitos de desarrollo de softwareinfo:eu-repo/semantics/articlehttp://purl.org/coar/resource_type/c_2df8fbb1info:eu-repo/semantics/publishedVersionhttp://purl.org/coar/version/c_970fb48d4fbd8a154http://purl.org/coar/version/c_970fb48d4fbd8a85Castillo-Motta, Mayra AlejandraDorado-Córdoba, Rubén-DaríoPardo-Calvache, César JesúsOrozco-Garcés, Carlos Eduardo001/14363oai:repositorio.uptc.edu.co:001/143632025-07-18 11:53:14.443metadata.onlyhttps://repositorio.uptc.edu.coRepositorio Institucional UPTCrepositorio.uptc@uptc.edu.co