An IDE-Based web search and software maintenance solution.

1. SurfClip
se
A Multi-purpose Eclipse Plug-in

2. Team Perfectionist
Shamima Yeasmin
(NSID: shy942)
Mohammad Masudur Rahman
(NSID:mor543)

3. SurfClip
se
Final Project Presentation

4. Motivating Example

7. What we started with?

9. Larger Objectives
Suggest Solution Pinpoint Error
Code Soundness
Program Flow

10. Low Fidelity Prototype

11. Design Approach
Low Fidelity
Prototype
Brainstorming

12. Low Fidelity Prototype
Suggesting solutions for errors
Pinpointing error location

13. Low Fidelity Prototype
Checking soundness of code
Showing program flow

14. Usability Inspection Results

18. Medium Fidelity Prototype

19. Medium-Fidelity Objectives
• Addressing those issues identified by
evaluators
Exploring real user’s thoughts

20. Medium-Fidelity Prototype
Suggesting solutions for errors

21. Medium-Fidelity Prototype
Pinpointing error location

22. Medium-Fidelity Prototype
Checking soundness of code

23. Medium-Fidelity Prototype
Showing program flow

24. Evaluation with Users

25. Rationale of Evaluation
Semi-structured Interview
Simple Observation
Evaluation Methods

26. Rationale of Evaluation
• Target Users: Graduate (2) and Postgraduate
(2) Students from Software Research Lab
Target Users (Evaluators)

27. Approach of Evaluation
Contact
SurfClipse
Team
Check
availability
Evaluator
Consent
Schedule meeting
Setting Evaluation Meeting

28. Approach of Evaluation
Explain Evaluation purpose
SurfClipse Demo
Analyzing Results Data
Simple Observation
Semi-structure Interview
Evaluation Process

29. Results of Evaluation

30. Quantitative Results

31. Evaluation Data
Quantitative Vs Qualitative

32. SurfClipse Feature Rating
SS=Suggest
Solution
PE=
Pinpointing
Error
CCS=Check
Code
Soundness
SSF= Show
Program Flow
Feature rating from 0 to 5

33. SurfClipse Beats ‘Web Search’
SurfClipse beats Web Search

34. Qualitative Results

35. Qualitative Feedback (Positive)
• “Pinpoint Error is the most
innovative, more informative and
important for novice users ”
• “Suggest Solution is the coolest
feature and faster than traditional
approach ”
• “Check code soundness reduces the
workload for developers ”

36. Qualitative Feedback (Negative)
• “Suggest Solution -Search results
should be able expandable or
reducible for display ”
• “Code Soundness – copyright
violation risk while using other’s
code”
• “Program Flow – implementation
will be unrealistic for millions
lines of codes”

37. Recommendation

38. Design Change Recommendation
• Suggest Solution
• Apply more intelligent filtering to avoid
irrelevant results in ‘Suggest Solution’
• Search results should be able
expandable or reducible for display
• Pinpointing Error
• Consider semantic analysis of code in
order to ensure better precision and
feasibility.

39. Design Change Recommendation
• Check Code Soundness
• Show scores against different metrics of
code quality individually
• Program Flow
• Make it more interactive and portion of
graph should expandable or reducible

40. Video Demonstration
• http://youtu.be/c02eXZwAHM4

41. Acknowledgment
• All images taken from
http://www.google.ca
• Background music
http://www.oregonmusic.com

42. Thank You !!!
Please ask your questions