This volume compiles the papers accepted for presentation at the 16thWorking C- ference on Requirements Engineering: Foundation for Software Quality (REFSQ 2010), held in Essen during June 30 and July 1-2, 2010. Since 1994, when the first REFSQ took place, requirements engineering (RE) has never ceased to be a dominant factor influencing the quality of software, systems and services. Initially started as a workshop, the REFSQ working conference series has now established itself as one of the leading international forums to discuss RE in its (many) relations to quality. It seeks reports of novel ideas and techniques that enhance the quality of RE products and processes, as well as reflections on current research and industrial RE practices. One of the most appreciated characteristics of REFSQ is that of being a highly interactive and structured event. REFSQ 2010 was no exception to this tradition. In all, we received a healthy 57 submissions. After all submissions had been ca- fully assessed by three independent reviewers and went through electronic disc- sions, the Program Committee met and finally selected 15 top-quality full papers (13 research papers and 2 experience reports) and 7 short papers, resulting in an acc- tance rate of 38 %. The work presented at REFSQ 2009 continues to have a strong anchoring in pr- tice with empirical investigations spanning over a wide range of application domains.
Author(s): Ian Alexander (auth.), Roel Wieringa, Anne Persson (eds.)
Series: Lecture Notes in Computer Science 6182 : Programming and Software Engineering
Edition: 1
Publisher: Springer-Verlag Berlin Heidelberg
Year: 2010
Language: English
Pages: 280
Tags: Software Engineering; Computer Communication Networks; Information Systems Applications (incl.Internet); Management of Computing and Information Systems; Computers and Society; Programming Languages, Compilers, Interpreters
Front Matter....Pages -
Keynote Talk Piecing Together the Requirements Jigsaw-Puzzle....Pages 1-1
Understanding the Scope of Uncertainty in Dynamically Adaptive Systems....Pages 2-16
Use of Personal Values in Requirements Engineering – A Research Preview....Pages 17-22
Requirements and Systems Architecture Interaction in a Prototypical Project: Emerging Results....Pages 23-29
Videos vs. Use Cases: Can Videos Capture More Requirements under Time Pressure?....Pages 30-44
Supporting the Consistent Specification of Scenarios across Multiple Abstraction Levels....Pages 45-59
Requirements Value Chains: Stakeholder Management and Requirements Engineering in Software Ecosystems....Pages 60-66
Binary Priority List for Prioritizing Software Requirements....Pages 67-78
Towards a Framework for Specifying Software Robustness Requirements Based on Patterns....Pages 79-84
A Metamodel for Software Requirement Patterns....Pages 85-90
Validation of the Effectiveness of an Optimized EPMcreate as an Aid for Creative Requirements Elicitation....Pages 91-105
Towards Multi-view Feature-Based Configuration....Pages 106-112
Evaluation of a Method for Proactively Managing the Evolving Scope of a Software Product Line....Pages 113-127
Challenges in Aligning Requirements Engineering and Verification in a Large-Scale Industrial Context....Pages 128-142
On the Perception of Software Quality Requirements during the Project Lifecycle....Pages 143-157
Lessons Learned from Integrating Specification Templates, Collaborative Workshops, and Peer Reviews....Pages 158-172
A Case Study on Tool-Supported Multi-level Requirements Management in Complex Product Families....Pages 173-187
A Domain Ontology Building Process for Guiding Requirements Elicitation....Pages 188-202
Tackling Semi-automatic Trace Recovery for Large Specifications....Pages 203-217
Ambiguity Detection: Towards a Tool Explaining Ambiguity Sources....Pages 218-232
Ambiguity in Natural Language Software Requirements: A Case Study....Pages 233-247
On the Role of Ambiguity in RE....Pages 248-254
Towards a Framework to Elicit and Manage Security and Privacy Requirements from Laws and Regulations....Pages 255-261
Visualizing Cyber Attacks with Misuse Case Maps....Pages 262-275
How Do Software Architects Consider Non-Functional Requirements: A Survey....Pages 276-277
Back Matter....Pages -
