Your SlideShare is downloading. ×
[VISSOFT2013] Visualizing the Workflow of Developers
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

[VISSOFT2013] Visualizing the Workflow of Developers

110
views

Published on

We present an approach to visualize the activities of developers within the IDE, implemented in a tool: DFlow. DFlow records all IDE interactions that occur during a development session and visualizes …

We present an approach to visualize the activities of developers within the IDE, implemented in a tool: DFlow. DFlow records all IDE interactions that occur during a development session and visualizes them through a web-based visualization platform.

Slides used at VISSOFT 2013 (http://icsm2013.tue.nl/VISSOFT)

Published in: Education, Technology

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
110
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Visualizing the Workflow of Developers Roberto Minelli and Michele Lanza REVEAL @ Faculty of Informatics University of Lugano, Switzerland http://dflow.inf.usi.ch
  • 2. Developers spend a large part of their working time using an Integrated Development Environment
  • 3. W riting
  • 4. W riting Navigating
  • 5. W riting Navigating “Programmers spend more time navigating the code than working with it.” M. Kersten and G.C. Murphy “Mylar: a degree-of-interest model for IDEs” AOSD 2005
  • 6. W riting Navigating 20% 80% DFlow Data 9,521 Events 7,588 Navigation Events 1,933 Editing events “Programmers spend more time navigating the code than working with it.” M. Kersten and G.C. Murphy “Mylar: a degree-of-interest model for IDEs” AOSD 2005
  • 7. Window-based IDE Tabs-based IDE D. Roethlisberger, O. Nierstrasz, S. Ducasse “Autumn leaves: Curing the window plague in IDEs” WCRE 2009 “Devs are forced to open multiple windows (tabs). The IDE becomes a crowded workspace.
  • 8. While the developer interacts with the IDE A tool records all the IDE interactions Generates a large amount of data (events) Reflect on the IDE DFlow
  • 9. How, when, why do developers use the IDE to navigate the system? To what extent does the IDE support the navigation? DFlow
  • 10. DFlow
  • 11. DFlow WEB Enables retrospective analyses through a web- based visual platform. IDE Records all the IDE interactions while the developer program.
  • 12. 9 types of Editing 18 types of Inspection 6 types of Navigation
  • 13. Browsing a class or a method Stepping in a debugger or inspecting the internals of an object Adding or removing a class or a method
  • 14. Browsing a class or a method Stepping in a debugger or inspecting the internals of an object Adding or removing a class or a method DFlow Data +20 Sessions 9,521 Events 7,367 Navigation Events 221 Inspecting events 1,933 Editing events
  • 15. What to do with this large amount of data?
  • 16. Compress Structure Present
  • 17. DEMO DFlow
  • 18. Insights Visualizations
  • 19. All navigation events and one single editing A debugging session
  • 20. Green navigation stacks (browsing the API of a class)
  • 21. Back edge means that she uses what she discovered in a different context
  • 22. What’s next?
  • 23. Refine the current visualizations and devise new views Devise a paern language from the visualizations Evaluate our visualizations (user study) What’s next?
  • 24. W riting Navigating What to do with this large amount of data? While the developer interacts with the IDE A tool records all the IDE interactions Generates a large amount of data (events) Reflect on the IDE DFlow Green navigation stacks (browsing the API of a class)
  • 25. W riting Navigating What to do with this large amount of data? While the developer interacts with the IDE A tool records all the IDE interactions Generates a large amount of data (events) Reflect on the IDE DFlow Green navigation stacks (browsing the API of a class) Any other idea? Talk to me (or drop me an email) robertominelli roberto.minelli@usi.ch