Accepted Papers
Last update: 2013-Jul-09
(University of Electro-Communications, Japan; National Institute of Informatics, Japan)
We propose an elaboration process for goal modeling that extracts control loops as highly independent modules, which localize changes in software evolution.
(DePaul University, USA; Siemens, USA)
This paper explores how to integrate expert systems into the automated tracing process; it attempts to address the terminology-mismatch problem faced by conventional trace retrieval techniques.
(University of Waterloo, Canada)
We propose a pattern for modelling feature requirements and an interface to features, which together may ease the readability and writability of feature requirements.
(University of Lancaster, UK)
Reviews Requirements Elicitation techniques and tools, proposes road map for future research towards 'Unknown' requirements in brown/green field domains.
(Politecnico di Milano, Italy; Universita dell'Insubria, Italy) VIDEO
Don't wait until the end: verify your incomplete models!
(SEI, USA)
This paper traces the history of the RE conference from its inception through the present, with insights from key players, and discussion of future directions.
(University of Southern California, USA)
We assist the decomposition of system-level requirements to models of individual components via requirements-driven heuristics that overcome the incompleteness proven to be induced by direct decomposition.
(University of Kentucky, USA)
Unstructured artifact tracing is improved by using reinforcement learning techniques, examining the context of words as opposed to treating artifacts as a "bag of words".
(CMU, USA)
Determining legal coverage from IT regulations isn't easy: we'll show you how (and how it fits in the big picture).
(North Carolina State University, USA; Georgia Tech, USA)
In our paper, we examine the ability of software practitioners to understand regulatory requirements, and discover that they need a lot of help in writing compliant software.
(ISCAS, China; UCAS, China)
A novel solution helps to downsize the workload of requirements volatility analysis by recommending a converging subset of change-prone requirements based on regression analysis.
(City University London, UK)
Every year a stampede of models passes through RE, and every year this herd is composed differently, defying proper classification but demanding some direction.
(University of Twente, Netherlands)
We propose a method to identify potential risks of using a dynamic service provisioning approach due to incomplete assumptions made, by the application programmer or by independent service providers, on component services.
(University of Zurich, Switzerland)
Cloud providers elicit consumer requirements differently from what you may think - We know how and why.
(Georgia Tech, USA; Ohio State University, USA)
Can requirements engineers use text mining to examine challenging-to-read policy documents for requirements artifacts on an industry-wide scale?
(TU Munich, Germany; University of Hamburg, Germany)
An exploratory study of the content and impact of feedback written by App users in Apple AppStore, with resulting insights into crowdsourcing requirements.
(University of Ottawa, Canada; McGill University, Canada)
Let's discuss arguments for our requirements/software engineering vision focusing on coordinated composition of generic, reusable, not-product-specific artifacts across the whole software development lifecycle!
(CMU, USA)
In a complex application ecosystem with multiple privacy policies and stakeholders, we enable identification of conflicting data privacy requirements, and data repurposing.
(ISCAS, China; UCAS, China; University of East London, UK)
Empirically investigate how requirements dependencies correlate with and predict software integration bugs, which can provide early estimate regarding software quality.
(Mississippi State University, USA)
Back to Nature: Restoring Lost Traceability Tracks through Refactoring.
(UC Irvine, USA)
Open source software development doesn't use classical requirements artifacts and processes, yet it works - what does it use instead, and how?
(Mississippi State University, USA)
Find out how visual requirements analytics helps create an efficient path from data to decision.
(TU Ilmenau, Germany)
Practitioners rarely follow explicit traceability strategies. But they should, because we revealed severe traceability problems in all 17 studied software projects that strategizing could avoid.
(University of Luxembourg, Luxembourg; University of Namur, Belgium; Ozemantics, Australia)
Want an effective visual notation? Don't let the experts do it, ask the users!
(Simula Research Laboratory, Norway)
Traceability research @ RE is on track !! But, does it meet our needs yet?
(Makerere University, Uganda; Uganda Police Force, Uganda)
This paper presents the experiences (techniques used & lessons learnt) of the authors in developing requirements for the Uganda Police Force Crime Records Management System
(University of Twente, Netherlands; IRCCCS Fondazione Salvarore Maugeri, Italy)
Requirements elicitation using scenarios, with engineering and domain concerns separation joined by a common discourse handshake, and application of model-based techniques to compensate missing primary stakeholders
(Intel, USA)
This paper will demonstrate the impact that well-written, well-reviewed requirements had on software quality across three product generations
(City of Munich, Germany)
Face the tough requirements reviews challenges and face open research questions that really bother the software industry
(Tata Consultancy Services, India)
An approach to identify inconsistencies in requirements and Compute Requirement consistency index (RCI) for overall requirements to provide a quantifiable measure on requirement quality
(University of Innsbruck, Austria; QE LaB Business Services, Austria; Beer Test Consulting, Austria)
This work shows how defect taxonomies are seamlessly integrated into the RE process and successfully applied for requirements reviewing and testing
(Simula Research Laboratory, Norway; University of Oslo, Norway)
We discuss potentials and limitations of existing requirement-based test generation techniques in automating the reuse of test artifacts in product lines of cyber-physical systems
(University of Waterloo, Canada)
Does seeding an industrial requirements idea brainstorming session with application-domain ignorant non-employees improve brainstorming effectiveness over brainstorming with only domain-aware employees?
(NTT DATA, Japan; Nanzan University, Japan)
We has been practiced "Requirements Clinic" for improving the quality of SRS for 2 years. It demonstrated 10.6 ROI for 12 projects
(Accenture Technology Labs, India)
A tool to automatically identify Domain Concepts in a Requirements Document thus promoting consistent interpretation among stakeholders and assisting automated forward engineering
(EPFL, Switzerland; Credit Suisse, Switzerland)
Reporting on a Requirements Engineering Project at the Intersection of Academia and Industry
(TU Munich, Germany; BMW, Germany)
Feature dependencies in a real automotive system: Numerous, pervasive, implicit, and in many cases unknown to developers
(Danfoss Power Electronics, Denmark; DTU, Denmark; Glasgow Caledonian University, UK)
We'll describe real projects that show when design information is viable in requirements specifications and when it should be avoided
(RWTH Aachen University, Germany)
(Politecnico di Milano, Italy; Cefriel, Italy; Lero, Ireland; University of Limerick, Ireland)
(DePaul University, United States; University of Kentucky, United States)
(LAAS-CNRS, France; University of Toulouse, France; SUPELEC, France)
(Universitat Politècnica de Catalunya, Spain)
(Fortiss, Germany)
(TU Munich, Germany; Siemens, USA)
(Lero, Ireland; Open University, UK)
(CMU, USA)
(Simula Research Laboratory, Norway)
(Mississippi State University, United States)
(Universidade Federal de Pernambuco (UFPE), Brasil)
Icons adapted from http://www.fatcow.com/free-icons.