User Stories or Use Cases? The Answer is: Requirements!

Until the promulgation of the Agile Manifesto, one of the primary issues in software development was the production of requirement specifications with many inconveniences. One of the four values of the Agile Manifesto was precisely “working software over comprehensive documentation”. However, many m...

Descripción completa

Guardado en:
Detalles Bibliográficos
Autor principal: Pinciroli, Fernando
Formato: Objeto de conferencia
Lenguaje:Inglés
Publicado: 2024
Materias:
Acceso en línea:http://sedici.unlp.edu.ar/handle/10915/176645
Aporte de:
id I19-R120-10915-176645
record_format dspace
spelling I19-R120-10915-1766452025-02-18T20:04:03Z http://sedici.unlp.edu.ar/handle/10915/176645 User Stories or Use Cases? The Answer is: Requirements! Pinciroli, Fernando 2024-10 2024 2025-02-18T14:11:04Z en Ciencias Informáticas software requirement use case user story story mapping top-down requirement development bottom-up requirement development dual-track agile Until the promulgation of the Agile Manifesto, one of the primary issues in software development was the production of requirement specifications with many inconveniences. One of the four values of the Agile Manifesto was precisely “working software over comprehensive documentation”. However, many misinterpreted this value, and, in practice, documentation was taken to the minimum expression, aiming more at doing agility than good software. Then, user stories took the place of use cases. After some years, it can be perceived that one problem was replaced with another: there is a significant loss of quality in the requirements. In this work, we aim to highlight two fundamental points: 1) the problem does not lie in the use of one technique over the other, but in the need to specify requirements correctly; 2) these techniques are not interchangeable, as they target different requirements approaches, to the extent that it is most effective to use them in combination. Red de Universidades con Carreras en Informática Objeto de conferencia Objeto de conferencia http://creativecommons.org/licenses/by-nc-sa/4.0/ Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0) application/pdf 825-836
institution Universidad Nacional de La Plata
institution_str I-19
repository_str R-120
collection SEDICI (UNLP)
language Inglés
topic Ciencias Informáticas
software requirement
use case
user story
story mapping
top-down requirement development
bottom-up requirement development
dual-track agile
spellingShingle Ciencias Informáticas
software requirement
use case
user story
story mapping
top-down requirement development
bottom-up requirement development
dual-track agile
Pinciroli, Fernando
User Stories or Use Cases? The Answer is: Requirements!
topic_facet Ciencias Informáticas
software requirement
use case
user story
story mapping
top-down requirement development
bottom-up requirement development
dual-track agile
description Until the promulgation of the Agile Manifesto, one of the primary issues in software development was the production of requirement specifications with many inconveniences. One of the four values of the Agile Manifesto was precisely “working software over comprehensive documentation”. However, many misinterpreted this value, and, in practice, documentation was taken to the minimum expression, aiming more at doing agility than good software. Then, user stories took the place of use cases. After some years, it can be perceived that one problem was replaced with another: there is a significant loss of quality in the requirements. In this work, we aim to highlight two fundamental points: 1) the problem does not lie in the use of one technique over the other, but in the need to specify requirements correctly; 2) these techniques are not interchangeable, as they target different requirements approaches, to the extent that it is most effective to use them in combination.
format Objeto de conferencia
Objeto de conferencia
author Pinciroli, Fernando
author_facet Pinciroli, Fernando
author_sort Pinciroli, Fernando
title User Stories or Use Cases? The Answer is: Requirements!
title_short User Stories or Use Cases? The Answer is: Requirements!
title_full User Stories or Use Cases? The Answer is: Requirements!
title_fullStr User Stories or Use Cases? The Answer is: Requirements!
title_full_unstemmed User Stories or Use Cases? The Answer is: Requirements!
title_sort user stories or use cases? the answer is: requirements!
publishDate 2024
url http://sedici.unlp.edu.ar/handle/10915/176645
work_keys_str_mv AT pincirolifernando userstoriesorusecasestheanswerisrequirements
_version_ 1845116792695947264