The document discusses how to better integrate user input and feedback into the software development process in a continuous and context-aware manner. It identifies issues with how user input is currently handled and proposes a continuous feedback model along with several technical enablers, like visual annotation tools and recommendation systems, to make user input a first-order concern in development. The goal is to help engineering teams get more direct and rich feedback from users to improve their applications.

1. When Users Become Collaborators: Towards Continuous and Context-Aware User Input Walid Maalej (TU München) Hans-Jörg Happel , Asarnusch Rashid (FZI Karlsruhe) OOPSLA Onward! Orlando, FL, October 29 th , 2009

2. Outline Motivation A Benchmarking A New Approach Technical Enablers Next Steps

4. Various concepts to address end users in software development

5. Outline Motivation A Benchmarking A New Approach Technical Enablers Next Steps

6. Various types of user input ? Perpetual Beta Legacy Documents Usage Data Implicit Explicit Pull Push Issue and Bug Report Enhancement Request Feature Request Workshop Interview, Survey Clarification Request Field Observation Lead Users (Not used in SE) Communication Feedback

7. Various realizations of user input

8. Mysterious stack traces

9. Bug reports from within a program

10. Application usage data

11. Discussions in user communities

12. Various realizations of user input …but most applications still do not consider feedback at all…

14. Streams of interaction Requirements Engineers Users Realization Provision Deployment Problem Usage Evolution Fix Question Support

15. Outline Motivation A Benchmarking A New Approach Technical Enablers Next Steps

16. A Continuous Feedback Model Prospective Observation Assisted Feedback Improvement D ecision Back- Feedback Systematic Analysis Application User Engineering Team Development Infrastructure Community Sharing

17. Outline Motivation A Benchmarking A New Approach Technical Enablers Next Steps

18. Technical building blocks Visual Annotation Recommend end user to share their experience with engineering teams end other end users Observation & Context Elicitation Allow user to annotate and „paint“ on the GUI in the work context Proactive Assistance Detect user intention and problem situations through observation of user and application Making user input a 1 st order concern

19. TeamWeaver Context Framework problem problem Execution Ontology Interaction Ontoloy Feedback Reporting Interface OS sensors User Profile Elicitation Problem events update trigger A pplication sensors Execution Env. sensors A dditional feedback interact Session- ization Context Observer http://www.teamweaver.org

20. Visual Annotation with OpenProposal End user application http://www.openproposal.de OpenProposal plus Username, Application, Version, Date, etc. Issue Tracker

22. Outline Motivation A Benchmarking A New Approach Technical Enablers Next Steps