Accepted Papers

Filter accepted papers by track
Filter accepted papers by topic Requirements elicitation, analysis, documentation, validation, and verification Requirements management, viewpoints, prioritization and negotiation Requirements specification languages, methods, processes and tools Modeling of requirements, goals and domains Evolution of requirements over time, product families, variability and reuse Relating requirements to business goals, architecture and testing Formal analysis and verification Social, cultural, global and cognitive factors in requirements engineering Requirements traceability Requirements related to safety, reliability, security, privacy and digital forensics Requirements in agile, product line and model-driven development Requirements in service-oriented, virtualization, embedded, cloud and mobile environments Empirical studies, measurements and prediction Tool support for requirements engineering Industry and research collaboration, interdisciplinary insights, learning from practice, and technology transfer Domain-specific problems, experiences, and solutions, including new and emerging domains Pragmatic requirements engineering: process efficiency, good-enough requirements, agile and lean approaches Collaboration with stakeholders: stakeholder management, creativity, requirements elicitation and negotiation, and crowdsourcing Large-scale requirements engineering: complex systems, product lines, value chains, software ecosystems, agile and lean practices at scale Requirements specification: natural language, model-driven approaches, formal techniques Requirements engineering for user experience, including ethnography, design, and usability Creativity, innovation, and requirements engineering
Requirements elicitation, analysis, documentation, validation, and verification
Requirements management, viewpoints, prioritization and negotiation
Requirements specification languages, methods, processes and tools
Modeling of requirements, goals and domains
Evolution of requirements over time, product families, variability and reuse
Relating requirements to business goals, architecture and testing
Formal analysis and verification
Social, cultural, global and cognitive factors in requirements engineering
Requirements traceability
Requirements related to safety, reliability, security, privacy and digital forensics
Requirements in agile, product line and model-driven development
Requirements in service-oriented, virtualization, embedded, cloud and mobile environments
Empirical studies, measurements and prediction
Tool support for requirements engineering
Industry and research collaboration, interdisciplinary insights, learning from practice, and technology transfer
Domain-specific problems, experiences, and solutions, including new and emerging domains
Pragmatic requirements engineering: process efficiency, good-enough requirements, agile and lean approaches
Collaboration with stakeholders: stakeholder management, creativity, requirements elicitation and negotiation, and crowdsourcing
Large-scale requirements engineering: complex systems, product lines, value chains, software ecosystems, agile and lean practices at scale
Requirements specification: natural language, model-driven approaches, formal techniques
Requirements engineering for user experience, including ethnography, design, and usability
Creativity, innovation, and requirements engineering
ID Paper Track Topics sort
R14 Exposing the Susceptibility of Off-Nominal Behaviors in Reactive System Requirements
Daniel Aceituna and Hyunsook Do
(North Dakota State University, USA)
Abstract  | Paper

Requirements are typically specified on the assumption that the system's operating environment will behave in what is considered to be an expected and nominal manner. When gathering requirements, one concern is whether the requirements are too incomplete to account for every possible, unintended, off-nominal behavior (ONB) that the operating environment can create in the system. In this paper, we present a semi-automated approach, based on the causal component model (CCM), which can expose, within a set of requirements, whether ONBs can result in undesired system states. We demonstrate how the CCM approach exposes and helps address potential off-nominal behavior problems in a set of requirements that represents a real-world product. Our case study shows that the approach can expose susceptibility to ONBs and can supply information in correcting requirements.

Research
Requirements elicitation, analysis, documentation, validation, and verification
Requirements specification languages, methods, processes and tools
Modeling of requirements, goals and domains
14
R11 Handling Knowledge Uncertainty in Risk-Based Requirements Engineering
Antoine Cailliau and Axel van Lamsweerde
(Université Catholique de Louvain, Belgium)
Abstract  | Paper

Requirements engineers are faced with multiple sources of uncertainty. In particular, the extent to which the identified software requirements and environment assumptions are adequate and sufficiently complete is uncertain; the extent to which they will be satisfied in the system-to-be is uncertain; and the extent to which obstacles to their satisfaction will occur is uncertain. The resolution of such domain-level uncertainty requires estimations of the likelihood that those different types of situations may or may not occur. However, the extent to which the resulting estimates are accurate is uncertain as well. This meta-level uncertainty limits current risk-based methods for requirements engineering. The paper introduces a quantitative approach for managing it. An earlier formal framework for probabilistic goals and obstacles is extended to explicitly cope with uncertainties about estimates of likelihoods of fine-grained obstacles to goal satisfaction. Such estimates are elicited from multiple sources and combined in order to reduce their uncertainty margins. The combined estimates and their uncertainties are up-propagated through obstacle refinement trees and then through the system’s goal model. Two metrics are introduced for measuring problematic uncertainties. When applied to the probability distributions obtained by up-propagation to the top-level goals, the metrics allow critical leaf obstacles with most problematic uncertainty margins to be highlighted. The proposed approach is evaluated on excerpts from a real ambulance dispatching system.

Research
Requirements elicitation, analysis, documentation, validation, and verification
Requirements specification languages, methods, processes and tools
Modeling of requirements, goals and domains
11
R15 Assessment of Risk Perception in Security Requirements Composition
Hanan Hibshi, Travis D. Breaux, and Stephen B. Broomell
(Carnegie Mellon University, Saudi Arabia; Carnegie Mellon University, USA)
Abstract  | Paper

Security requirements analysis depends on how well-trained analysts perceive security risk, understand the impact of various vulnerabilities, and mitigate threats. When systems are composed of multiple machines, configurations, and software components that interact with each other, risk perception must account for the composition of security requirements. In this paper, we report on how changes to security requirements affect analysts risk perceptions and their decisions about how to modify the requirements to reach adequate security levels. We conducted two user surveys of 174 participants wherein participants assess security levels across 64 factorial vignettes. We analyzed the survey results using multi-level modeling to test for the effect of security requirements composition on participants’ overall security adequacy ratings and on their ratings of individual requirements. We accompanied this analysis with grounded analysis of elicited requirements aimed at lowering the security risk. Our results suggest that requirements composition affects experts’ adequacy ratings on security requirements. In addition, we identified three categories of requirements modifications, called refinements, replacements and reinforcements, and we measured how these categories compare with overall perceived security risk. Finally, we discuss the future impact of our work in security requirements assessment practice.

Research
Requirements elicitation, analysis, documentation, validation, and verification
Social, cultural, global and cognitive factors in requirements engineering
Empirical studies, measurements and prediction
15
R18 A Quality Model for the Systematic Assessment of Requirements Traceability
Patrick Rempel and Patrick Mäder
(TU Ilmenau, Germany)
Abstract  | Paper

Traceability is an important quality of software requirements and allows to describe and follow their life throughout a development project. The importance of traceable requirements is reflected by the fact that requirements standards, safety regulations, and maturity models explicitly demand for it. In practice, traceability is created and maintained by humans, which make mistakes. In result, existing traces are potentially of dubious quality but serve as the foundation for high impact development decisions. We found in previous studies that practitioners miss clear guidance on how to systematically assess the quality of existing traces. In this paper, we review the elements involved in establishing traceability in a development project and derive a quality model that specifies per element the acceptable state (Traceability Gate) and unacceptable deviations (Traceability Problem) from this state. We describe and formally define how both, the acceptable states and the unacceptable deviations can be detected in order to enable practitioners to systematically assess their project's traceability. We evaluated the proposed model through an expert survey. The participating experts considered the quality model to be complete and attested that its quality criteria are of high relevance. We further found that the experts weight the occurrence of different traceability problems with different criticality. This information can be used to quantify the impact of traceability problems and to prioritize the assessment of traceability elements.

Research
Requirements traceability
18
I07 Understanding Changes in Use Cases: A Case Study
Mohammad R. Basirati, Henning Femmer, Sebastian Eder, Martin Fritzsche, and Alexander Widera
(TU München, Germany; Munich Re, Germany)
Abstract  | Paper

Requirements change and so (should) do requirements artifacts, such as use cases. However, we have little knowledge about which changes requirements engineers actually perform on use cases. We do not know what is changing, at which locations use cases change and need a deeper understanding of which changes are problematic in terms of difficult or risky. To explore these challenges from an industrial point of view, we conducted a mixed methods case study in which we analyze 15 month of changes in use cases in an industrial software project. The study provided interesting observations for both practitioners and researchers involved: First, the most frequently changing use cases had an issue in their structuring. Second, alternative flows (i.e., variations or extensions of the main flow) were especially prone to changes. Third, changes in content (semantic changes) and in presentation of the content (syntactic changes) happen similarly frequently. Last, a qualitative and quantitative analysis aiming at a deeper understanding of problematic changes identified taxonomy changes, as well as locally or temporally dispersed changes as particularly difficult and risky. In this paper, we contribute a first empirical inquiry for understanding the maintainability of use cases: The presented study provides empirical evidence that there are particular maintenance risks and suggests to continuously analyze local and temporal dispersion.

Industry
Collaboration with stakeholders: stakeholder management, creativity, requirements elicitation and negotiation, and crowdsourcing
Large-scale requirements engineering: complex systems, product lines, value chains, software ecosystems, agile and lean practices at scale
Industry and research collaboration: learning from practice, training practitioners, technology transfer
41
R04 An Information Theoretic Approach for Extracting and Tracing Non-functional Requirements
Anas Mahmoud
(Louisiana State University, USA)
Abstract  | Paper

Non-functional requirements (NFRs) are high-level quality constraints that a software system should exhibit. Detecting such constraints early in the process is critical for the stability of software architectural design. However, due to their pervasive nature, and the lack of robust modeling and documentation techniques, NFRs are often overlooked during the requirements elicitation phase. Realizing such constraints at later stages of the development process often leads to architecture erosion and poor traceability. Motivated by these observations, we propose an unsupervised, computationally efficient, and scalable approach for extracting and tracing NFRs in software systems. Based on main assumptions of the cluster hypothesis and information theory, the proposed approach exploits the semantic knowledge embedded in the textual content of requirements specifications to discover, classify, and trace high-level software quality constraints imposed by the system’s functional features. Three experimental systems are used to conduct the experimental analysis in this paper. Results show that the proposed approach can discover software NFRs with an average accuracy of 73%, enabling these NFRs to be traced to their implementations with accuracy levels adequate for practical applications.

Research
Requirements elicitation, analysis, documentation, validation, and verification
Requirements traceability
04
R10 A Requirements Monitoring Model for Systems of Systems
Michael Vierhauser, Rick Rabiser, Paul Grünbacher, and Benedikt Aumayr
(JKU Linz, Austria)
Abstract  | Paper

Many software systems today can be characterized as systems of systems (SoS) comprising interrelated and heterogeneous systems developed by diverse teams over many years. Due to their scale, complexity, and heterogeneity engineers face significant challenges when determining the compliance of SoS with their requirements. Requirements monitoring approaches are a viable solution for checking system properties at runtime. However, existing approaches do not adequately consider the characteristics of SoS: different types of requirements exist at different levels and across different systems; requirements are maintained by different stakeholders; and systems are implemented using diverse technologies. This paper describes a three-dimensional requirements monitoring model (RMM) for SoS providing the following contributions: (i) our approach allows modeling the monitoring scopes of requirements with respect to the SoS architecture; (ii) it employs event models to abstract from different technologies and systems to be monitored; and (iii) it supports instantiating the RMM at runtime depending on the actual SoS configuration. To evaluate the feasibility of our approach we created a RMM for a real-world SoS from the automation software domain. We evaluated the model by instantiating it using an existing monitoring framework and a simulator running parts of this SoS. The results indicate that the model is sufficiently expressive to support monitoring SoS requirements of a directed SoS. It further facilitates diagnosis by discovering violations of requirements across different levels and systems in realistic monitoring scenarios.

Research
Requirements elicitation, analysis, documentation, validation, and verification
Modeling of requirements, goals and domains
Relating requirements to business goals, architecture and testing
Requirements traceability
Domain-specific problems, experiences, and solutions, including new and emerging domains
10
I04 Experience Requirements in Video Games: Definition and Testability
David Callele, Philip Dueck, Krzysztof Wnuk, and Peitsa Hynninen
(Experience First Design, Canada; Blekinge Institute of Technology, Sweden; Aalto University, Finland)
Abstract  | Paper

A properly formed requirement is testable, a necessity for ensuring that design goals are met. While challenging in productivity applications, entertainment applications such as games compound the problem due to their subjective nature. We report here on our efforts to create testable experience requirements, the associated scope challenges and challenges with test design and result interpretation. We further report on issues experienced when performing focus group testing and provide practitioner guidance.

Industry
Requirements engineering for user experience, including ethnography, design, and usability
Creativity, innovation, and requirements engineering
Performance improvement: best practices, measurement, process development
Industry and research collaboration: learning from practice, training practitioners, technology transfer
38
I08 Using the Requirements Specification to Infer the Implicit Test Status of Requirements
Tobias Morciniec and Andreas Podelski
(Daimler, Germany; University of Freiburg, Germany)
Abstract  | Paper

We investigate a method to infer the implicit test status of requirements and thus increase the number of requirements for which the test status is known. The general idea is to improve the data set for measuring the maturity of the system in the current release. The inference is based on the structuring mechanisms (hierarchy, types) which are typically used to document the (natural language) requirements specification. We present a case study in the context of the development process for Mercedes-Benz passenger cars at Daimler AG. The results of the case study indicate the usefulness of the structuring mechanisms in the requirements specification as the basis for the inference. In particular, the number of requirements for which the status is known could be increased by almost a third.

Industry
Collaboration with stakeholders: stakeholder management, creativity, requirements elicitation and negotiation, and crowdsourcing
Large-scale requirements engineering: complex systems, product lines, value chains, software ecosystems, agile and lean practices at scale
Performance improvement: best practices, measurement, process development
42
R07 Selecting Creativity Techniques for Creative Requirements: An Evaluation of Four Techniques using Creativity Workshops
Richard Berntsson Svensson and Maryam Taghavianfar
(Blekinge Institute of Technology, Sweden; Chalmers University of Technology, Sweden)
Abstract  | Paper

Requirements engineering is recognized as a creative process where stakeholders jointly discover new creative ideas for innovative and novel products that eventually are expressed as requirements. This paper evaluates four different creativity techniques, namely Hall of Fame, Constraint Removal, Brainstorming, and Idea Box, using creativity workshops with students and industry practitioners. In total, 34 creativity workshops were conducted with 90 students from two universities, and 86 industrial practitioners from six companies. The results from this study indicate that Brainstorming can generate by far the most ideas, while Hall of Fame generates most creative ideas. Idea Box generates the least number of ideas, and the least number of creative ideas. Finally, Hall of Fame was the technique that led to the most number of requirements that was included in future releases of the products.

Research
Requirements elicitation, analysis, documentation, validation, and verification
Empirical studies, measurements and prediction
07
R19 Sketching and Notation Creation with FlexiSketch Team: Evaluating a New Means for Collaborative Requirements Elicitation
Dustin Wüest, Norbert Seyff, and Martin Glinz
(University of Zurich, Switzerland; University of Applied Sciences and Arts Northwestern Switzerland, Switzerland)
Abstract  | Paper

Whiteboards and paper allow for any kind of notations and are easy to use. Requirements engineers love to use them in creative requirements elicitation and design sessions. However, the resulting diagram sketches cannot be interpreted by software modeling tools. We have developed FlexiSketch as an alternative to whiteboards in previous work. It is a mobile tool for model-based sketching of free-form diagrams that allows the definition and re-use of diagramming notations on the fly. The latest version of the tool, called FlexiSketch Team, supports collaboration with multiple tablets and an electronic whiteboard, such that several users can work simultaneously on the same model sketch. In this paper we present an exploratory study about how novice and experienced engineers sketch and define ad-hoc notations collaboratively in early requirements elicitation sessions when supported by our tool. Results show that participants incrementally build notations by defining language constructs the first time they use them. Participants considered the option to re-use defined constructs to be a big motivational factor for providing type definitions. They found our approach useful for longer sketching sessions and situations where sketches are re-used later on.

Research
Modeling of requirements, goals and domains
Social, cultural, global and cognitive factors in requirements engineering
Tool support for requirements engineering
19
R02 Requirements Engineering: The Quest for the Dependent Variable
Hannes Holm, Teodor Sommestad, and Johan Bengtsson
(Swedish Defence Research Agency, Sweden)
Abstract  | Paper

Requirements engineering is a vibrant and broad research area. It covers a range of activities with different objectives. By reviewing experiments previously included in systematic literature reviews, this paper provides an overview of the dependent variables used in experimental requirements engineering research. This paper also identifies the theoretical motivation for the use of these variables in the experiments. The results show that a wide range of different variables has been applied in experiments and operationalized through both subjective assessments (e.g., subjects’ perceived utility of a technique) and objective measurements (e.g., the number of defects found in a requirements specification). The theoretical basis for these variables and operationalizations are unclear in most cases. Directions for theoretical work to identify suitable dependent variables are provided.

Research
Requirements elicitation, analysis, documentation, validation, and verification
02
I02 Systematic Elicitation of Mode Models for Multifunctional Systems
Andreas Vogelsang, Henning Femmer, and Christian Winkler
(TU München, Germany; MAN Truck & Bus, Germany)
Abstract  | Paper

Many requirements engineering approaches structure and specify requirements based on the notion of modes or system states. The set of all modes is usually considered as the mode model of a system or problem domain. However, it is neither clear how such a mode model can be elicited systematically, nor whether it is realistic to elicit a mode model for a productive system with regard to size and comprehensibility. In this paper, we introduce three elicitation approaches for mode models. We applied the three approaches in an industrial automotive context and assessed the resulting mode models with respect to size, complexity, and differences to each other. Our results show that all elicitation approaches were capable of eliciting modes, which were structured in mode models with 20 to 42 modes. From these results, we conclude that it is possible to elicit manageable mode models for an entire system in a productive context. In our case, the practitioners decided to integrate our model in their feature specification and analysis process.

Industry
Requirements specification: natural language, model-driven approaches, formal techniques
Industry and research collaboration: learning from practice, training practitioners, technology transfer
36
I03 Requirements Problems in the Development of a New User Interface for Healthcare Equipment
Maria Holmegaard, Jens Bæk Jørgensen, Michael Sørensen Loft, and Martin Stig Stissing
(Mjølner Informatics, Denmark)
Abstract  | Paper

In August 2013, our company started work for an industrial customer. First, we developed a prototype and conducted field studies in small-scale projects. This was successful and the basis for a larger project about development of a new user interface for healthcare equipment. A main aim for us was to use this project as starting point for establishing a strategic, long-term relationship with this customer. However, we were not successful. In November 2014, our customer chose to take over the development themselves. We were too expensive, used too many hours and were not able to provide useful estimates, they said. In this paper, we describe the project and analyze causes to our customer’s decision. We also look at possible alternatives to the actions we took in the project and discuss whether we could have done better. A root cause to our customer’s dissatisfaction is related to requirements and handling of requirements.

Industry
Pragmatic requirements engineering: process efficiency, good-enough requirements, agile and lean approaches
Collaboration with stakeholders: stakeholder management, creativity, requirements elicitation and negotiation, and crowdsourcing
Requirements engineering for user experience, including ethnography, design, and usability
37
R13 Forging High-Quality User Stories: Towards a Discipline for Agile Requirements
Garm Lucassen, Fabiano Dalpiaz, Jan Martijn E. M. van der Werf, and Sjaak Brinkkemper
(Utrecht University, Netherlands)
Abstract  | Paper

User stories are a widely used notation for formulating requirements in agile development projects. Despite their popularity in industry, little to no academic work is available on assessing their quality. The few existing approaches are too generic or employ highly qualitative metrics. We propose the Quality User Story Framework, consisting of 14 quality criteria that user story writers should strive to conform to. Additionally, we introduce the conceptual model of a user story, which we rely on to design the AQUSA software tool. AQUSA aids requirements engineers in turning raw user stories into higher-quality ones by exposing defects and deviations from good practice in user stories. We evaluate our work by applying the framework and a prototype implementation to three user story sets from industry.

Research
Requirements in agile, product line and model-driven development
13
I05 Agile Requirements Engineering with Prototyping: A Case Study
Marja Käpyaho and Marjo Kauppinen
(Futurice, Finland; Aalto University, Finland)
Abstract  | Paper

The rise of agile software development methods has led to the abandonment of many traditional practices especially in requirements engineering (RE). Agile RE is still a relatively new research area and the growing use of agile methods in large projects is forcing companies to look for more formal practices for RE. This paper describes experiences gained from a case study of a large agile project. The goal of this case study was to explore how prototyping can solve the challenges of agile RE. Our findings indicate that while prototyping can help with some challenges of agile RE such as lack of documentation, motivation for RE work and poor quality communication, it also needs complementary practices to reach its full potential. These practices include reviewing the big picture regularly, keeping track of quality requirements, and using ATDD (Acceptance Test Driven Development). Key words: prototyping, agile requirements engineering

Industry
Pragmatic requirements engineering: process efficiency, good-enough requirements, agile and lean approaches
Large-scale requirements engineering: complex systems, product lines, value chains, software ecosystems, agile and lean practices at scale
Industry and research collaboration: learning from practice, training practitioners, technology transfer
39
I09 The Need of Complementing Plan-Driven Requirements Engineering with Emerging Communication: Experiences from Volvo Car Group
Ulf Eliasson, Rogardt Heldal, Eric Knauss, and Patrizio Pelliccione
(Volvo, Sweden; Chalmers University of Technology, Sweden)
Abstract  | Paper

The automotive industry is currently going through an enormous change, transitioning from being pure hardware and mechanical companies to becoming more software focused. Currently, software development is embedded into a V-Model process that defines how software requirements are extracted from system requirements. In recent years, OEMs have come to recognize the importance and opportunities offered by software, which include better management and shorter time-to-market of distinguishing features. Strategies to better utilize software include in-house software development and new ways to collaborate with suppliers. However, in their effort to take advantage of these opportunities, engineers struggle with the formal process imposed on software development. In this paper, we investigate the impact of this struggle on the flow of requirements, including challenges and practices. We found that new ways of working with requirements had emerged that are partly not supported, partly hindered by the old tooling and processes for requirements engineering. Requirements flow both vertical and horizontal in the organization and across the supply-chain. Support for the new way of working should allow us to refine requirements iteratively throughout their life-cycle, handle the discussion of rationales, and to manage assumptions. We found strategies of achieving this to differ not only between OEMs, but also between different divisions inside the OEMs.

Industry
Pragmatic requirements engineering: process efficiency, good-enough requirements, agile and lean approaches
Large-scale requirements engineering: complex systems, product lines, value chains, software ecosystems, agile and lean practices at scale
Performance improvement: best practices, measurement, process development
Tools for requirements engineering: requirements modeling, requirements management, social networks
43
R03 Ambiguity as a Resource to Disclose Tacit Knowledge
Alessio Ferrari, Paola Spoletini, and Stefania Gnesi
(ISTI-CNR, Italy; Kennesaw State University, USA)
Abstract  | Paper

Interviews are the most common and effective means to perform requirements elicitation and support knowledge transfer between a customer and a requirements analyst. Ambiguity in communication is often perceived as a major obstacle for knowledge transfer, which could lead to unclear and incomplete requirements documents. In this paper, we analyse the role of ambiguity in requirements elicitation interviews. To this end, we have performed a set of customer-analyst interviews to observe how ambiguity occurs during requirements elicitation. From this direct experience, we have observed that ambiguity is a multi-dimensional cognitive phenomenon with a dominant pragmatic facet, and we have defined a phenomenological framework to describe the different types of ambiguity in interviews. We have also discovered that, rather than an obstacle, the occurrence of an ambiguity is often a resource for discovering tacit knowledge. Starting from this observation, we have envisioned the further steps needed in the research to exploit these findings.

Research
Requirements elicitation, analysis, documentation, validation, and verification
Social, cultural, global and cognitive factors in requirements engineering
03
R05 From Requirements Elicitation to Variability Analysis using Repertory Grid: A Cognitive Approach
Sangeeta Dey and Seok-Won Lee
(Ajou University, South Korea)
Abstract  | Paper

The growing complexity and dynamics of the execution environment have been major motivation for designing self-adaptive systems. Although significant work can be found in the field of formalizing or modeling the requirements of adaptive system, not enough attention has been paid towards the requirements elicitation techniques for the same. It is still an open challenge to elicit the users' requirements in the light of various contexts and introduce the required flexibility in the system's behavior at an early phase of requirements engineering. We explore the idea of using a cognitive technique, repertory grid, to acquire the knowledge of various stakeholders along multiple dimensions of problem space and design space. We aim at discovering the scope of variations in the features of the system by capturing the intentional and technical variability in the problem space and design space respectively. A stepwise methodology for finding the right set of features in the changing context has also been provided in this work. We evaluate the proposed idea by a preliminary case study using smart home system domain.

Research
Requirements elicitation, analysis, documentation, validation, and verification
Social, cultural, global and cognitive factors in requirements engineering
05
R16 Resolving Goal Conflicts via Argumentation-Based Analysis of Competing Hypotheses
Pradeep K. Murukannaiah, Anup K. Kalia, Pankaj R. Telang, and Munindar P. Singh
(North Carolina State University, USA; Cisco Systems, USA)
Abstract  | Paper

A stakeholder’s beliefs influence his or her goals. However, a stakeholder's beliefs may not be consistent with the goals of all stakeholders of a system being constructed. Such belief-goal inconsistencies could manifest themselves as conflicting goals of the system to be. We propose Arg-ACH, a novel approach for capturing inconsistencies between stakeholders' goals and beliefs, and resolving goal conflicts. Arg-ACH employs a hybrid of (1) the analysis of competing hypotheses (ACH), a structured analytic technique, for systematically eliciting stakeholders' goals and beliefs, and (2) rational argumentation for determining belief-goal inconsistencies to resolve conflicts. Arg-ACH treats conflicting goals as hypotheses that compete with each other and the winning hypothesis as a goal of the system to be. Arg-ACH systematically captures the trail of a requirements engineer's thought process in resolving conflicts. We evaluated Arg-ACH via a study in which 20 subjects applied Arg-ACH or ACH to resolve goal conflicts in a sociotechnical system concerning national security. We found that Arg-ACH is superior to ACH with respect to completeness and coverage of belief search; length of belief chaining; ease of use; explicitness of the assumptions made; and repeatability of conclusions across subjects. Not surprisingly, Arg-ACH required more time than ACH: although this is justified by improvements in quality, the gap could be reduced through better tooling.

Research
Requirements management, viewpoints, prioritization and negotiation
Modeling of requirements, goals and domains
Empirical studies, measurements and prediction
16
R08 Feature Lifecycles as They Spread, Migrate, Remain, and Die in App Stores
Federica Sarro, Afnan Al-Subaihin, Mark Harman, Yue Jia, William Martin, and Yuanyuan Zhang
(University College London, UK)
Abstract  | Paper  | Additional information

We introduce a theoretical characterisation of feature lifecycles in app stores, to help app developers to identify trends and to find undiscovered requirements. To illustrate and motivate app feature lifecycle analysis, we use our theory to empirically analyse the migratory and non-migratory behaviours of 4,053 non-free features from two App Stores (Samsung and BlackBerry). The results reveal that, in both stores, intransitive features (those that neither migrate nor die out) exhibit significantly different behaviours with regard to important properties, such as their price. Further correlation analysis also highlights differences between trends relating price, rating, and popularity. Our results indicate that feature lifecycle analysis can yield insights that may also help developers to understand feature behaviours and attribute relationships.

Research
Requirements elicitation, analysis, documentation, validation, and verification
Evolution of requirements over time, product families, variability and reuse
Empirical studies, measurements and prediction
08
R12 Bug Report, Feature Request, or Simply Praise? On Automatically Classifying App Reviews
Walid Maalej and Hadeer Nabil
(University of Hamburg, Germany)
Abstract  | Paper

App stores like Google Play and Apple App Store have over 3 Million apps covering nearly every kind of software and service. Billions of users regularly download, use, and review these apps. Recent studies have shown that reviews written by the users represent a rich source of information for the app vendors and the developers, as they include information about bugs, ideas for new features, or documentation of released features. This paper introduces several probabilistic techniques to classify app reviews into four types: bug reports, feature requests, user experiences, and ratings. For this we use review metadata such as the star rating and the tense, as well as, text classification, natural language processing, and sentiment analysis techniques. We conducted a series of experiments to compare the accuracy of the techniques and compared them with simple string matching. We found that metadata alone results in a poor classification accuracy. When combined with natural language processing, the classification precision got between 70-95% while the recall between 80-90%. Multiple binary classifiers outperformed single multiclass classifiers. Our results impact the design of review analytics tools which help app vendors, developers, and users to deal with the large amount of reviews, filter critical reviews, and assign them to the appropriate stakeholders.

Research
Requirements elicitation, analysis, documentation, validation, and verification
Requirements in service-oriented, virtualization, embedded, cloud and mobile environments
Empirical studies, measurements and prediction
Tool support for requirements engineering
12
R17 Detecting Repurposing and Over-Collection in Multi-party Privacy Requirements Specifications
Travis D. Breaux, Daniel Smullen, and Hanan Hibshi
(Carnegie Mellon University, USA; Carnegie Mellon University, Saudi Arabia)
Abstract  | Paper

Mobile and web applications increasingly leverage service-oriented architectures in which developers integrate third-party services into end user applications. This includes identity management, mapping and navigation, cloud storage, and advertising services, among others. While service reuse reduces development time, it introduces new privacy and security risks due to data repurposing and over-collection as data is shared among multiple parties who lack transparency into third-party data practices. To address this challenge, we propose new techniques based on Description Logic (DL) for modeling multi-party data flow requirements and verifying the purpose specification and collection and use limitation principles, which are prominent privacy properties found in international standards and guidelines. We evaluate our techniques in an empirical case study that examines the data practices of the Waze mobile application and three of their service providers: Facebook Login, Amazon Web Services (a cloud storage provider), and Flurry.com (a popular mobile analytics and advertising platform). The study results include detected conflicts and violations of the principles as well as two patterns for balancing privacy and data use flexibility in requirements specifications. Analysis of automation reasoning over the DL models show that reasoning over complex compositions of multi-party systems is feasible within exponential asymptotic timeframes proportional to the policy size, the number of expressed data, and orthogonal to the number of conflicts found.

Research
Formal analysis and verification
Requirements related to safety, reliability, security, privacy and digital forensics
17
R01 Change Impact Analysis for Natural Language Requirements: An NLP Approach
Chetan Arora, Mehrdad Sabetzadeh, Arda Goknil, Lionel C. Briand, and Frank Zimmer
(University of Luxembourg, Luxembourg; SES TechCom, Luxembourg)
Abstract  | Paper  | Additional information

Requirements are subject to frequent changes as a way to ensure that they reflect the current best understanding of a system, and to respond to factors such as new and evolving needs. Changing one requirement in a requirements specification may warrant further changes to the specification, so that the overall correctness and consistency of the specification can be maintained. A manual analysis of how a change to one requirement impacts other requirements is time-consuming and presents a challenge for large requirements specifications. We propose an approach based on Natural Language Processing (NLP) for analyzing the impact of change in Natural Language (NL) requirements. Our focus on NL requirements is motivated by the prevalent use of these requirements, particularly in industry. Our approach automatically detects and takes into account the phrasal structure of requirements statements. We argue about the importance of capturing the conditions under which change should propagate to enable more accurate change impact analysis. We propose a quantitative measure for calculating how likely a requirements statement is to be impacted by a change under given conditions. We conduct an evaluation of our approach by applying it to 14 change scenarios from two industrial case studies.

Research
Evolution of requirements over time, product families, variability and reuse
Requirements traceability
Empirical studies, measurements and prediction
Industry and research collaboration, interdisciplinary insights, learning from practice, and technology transfer
01
R06 Goal and Preference Identification through Natural Language
Fatima Alabdulkareem, Nick Cercone, and Sotirios Liaskos
(York University, Canada)
Abstract  | Paper

Goal models allow efficient representation of stakeholder goals and alternative ways by which these can be satisfied. Preferences over goals in the goal model are then used to specify criteria for selecting alternatives that fit specific contexts, situations and strategies. Given such preferences, automated reasoning tools allow for efficient exploration of such alternatives. Nevertheless, to be amenable to such automated processing, goals and preferences need to be specified in a formal language, making automated processing inaccessible to the very bearers of goals and preferences, i.e., the stakeholders. We combine natural language processing techniques to allow specification of preferences through natural language statements. The natural language statement is first matched through regular expressions to distinguish between the preference component and the goal component. The former is then mapped to a preferential strength measure, while the latter is used to identify the relevant goal in the goal model through statistical semantic similarity techniques. The result constitutes a formal representation that can be used for alternatives analysis. In this way, stakeholders can access advanced goal reasoning techniques through simple natural language preference expressions, facilitating their decision making in various requirements analysis contexts. An experimental evaluation with human participants shows that the proposed system is of substantial precision and that a mapping from natural preferential verbalizations to predefined preferential strength labels is possible through sampling from crowds.

Research
Requirements elicitation, analysis, documentation, validation, and verification
Requirements specification languages, methods, processes and tools
06
I06 The Myth of Bad Passive Voice and Weak Words: An Empirical Investigation in the Automotive Industry
Jennifer Krisch and Frank Houdek
(Daimler, Germany)
Abstract  | Paper

In requirements engineering literature dealing with natural language specifications, we usually find writing rules like avoid passive voice or do not use weak words. Adhering to such rules should result in understandable and unambiguous requirements. Passive voice, especially when used without an explicit actor, is considered to result in incomplete requirements. The usage of weak words is considered to result in imprecise requirements that are hardly testable. But is the inversion of the claim correct, i.e. does the violation of the writing rules result in problematic specifications? At least in our environment (the passenger car development of Mercedes-Benz) we observe that authors often use passive voice, and there are many requirements containing weak words. To answer this question, we conducted an empirical investigation whose results we report in this paper. The results of this investigation are quite surprising: The use of passive voice, even when the actor is missing, is almost never problematic, as the missing information (the actor) can in most cases easily derived from the context (i.e. surrounding requirements or the general project context). The usage of weak words may be considered problematic in approximately 12% of all occurrences. For an automatic analysis on weak words linguistic patterns can be defined to detect these problematic occurrences.

Industry
Requirements specification: natural language, model-driven approaches, formal techniques
40
R09 What You Ask Is What You Get: Understanding Architecturally Significant Functional Requirements
Preethu Rose Anish, Maya Daneva, Jane Cleland-Huang, Roel J. Wieringa, and Smita Ghaisas
(Tata Consultancy Services, India; University of Twente, Netherlands; DePaul University, USA)
Abstract  | Paper

Software architects are responsible for designing an architectural solution that satisfies the functional and non-functional requirements of the system to the fullest extent possible. However, the details they need to make informed architectural decisions are often missing from the requirements specification. An earlier study we conducted indicated that architects intuitively recognize architecturally significant requirements in a project, and often seek out relevant stakeholders in order to ask Probing Questions (PQs) that help them acquire the information they need. This paper presents results from a qualitative interview study aimed at identifying architecturally significant functional requirements’ categories from various business domains, exploring relevant PQs for each category, and then grouping PQs by type. Using inter-view data from 14 software architects in three countries, we identified 15 categories of architecturally significant functional requirements and 6 types of PQs. We found that the domain knowledge of the architect and her experience influence the choice of PQs significantly. A preliminary quantitative evaluation of the results against real-life software requirements specification documents indicated that software specifications in our sample largely do not contain the crucial architectural differentiators that may impact architectural choices and that PQs are a necessary mechanism to unearth them. Further, our findings provide the initial list of PQs which could be used to prompt business analysts to elicit architecturally significant functional requirements that the architects need.

Research
Requirements elicitation, analysis, documentation, validation, and verification
Relating requirements to business goals, architecture and testing
Empirical studies, measurements and prediction
Industry and research collaboration, interdisciplinary insights, learning from practice, and technology transfer
09
I01 Reuse of Architecturally Derived Standards Requirements
Michael C. Panis
(Teradyne, USA)
Abstract  | Paper

Requirements reuse promises to reduce product development cost and improve product quality. Applying a standard set of requirements to multiple products configured into the same system can ensure all the products take advantage of the system’s architectural features and do not adversely interact with each other. While existing literature provides guidance for developing requirements suitable for reuse, little has been written on the practical realities an organization faces in attempting to reuse requirements. This paper addresses that gap by describing a commercial engineering company’s deployment of a requirements reuse process, the problems encountered, the results obtained, and the plans for future improvement of the process.

Industry
Performance improvement: best practices, measurement, process development
Tools for requirements engineering: requirements modeling, requirements management, social networks
35
N09 Inherent Characteristics of Traceability Artifacts: Less is More
Jane Huffman Hayes, Giuliano Antoniol, Bram Adams, and Yann-Gaël Guéhéneuc
(University of Kentucky, USA; Polytechnique Montréal, Canada)
Abstract  | Paper

This paper describes ongoing work to characterize the inherent ease with which a textual artifact pair can be traced using an automated technique. Software traceability approaches collect varied measures to build models that automatically recover links between pairs of natural language documents. Thus far, most of the approaches use a single-step model, such as logistic regression, to identify new traceability links; however, true traceability links are by far in the minority of what is retrieved for a typical artifact pair and this reduces the performance of such models. Instead, this paper formulates the problem of traceability links as the problem of finding, for a given logistic regression model (first step), the subsets of links in the training set giving the best accuracy (in terms of G-metric) on the test set (second step). Using hill climbing with random restart for subset selection, we found that for the ChangeStyle dataset, we can classify links with a precision up to about 83% and a recall up to about 42% using a training set as small as nine true candidate links (27%) and 136 false links (out of 503 wrong links). In order to get better performance and learn the best possible logistic regression classifier, we must “discard” elements in the trace dataset that increase noise and avoid learning on links that are not representative. This is preliminary work, but has promise as it shows that few correct examples may perform better than several poor examples. Keywords: traceability, machine learning, model, logistic regression

RE:Next!
Requirements traceability
28
N11 Trace Links Explained: An Automated Approach for Generating Rationales
Jin Guo, Natawut Monaikul, and Jane Cleland-Huang
(DePaul University, USA)
Abstract  | Paper

Software Traceability is a critical element in all safety critical software systems. Trace links are created across diverse artifacts such as requirements, design, code, test cases, and hazards -- either manually or with the help of supporting tools. The links are then used to support a range of software engineering activities including impact analysis, compliance verification, and safety inspections. For traceability to effectively support these activities it is important for the meaning and rationale of each link to be clearly communicated. It is often insufficient to know that one artifact satisfies, realizes, or complies to another. Instead, it is important to know why and how it does so. Terms and phrases used to describe artifacts are connected through composition, synonymic, and generalization relationships which often can only be interpreted by domain experts. In this RE:Next! paper we propose a novel approach for utilizing domain-specific knowledge bases to generate trace link rationales. We illustrate our approach with examples of automatically generated rationales taken from the domain of Communication and Control of a Transportation system, and from a Medical Infusion pump domain.

RE:Next!
Requirements traceability
30
N02 Handling Non-functional Requirements in Model-Driven Development: An Ongoing Industrial Survey
David Ameller, Xavier Franch, Cristina Gómez, João Araujo, Richard Berntsson Svensson, Stefan Biffl, Jordi Cabot, Vittorio Cortellessa, Maya Daneva, Daniel Méndez Fernández, Ana Moreira, Henry Muccini, Antonio Vallecillo, Manuel Wimmer, Vasco Amaral, Hugo Brunelière, Loli Burgueño, Miguel Goulão, Bernhard Schätz, and Sabine Teufl
(Universitat Politècnica de Catalunya, Spain; Universidade Nova de Lisboa, Portugal; Blekinge Institute of Technology, Sweden; Vienna University of Technology, Austria; Open University of Catalonia, Spain; University of L'Aquila, Italy; University of Twente, Netherlands; TU München, Germany; University of Málaga, Spain; AtlanMod Team, France; Fortiss, Germany)
Abstract  | Paper

Model-Driven Development (MDD) is no longer a novel development paradigm. It has become mature from a research perspective and recent studies show its adoption in industry. Still, some issues remain a challenge. Among them, we are interested in the treatment of non-functional requirements (NFRs) in MDD processes. Very few MDD approaches have been reported to deal with NFRs (and they do it in a limited way). However, it is clear that NFRs need to be considered somehow in the final product of the MDD process. To better understand how NFRs are integrated into the existing MDD approaches, we have initiated the NFR4MDD project, a multi-national empirical study, based on interviews with companies working on MDD projects. Our project aims at surveying the state of the practice for this topic. In this paper, we summarize our research protocol and present the current status of our study. The discussion will focus on the peculiarities of our study's context and organization involving about 20 researchers from 8 European countries.

RE:Next!
Requirements in agile, product line and model-driven development
Empirical studies, measurements and prediction
21
N03 Scalable Modeling and Analysis of Requirements Preferences: A Qualitative Approach using CI-Nets
Zachary J. Oster, Ganesh Ram Santhanam, and Samik Basu
(University of Wisconsin-Whitewater, USA; Iowa State University, USA)
Abstract  | Paper

We present a framework for reasoning with preferences in the context of Goal-Oriented Requirements Engineering (GORE). Our choice of preference language, conditional importance networks (CI-nets), is motivated by the occurrence in requirements engineering of qualitative preferences and tradeoffs involving sets of items; such preferences are expressed more naturally in CI-nets than in other representations. Building on our past experience with CI-nets, we are improving the scalability and usability of CI-nets for specifying and analyzing requirements preferences. We discuss our ongoing work and long-term plans, including efforts to develop more efficient methods to identify conflicting preferences among possible requirements, guide negotiation of resolutions to such conflicts, and improve traceability and comprehension of requirements preferences.

RE:Next!
Requirements management, viewpoints, prioritization and negotiation
Requirements specification languages, methods, processes and tools
Formal analysis and verification
22
N14 Rationalization of Goal Models in GRL using Formal Argumentation
Marc van Zee, Floris Bex, and Sepideh Ghanavati
(University of Luxembourg, Luxembourg; Utrecht University, Netherlands; Carnegie Mellon University, Luxembourg)
Abstract  | Paper

We apply an existing formal framework for practical reasoning with arguments and evidence to the Goal-oriented Requirements Language (GRL), which is part of the User Requirements Notation (URN). This formal framework serves as a rationalization for elements in a GRL model: using attack relations between arguments we can automatically compute the acceptability status of elements in a GRL model, based on the acceptability status of their underlying arguments and the evidence. We integrate the formal framework into the GRL metamodel and we set out a research to further develop this framework.

RE:Next!
Modeling of requirements, goals and domains
Formal analysis and verification
Requirements traceability
33
N04 Cognitive Factors in Inconsistency Management
Irit Hadar and Anna Zamansky
(University of Haifa, Israel)
Abstract  | Paper

Inconsistency is a major challenge in requirements engineering, commonly perceived as a problem that needs to be eliminated on sight. However, in practice maintaining consistency at all times is an intractable problem. Accordingly, recent paradigms for inconsistency management acknowledge that it is sometimes desirable to tolerate inconsistency, e.g. to allow distributed teamwork and prevent premature commitment to design decisions. However, a successful adoption of inconsistency management paradigms in industry highly depends on the human factor: intolerant attitudes of practitioners toward inconsistency may pose significant barriers to a wider acceptance of these paradigms. Thus, a thorough analysis of cognitive factors is a key to overcoming these barriers. In this paper we report on our preliminary empirical findings highlighting existing perceptions and attitudes of practitioners toward inconsistency, and propose dimensions for their classification. Based on these results, we outline a general research program for exploring cognitive factors in inconsistency management.

RE:Next!
Requirements management, viewpoints, prioritization and negotiation
Requirements specification languages, methods, processes and tools
Social, cultural, global and cognitive factors in requirements engineering
23
N12 Using Real Options to Manage Technical Debt in Requirements Engineering
Zahra Shakeri Hossein Abad and Guenther Ruhe
(University of Calgary, Canada)
Abstract  | Paper

Abstract- Despite the importance of Requirements Engineering (RE) for the success of software products, most of the requirements decisions such as requirements specification and prioritization are still ad hoc and depend upon the managers' preferences and the trade-offs they make. The Technical Debt (TD) metaphor looks into the trade-offs between short term and long-term goals in software development projects that may lead to increased cost in the future. This problem is mainly due to the lack of a systematic and well-defined approach to manage the high level of uncertainty in requirements decisions. In this paper, we propose to apply the real options thinking to develop a quantitative method for managing requirements decisions under uncertainty and, more specifically for managing requirements debt in software development projects. A real option is a right without an obligation to make a specific future decision depending on how uncertainty resolves. We demonstrate the application of real options in the context of requirements debt valuation by using the binomial model combined with dynamic programming. We provide an illustrative example to show how uncertainty creates option value and influences requirements decisions and finally outline a future research agenda.

RE:Next!
Requirements management, viewpoints, prioritization and negotiation
Evolution of requirements over time, product families, variability and reuse
Relating requirements to business goals, architecture and testing
Domain-specific problems, experiences, and solutions, including new and emerging domains
31
N15 QuantUn: Quantification of Uncertainty for the Reassessment of Requirements
Nelly Bencomo
(Aston University, UK)
Abstract  | Paper

Self-adaptive systems (SASs) should be able to adapt to new environmental contexts dynamically. The uncertainty that demands this runtime self-adaptive capability makes it hard to formulate, validate and manage their requirements. QuantUn is part of our longer-term vision of requirements reflection, that is, the ability of a system to dynamically observe and reason about its own requirements. QuantUn's contribution to the achievement of this vision is the development of novel techniques to explicitly quantify uncertainty to support dynamic re-assessment of requirements and therefore improve decision-making for self-adaption. This short paper discusses the research gap we want to fill, present partial results and also the plan we propose to fill the gap.

RE:Next!
Evolution of requirements over time, product families, variability and reuse
Relating requirements to business goals, architecture and testing
34
N01 Towards Reuse in Safety Risk Analysis Based on Product Line Requirements
Hermann Kaindl, Roman Popp, and David Raneburger
(Vienna University of Technology, Austria)
Abstract  | Paper

Risk analysis and requirements engineering for safety-critical systems are expensive and challenging, especially for the very high reliability required, e.g., in the automotive and railway industries. Currently, risk analysis is performed by safety engineers with little or no explicit reuse. Of course, these engineers build on their previous experience in this course, but explicit reuse of related artefacts, e.g., from a dedicated repository is not available according to our best knowledge. The key idea of our approach is reuse in risk analysis based on development and look-up of a repository built around product line requirements. We propose explicit reuse of related artefacts from previous risk analyses, such as information on failures, hazards and safety-related risks. Our assumption is that the risk analysis of a new product of the product line can utilize this information from similar existing products, if available. Therefore, we plan to build a repository of such artefacts and to facilitate its look-up in the course of doing risk analysis. Our innovative approach to extend product-line technology has the expected result of substantially less expensive development of safety-critical systems and shorter time-to-market in such domains through reuse of existing risk-analysis artefacts.

RE:Next!
Requirements related to safety, reliability, security, privacy and digital forensics
Requirements in agile, product line and model-driven development
20
N07 An Environment-Driven Ontological Approach to Requirements Elicitation for Safety-Critical Systems
Jiale Zhou, Kaj Hänninen, Kristina Lundqvist, Yue Lu, Luciana Provenzano, and Kristina Forsberg
(Mälardalen University, Sweden; Bombardier Transportation, Sweden; Saab, Sweden)
Abstract  | Paper

The environment, where a safety critical system (SCS) operates, is an important source from which safety requirements of the SCS can originate. By treating the system under construction as a black box, the environment is typically documented as a number of assumptions, based on which a set of environmental safety requirements will be elicited. However, it is not a trivial task in practice to capture the environmental assumptions to elicit safety requirements. The lack of certain assumptions or too strict assumptions will either result in incomplete environmental safety requirements or waste many efforts on eliciting incorrect requirements. Moreover, the variety of operating environment for an SCS will further complicate the task, since the captured assumptions are at risk of invalidity, and consequently the elicited requirements need to be revisited to ensure safety has not been compromised by the change. This short paper presents an on-going work aiming to 1) systematically organize the knowledge of system operating environment and, 2) facilitate the elicitation of environmental safety requirements. We propose an ontological approach to achieve the objectives. In particular, we utilize conceptual ontologies to organize the environment knowledge in terms of relevant environment concepts, relations among them and axioms. Environmental assumptions are captured by instantiating the environment ontology. An ontological reasoning mechanism is also provided to support elicitation of safety requirements from the captured assumptions.

RE:Next!
Requirements elicitation, analysis, documentation, validation, and verification
26
N08 Goals at Risk? Machine Learning at Support of Early Assessment
Paolo Avesani, Anna Perini, Alberto Siena, and Angelo Susi
(Fondazione Bruno Kessler, Italy)
Abstract  | Paper

A relevant activity in the requirements engineering process consists in the identification, assessment and management of potential risks, which can prevent the system-to-be from meeting stakeholder needs. However, risk analysis techniques are often time- and resource- consuming activities, which may introduce in the requirements engineering process a significant overhead. To overcome this problem, we aim at supporting risk management activity in a semi-automated way, merging the capability to exploit existing risk-related information potentially present in a given organisation, with an automated ranking of the goals with respect to the level of risk the decision-maker estimates for them. In particular, this paper proposes an approach to address the general problem of risk decision-making, which combines knowledge about risks assessment techniques and Machine Learning to enable an active intervention of human evaluators in the decision process, learning from their feedback and integrating it with the organisational knowledge. The long term objective is that of improving the capacity of an organisation to be aware and to manage risks, by introducing new techniques in the field of risk management that are able to interactively and continuously extract useful knowledge from the organisation domain and from the decision-maker expertise.

RE:Next!
Requirements management, viewpoints, prioritization and negotiation
27
N06 Democratic Mass Participation of Users in Requirements Engineering?
Timo Johann and Walid Maalej
(University of Hamburg, Germany)
Abstract  | Paper

A large part of Requirements Engineering is concerned with involving system users, capturing their needs, and getting their feedback. As users are becoming more and more demanding, markets and technologies are evolving fast, and systems are getting more and more individual, a broad and systematic user involvement in Requirements Engineering is becoming more important than ever. This paper presents the idea of pushing user involvement in Requirements Engineering to its extreme by systematically delegating the responsibility for developing the requirements and deciding about future releases to the crowd of users. We summarize the pros and cons of this vision, its main challenges, and sketch promising solution concepts, which have been proposed and used in E-Participation and E-Democracy. We discussed our vision with ten experts from the fields of Requirements Engineering, politics, psychology, and market research, who were partly supportive partly skeptical.

RE:Next!
Requirements elicitation, analysis, documentation, validation, and verification
Requirements management, viewpoints, prioritization and negotiation
Social, cultural, global and cognitive factors in requirements engineering
25
N13 Exploiting Online Human Knowledge in Requirements Engineering
Anas Mahmoud and Doris Carver
(Louisiana State University, USA)
Abstract  | Paper

Data-driven Natural Language Processing (NLP) methods have noticeably advanced in the past few years. These advances can be tied to the drastic growth of the quality of collaborative knowledge bases (KB) available on the World Wide Web. Such KBs contain vast amounts of up-to-date structured human knowledge and common sense data that can be exploited by NLP methods to discover otherwise-unseen semantic dimensions in text, aiding in tasks related to natural language understanding, classification, and retrieval. Motivated by these observations, we describe our research agenda for exploiting online human knowledge in Requirements Engineering (RE). The underlying assumption is that requirements are a product of the human domain knowledge that is expressed mainly in natural language. In particular, our research is focused on methods that exploit the online encyclopedia Wikipedia as a textual corpus. Wikipedia provides access to a massive number of real-world concepts organized in hierarchical semantic structures. Such knowledge can be analyzed to provide automated support for several exhaustive RE activities including requirements elicitation, understanding, modeling, traceability, and reuse, across multiple application domains. This paper describes our preliminary findings in this domain, current state of research, and prospects of our future work.

RE:Next!
Requirements elicitation, analysis, documentation, validation, and verification
Modeling of requirements, goals and domains
Requirements traceability
Empirical studies, measurements and prediction
Tool support for requirements engineering
32
N05 Towards Engineering Transparency as a Requirement in Socio-technical Systems
Mahmood Hosseini, Alimohammad Shahri, Keith Phalp, and Raian Ali
(Bournemouth University, UK)
Abstract  | Paper

The improvement and success of socio-technical systems depend on the joint optimisation of both the social and the technical parts. Improving the social part of a socio-technical system is a meticulous task, as social requirements are diverse and dynamic, and they usually evolve with time and context. Information transparency (henceforth, transparency) is one of the social requirements that can affect the overall attitude of the stakeholders present within a socio-technical system, and influence their other social requirements such as privacy, trust, collaboration and non-bias. In this paper, we advocate the need to engineer transparency as a first class requirement, propose a baseline model for transparency and show how this model can be a starting point for the analysis of transparency requirements of different stakeholders. We showcase our on-going research in the modelling and analysis of transparency as a requirement, discuss some of the challenges of transparency requirements elicitation, and present our future work.

RE:Next!
Requirements management, viewpoints, prioritization and negotiation
Modeling of requirements, goals and domains
Relating requirements to business goals, architecture and testing
24
N10 Towards a General Formal Framework of Coherence Management in RE
Alexander Borgida, Ivan Jureta, and Anna Zamansky
(Rutgers University, USA; University of Namur, Belgium; University of Haifa, Israel)
Abstract  | Paper

Coherence Management refers to all efforts one needs to invest, in order to ensure that information shown in, and implied by a representation of requirements makes sense as a whole, is coherent. Coherence Management is an umbrella term we use to cover, and more importantly, stimulate research on relationships between identification, measurement, and action on phenomena which reflect tensions between information in requirements representations. Such tensions exist between information which is, for example, logically inconsistent, or stakeholders disagree on, or signals tradeoffs (meaning that improvement on some requirements, for instance, necessarily means some quantifiable (or not) deterioration of others). These tensions are an important topic of research in Requirements Engineering, and various methods have been proposed for the identification, measurement, and action on logical inconsistency in requirements models, on negotiating disagreements, and on settling tradeoffs. Despite focusing on related phenomena, these methods are different and each come with their own specific definition of when a representation of requirements is incoherent and what to do about it. This makes it hard to compare existing methods, design new ones, and choose those to apply when doing RE. In this short communication we outline our research agenda for developing a unified formal framework for the systematization and classification of Coherence Management efforts in the context of RE, as well as exploring their compatibility.

RE:Next!
Requirements management, viewpoints, prioritization and negotiation
Requirements specification languages, methods, processes and tools
Modeling of requirements, goals and domains
Evolution of requirements over time, product families, variability and reuse
Formal analysis and verification
Requirements in agile, product line and model-driven development
29

Organizers

Program Co-Chair

Didar Zowghi
University of Technology, Sydney, Australia

Program Co-Chair

Vincenzo Gervasi
University of Pisa, Italy

Industry Track Co-Chair

Sarah C. Gregory
Intel Corporation, USA

Industry Track Co-Chair

Richard Berntsson Svensson
Blekinge Institute of Technology, Sweden