The authors' visual analytics tool, MetroEyes, can help people who are not data scientists to analyze software engineering data.
Accessible?
Yes, except for the SQL query, but I think that's fine.
Size?
Is the chapter the right length? Yes
Should anything missing be added?
Perhaps an example of a success story with MetroEyes would make this chapter more salient.
Can anything superfluous be removed (e.g. by deleting some section that does not work so well or by using less jargon, less formulae, lees diagrams, less references).?
No
What are the aspects of the chapter that authors SHOULD change?
I feel that the sales of a software product, which is the example task shown in this chapter, is only tangentially considered "software engineering data". Perhaps a more appropriate example task could be visualizing the bugs, or time spent developing each software component, etc.
Gotta Mantra?
We encouraged (but did not require) the chapter title to be a mantra or something cute/catchy, i.e., some slogan reflecting best practice for data science for SE? If you have suggestion for a better title, please put them here.
Current title seems appropriate. Can't think of a mantra.
Best Points
What are the best points of the chapter that the authors should NOT change?
The explanation of the visual objects in terms of SQL queries immediately made me understand what MetroEyes does.
Review template
Before filling in this review, please read our Advice to Reviewers.
(If you have confidential comments about this chapter, please email them to one of the book editors.)
Title of chapter
Democratizing Data Analysis in Software Engineering
URL to the chapter
https://github.com/ds4se/chapters/blob/master/hongyu/DemocratizingData.md
Message?
The authors' visual analytics tool, MetroEyes, can help people who are not data scientists to analyze software engineering data.
Accessible?
Yes, except for the SQL query, but I think that's fine.
Size?
Is the chapter the right length? Yes
Should anything missing be added?
Perhaps an example of a success story with MetroEyes would make this chapter more salient.
Can anything superfluous be removed (e.g. by deleting some section that does not work so well or by using less jargon, less formulae, lees diagrams, less references).?
No
What are the aspects of the chapter that authors SHOULD change?
I feel that the sales of a software product, which is the example task shown in this chapter, is only tangentially considered "software engineering data". Perhaps a more appropriate example task could be visualizing the bugs, or time spent developing each software component, etc.
Gotta Mantra?
We encouraged (but did not require) the chapter title to be a mantra or something cute/catchy, i.e., some slogan reflecting best practice for data science for SE? If you have suggestion for a better title, please put them here.
Current title seems appropriate. Can't think of a mantra.
Best Points
What are the best points of the chapter that the authors should NOT change?
The explanation of the visual objects in terms of SQL queries immediately made me understand what MetroEyes does.