Building a rationale diagram for evaluating user story sets

Requirements representation in agile methods is often done on the basis of User Stories (US) which are short sentences relating a WHO, WHAT and (possibly) WHY dimension. They are by nature very operational and simple to understand thus very efficient. Previous research allowed to build a unified mod...

Full description

Saved in:
Bibliographic Details
Published in2016 IEEE Tenth International Conference on Research Challenges in Information Science (RCIS) pp. 1 - 12
Main Authors Wautelet, Yves, Heng, Samedi, Kolp, Manuel, Mirbel, Isabelle, Poelmans, Stephan
Format Conference Proceeding Journal Article
LanguageEnglish
Published IEEE 01.06.2016
Subjects
Agile Requirements Modeling
Buildings
Computer aided software engineering
Computer programs
Concrete
Conferences
Construction
Electronic mail
eXtreme Programming
Feasibility
Rationale Diagram
Representations
SCRUM
Semantics
Sentences
User Story
User Story Template
Visualization
Online AccessGet full text
ISSN2151-1357
DOI10.1109/RCIS.2016.7549299

Cover

More Information
Summary:Requirements representation in agile methods is often done on the basis of User Stories (US) which are short sentences relating a WHO, WHAT and (possibly) WHY dimension. They are by nature very operational and simple to understand thus very efficient. Previous research allowed to build a unified model for US templates associating semantics to a set of keywords based on templates collected over the web and scientific literature. Since the semantic associated to these keywords is mostly issued of the i* framework we overview in this paper how to build a custom rationale diagram on the basis of a US set tagged using that unified template. The rationale diagram is strictly speaking not an i* strategic rationale diagram but uses parts of its constructs and visual notation to build various trees of relating US elements in a single project. Indeed, the benefits of editing such a rationale diagram is to identify depending US, identifying EPIC ones and group them around common Themes. The paper shows the feasibility of building the rationale diagram, then points to the use of these consistent sets of US for iteration content planning. To ensure the US set and the rationale diagram constitute a consistent and not concurrent whole, an integrated Computer-Aided Software Engineering (CASE) tool supports the approach.
Bibliography:ObjectType-Article-2
SourceType-Scholarly Journals-1
ObjectType-Conference-1
ObjectType-Feature-3
content type line 23
SourceType-Conference Papers & Proceedings-2
ISSN:2151-1357
DOI:10.1109/RCIS.2016.7549299