The document discusses bug reporting with a focus on a system developed by Tommaso Dal Sasso, Andrea Mocci, and Michele Lanza at the University of Lugano. It highlights the architecture, features, and future plans for the bug report management model known as Shoreline, covering aspects such as data collection, extensibility, and integration with other systems. The authors emphasize the importance of context and structure in bug reporting while outlining short-term goals for improved functionality.

1. Talking
About Bugs
With Bugs
Tommaso Dal Sasso
Andrea Mocci
Michele Lanza University of Lugano

2. Bug Reports
Text
Time
Automation
Model
Interface

3. Bug Reports

4. Bug Reports
flexibility context

5. ShoreLine
Reporter

8. Source Code Change
Stack Trace
IDE Interaction
Primary Colors
B
C
D E
NOM
NOA NOA
Package
Class
Selected
Class
A

10. ShoreLine
Next

11. Reporting an Error

12. Reporting an Error

13. Reporting an Error

14. Reporting an Error

15. DEMO
TIME
Demo

16. Extending Data Collection
Collect custom data by subclassing SlCollector
SlCollector>>extractFrom:
how to collect the data
SlCollector class>>description
a text description of the collected data
SlCollector class>>tag
the name of the collector

17. Domain Specific Information
‣ Roassal — number of nodes in a view
‣ PetitParser — input string
‣ Voyage — object description

18. ShoreLine Model

19. ShoreLine Model
Bug #1337
Metadata
Comment
Comment
Stack Trace
Patch

20. ShoreLine Model
Bug #1337
Metadata
Comment
Comment
Stack Trace
Patch
Comment
Comment
Comment
Bug #42
Metadata

21. Shards
Each shard knows its context
Each Shard can be linked to other shards
Many linked shards form a stream that describes a behavior

22. Talking With Bug Reports
‣ Bug reports are objects
‣ Events are objects
‣ Links are objects
We can inspect and navigate our data

23. DEMO
TIME
Demo

24. Accessing the data
Context
Structure
Automation

25. The Architecture
Clients (ShoreLine, Browser)
Connector
Server
Teapot
Voyage
NeoJSON

26. ShoreLine Design Principles
‣ Extensible
‣ Privacy Friendly
‣ “Business” Friendly

27. What Next?
FogBugz
importing existing data
export new bug reports
bug report management
assign a bug report
authentication
What is There What is Not There Yet

28. Short Term Plans
‣ Stable version
‣ Report Browser
‣ Interaction with FogBugz
‣ Data Analysis

29. Conclusion
Bug Reports Reporting an Error
ShoreLine Model
Metadata
Comment
Comment
Stack Trace
Patch
Comment
Comment
Comment

30. Talking
About Bugs
With Bugs
Tommaso Dal Sasso
Andrea Mocci
Michele Lanza University of Lugano
Thanks!