The following Posters will be presented at Refsq:


1. Managing Requirements Interdependencies in Agile Software Development: A Preliminary Result

Indira Nurdiani

Abstract: Currently managing requirement interdependencies using Agile practices is relatively unexplored. This study explores the state of practice of managing requirements interdependencies in Agile software development through a survey. A total of 52 complete responses were obtained, with 50% of the respondents suggesting that they consider requirements interdependencies. The preliminary result indicates that requirements interdependencies become a greater concern as the project and product complexity increases


2. Reviewing Inconsistent Behavioral Properties

Jennifer Brings and Marian Daun

Abstract: During model-based engineering numerous diagrams are created, some of which document the same behavioral properties of the system from different perspectives. In industrial practice these diagrams are often developed or revised independently of each other. In consequence, inconsistencies will almost inevitably arise during the development. This situation may, for example, occur in function-centered engineering when just one of the two main artifacts, the behavioral requirements or the functional design, is updated with new or changed stakeholder intentions. While it is possible to automatically detect these inconsistencies, it is impossible to resolve them automatically if it is unclear, whether the requirements are up-to-date. Hence, manual reviews are needed to determine the current stakeholder intentions and to ensure their correct representation in requirements and later on in design artifacts. Manual reviews, however, tend to be error prone and time consuming. To aid manual reviews of model-based specifications and in particular, the review of behavioral requirements and functional design, we proposed the use of a dedicated review model, which represents both artifacts within one model. Experiments have shown that the use of the review model increases effectiveness, efficiency, user-confidence, and supportiveness compared to the review of the two original artifacts. However, so far the distinction between consistencies and inconsistencies has only been made for entire diagrams in the review model. This may lead to the review model containing two very similar diagrams. To further investigate whether an integrated representation of two inconsistent behavioral properties not only in the review model at large, but in one single diagram can improve manual reviews even more, we extended our approach to automatically merge two inconsistent basic message sequence charts.


3. Experimentation with Self-configuring Systems

Erik Kamsties and Fabian Kneer

Abstract: Self-configuring systems are defined by IBM as systems that ”can dynamically adapt to changing environments. Self-configuring components adapt dynamically to changes in the environment, using policies provided by the IT professional. Such changes could include the deployment of new components or the removal of existing ones, or dramatic changes in the system characteristics.” Self-configuring systems can be found in various application areas. Typically, they are used in situations, where the typical adaptive/perfective maintenance activities to make a system fit to changed used needs or environmental properties cannot take place. One reason is lack of time, e.g. the user expects instantaneous adaption to his needs. This is the case with service-oriented systems or some kinds of embedded systems. It is expected that self-configuration becomes an increasingly important subject with the Internet of Things. In our everyday life we are interacting with many things (e.g. cars, traffic lights, buildings, sensors, mobile phones, etc) which we rely on. These things that surround us get more and more smarter as they are equipped with increasing computing power and communication capabilities. The systems that results by connecting these things are called Internet of Things (IoT). The synergistic services of these connected devices go beyond what is provided by the isolated devices. The Internet of Things is characterized by a loose coupling of devices. That is, they collaborate rather than depending on each other as in an ordinary distributed system. Self-configuration in these systems-of-systems becomes a challenge as the collaborating systems need to follow joint goals. An increasing number of publications is treating the subject of self-configuration /-adaption for systems-of-systems. This poster presents a proposal for experimentation with self-configuring systems targeting at both researchers and practitioners in the field.


The following Tools will be presented:


1. AQUSA: The Automatic Quality User Story Artisan for Agile Software Development

Garm Lucassen, Fabiano Dalpiaz, Jan Martijn Van Der Werf, and Sjaak Brinkkemper

User stories are an increasingly popular textual notation to capture requirements in agile software development. Despite this popularity, the number of methods to assess and improve user story quality is limited. This prompted the authors to introduce the Quality User Story (QUS) framework in earlier work. We take advantage of the potential offered by natural language processing (NLP) techniques to present the Automatic Quality User Story Artisan or AQUSA. This tool takes a set of user stories in input and outputs errors and warnings that expose possible defects. During our interactive demonstration, the participant will learn how and why specific quality defects are exposed by the AQUSA tool.


2. QoE Probe: A Requirement-Monitoring tool

Farnaz Fotrousi and Samuel Fricker

Abstract: Runtime requirement monitoring is used for verification and validation of implemented requirements. To monitor the requirements in runtime; we propose a “QoE probe” tool, a mobile application integrated through an API, to collect usage logs as well as users’ Quality of Experience (QoE) in the form of user feedback. The analysis of the collected data guides requirement monitoring of functional and non-functional requirements as well as capturing new requirements.