This document summarizes the development of an interactive visualization tool called Papertrends. It describes the research question of comparing word appearances over time, prototypes created with user testing, implementation including a redesign based on feedback, programming problems encountered, lessons learned regarding data and teamwork, and a link to demo the final project.

1. PAPERTRENDS
Stijn Adams
Niels Billen
Robin De Croon
findingvisos.wordpress.com

2. Content
• Research Question
• Prototype
• Implementation
• Programming Problems
• What we’ve learnt
• Demo
May 22, 2013 2
http://blog.thoughtpick.com/wp-content/uploads/2011/01/web_design_services.11-18.web_content.jpg

3. RESEARCH
QUESTION
Research Question
Prototype
Implementation
Programming Problems
What we’ve learnt
Demo
May 22, 2013 3

4. ResearchQuestion
Trends
May 22, 2013 4
Where?
When?
Compare!
What? Who?

5. Alternatives
• Compare appearances of 2 words
• EDM vs. LAK papers per country
(already taken)
• Collaboration between authors/
universities/countries
• Influence of organizing city
May 22, 2013 5

6. PROTOTYPE
Research Question
Prototype
Implementation
Programming Problems
What we’ve learnt
Demo
May 22, 2013 6

7. Prototype: design
May 22, 2013 7

8. Prototype: design
May 22, 2013 8

9. Prototype: design
May 22, 2013 9

10. Prototype: design
May 22, 2013 10

11. Prototype: design
May 22, 2013 11

12. Prototype: design
May 22, 2013 12

13. Prototype: design
May 22, 2013 13

14. Prototype: evaluation
• User tests withThink Aloud method
• SUS questionnaire
• 4 users (students)
• Simple scenario
• Powerpoint presentation
May 22, 2013 14

15. Prototype: problems
May 22, 2013 15
• Sidebar mostly useless
• 2 persons
 Only show it when necessary ( = when paper selected)
• Word cloud not clear
• 1 person
 Show multiple words on a location

16. Prototype: SUS results
May 22, 2013 16
•Average: 89,4
•Maximum: 95
•Minimum: 82,5
• Mostly low scores on
‘Future Use’
• Average: 2.25 / 5

17. IMPLEMENTATION
Research Question
Alternatives
Prototype
Implementation
What we’ve learnt
Demo
May 22, 2013 17

18. First Design
May 22, 2013 20

19. Feedback during demo
May 22, 2013 21
•Use a gradient scale instead of 5 different, unrelated colors
•Overlapping word clouds are disturbing

20. Second Design
May 22, 2013 22

21. Other Modifications
May 22, 2013 23
•Sidebar functional
•Years also in papers
•Performance
•Tuio Multitouch
•Native versions
http://blog.kace.com/2013/01/17/keys-to-a-successful-upgrade-every-time/upgrade-8/

22. Sidebar
May 22, 2013 24

23. Sidebar
May 22, 2013 25
Bad data

24. MultiTouch
May 22, 2013 26

25. PROGRAMMING
PROBLEMS
Research Question
Alternatives
Prototype
Programming Problems
What we’ve learnt
Demo
May 22, 2013 27

26. Programming Problems
• Bug in Processing
• Unfolding uses old Processing
• Zooming does not working inWindows (8)
• Performance
• Other threads delete non visible items
• Image of circle instead of drawing it
May 22, 2013 28

27. Programming Problems
May 22, 2013 29

28. Programming Problems
• Order of drawing
• Interface problem
• Swing vs AWT applet
• Custom MapTiles
• TileMill
May 22, 2013 30

29. WHATWE’VE
LEARNT
Research Question
Alternatives
Prototype
Programming Problems
What we’ve learnt
Demo
May 22, 2013 31

30. What we’ve learnt
• Always start with defining the research
question!
•  - Each dataset has a lot of hidden (and
interesting) stories to tell.
•  - Datasets are often incomplete…
May 22, 2013 32

31. Teamwork
• Facebook
• Git
• Meetings
May 22, 2013 33

32. DEMO
Research Question
Alternatives
Prototype
Programming Problems
What we’ve learnt
Demo
May 22, 2013 34

33. http://2.bp.blogspot.com/-gZjNR3XVULs/T_ZOVgE-5lI/AAAAAAAAAg8/6YVmd5Q064o/s1600/questions11.jpg
May 22, 2013 35
http://findingvisos.wordpress.com/