The primary purpose of the tool to is to surface what a software application is good at by bench-marking the features & functionality across the whole category(

The primary purpose of the tool to is to surface what a software application is good at by bench-marking the features & functionality across the whole category(s) that the app in question belongs to. Most of my time goes into normalizing feature set across a category of software so that you can do apples-to-apples comparison. Then I am quantifying how well that feature is implemented within the product, hopefully extrapolate that to the whole category, essentially a ranking system for the features. To do that, I need to collect and normalize those feature sets. W.r.t. treemap, I am trying different visualization techniques and seems like treemap is pretty good in answering these questions quickly: 1. Which product is a dominant product in a particular category? 2. Which feature dominates a product/category? After doing a few user interviews people honestly don't care about the ranking or a better framework to search for software. They mostly care about how can software evaluation and procurement can be less painful. Thanks for the comment and sharing the link of eoc. That's pretty much what I am trying to do for apps. I hope to extend this to libraries/packages which can be very helpful in knowing what are the strengths of a particular library or package in a snapshot.