Abstract is missing.
- Recommending rename refactoringsAndreas Thies, Christian Roth. 1-5 [doi]
- Utilizing recommender systems to support software requirements elicitationCarlos Castro-Herrera, Jane Cleland-Huang. 6-10 [doi]
- Recommendation and decision technologies for requirements engineeringAlexander Felfernig, Monika Schubert, Monika Mandl, Francesco Ricci, Walid Maalej. 11-15 [doi]
- Towards knowledge assisted agile requirements evolutionManish Kumar, Nirav Ajmeri, Smita Ghaisas. 16-20 [doi]
- Recommending source code examples via API call usages and documentationCollin McMillan, Denys Poshyvanyk, Mark Grechanik. 21-25 [doi]
- Towards a better code completion system by API grouping, filtering, and popularity-based rankingDaqing Hou, David M. Pletcher. 26-30 [doi]
- KAdvice: infering synchronization patterns from an existing codebaseAlexander Schmidt, Andreas Polze. 31-35 [doi]
- A recommendation framework for allocating global software teams in software product line projectsThaís Alves Burity Pereira, Vinicius Souza dos Santos, Bruno Luna Ribeiro, Glêdson Elias. 36-40 [doi]
- Recommending experts using communication historyAlan Moraes, Eduardo Silva, Cleyton da Trindade, Yuri Barbosa, Silvio Meira. 41-45 [doi]
- The weHelp reference architecture for community-driven recommender systemsSwapneel Sheth, Nipun Arora, Christian Murphy, Gail E. Kaiser. 46-47 [doi]
- Component recommendation for cloud applicationsZibin Zheng, Michael R. Lyu. 48-49 [doi]
- On recommending meaningful names in source and UMLAdrian Kuhn. 50-51 [doi]
- Predicting the fix time of bugsEmanuel Giger, Martin Pinzger, Harald C. Gall. 52-56 [doi]
- What is trust in a recommender for software development?Gail C. Murphy, Emerson R. Murphy-Hill. 57-58 [doi]
- Assisting engineers in switching artifacts by using task semantic and interaction historyWalid Maalej, Alexander Sahm. 59-63 [doi]
- Proposing software design recommendations based on component interface intersectingOliver Hummel, Werner Janjic, Colin Atkinson. 64-68 [doi]