Change search
ReferencesLink to record
Permanent link

Direct link
A Multi-Case Study of Agile Requirements Engineering and the Use of Test Cases as Requirements
RISE, Swedish ICT, SICS. RISE, Swedish ICT, SICS, Security Lab.
Number of Authors: 4
2016 (English)In: Information and Software Technology, Vol. 77, 61-79 p.Article in journal (Refereed) Published
Abstract [en]

[Context] It is an enigma that agile projects can succeed "without requirements" when weak requirements engineering is a known cause for project failures. While agile development projects often manage well without extensive requirements test cases are commonly viewed as requirements and detailed requirements are documented as test cases. [Objective] We have investigated this agile practice of using test cases as requirements to understand how test cases can support the main requirements activities, and how this practice varies. [Method] We performed an iterative case study at three companies and collected data through 14 interviews and 2 focus groups. [Results] The use of test cases as requirements poses both benefits and challenges when eliciting, validating, verifying, and managing requirements, and when used as a documented agreement. We have identified five variants of the test-cases-as-requirements practice, namely de facto, behaviour-driven, story-test driven, stand-alone strict and stand-alone manual for which the application of the practice varies concerning the time frame of requirements documentation, the requirements format, the extent to which the test cases are a machine executable specification and the use of tools which provide specific support for the practice of using test cases as requirements. [Conclusions] The findings provide empirical insight into how agile development projects manage and communicate requirements. The identified variants of the practice of using test cases as requirements can be used to perform in-depth investigations into agile requirements engineering. Practitioners can use the provided recommendations as a guide in designing and improving their agile requirements practices based on project characteristics such as number of stakeholders and rate of change.

Place, publisher, year, edition, pages
Elsevier , 2016, 16. Vol. 77, 61-79 p.
Keyword [en]
Agile development, Requirements, Testing, Test-first development, Test-driven development, Behaviour-driven development, Acceptance test, Case study, Empirical software engineering
National Category
Computer and Information Science
Identifiers
URN: urn:nbn:se:ri:diva-24541DOI: 10.1016/j.infsof.2016.03.008OAI: oai:DiVA.org:ri-24541DiVA: diva2:1043625
Available from: 2016-10-31 Created: 2016-10-31

Open Access in DiVA

fulltext(1710 kB)7 downloads
File information
File name FULLTEXT01.pdfFile size 1710 kBChecksum SHA-512
55e09b4a5711c5a2f0d6b03ced563062fc31abd853f673a871c60b906ff9c65063d5f1fef57d20e2db174ddf92e97a20c9d0ed70908782f08b4b3df681f7064b
Type fulltextMimetype application/pdf

Other links

Publisher's full texthttp

Search in DiVA

By author/editor
Bjarnason, ElizabethEngström, Emelie
By organisation
SICSSecurity Lab
Computer and Information Science

Search outside of DiVA

GoogleGoogle Scholar
Total: 7 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

Altmetric score

Total: 61 hits
ReferencesLink to record
Permanent link

Direct link