Beyond Data Mining
This article first appeared in IEEE Software magazine and is brought to you by InfoQ & IEEE Computer Society.
The predictive modeling community applies data miners to artifacts from software projects. This work has been very successful-we now know how to build predictive models for software effects and defects and many other tasks such as learning 'developers' programming patterns (see the extended version of this article for more detail).
That said, to truly impact the work of industrial practitioners, we need to change the predictive modeling community's focus. To date, it has spent too much time on algorithm mining when the field is moving into what I call landscape mining. To support industrial practitioners, we're going to have to move on to something I call decision mining and then discussion mining.
This article compares and contrasts the four kinds of miners shown in Figure 1:
- Algorithm miners explore tuning parameters in data mining algorithms.
- Landscape miners reveal the shape of the decision space.
- Decision miners comment on how best to change a project.
- Discussion miners help the community debate trade-offs regarding the different decisions.
Note that algorithm and landscape mining are more research-focused activities that explore the miners' internal details. However, decision and discussion miners are more practitioner-oriented because they're focused on how a community can use conclusions.
While it's rarely stated, the original premise of predictive modeling was that predictions should guide software management-in other words, once upon a time, the aim of a prediction was a decision.
Sadly, that original aim seems to be forgotten. Too many researchers in the field are stuck in a rut, publishing papers that spend very little time exploring the data and much more time on the data algorithms. Most of these papers focus on exploring configuration options with the algorithms, rather than reflecting on the underlying data. Recent papers report that there's little to be gained from such algorithm mining because the "improvements" found from this approach are marginal, at best-for example, for effort estimation and defect prediction, simpler data miners do just as well or better than more elaborate ones.1,2
Algorithm mining is a "leap before your look" approach in which researchers throw algorithms at data and then see what comes out. A second approach is the "look before you leap" option-mining the data to find the space of possible inferences before leaping in with the learners. This is the data's "landscape."
Figure 1. Four kinds of miners shown left to right, past to future.
Consider the W1 case-based reasoning (CBR) system, also known as "Dub-ya" or the "the decider."3 CBR makes conclusions by inspecting the nearest similar historical cases. To make W1 a landscape miner (which we'll call W2), we can cluster the training data into a tree of clusters, where child nodes contain subclusters of the parents. Then, a feature selector runs over the data to reject features whose values can't distinguish the clusters. Specifically, we're checking the entropy of each attribute value over all clusters and deleting those with the highest entropy. Finally, we can replace all leaf clusters with the median of each cluster. The resulting space of features and examples is very small: dozens of features reduce down to just a handful, and hundreds of examples reduce down to just one example per cluster.
By restricting inference to just some subtree of clusters (where the leaves now contain just one representative example), we can quickly build many local models specialized to particular contexts.
W2 has two important features. First, it's a landscape miner in that it maps out different regions of data inside of which we might build different models. Second, while the assembly of ideas is somewhat unique, each part of W2 is a known tool to the predictive modeling community. That is, it's possible for the predictive community modeling community to refocus and redirect its tools toward an interesting new goal.
At a recent panel on software analytics at ICSE 2012, industrial practitioners reviewed the state of the art in data mining.4 Panelists commented, "Prediction is all well and good, but what about decision making?" Data mining is useful because it focuses an inquiry onto particular issues, but data miners are subroutines in a higher-level decision process.
To convert W2 into a decision miner (which we'll call W3), we add contrast set learning. While classifiers report what's true about different regions of data, contrast set learners report how those regions differ. Contrast sets can be much smaller than classification rules, particularly if they're generated as a postprocessor to some decision tree process. Contrast sets learned high in a decision tree tend to wipe out most possibilities and select for few classes-they do this by using fewer extra constraints.
W3 uses the same clusters as found by W2, but applies the principle of envy. Each cluster finds the closest neighboring cluster that it most desires-for example, for effort estimation, the neighboring cluster with the projects that are cheaper to build. W3 then applies a contrast set learner to the neighboring cluster to find best practices for achieving those better results in that cluster. In a recent IEEE Transactions on Software Engineering paper, I showed that such envy-based "local learning" can result in much better models than if we overgeneralize by learning from all the data.5
The lesson of W3 is the same as W2: new and innovative approaches to predictive modeling can be achieved by refactoring our current tools.
Pablo Picasso once said "computers are stupid; they only give you answers." Discussion miners aren't stupid; they know that while predictions and decisions are important, so too are the questions and insights generated on the way to those conclusions. In my view, discussion mining is the next great challenge for the predictive modeling community. In the coming century's heavily digital world, such discussion tools are going to be essential. Without them, humans will be unable to navigate and exploit the ever-increasing quantity of readilyaccessible digital information.
In some sense, discussion miners are the very opposite of the Web:
- The Web was designed for information transport and access, with a primary goal of rapid sharing of new information.
- If the Web were a discussion miner, it would be possible to instantly query each webpage to find other pages with similar (or disputing) beliefs, find the contrast set between then agreeing and disputing pages, and then run queries that helped the reader assess the plausibility of each item in that contrast set.
Note that much of the current predictive modeling research wouldn't qualify as a discussion miner because, in the usual case, most of that literature is still struggling with methods to create one model, let alone updating a model as time progresses.
|0||Do||Predict, decide||Regression, classification, nearest neighbor reasoning|
|1||Say||Summarize, plan, describe||Instance section, feature selection, contras sets|
|2||Reflect||Trade-offs, envelopes, diagnosis, monitoring||Clustering, multiobjective optimization, anomaly detectors|
|3||Share||Privacy, data comression, integrate old new ules,
recognize and debate deltas between competing models
|Contrast set learning, transfer learning|
|4||Scale||Do all of the above, quickly||?|
Tabel 1 Internals of a discussion miner
One fascinating open issue with discussion miners is how they should be assessed. In discussion mining, the model's goal is to find its own flaws and replace itself with something better, which brings to mind a quote from Susan Sontag: "The only good answers are the ones that destroy the questions." In other words, we shouldn't assess such models by accuracy, recall, or precision-rather, we should assess the audience engagement they engender. No, I don't know how to do that either, but I find it exciting that there are such clear and important problems waiting for us to solve tomorrow.
In terms of engineering principles, Table 1 shows the internals of a discussion miner. Note that the predictive modeling community already has the parts needed to assemble this and other new kinds of miners.
We must move on, and we can. Enough already with algorithm mining: it's time to do other things. Industrial practitioners aren't really concerned with the internal details of our algorithms or how our data divides into regions. They're more concerned with the tools needed to help push the community to debate different possible decisions.
1 K. Dejaeger et al., "Data Mining Techniques for Software Effort Estimation: A Comparative Study," IEEE Trans. Software Eng., vol. 28, no. 2, pp. 375-397.
2 T. Hall et al., "A Systematic Review of Fault Prediction Performance in Software Engineering,"IEEE Trans. Software Eng., vol. 38, no. 6, pp. 1276-1304.
3 A. Brady and T. Menzies, "Case-Based Reasoning vs. Parametric Models for Software Quality Optimization," Proc. 6th Int'l Conf. Predictive Models in Software Eng. (PROMISE 10), ACM, 2010;
4 T. Menzies and T. Zimmermann, "Goldfish Bowl Panel: Software Development Analytics," Proc. 2012 Int'l Conf. Software Eng. (ICSE 2012), IEEE, 2012, pp. 1032-1033.
5 T. Menzies et al., "Local vs. Global Lessons for Defect Prediction and Effort Estimation,"IEEE Trans. Software Eng., preprint, published online Dec. 2012;
About the Author
Tim Menzies is a full professor of computer science at the Lane Department of Computer Science and Electrical Engineering, West Virginia University. Contact him at email@example.com.
This article first appeared in IEEE Software magazine. IEEE Software's mission is to build the community of leading and future software practitioners. The magazine delivers reliable, useful, leading-edge software development information to keep engineers and managers abreast of rapid technology change.
John Krewson, Steve Ropa and Matt Badgley Nov 24, 2014