Abstract is missing.
- Why the Electronic Land Registry FailedSøren Lauesen. 1-15 [doi]
- Answering a Request for Proposal - Challenges and Proposed SolutionsBarbara Paech, Robert Heinrich, Gabriele Zorn-Pauli, Andreas Jung, Siamak Tadjiky. 16-29 [doi]
- Impediments to Requirements-ComplianceMd. Rashed Iqbal Nekvi, Nazim H. Madhavji, Remo Ferrari, Brian Berenbach. 30-36 [doi]
- How Architects See Non-Functional Requirements: Beware of ModifiabilityEltjo R. Poort, Nick Martens, Inge van de Weerd, Hans van Vliet. 37-51 [doi]
- Research Preview: Prioritizing Quality Requirements Based on Software Architecture Evaluation FeedbackAnne Koziolek. 52-58 [doi]
- A Simulation Approach for Impact Analysis of Requirement Volatility Considering Dependency ChangeJunjie Wang, Juan Li, Qing Wang, He Zhang, Haitao Wang. 59-76 [doi]
- Collaborative Resolution of Requirements Mismatches When Adopting Open Source ComponentsNguyen Duc Anh, Daniela S. Cruzes, Reidar Conradi, Martin Höst, Xavier Franch, Claudia P. Ayala. 77-93 [doi]
- High-Level Requirements Management and Complexity Costs in Automotive Development Projects: A Problem StatementTim Gülke, Bernhard Rumpe, Martin Jansen, Joachim Axmann. 94-100 [doi]
- Choose Your Creativity: Why and How Creativity in Requirements Engineering Means Different Things to Different PeopleMartin Mahaux, Alistair Mavin, Patrick Heymans. 101-116 [doi]
- Supporting Failure Mode and Effect Analysis: A Case Study with Failure Sequence DiagramsChristian Raspotnig, Andreas L. Opdahl. 117-131 [doi]
- Aligning Mal-activity Diagrams and Security Risk Management for Security Requirements DefinitionsMohammad Jabed Morshed Chowdhury, Raimundas Matulevicius, Guttorm Sindre, Péter Kárpáti. 132-139 [doi]
- Towards a More Semantically Transparent i* Visual SyntaxNicolas Genon, Patrice Caire, Hubert Toussaint, Patrick Heymans, Daniel Laurence Moody. 140-146 [doi]
- Providing Software Product Line Knowledge to Requirements Engineers - A Template for Elicitation InstructionsSebastian Adam. 147-164 [doi]
- Supporting Learning Organisations in Writing Better Requirements Documents Based on Heuristic CritiquesEric Knauss, Kurt Schneider. 165-171 [doi]
- Managing Implicit Requirements Using Semantic Case-Based Reasoning Research PreviewOlawande Daramola, Thomas Moser, Guttorm Sindre, Stefan Biffl. 172-178 [doi]
- Trace Queries for Safety Requirements in High Assurance SystemsJane Cleland-Huang, Mats Per Erik Heimdahl, Jane Huffman Hayes, Robyn R. Lutz, Patrick Maeder. 179-193 [doi]
- Which Traceability Visualization Is Suitable in This Context? A Comparative StudyYang Li, Walid Maalej. 194-210 [doi]
- The Case for Dumb Requirements Engineering ToolsDaniel M. Berry, Ricardo Gacitua, Pete Sawyer, Sri Fatimah Tjong. 211-217 [doi]
- Automatic Analysis of Multimodal Requirements: A Research PreviewElia Bruni, Alessio Ferrari, Norbert Seyff, Gabriele Tolomei. 218-224 [doi]
- 10 Myths of Software QualityElke Hochmüller. 225-231 [doi]
- Empirical Analysis of the Impact of Requirements Engineering on Software QualityLukasz Radlinski. 232-238 [doi]
- A Systematic Literature Review on Service Description MethodsAbelneh Y. Teka, Nelly Condori-Fernández, Brahmananda Sapkota. 239-255 [doi]
- A Pattern-Based Method for Identifying and Analyzing LawsKristian Beckers, Stephan Faßbender, Jan-Christoph Küster, Holger Schmidt. 256-262 [doi]
- Towards a Requirements Modeling Language for Self-Adaptive SystemsNauman A. Qureshi, Ivan Jureta, Anna Perini. 263-279 [doi]
- Requirements Monitoring for Adaptive Service-Based ApplicationsMarc Oriol, Nauman A. Qureshi, Xavier Franch, Anna Perini, Jordi Marco. 280-287 [doi]
- Release Planning with Feature Trees: Industrial CaseSamuel Fricker, Susanne Schumacher. 288-305 [doi]
- Goal-Oriented Requirements Engineering and Enterprise Architecture: Two Case Studies and Some Lessons LearnedWilco Engelsman, Roel Wieringa. 306-320 [doi]