Abstract is missing.
- Luhmann's Slip Box - What can we Learn from the Device for Knowledge Representation in Requirements Engineering?Andreas Faatz, Birgit Zimmermann, Eicke Godehardt. 1-3 [doi]
- Domain Knowledge Wiki for Eliciting RequirementsTakanori Ugai, Kouji Aoyama. 4-6 [doi]
- Reasoning on Requirements Knowledge to Support CreativityKlaus Schmid. 7-11 [doi]
- Using Defect Reports to Build Requirements Knowledge in Product LinesRobyn R. Lutz, Nicolas Rouquette. 12-21 [doi]
- Utilizing Rule Deviations in IT Ecosystems for Implicit Requirements ElicitationLeif Singer, Olesia Brill, Sebastian Meyer 0001, Kurt Schneider. 22-26 [doi]
- On Presuppositions in RequirementsLin Ma, Bashar Nuseibeh, Paul Piwek, Anne N. De Roeck, Alistair Willis. 27-31 [doi]
- Towards a Research Agenda for Recommendation Systems in Requirements EngineeringWalid Maalej, Anil Kumar Thurimella. 32-39 [doi]
- Making Tacit Requirements ExplicitRicardo Gacitua, Lin Ma, Bashar Nuseibeh, Paul Piwek, Anne N. De Roeck, Mark Rouncefield, Peter Sawyer, Alistair Willis, H. Yang. 40-44 [doi]
- A Machine Learning Approach for Identifying Expert StakeholdersCarlos Castro-Herrera, Jane Cleland-Huang. 45-49 [doi]
- How to Keep Domain Requirements Models Reasonably SizedHans W. Nissen, Dominik Schmitz, Matthias Jarke, Thomas Rose 0001. 50-59 [doi]
- Modeling and Managing Tacit Product Line Requirements KnowledgeReinhard Stoiber, Martin Glinz. 60-64 [doi]
- Continuous and Collaborative Validation: A Field Study of Requirements Knowledge in AgileRosalva E. Gallardo-Valencia, Susan Elliott Sim. 65-74 [doi]
- Capturing, Organizing, and Reusing Knowledge of NFRs: An NFR Pattern ApproachSam Supakkul, Tom Hill, Ebenezer Akin Oladimeji, Lawrence Chung. 75-84 [doi]
- The Papyrus Tool as an Eclipse UML2-modeling Environment for RequirementsHubert Dubois, Fadoi Lakhal, Sébastien Gérard. 85-88 [doi]