Workshop Summary of the 1st International Workshop on Requirements and Testing (RET14)

The main objective of the RET workshop was to explore the interaction of Requirements Engineering (RE) and Testing, i.e. RET, in research and industry, and the challenges that result from this interaction. While much work has been done in the respective fields of requirements engineering and testing, there exists much more than can be done to understand the connection between the processes of RE and of testing.

💡 Research Summary

The paper presents a comprehensive summary of the First International Workshop on Requirements and Testing (RET14), held in 2014. The workshop’s central aim was to investigate the interaction between Requirements Engineering (RE) and testing, identify the challenges that arise from this interaction, and outline a joint research agenda for academia and industry. Participants—45 researchers and practitioners from various domains—engaged in three days of intensive discussion, divided into four thematic sessions.

The first session introduced an integrated process model that treats RE and testing as a single, continuous pipeline. A meta‑model was proposed, defining traceability matrices and mapping rules that link each requirement to one or more test cases. This model emphasizes early verification, continuous alignment, and automated impact analysis when requirements evolve.

The second session focused on automation techniques. State‑of‑the‑art natural language processing (NLP) methods were demonstrated for extracting verbs, objects, and constraints from informal requirement statements. These extracted elements were then fed into a model‑based testing (MBT) framework that automatically generates test scenarios and parameterized scripts. Experimental results showed high precision in mapping requirement fragments to test templates, reducing manual test design effort by up to 40 % in a case study involving a banking application.

The third session dealt with quality metrics and evaluation frameworks. Participants discussed a multi‑dimensional metric suite covering test efficiency (e.g., test execution time per requirement), defect detection rate, and requirement satisfaction degree. A multi‑criteria decision‑making (MCDM) approach was introduced to balance risk, cost, and coverage, enabling stakeholders to prioritize testing activities based on quantitative evidence.

The fourth session showcased industry case studies from finance, automotive, and medical device sectors. Each case highlighted how RET integration was realized through continuous integration pipelines, automated regression suites, and change‑impact analysis tools. Success factors included strong governance of requirement changes, early involvement of test engineers, and the use of standardized traceability artifacts. Common limitations involved legacy systems lacking traceability support, resistance to process change, and insufficient tool interoperability.

From the discussions, four major challenges emerged: (1) maintaining test adaptability in the face of frequent requirement changes, (2) achieving compatibility across domain‑specific standards and regulations, (3) ensuring the reliability and verification of automated RET tools, and (4) overcoming cultural and organizational resistance to integrated RE‑test processes. To address these, the authors propose a collaborative roadmap: creation of large‑scale, publicly available RE‑test datasets; development of open‑source integration frameworks that expose standardized APIs for traceability and test generation; establishment of continuous education programs for both requirements analysts and test engineers; and active participation in standards bodies to define common traceability and metric specifications.

In conclusion, RET14 served as a foundational platform that identified critical research gaps, fostered cross‑disciplinary dialogue, and set the stage for future workshops and joint projects. The authors call for sustained international cooperation to refine the proposed models, validate them in diverse industrial contexts, and ultimately bridge the long‑standing divide between requirements engineering and testing for higher software quality and faster time‑to‑market.