An Industrial Case Study on Test Cases as Requirements

@inproceedings{Bjarnason2015AnIC,
  title={An Industrial Case Study on Test Cases as Requirements},
  author={Elizabeth Bjarnason and Michael Unterkalmsteiner and Emelie Engstr{\"o}m and Markus Borg},
  booktitle={XP},
  year={2015}
}
It is a conundrum 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 documentation, test cases are commonly used as requirements. We have investigated this agile practice at three companies in order to understand how test cases can fill the role of requirements. We performed a case study based on twelve interviews performed in a previous… 
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.
Alignment of Requirements Engineering and Software Testing
TLDR
The main benefits of aligning RE and ST, together with the right tool support for automation, are the decreased burden of engineers, shorter time to market, reduced cost of the development process, and more satisfied customers.
A systematic literature review on quality criteria for agile requirements specifications
TLDR
A systematic literature review is conducted to investigate what quality criteria for assessing the correctness of written agile requirements exist and categorize and analyze these criteria and compare them with those from traditional requirements engineering.
A Qualitative Study on using GuideGen to Keep Requirements and Acceptance Tests Aligned
TLDR
The results indicate that GuideGen is a useful approach that facilitates requirements change management and the communication of changes between requirements and test engineers and its applicability to real software projects.
What Do We Know about Alignment of Requirements Engineering and Software Testing?
TLDR
Despite the numerous approaches that are proposed, it is not clear what approach is suitable in what context and why to support industry in RE and ST alignment, guidelines and tool support are needed.
Literature Review of Empirical Research Studies within the Domain of Acceptance Testing
TLDR
A systematic literature review in the field of acceptance test driven development is reported, with the aim of studying existing knowledge and observations in this area.
The impact of RE process factors and organizational factors during alignment between RE and VaV : Systematic Literature Review and Survey
Context: Requirements engineering (RE) and Verification and validation (V&V) areas are treated to be integrated and assure successful development of the software project. Therefore, activation of
Guiding Development of Contribution and Community Strategies in Open Source Software Requirements Engineering
TLDR
This thesis introduces the two concepts of contribution and community strategy and offers problem understanding of how organizations reason in terms of these questions, as well as guidance for how the different types of strategies may be developed.
Open innovation using open source tools: a case study at Sony Mobile
TLDR
This study explores the involvement of a software organization (Sony Mobile) in OSS communities from an OI perspective and what SE practices (requirements engineering and testing) have been adapted in relation to OI, and highlights the innovative outcomes resulting from OI.
...
...

References

SHOWING 1-10 OF 36 REFERENCES
Agile requirements engineering practices and challenges: an empirical study
TLDR
This paper describes empirical research into agile requirements engineering (RE) practices and provides a framework for evaluating the impact and appropriateness of agile RE practices by relating them to RE risks.
Agile Processes in Software Engineering and Extreme Programming, 11th International Conference, XP 2010, Trondheim, Norway, June 1-4, 2010. Proceedings
Research Papers.- Extending Refactoring Guidelines to Perform Client and Test Code Adaptation.- Security Testing in Agile Web Application Development - A Case Study Using the EAST Methodology.-
Factors Limiting Industrial Adoption of Test Driven Development: A Systematic Review
TLDR
A systematic literature review on empirical studies explicitly focusing on TDD as well as indirectly addressing TDD identified seven limiting factors viz., increased development time, insufficient TDD experience/knowledge, lack of upfront design, domain and tool specific issues, and legacy code.
Automated Acceptance Testing: A Literature Review and an Industrial Case Study
TLDR
It is shown that some of the proposed benefits of automated acceptance testing are realistic but that further research and improvements are needed to get the full potential value.
Challenges and practices in aligning requirements with verification and validation: a case study of six companies
TLDR
A multi-unit case study is performed to gain insight into issues around aligning RE and VV by interviewing 30 practitioners from 6 software developing companies, involving 10 researchers in a flexible research process for case studies and provides a strategic roadmap for practitioners improvement work to address alignment challenges.
Agile Processes, in Software Engineering, and Extreme Programming
  • H. Sharp, T. Hall
  • Computer Science
    Lecture Notes in Business Information Processing
  • 2016
This book contains the refereed proceedings of the 17th International Conference on Agile Software Development, XP 2016, held in Edinburgh, UK, in May 2016. While agile development has already become
A successful application of a Test-Driven Development strategy in the industrial environment
  • R. Latorre
  • Business
    Empirical Software Engineering
  • 2013
TLDR
The main conclusions drawn from this project are that ATDD contributes to clearly capture and validate the business requirements, but it requires an extensive cooperation from the customer; and that UTDD has not a significant impact neither on productivity nor on software quality.
Managing Agile Project Requirements with Storytest-Driven Development
TLDR
Using FitLibrary eases storytest-driven development, which brings together requirements and automated testing ideas and practices to support agile software development.
Software requirements and acceptance testing
TLDR
A new approach based on the formal scenario analysis is presented, which is systematic, and easily applicable to any software or system, and its benefits and its applicability are summarized.
How software engineers use documentation: the state of the practice
TLDR
The results confirm the widely held belief that SEs typically do not update documentation as timely or completely as software process personnel and managers advocate, however, the results also reveal that out-of-date software documentation remains useful in many circumstances.
...
...