It seems this is the primary mechanism used by Sparx to decide how to prioritize changes. While I agree it is important to respond when there is a weight of opinion pushing for something, I also think this is an incomplete and flawed approach. If companies only did what many people asked them for, there would be no innovation, no new products to catch the imagination, e.g. no iPod, no iPhone (although Apple don't have a monopoly on this) etc..
I would suggest that quite a few of the suggestions here and their associated feature requests, would not occur to most people using EA, so there will never be a "weight of opinion" about them, but a proportion of these suggested changes would increase the usability and power of the product, and move it towards really being a killer tool. Those people who did not see the need before would suddenly be on board with these changes, and would accrue the productivity gains. That can only lead to a positive snowball effect for Sparx.
So, in my view, Sparx should have a process whereby forward looking open minded personnel look at feature requests to assess how useful to the whole EA community a change may be, even though only a single user has requested it. Those changes should then be developed alongside the most requested enhancements.