User Stories or Use Cases? The Answer is: Requirements!
- Autores
- Pinciroli, Fernando
- Año de publicación
- 2024
- Idioma
- inglés
- Tipo de recurso
- documento de conferencia
- Estado
- versión publicada
- Descripción
- 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 - Materia
-
Ciencias Informáticas
software requirement
use case
user story
story mapping
top-down requirement development
bottom-up requirement development
dual-track agile - Nivel de accesibilidad
- acceso abierto
- Condiciones de uso
- http://creativecommons.org/licenses/by-nc-sa/4.0/
- Repositorio
.jpg)
- Institución
- Universidad Nacional de La Plata
- OAI Identificador
- oai:sedici.unlp.edu.ar:10915/176645
Ver los metadatos del registro completo
| id |
SEDICI_8323ff34f44baee618b3bcb38d86b0a3 |
|---|---|
| oai_identifier_str |
oai:sedici.unlp.edu.ar:10915/176645 |
| network_acronym_str |
SEDICI |
| repository_id_str |
1329 |
| network_name_str |
SEDICI (UNLP) |
| spelling |
User Stories or Use Cases? The Answer is: Requirements!Pinciroli, FernandoCiencias Informáticassoftware requirementuse caseuser storystory mappingtop-down requirement developmentbottom-up requirement developmentdual-track agileUntil 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ática2024-10info:eu-repo/semantics/conferenceObjectinfo:eu-repo/semantics/publishedVersionObjeto de conferenciahttp://purl.org/coar/resource_type/c_5794info:ar-repo/semantics/documentoDeConferenciaapplication/pdf825-836http://sedici.unlp.edu.ar/handle/10915/176645enginfo:eu-repo/semantics/altIdentifier/isbn/978-950-34-2428-5info:eu-repo/semantics/reference/hdl/10915/172755info:eu-repo/semantics/openAccesshttp://creativecommons.org/licenses/by-nc-sa/4.0/Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0)reponame:SEDICI (UNLP)instname:Universidad Nacional de La Platainstacron:UNLP2025-09-29T11:47:29Zoai:sedici.unlp.edu.ar:10915/176645Institucionalhttp://sedici.unlp.edu.ar/Universidad públicaNo correspondehttp://sedici.unlp.edu.ar/oai/snrdalira@sedici.unlp.edu.arArgentinaNo correspondeNo correspondeNo correspondeopendoar:13292025-09-29 11:47:29.589SEDICI (UNLP) - Universidad Nacional de La Platafalse |
| dc.title.none.fl_str_mv |
User Stories or Use Cases? The Answer is: Requirements! |
| title |
User Stories or Use Cases? The Answer is: Requirements! |
| spellingShingle |
User Stories or Use Cases? The Answer is: Requirements! Pinciroli, Fernando Ciencias Informáticas software requirement use case user story story mapping top-down requirement development bottom-up requirement development dual-track agile |
| 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! |
| dc.creator.none.fl_str_mv |
Pinciroli, Fernando |
| author |
Pinciroli, Fernando |
| author_facet |
Pinciroli, Fernando |
| author_role |
author |
| dc.subject.none.fl_str_mv |
Ciencias Informáticas software requirement use case user story story mapping top-down requirement development bottom-up requirement development dual-track agile |
| topic |
Ciencias Informáticas software requirement use case user story story mapping top-down requirement development bottom-up requirement development dual-track agile |
| dc.description.none.fl_txt_mv |
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 |
| 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. |
| publishDate |
2024 |
| dc.date.none.fl_str_mv |
2024-10 |
| dc.type.none.fl_str_mv |
info:eu-repo/semantics/conferenceObject info:eu-repo/semantics/publishedVersion Objeto de conferencia http://purl.org/coar/resource_type/c_5794 info:ar-repo/semantics/documentoDeConferencia |
| format |
conferenceObject |
| status_str |
publishedVersion |
| dc.identifier.none.fl_str_mv |
http://sedici.unlp.edu.ar/handle/10915/176645 |
| url |
http://sedici.unlp.edu.ar/handle/10915/176645 |
| dc.language.none.fl_str_mv |
eng |
| language |
eng |
| dc.relation.none.fl_str_mv |
info:eu-repo/semantics/altIdentifier/isbn/978-950-34-2428-5 info:eu-repo/semantics/reference/hdl/10915/172755 |
| dc.rights.none.fl_str_mv |
info:eu-repo/semantics/openAccess http://creativecommons.org/licenses/by-nc-sa/4.0/ Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0) |
| eu_rights_str_mv |
openAccess |
| rights_invalid_str_mv |
http://creativecommons.org/licenses/by-nc-sa/4.0/ Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0) |
| dc.format.none.fl_str_mv |
application/pdf 825-836 |
| dc.source.none.fl_str_mv |
reponame:SEDICI (UNLP) instname:Universidad Nacional de La Plata instacron:UNLP |
| reponame_str |
SEDICI (UNLP) |
| collection |
SEDICI (UNLP) |
| instname_str |
Universidad Nacional de La Plata |
| instacron_str |
UNLP |
| institution |
UNLP |
| repository.name.fl_str_mv |
SEDICI (UNLP) - Universidad Nacional de La Plata |
| repository.mail.fl_str_mv |
alira@sedici.unlp.edu.ar |
| _version_ |
1844616338551603200 |
| score |
13.070432 |