11 Towards a Research Agenda for Recommendation Systems in Requirements Engineering

941 views

Published on

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
941
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

11 Towards a Research Agenda for Recommendation Systems in Requirements Engineering

  1. 1. Towards a Research Agenda forRecommendation Systems in Requirements Engineering <br />Walid Maalej, TU München &lt;maalejw@cs.tum.edu&gt;<br />AnilKumarThurimella, Harman Becker Automotive Systems<br />
  2. 2. 2<br />Outline<br />Motivation<br />State of the Art<br />Enablers<br />Applications<br />Next Steps <br />1<br />2<br />3<br />4<br />5<br />Towards a Research Agenda for RS in RE<br />
  3. 3. Towards a Research Agenda for RS in RE<br />3<br />Today’s Challenges of Software Projects<br />Daily Change<br /><ul><li>Change in design, requirements and project settings
  4. 4. Knowledge ages quickly</li></ul>Information Overload<br /><ul><li>Immense information sources
  5. 5. Diverse and complex technologies, frameworks and requirements</li></ul>2<br />“Multiple” Distribution<br /><ul><li>Outsourcing, offshoring, open source, multi-organizational projects
  6. 6. Problems in coordination, knowledge sharing
  7. 7. Problems in efficiency </li></ul>1<br />Four dynamic and increasing factors<br />3<br />4<br />High Competition<br /><ul><li>Short “time to market”
  8. 8. Highest productivity, flexibility and quality is required</li></li></ul><li>Need & Chance of RS in Requirements Engineering<br />Towards a Research Agenda for RS in RE<br />4<br />Chances for RS<br /><ul><li>To deal with today’s project challenges, stakeholders need an effective and “intelligent” support:
  9. 9. Proactive assistancein collaboration, management and engineering work
  10. 10. Information push instead of Information pull
  11. 11. Nature of Software Engineering projects increases potentials of RS
  12. 12. Project data have a structured or semi-structured format
  13. 13. Both engineering activities and artifacts have well defined semantics</li></ul>Needs for Support<br />
  14. 14. 5<br />Outline<br />Motivation<br />State of the Art<br />Enablers<br />Applications<br />Next Steps <br />1<br />2<br />3<br />4<br />5<br />Towards a Research Agenda for RS in RE<br />
  15. 15. Towards a Research Agenda for RS in RE<br />6<br />Research Reaped Several Tools*<br />* Happel & Maalej: RSSE08, Potentials And Challenges of Recommendation Systems in Software Development<br />
  16. 16. Towards a Research Agenda for RS in RE<br />7<br />Limitations of Current Approaches<br />No support for requirements engineering work, no use of requirements as recommendation items<br />3<br />Information provision and experience capture not supported<br />Limited pro-activeness, personalization and use of context<br />2<br />1<br />Inflexible, hard-coded knowledge representation and heuristics<br />Centralized and inflexible architecture<br />Limitation in functionality and technology<br />To tape the potentials of RS in RE, a systematic account is required<br />
  17. 17. 8<br />Outline<br />Motivation<br />State of the Art<br />Enablers<br />Applications<br />Next Steps <br />1<br />2<br />3<br />4<br />5<br />Towards a Research Agenda for RS in RE<br />
  18. 18. Towards a Research Agenda for RS in RE<br />9<br />Systematic Elicitation and Processing of Working Context*<br />Time<br />Short Term Context<br />Long Term Context<br />Component<br />Reuse<br /><ul><li>External libraries imported
  19. 19. Documentation read
  20. 20. Documents changed
  21. 21. Developer’s experience on reusing this API</li></ul>Context<br />Other interpreted information<br />Other observed events<br />Other<br />Activities<br />Activity<br /><ul><li>Error message
  22. 22. Environments
  23. 23. Search keywords
  24. 24. Discussion threads</li></ul>Error <br />Handling<br /><ul><li>Developer’s experience on handling this error</li></ul>* Maalej & Happel: PAKM08, A Lightweight Approach forKnowledgeSharing in Distributed Software Teams<br />
  25. 25. Towards a Research Agenda for RS in RE<br />10<br />Information Seeker<br />InformationProvider<br />Inverse Search to Support Information Providers<br /><ul><li>Conventional recommendation systems:</li></ul>Match queries of information seekers against a given corpus <br />Pull information into their local space <br /><ul><li>Information providers are not part of this model although they are potential providers of additional information
  26. 26. RS using inverse search:</li></ul>Matches the corpus of information providers against a given set of queries<br />Identify information worth sharing<br />Index<br /> 3. inSearch<br />1. Query<br />Queries<br /> 4. Share<br />2. Results<br />* Maalej & Happel: PAKM08, A Lightweight Approach forKnowledgeSharing in Distributed Software Teams<br />
  27. 27. 11<br />Outline<br />Motivation<br />State of the Art<br />Enablers<br />Applications<br />Next Steps <br />1<br />2<br />3<br />4<br />5<br />Towards a Research Agenda for RS in RE<br />
  28. 28. Towards a Research Agenda for RS in RE<br />12<br />Recommendation Landscape For RE<br />
  29. 29. Recommendation Landscape For RE Cont.<br />Towards a Research Agenda for RS in RE<br />13<br />
  30. 30. 14<br />Outline<br />Motivation<br />State of the Art<br />Enablers<br />Applications<br />Next Steps <br />1<br />2<br />3<br />4<br />5<br />Towards a Research Agenda for RS in RE<br />
  31. 31. Open Research and Realization Issues<br />Towards a Research Agenda for RS in RE<br />15<br />Recommendation Systems in RE Work<br />5<br />1<br />RS & RE Models<br /><ul><li>adjustment of RS models to RE and of RE processes to RS</li></ul>Users’ Privacy<br /><ul><li>Missuse of collected, sensitive information</li></ul>2<br />3<br />4<br />Information & Tool Integration<br /><ul><li>Information scattered across many heterogeneous tools
  32. 32. Recommendations integrated into work tools</li></ul>Context-Awareness<br /><ul><li>Sessionization of the work
  33. 33. Detection of problem situations
  34. 34. Understanding of users behavior, empirically proofed heuristics </li></ul>Knowledge Representation<br /><ul><li>Automatic reasoning,
  35. 35. Content comparison
  36. 36. Transparency of the recommendations </li></li></ul><li>Towards a Research Agenda for RS in RE<br />16<br />Summary of the Talk<br />1<br />Existing approaches are promising but have limitations and do not support requirements engineering work<br />2<br />Recent research on context aware working infrastructure and inverse search brings additional potentials for RS<br />4<br />Context-awareness, integration, knowledge representation, privacy and RS models are major research challenges<br />3<br />Many scenarios for RS in RE to support knowledge- consumer & -provider on collaboration and engineering work<br />
  37. 37. Towards a Research Agenda for RS in RE<br />17<br />Backups<br />
  38. 38. Towards a Research Agenda for RS in RE<br />18<br />Challenges of Context Awareness<br />Design<br />How can we model abstract concepts to support unique scenarios?<br />Long-Term Context<br />Can we objectively model a subjective topic like experience?<br />Sessionization <br />How can we “package” context based on the time and content?<br />Six major research challenges<br />Aggregation <br />How can we support different levels of abstractions with different factors?<br />Context Representation <br />Can we efficiently represent data and enable simple and semantic interpretation?<br />Context Factors<br />What should be observed, what is a part of the context?<br />
  39. 39. Towards a Research Agenda for RS in RE<br />19<br />Open Source Platform: TeamWeaver <br />www.teamweaver.org<br />
  40. 40. Towards a Research Agenda for RS in RE<br />20<br />Four States of Private and Organizational Knowledge Space<br />There is enough knowledge w.r.t. a certain topic, both locally and in the organization<br />A user has lots of knowledge about a topic, while there is not much knowledge in the organization<br />many<br />Information overload<br />Organizational <br />Information gap<br />few<br />Documents in private space<br />Personal information gap<br />Information<br />shortage<br />few<br />many<br />Documents in organizational space<br />While there is lots of knowledge in the organization, the user does not have much knowledge<br />Few knowledge exists both locally and globally<br />
  41. 41. Towards a Research Agenda for RS in RE<br />21<br />The Big Picture of Context Aware Development Environments<br />Time<br />Short Term Context<br />Long Term Context<br />Component <br />Reuse<br /><ul><li>Import of external components
  42. 42. Documentation used
  43. 43. Documents changed
  44. 44. Developers profiles on reusing APIs</li></ul>Context<br />Scenario<br />Error <br />Handling<br /><ul><li>Error message
  45. 45. Environments
  46. 46. Search keywords
  47. 47. Discussion threads
  48. 48. Developers profiles on handling errors</li></li></ul><li>Towards a Research Agenda for RS in RE<br />22<br />Information Seeker<br />Information Provider<br />Information Seeker<br />Retroactive Search<br />Index<br />Query<br />Synchronous<br />Queries<br />Results<br />Inverse Search<br />Prospective Search<br />Index<br />inverse Search<br />Subscription<br />Queries<br />Asynchronous<br /> Sharing<br />Notification<br />Provider<br />Consumer<br />Roles and Time in Information Access<br />

×