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...
Guardado en:
| Autor principal: | |
|---|---|
| Formato: | Objeto de conferencia |
| Lenguaje: | Inglés |
| Publicado: |
2024
|
| Materias: | |
| Acceso en línea: | http://sedici.unlp.edu.ar/handle/10915/176645 |
| Aporte de: |
| Sumario: | 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. |
|---|