Requirements Elicitation Based on Inception Deck and Business Processes Models in Scrum

Pardo, Manuel Alejandro Pastrana; Ordóñez, Hugo; Ordóñez, Armando; Merchán, Luis

doi:10.1007/978-3-319-66562-7_24

Cited by 5 publications

(3 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…As an example, the proposed approach could be applied to a SCRUM methodology, in which BPMN models could be used to convey the stakeholders' needs, so to properly build requirements documentation in terms of so-called user stories [19]. In such a case, the proposed approach could be used either by preserving the original SCRUM process, thus making BPMN models not part of the product backlog (the list of maintained artifacts), or by adding BPMN models to the product backlog, in order to properly integrate user stories, as reported in [20].…”

Section: Related Workmentioning

confidence: 99%

A Lightweight BPMN Extension for Business Process-Oriented Requirements Engineering

2021

View full text Add to dashboard Cite

Process-oriented requirements engineering approaches are often required to deal with the effective adaptation of existing processes in order to easily introduce new or updated requirements. Such approaches are based on the adoption of widely used notations, such as the one introduced by the Business Process Model and Notation (BPMN) standard. However, BPMN models do not convey enough information on the involved entities and how they interact with process activities, thus leading to ambiguities, as well as to incomplete and inconsistent requirements definitions. This paper proposes an approach that allows stakeholders and software analysts to easily merge and integrate behavioral and data properties in a BPMN model, so as to fully exploit the potential of BPMN without incurring into the aforementioned limitation. The proposed approach introduces a lightweight BPMN extension that specifically addresses the annotation of data properties in terms of constraints, i.e., pre- and post-conditions that the different process activities must satisfy. The visual representation of the annotated model conveys all the information required both by stakeholders, to understand and validate requirements, and by software analysts and developers, to easily map these updates to the corresponding software implementation. The presented approach is illustrated by use of two running examples, which have also been used to carry out a preliminary validation activity.

show abstract

Section: Related Workmentioning

confidence: 99%

A Lightweight BPMN Extension for Business Process-Oriented Requirements Engineering

2021

View full text Add to dashboard Cite

show abstract

“…Further complicating matters, the task of "Architecting" can be articulated in different ways depending on the chosen background. A technically-minded team member may call for "traceability procedures" (Gayer et al, 2016) or a better approach to the pre-development phase and improving requirements elicitation (Pastrana et al, 2017) which can be supported with tools (Farid, 2012). Particularly, non-functional requirements seem to pose a challenge (Farid, 2012).…”

Section: Architectingmentioning

confidence: 99%

Why and how is Scrum being adapted in practice: A systematic review

Hron

Obwegeser

2022

Journal of Systems and Software

View full text Add to dashboard Cite

“…A partir de una problemática o de una oportunidad identificada, se contempla una reunión inicial entre todos los interesados, para establecer de manera colaborativa la visión del proyecto, incluyendo un plan preliminar de iteraciones. Esta reunión tiene, internamente, una serie de actividades, basadas en la práctica ágil "Inception Deck" [23].…”

Section: Generalidadesunclassified

AgilUC: Software development process for small teams and a strategy for its teaching

Hurtado Gil

2020

rev.digit.educ.ing

View full text Add to dashboard Cite

La norma ISO/IEC 29110 se creó como un modelo para el desarrollo de software para pequeñas entidades, dado que este tipo de equipos cuentan con recursos limitados para mejorar sus procesos. Por otra parte, estos equipos por lo general usan métodos ágiles de desarrollo de software, por sus características de flexibilidad y entrega de valor a los clientes. Buscando relacionar estas dos tendencias, se definió un proceso basado en la norma ISO/IEC 29110, que además incluye prácticas de procesos ágiles, para ser usado en equipos pequeños de desarrollo. Además del proceso, también se definió una estrategia para enseñarlo en los cursos de Ingeniería de Software de la Universidad de Caldas, buscando que los estudiantes puedan aplicarlo en sus proyectos y en sus futuros trabajos. Este artículo presenta la definición general del proceso (ÁgilUC), la estrategia de enseñanza y algunos resultados de su aplicación parcial en un curso.

show abstract

Requirements Elicitation Based on Inception Deck and Business Processes Models in Scrum

Cited by 5 publications

References 4 publications

A Lightweight BPMN Extension for Business Process-Oriented Requirements Engineering

A Lightweight BPMN Extension for Business Process-Oriented Requirements Engineering

Why and how is Scrum being adapted in practice: A systematic review

AgilUC: Software development process for small teams and a strategy for its teaching

Contact Info

Product

Resources

About