What Makes Agile Test Artifacts Useful?: An Activity-Based Quality Model from a Practitioners' Perspective

@article{Fischbach2020WhatMA,
  title={What Makes Agile Test Artifacts Useful?: An Activity-Based Quality Model from a Practitioners' Perspective},
  author={Jannik Fischbach and Henning Femmer and D. M{\'e}ndez and Davide Fucci and Andreas Vogelsang},
  journal={Proceedings of the 14th ACM / IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)},
  year={2020}
}
Background: The artifacts used in Agile software testing and the reasons why these artifacts are used are fairly well-understood. However, empirical research on how Agile test artifacts are eventually designed in practice and which quality factors make them useful for software testing remains sparse. Aims: Our objective is two-fold. First, we identify current challenges in using test artifacts to understand why certain quality factors are considered good or bad. Second, we build an Activity… Expand

Figures from this paper

Toward software artifacts ecosystem
In the process of developing and maintaining a software product, many things are created and used that are called software artefacts. Software artifacts are created, changed, reused, and changeExpand
CiRA: A Tool for the Automatic Detection of Causal Relationships in Requirements Artifacts
TLDR
This paper presents the tool CiRA (Causality detection in Requirements Artifacts), which represents a first step towards automatic causality extraction from requirements and achieves a macro F_1 score of 83%, which corroborates the feasibility of the approach. Expand
Semi-Automated Labeling of Requirement Datasets for Relation Extraction
Creating datasets manually by human annotators is a laborious task that can lead to biased and inhomogeneous labels. We propose a flexible, semi-automatic framework for labeling data for relationExpand

References

SHOWING 1-10 OF 31 REFERENCES
Working software over comprehensive documentation – Rationales of agile teams for artefacts usage
TLDR
This work substantiates the theoretical basis of the Agile Manifesto in general and contributes to the current research with regard to the usage of artefacts in ASD in particular. Expand
Necessary and neglected?: an empirical study of internal documentation in agile software development teams
TLDR
A questionnaire is employed to measure the perceptions of a group of agile practitioners with regard to the documentation in their projects and finds that over half of developers in this data set find documentation important or even very important but that too little documentation is available in their project. Expand
Artefacts and agile method tailoring in large-scale offshore software development programmes
  • J. Bass
  • Engineering, Computer Science
  • Inf. Softw. Technol.
  • 2016
TLDR
The development programmes in this study create agile and plan-based artefacts to improve compliance with enterprise quality standards and technology strategies, whilst also mitigating risk of failure. Expand
An Exploratory Study on Handling Requirements and Acceptance Test Documentation in Industry
TLDR
A qualitative study to explore the current practices for managing two related types of software documentation: requirements and acceptance tests finds that technical people are usually not involved in the requirements engineering activities, which often results in misunderstood or underestimated requirements. Expand
How Artifacts Support and Impede Requirements Communication
TLDR
The findings can support software developers in planning and improving their processes with regard to better requirements communication and researchers in making mapping methods more applicable in industry. Expand
SPECMATE: Automated Creation of Test Cases from Acceptance Criteria
TLDR
An approach for the automatic extraction of test cases from informal acceptance criteria and a study demonstrating the feasibility of this approach in cooperation with an industry partner are made. Expand
Artefacts in Agile Software Development
TLDR
A Scrum artefact model is presented, on the basis of existing artefact models and results from three case studies, that notices teams using Scrums but decided to produce various non-Scrum artefacts, most notably design documents, test plans and user or release related materials. Expand
The Goal Question Metric Approach
As with any engineering discipline, software development requires a measurement mechanism for feedback and evaluation. Measurement is a mechanism for creating a corporate memory and an aid inExpand
Naming the pain in requirements engineering: A design for a global family of surveys and first results from Germany
TLDR
The design of the family of surveys, its underlying theory, and the full results obtained from Germany reveal a tendency to improve RE via internally defined qualitative methods rather than relying on normative approaches like CMMI. Expand
Rapid quality assurance with Requirements Smells
TLDR
Lightweight smell detection can uncover many practically relevant requirements defects in a reasonably precise way and provides a helpful means to support quality assurance in requirements engineering, for instance, as a supplement to reviews. Expand
...
1
2
3
4
...