1. Code churn: it's always what you get what you ask for. We have experienced this situation before. I know that for LOC, "**" and "**/*.java" means the same thing, since LOCC only sends java sizes. People tend to use "**", and take it for granted that it's for java code. There is really nothing I can do here.
agreed.
2. More detailed information about telemetry and chart parameters.
I concur that this is a very important usability issue.
I'm not so sure. When I was working with the existing definitions, I simply ran the report three times in different tabbed windows, then switched back and forth between tabs to see what I needed. That was actually better for defining forms than seeing one single definition splayed out.
Let's hold off on this for now. It might be useful to talk about displaying the pages in separate tabs in Chapter 5.
3. Standard deviation line:
(a) So far we don't understand how statistical procss control can be applied to telemetry. I think this is one of the future researches of telemetry, perhaps another Ph.D. thesis.
Yes. Also we might find that box and whisker plots are actually more helpful than standard deviation.
Cheers, Philip
