Calidad de productos de Software: un aporte para criterios de aceptación no funcionales en historias de usuario
Date
2023-12
Journal Title
Journal ISSN
Volume Title
Publisher
AJEA- Actas de Jornadas y Eventos Académicos de UTN
Abstract
En el contexto de las metodologías ágiles para el desarrollo de software, las Historias de Usuario son una
práctica común para introducir requisitos del sistema. Con el propósito de determinar si el producto de software que se está desarrollando satisface los requisitos establecidos, se crean ciertos Criterios de Aceptación (funcionales y no funcionales), los cuales representan las condiciones de satisfacción que se deben cumplir para cada Historia de Usuario. Como se mencionó anteriormente, los Criterios de Aceptación pueden ser de tipo funcional o no funcional, por lo general a estos últimos se los asocia con requisitos de calidad o a restricciones que tendrá el sistema. En este trabajo se presenta una propuesta para facilitar la especificación de requisitos de calidad para Criterios de Aceptación no funcionales, tomando como perspectiva la calidad de productos de software, y lo establecido en la familia de normas ISO/IEC 25000.
In the context of agile methodologies for software development, User Stories are a common practice to introduce requirements in the development process. To determine if the software product being developed satisfies the established requirements, certain Acceptance Criteria are created, which can be functional and nonfunctional, and are the satisfaction conditions that must be met for each User Story As mentioned, the Acceptance Criteria can be of a functional or non-functional type, generally the latter are associated with quality requirements or restrictions that the system will have. This paper presents a proposal to facilitate the specification of quality requirements for non-functional Acceptance Criteria, taking as a perspective the quality of software products and what is established in the ISO/IEC 25000 family of standards.
In the context of agile methodologies for software development, User Stories are a common practice to introduce requirements in the development process. To determine if the software product being developed satisfies the established requirements, certain Acceptance Criteria are created, which can be functional and nonfunctional, and are the satisfaction conditions that must be met for each User Story As mentioned, the Acceptance Criteria can be of a functional or non-functional type, generally the latter are associated with quality requirements or restrictions that the system will have. This paper presents a proposal to facilitate the specification of quality requirements for non-functional Acceptance Criteria, taking as a perspective the quality of software products and what is established in the ISO/IEC 25000 family of standards.
Description
Keywords
Calidad, Metodologías Ágiles, Requisitos No Funcionales, Software, Quality, Agile Methodologies, Requirements non-functional, Software
Citation
Jornadas de Ciencia y Tecnología 2023
Collections
Endorsement
Review
Supplemented By
Referenced By
Creative Commons license
Except where otherwised noted, this item's license is described as openAccess