About the workshop
Thank your for participating and making the workshop a success!
You can download a summary of the workshop, all presentation slides and accepted papers here
Requirements Engineering and Testing are both important areas within software engineering, each with their research communities and set of practitioners. The coordination of these two fields affects the efficiency and the effectiveness of the entire software development cycle and its lead time, making this an important topic from a business perspective. While much work has been done in the respective fields of Requirements Engineering (RE) and Testing, there exists much more that can be done to increase the connection between the RE and the Testing process.
The objective of this workshop is to address the interplay of Requirements Engineering (RE) and Testing, in research and industry, including the challenges that come with connecting requirements and testing. The goal of this workshop is to highlight the importance of this cross-disciplinary research area and to develop a body of knowledge for RET. The first workshop (held in conjunction with the IEEE International Requirements Engineering Conference 2014) produced a map of the area of RET including 20 topics covered by this new research area. This map includes topics that are related to processes, practices, artefacts, methods, techniques, tools and softer aspects like the communication between roles in the software engineering processes.
The workshop aims to provide a dedicated forum for exchanging ideas and best practices and to foster industry-academia collaboration on this topic. In this way, the workshop connects the (currently) separate communities of RE and Testing.
Baldvin Gislason Bern
Axis Communications AB
Tests as requirements - Why we don't do requirements at Axis
Does successful product development need requirements engineering? And what happens to testing when there are no requirements?
In this talk we will look at an example of a successful company that develops complex embedded products in a software product line, but where there is little effort put into software requirements. We will explore why this strategy has come to be and the context for why this strategy works. We will also look into how testing copes with the limited requirements and how testing compensates for the downsides of missing requirements.
Baldvin Gislason Bern works at Axis Communications as an R&D Expert, where his main responsibility is test strategy. Past experiences include leading teams of engineers from Bosch, Panasonic, Siemens and Sony in creating certification test tools for API standards. Baldvin is currently involved in the Swedish Software Center research project, where companies cooperate with universities to improve software development in the Nordic countries.
Paper Submission: January 15, 2016
Author Notification: February 5, 2016
Camera-Ready Due: February 18, 2016
Early-Bird ends: February 26, 2016
Workshop Date: March 14, 2016