Table of Contents

• Characteristics of New Requirements in the Presence or Absence of an Existing System ArchitectureJames A. Miller, Remo Ferrari, Nazim H. Madhavji. 5-14 [doi]
• Practical Challenges for Methods Transforming i* Goal Models into Business Process ModelsKen Decreus, Monique Snoeck, Geert Poels. 15-23 [doi]
• Intellectual Property Rights Requirements for Heterogeneously-Licensed SystemsThomas A. Alspaugh, Hazeline U. Asuncion, Walt Scacchi. 24-33 [doi]
• Enhancing Stakeholder Profiles to Improve Recommendations in Online Requirements ElicitationCarlos Castro-Herrera, Jane Cleland-Huang, Bamshad Mobasher. 37-46 [doi]
• EPC vs. UML Activity Diagram - Two Experiments Examining their Usefulness for Requirements EngineeringAnne Gross, Jörg Dörr. 47-56 [doi]
• Analysis of Multi-Party Agreement in Requirements ValidationIvan Jureta, John Mylopoulos, Stéphane Faulkner. 57-66 [doi]
• Reasoning on Non-Functional Requirements for Integrated ServicesCarlo Ghezzi, Giordano Tamburrelli. 69-78 [doi]
• RELAX: Incorporating Uncertainty into the Specification of Self-Adaptive SystemsJon Whittle, Peter Sawyer, Nelly Bencomo, Betty H. C. Cheng, Jean-Michel Bruel. 79-88 [doi]
• What Happened to Our Features? Visualization and Understanding of Scope Change Dynamics in a Large-Scale Industrial SettingKrzysztof Wnuk, Björn Regnell, Lena Karlsson. 89-98 [doi]
• Developing Production Rule Models to Aid in Acquiring Requirements from Legal TextsJeremy C. Maxwell, Annie I. Antón. 101-110 [doi]
• Forensic System VerificationRobert J. Hall. 111-120 [doi]
• A Use Case Based Approach to Feature Models ConstructionBo Wang, Wei Zhang, Haiyan Zhao, Zhi Jin, Hong Mei. 121-130 [doi]
• Compliance Analysis Based on a Goal-oriented Requirement Language Evaluation MethodologySepideh Ghanavati, Daniel Amyot, Liam Peyton. 133-142 [doi]
• Motivation Matters in the Traceability TrenchesPatrick Mäder, Orlena Gotel, Ilka Philippow. 143-148 [doi]
• Toward Automating Requirements Satisfaction AssessmentElizabeth Ashlee Holbrook, Jane Huffman Hayes, Alex Dekhtyar. 149-158 [doi]
• Evaluating the Completeness and Granularity of Functional Requirements Specifications: A Controlled ExperimentSergio España, Nelly Condori-Fernández, Arturo González, Oscar Pastor. 161-170 [doi]
• Improving the Effectiveness of Visual Representations in Requirements Engineering: An Evaluation of i* Visual SyntaxDaniel Laurence Moody, Patrick Heymans, Raimundas Matulevicius. 171-180 [doi]
• Semantic Criteria for Choosing a Language for Big-Step ModelsShahram Esmaeilsabzali, Nancy A. Day, Joanne M. Atlee, Jianwei Niu. 181-190 [doi]
• [vem: xi: ] - A Methodology for Process Based Requirements EngineeringPhilipp Liegl, Rainer Schuster, Marco Zapletal, Christian Huemer, Hannes Werthner, Michael Aigner, Martin Bernauer, Bjoern Klinger, Michaela Mayr, Ramin Mizani, Martin Windisch. 193-202 [doi]
• Semantic-Based Interaction Detection in Aspect-Oriented ScenariosGunter Mussbacher, Jon Whittle, Daniel Amyot. 203-212 [doi]
• Finding Defects in Natural Language Confidentiality RequirementsJens H. Weber-Jahnke, Adeniyi Onabajo. 213-222 [doi]
• Exercising Due Diligence in Legal Requirements Acquisition: A Tool-supported, Frame-Based ApproachTravis D. Breaux. 225-230 [doi]
• Modeling Service-Level Requirements: A Constancy PerspectiveGil Regev, Olivier Hayard, Donald C. Gause, Alain Wegmann. 231-236 [doi]
• Use Case to Source Code Traceability: The Developer Navigation View PointInah Omoronyia, Guttorm Sindre, Marc Roper, John D. Ferguson, Murray Wood. 237-242 [doi]
• Trust Trade-off Analysis for Security Requirements EngineeringGolnaz Elahi, Eric S. K. Yu. 243-248 [doi]
• Improving the Exchange of Requirements and Specifications between Business PartnersManuel Reis Monteiro, Christof Ebert, Matthias Recknagel. 253-260 [doi]
• Understanding Chinese Characteristics of Requirements EngineeringLin Liu, Hongyu Zhang, Fei Peng, Wenting Ma, Yuhui Shan, Jun Xu, Tomas Burda. 261-266 [doi]
• Using Task-oriented Requirements Engineering in Different Domains Sébastian Adam, Jörg Dörr, Michael Eisenbarth, Anne Gross. 267-272 [doi]
• From Feature Development to Customer Value CreationMarjo Kauppinen, Juha Savolainen, Laura Lehtola, Marko Komssi, Harri Tohonen, Alan M. Davis. 275-280 [doi]
• Customer Involvement in Requirements Management: Lessons from Mass Market Software DevelopmentJaap Kabbedijk, Sjaak Brinkkemper, Slinger Jansen, Bas van der Veldt. 281-286 [doi]
• On the Use of Requirements for Driving Call-for-Tender Processes for Procuring Coarse-grained OTS ComponentsJuan Pablo Carvallo, Xavier Franch. 287-292 [doi]
• Linking Functional Requirements and Software VerificationHendrik Post, Carsten Sinz, Florian Merz, Thomas Gorges, Thomas Kropf. 295-302 [doi]
• Bridging the Gap Between Usability and Requirements EngineeringJuho Heiskari, Marjo Kauppinen, Mikael Runonen, Tomi Männistö. 303-308 [doi]
• Requirements Elicitation in a Telemedicine Pain-treatment TrialIng Widya, Richard Bults, Bert-Jan van Beijnum, Leif Sandsjö, Leendert Schaake, Rianne Huis in t Veld, Val Jones, Hermie Hermens. 309-314 [doi]
• Easy Approach to Requirements Syntax (EARS)Alistair Mavin, Philip Wilkinson, Adrian Harwood, Mark Novak. 317-322 [doi]
• Evolution in Domain Model-Based Requirements Engineering for Control Systems DevelopmentHans W. Nissen, Dominik Schmitz, Matthias Jarke, Thomas Rose, Peter Drews, Frank J. Hesseler, Michael Reke. 323-328 [doi]
• Feature-oriented Requirements Satisfy Needs for Reuse and Systems ViewBernd Waldmann, Pete Jones. 329-334 [doi]
• Experiences in Developing Quantifiable NFRs for the Service-Oriented Software PlatformXiping Song, Beatrice Hwong, Johannes Ros. 337-342 [doi]
• Are Your Lights Off? Using Problem Frames to Diagnose System FailuresThein Than Tun, Michael Jackson, Robin C. Laney, Bashar Nuseibeh, Yijun Yu. 343-348 [doi]
• Lessons Learned from the Use of Artifact Models in Industrial ProjectsSascha Konrad, Helmut Degen. 349-354 [doi]
• Next Top Model: A Requirements Engineering Reality PanelOrlena Gotel, Jane Cleland-Huang. 357 [doi]
• Requirements Engineering Education and Training: Key Challenges and Practical SolutionsDidar Zowghi. 358 [doi]
• How to Write and Read a Scientific Evaluation PaperRoel Wieringa, Hans Heerkens, Björn Regnell. 361-364 [doi]
• How to Select a Requirements Management Tool: Initial StepsOrlena Gotel, Patrick Mäder. 365-367 [doi]
• Building Multi-View System Models for Requirements EngineeringAxel van Lamsweerde. 368-369 [doi]
• Augmenting Emotional Requirements with Emotion Markers and Emotion PrototypesDavid Callele, Eric Neufeld, Kevin Schneider. 373-374 [doi]
• Exploiting the Versatility of Constraint Programming over Finite Domains to Integrate Product Line ModelsCamille Salinesi, Daniel Diaz, Olfa Djebbi, Raúl Mazo, Colette Rolland. 375-376 [doi]
• AVT Vector: A Quantitative Security Requirements Evaluation Approach Based on Assets, Vulnerabilities and Trustworthiness of EnvironmentTeng Long, Lin Liu, Yijun Yu, Zhi Jin. 377-378 [doi]
• Context-Sensitive Requirements and Risk Management with IRISShamal Faily, Ivan Flechais. 379-380 [doi]
• Analysis of Feature Configuration WorkflowsAndreas Classen, Arnaud Hubaux, Patrick Heymans. 381-382 [doi]
• Modeling and Analysis of URN Goals and Scenarios with jUCMNavGunter Mussbacher, Sepideh Ghanavati, Daniel Amyot. 383-384 [doi]
• Looking for Product Line Feature Models Defects: Towards a Systematic Classification of Verification CriteriaCamille Salinesi, Colette Rolland, Daniel Diaz, Raúl Mazo. 385-386 [doi]
• Learning to Write Better Requirements through Heuristic CritiquesEric Knauss, Kurt Schneider, Kai Stapel. 387-388 [doi]